Six free employee expectations templates: setting form, duties and standards worksheet, behavior and communication rules, reset memo, example, tracker.
Six expectations templates a manager can fill in the same afternoon: the core expectations form, a worksheet that turns duties into standards anyone can check, a behavior and communication sheet, a reset memo for an employee who is already here, a filled-in example, and a three-tab tracker. Editable Word and Excel files, no email form in the way.
The first time I wrote down what I expected from someone, it was because I had already been disappointed twice. He was doing the job as he understood it. I was measuring it against a version that existed only in my head, and I had never said a word of it out loud.
That is the shape of this problem at a small company. Nobody is being unreasonable. There is just no document, so the standard lives in the owner's memory and gets applied backwards, usually in a bad week. Six months later somebody is surprised, and they have every right to be.
So there are six templates here rather than one, because setting expectations with a new hire and resetting them with someone who has been drifting for a year are different conversations that need different paperwork. Five download as editable Word files and one as a spreadsheet, free, with no email form in the way.
TL;DR
An employee expectations document states what a role owns, the standard each duty is judged against, and how the person is expected to behave and communicate. Both people sign it and it gets a review date. Six free templates below cover the setting form, duties and standards, behavior, a reset memo, a filled example, and a tracker.
What an Employee Expectations Document Is
An employee expectations document is a short written agreement between a manager and one employee, stating what the role owns, the standard attached to each duty, and how the person is expected to behave and communicate with everyone else. Both parties sign it and it carries a review date.
It is deliberately narrower than a job description, which defines the role for hiring and the file. The expectations form is about one person in one period, and it covers the things a description leaves out on purpose: how well, how often, who decides, and what the manager owes back.
Only Half Strongly Agree They Know What Is Expected
In the first half of 2026, 49 percent of U.S. employees strongly agreed that they know what is expected of them at work, up two points from 47 percent and still far below the 61 percent recorded in 2015 (Gallup, July 2026). Overall engagement was 31 percent over the same period. Of the things that move those numbers, clear expectations is the cheapest, and it is fixed with a page of writing rather than a program.
Expectations, Description, Review, Plan, and Warning
Five documents get confused with each other, and the confusion is expensive. Using a review form to introduce a standard for the first time, or a warning to explain a job, is how a manageable situation turns into a dispute about fairness.
Document
What it does
When it is written
What it is not
Employee expectations form
States the standard for the role before anything has gone wrong
Week one, and again whenever the job changes
Not a disciplinary record and not a contract
Job description
Defines the role for hiring, classification, and the file
Before you advertise the job
Not a statement of how well the work has to be done
Performance review form
Judges work already done against a standard that was set earlier
At the end of a review period
Not the place to introduce a standard for the first time
Performance improvement plan
Records a specific gap, the required change, and a deadline
After a standard was set and then missed
Not a substitute for having set expectations at all
Written warning
Records an incident, the rule it broke, and what happens next
After a rule or a stated standard is broken
Not a performance conversation and not a reset
The order matters more than the paperwork. Expectations first, feedback in between, and only then a review form or, if it comes to it, a formal plan. Skipping the first step is what makes the last one feel arbitrary.
The Four Layers Inside One
A complete expectations document has four layers: what the role is for, the duties with a standard beside each, the behavior and communication rules, and what the manager provides in return. Miss the fourth and you have written a list of demands.
What the role is for
Why the job exists, in one sentence
The two or three things this person owns
What the role does not cover, and who does
Who to ask when the answer is not obvious
Duties and standards
Each duty with a standard beside it
How often the work is expected
Where the evidence comes from
What not yet looks like, written down
Behavior and communication
Which channel is for what, and response times
Hours, availability, and the after-hours rule
How disagreement gets raised, and with whom
Conduct in front of customers
The manager side
What the manager provides, with dates
Check-in cadence and who books it
How quickly bad news travels back
Both signatures, and a review date
Most templates cover the first two layers and stop. The third is what prevents the majority of small-team friction, because almost none of that friction is about tasks. It is about response times, interruptions, and who was supposed to be told what.
The U.S. Office of Personnel Management gives the same test in plain language: performance elements and standards should be measurable, understandable, verifiable, equitable, and achievable, and involving employees in planning helps them understand what needs to be done and how well. Verifiable is the word to keep. If nobody could verify it, it is a value, not a standard.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
A standard is the version of a duty that two people could check independently and reach the same conclusion about. The duty says what the person does. The standard says how well, how often, and where you would look to find out.
Duty as most people write it
The same thing as a standard
What changed
Answer the phones
Answer within three rings during shift hours, and return every voicemail the same working day
Adds a window and a deadline you could check tomorrow
Keep the shop tidy
Bench cleared and tools back on the board before the end of each shift, checked at closing
Turns a judgment call into a state anyone can look at
Be responsive on email
Acknowledge customer email within four working hours, even when the answer takes longer
Separates acknowledgment from resolution, which is where most complaints start
Own the schedule
Publish next week by Thursday noon, and fill a same-day callout without asking first
States the decision right, not only the task
Have a good attitude
Raise a disagreement with me directly within a day rather than with the crew afterwards
Replaces a trait with a behavior somebody could witness
Help with inventory
Count the fast-moving bins every Monday and flag anything under the reorder point
Replaces help with an owner, a frequency, and a trigger
Two tests catch almost every weak line. The observation test: could somebody who was not in the room tell from the evidence whether it happened? The influence test: can this person move it through their own work, or is it a company result they will be judged on like weather?
Write the other half too. For every standard, add one line describing what falling short looks like. It takes ten seconds and it removes the argument later, because the person already knows where the line sits rather than learning it from your tone in a review.
Keep the Duties Consistent With the Job Description
Under federal disability law, which applies to employers with 15 or more employees, your judgment about which functions are essential and a written job description prepared before advertising or interviewing are both treated as evidence of the essential functions of a role. An expectations form that quietly reassigns duties creates a second document saying something different. If the two diverge, update the job description rather than leaving a contradiction in the file. This is general information, not legal advice.
Which Template Should You Use?
Pick by the situation, not by the title. Setting expectations with someone new, restating them with someone who has been here two years, and writing the team-wide communication rules are three different jobs.
Employee Expectations Form
Start here
The core document. Why the role exists and what it owns outright, six to eight duties with a standard beside each, decision rights including a spending limit, behavior and communication expectations, what the manager owes back with dates, and a signature line.
Duties and Standards Worksheet
Fill this in first
Six steps for turning a duty list into a list of standards. Includes the two tests every standard has to pass, a decision-rights grid, a section for what the role does not cover, and a rule for how much of it moves onto the form.
Behavior and Communication
How we work together
Channels and response times, hours and after-hours rules, meetings, how disagreement gets raised, conduct in front of customers, and an explicit paragraph naming what the document does not restrict.
Expectations Reset Memo
For a current employee
For the conversation where the job has drifted or the standard was never said out loud. Opens by declaring whether anything is on the line, records dated observations rather than adjectives, and leaves two sections to fill in together.
Filled-In Example
Service coordinator
A complete worked sample for a fourteen-person heating and air company, with real times, a real spending limit, and standards written to be checked. Useful as a calibration check for how specific your own version should be.
Expectations Tracker
Spreadsheet, three tabs
One tab holding every role standard with its evidence source and decision right, a dated check-in log recording what was actually observed, and a reset log with a column for whether the standard had ever been written down before.
If You Have Never Written One Before
Do the worksheet first and the form second, with one person, not the whole team. Sit down with whoever currently does the work, list what the job actually involves, and write a standard for the six to eight duties that matter most. That takes about forty minutes and produces a better document than an hour spent alone with a blank form. Skip the behavior sheet and the tracker until the first form is signed, because building the system before you have one filled-in example is the most reliable way to abandon the whole thing.
6 Free Employee Expectations Templates
Download all six together as a zip file, or copy an individual template from the page. Five are editable Word documents and one is an Excel workbook with three tabs. Fill in the brackets, replace the example numbers with your own, and delete any section that does not match how your business runs.
Download All 6 Employee Expectations Templates
Expectations form, duties and standards worksheet, behavior and communication sheet, reset memo, filled-in example, and the tracker. Five DOCX files and one XLSX, each a separate file in one zip.
Template 1: Employee Expectations Form
The core document. Role purpose and what the person owns outright, duties with a standard and an evidence source beside each, decision rights with a spending limit, behavior and communication expectations, what the manager provides with dates, and a signature line.
Employee Expectations Form
EMPLOYEE EXPECTATIONS
[Company Name]
Employee: Role: [ ]
Manager:
Date written: [MM/DD/YYYY] Covers period: [MM/DD] to [MM/DD]
First review date: [MM/DD/YYYY]
Why this document exists: so that neither of us is guessing. It says what the
role owns, the standard each part is judged against, and how we work together.
It is not a disciplinary record and it is not an employment contract.
1. WHAT THIS ROLE IS FOR
In one sentence, why this job exists:
[ ]
The two or three things this person owns outright, not helps with:
•[ ]
•[ ]
•[ ]
What this role does not cover, and who owns it instead:
•[Task] belongs to [role]
•[Task] belongs to [role]
Who to go to when the answer is not obvious:
2. DUTIES AND THE STANDARD FOR EACH
One line per duty. The standard is the part most forms skip, and it is the only
part that makes the duty checkable.
Six to eight lines. More than that and the document stops being reread.
Duty | How often | The standard (what good looks like) | Checked against
[ ] | [daily] | [ ] | [report, log, or person]
[ ] | [weekly] | [ ] | [ ]
[ ] | [monthly] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
Test for every line above: could two people look at the same evidence next
month and agree on whether it happened? If not, rewrite the standard.
3. DECISIONS THIS PERSON MAKES
Decides alone, no approval needed: [ ]
Decides, then tells me: [ ]
Recommends, I decide: [ ]
Always ask first: [ ]
Spending limit without approval: $[ ]
4. BEHAVIOR EXPECTATIONS
Write behaviors somebody could witness, not personality traits.
•[ ]
•[ ]
•[ ]
In front of customers, this means: [ ]
When something goes wrong, the first thing I expect is: [ ]
5. COMMUNICATION EXPECTATIONS
Channel | Use it for | Expected response
Phone | [ ] | [ ]
Chat | [ ] | [ ]
Email | [ ] | [ ]
Working hours: [ ] Breaks: [ ]
After hours: [what, if anything, is expected outside scheduled hours]
Time off and shift swaps: [how much notice, and who approves]
If we disagree, I expect you to: [raise it with me directly, within a day]
6. WHAT YOU CAN EXPECT FROM ME
The half of the agreement that usually goes missing. Put dates on it.
I will provide | By when
[training, access, tools, budget] | [MM/DD]
[ ] | [MM/DD]
[ ] | [MM/DD]
Check-in: [weekly / every two weeks], [ ] minutes, booked by [ ]
You will hear from me about your performance: [how often, and in what form]
If something is not working, I will tell you within: [ ] days
7. HOW THIS GETS REVIEWED
We revisit this document when the job changes, and at least every [quarter].
Next review: [MM/DD/YYYY]
8. AGREED
Employee: Date:
Manager: Date:
Signing means we have read this together and agree it describes the job. It is
not an employment contract and does not change at-will employment.
Copy given to the employee: [ ] Yes Filed in the employee record: [ ] Yes
DISCLAIMER: This is a sample template for general information only and is not
legal advice. Employment rules vary by state and change over time. Review the
wording before you use it, particularly anything about conduct, availability,
or discipline.
Template 2: Duties and Performance Standards Worksheet
Six steps for turning a duty list into standards. Includes the observation and influence tests, a decision-rights grid, a section for what the role does not cover, and a rule about how much of it should move onto the form.
Role Duties and Performance Standards Worksheet
ROLE DUTIES AND PERFORMANCE STANDARDS WORKSHEET
[Company Name]
Role: Prepared by: [Name]
Date: [MM/DD/YYYY]
Use this before you fill in the expectations form. It turns a list of duties
into a list of standards, which is the difference between a document people nod
at and a document that settles an argument.
STEP 1: LIST WHAT THE ROLE ACTUALLY DOES
Ask the person doing the work rather than writing from memory. Include the
small recurring tasks nobody mentions, because those are what a new hire is
blindsided by in week two.
Task | How often | Rough time share
[ ] | [daily] | [ %]
[ ] | [weekly] | [ %]
[ ] | [monthly] | [ %]
[ ] | [ ] | [ %]
[ ] | [ ] | [ %]
[ ] | [ ] | [ %]
[ ] | [ ] | [ %]
[ ] | [ ] | [ %]
STEP 2: WRITE THE STANDARD FOR EACH ONE
For every task above, answer four questions. If you cannot answer the fourth,
the standard is not finished.
Task: [ ]
What good looks like: [ ]
How often it is expected: [ ]
Where the evidence comes from: [system, report, log, or named person]
What not yet looks like: [ ]
Task: [ ]
What good looks like: [ ]
How often it is expected: [ ]
Where the evidence comes from: [ ]
What not yet looks like: [ ]
Task: [ ]
What good looks like: [ ]
How often it is expected: [ ]
Where the evidence comes from: [ ]
What not yet looks like: [ ]
STEP 3: CHECK EACH STANDARD AGAINST THE TWO TESTS
The observation test: could somebody who was not in the room tell from the
evidence whether this happened? Adjectives fail this test. Numbers, dates, and
states of the world pass it.
The influence test: can this person move it through their own work? If the
answer is no, you have written a company result rather than an expectation, and
the person will be judged on weather.
Standard | Observable? | They control it? | Rewrite?
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
[ ] | [ ] | [ ] | [ ]
STEP 4: DECISION RIGHTS
Most role confusion at a small company is not about tasks. It is about who is
allowed to decide.
Decides alone: [ ]
Decides, then tells the manager: [ ]
Recommends, manager decides: [ ]
Always asks first: [ ]
Spending limit without approval: $[ ]
STEP 5: WHAT THIS ROLE DOES NOT COVER
The section that prevents the same question every month.
•[Task] belongs to [role]
•[Task] belongs to [role]
•[Task] belongs to [role]
STEP 6: MOVE IT ONTO THE EXPECTATIONS FORM
Carry across the six to eight duties that matter most, with the standard beside
each one. Leave the rest in this worksheet. An expectations document longer than
two pages does not get reread, and a document nobody rereads is decoration.
Duties carried across: [ ] of [ ]
Date moved onto the form: [MM/DD/YYYY]
DISCLAIMER: This is a sample template for general information only and is not
legal advice.
Template 3: Behavior and Communication Expectations
Channels and response times, hours and the after-hours rule, meetings, how disagreement gets raised, conduct in front of customers, and a short paragraph stating what the document does not restrict. Written for a team rather than a single person.
Behavior and Communication Expectations
BEHAVIOR AND COMMUNICATION EXPECTATIONS
[Company Name]
Team or role:
Written by: [Name] Date: [MM/DD/YYYY]
How we work together, written down once so it stops being a matter of guesswork
or mood. Every line here should describe something a person could be observed
doing. If a line describes a personality, rewrite it or delete it.
1. HOW WE COMMUNICATE
Channel | Use it for | Response expected
Phone | [work stopped, customer on site] | [immediately, during shift]
Chat | [coordination, quick questions] | [within 2 working hours]
Email | [customers, anything on record] | [same working day]
In person | [feedback, workload, the person] | [booked weekly]
Anything that needs a record goes in email, not chat.
Anything urgent goes by phone, not email.
2. HOURS AND AVAILABILITY
Scheduled hours: [ ]
Expected on site or online by: [ ]
Break and meal times: [ ]
After hours: [state plainly whether any reply is expected, and from whom]
On-call rotation, if any: [ ]
Time off: [ ] days notice, requested to [ ], approved by [ ]
Shift swap: [who arranges it, who has to know]
Running late or sick: [who you tell, by what time, on which channel]
3. MEETINGS
Which meetings are required: [ ]
What you bring to the weekly one-to-one: [ ]
Cameras, phones, and laptops: [state the actual rule, not an implied one]
If you cannot attend: [what you do instead]
4. WHEN WE DISAGREE
Raise it with the person directly, within [ ] working day(s).
If that does not resolve it, bring it to:
What is not acceptable: [describe the specific behavior, for example agreeing in
the meeting and reopening it with the crew afterwards]
Disagreeing with a decision is expected. Working around it quietly is not.
5. IN FRONT OF CUSTOMERS
•[ ]
•[ ]
•[ ]
When something goes wrong in front of a customer, the first thing to do is: [ ]
Who you tell, and by when: [ ]
6. THE THINGS WE DO NOT RESTRICT
Worth stating explicitly, because vague conduct rules cause more trouble than
they prevent. Nothing in this document limits your right to discuss your pay,
hours, or working conditions with your coworkers, or to raise a concern with a
government agency.
7. ACKNOWLEDGMENT
Employee: Date:
Manager: Date:
Reviewed on: [MM/DD/YYYY] Next review: [MM/DD/YYYY]
DISCLAIMER: This is a sample template for general information only and is not
legal advice. Rules about employee conduct, availability, and off-duty
communication are regulated differently from state to state, and broadly worded
conduct rules carry legal risk. Have your wording reviewed before you use it.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
For an employee who is already here and where the job has drifted. Opens by declaring whether anything is on the line, records dated observations instead of adjectives, and leaves two sections deliberately blank to fill in during the conversation.
Expectations Reset Memo
EXPECTATIONS RESET
[Company Name]
Employee: Role: [ ]
Manager:
Meeting date: [MM/DD/YYYY] Written on: [MM/DD/YYYY]
For an employee who is already here, where the job has drifted or the standard
was never stated out loud. Fill this in before the meeting, then walk through it
together and write the last two sections during the conversation.
WHAT THIS IS, AND WHAT IT IS NOT
Tick one, and say the same thing out loud in the meeting. Ambiguity here is the
single most common reason these conversations go badly.
[ ] This is a reset. Nothing is on the line. I am telling you the standard
because I have not stated it clearly before.
[ ] This is a formal step. It is on record and there are consequences if the
standard is not met by [MM/DD/YYYY].
1. WHY WE ARE HAVING THIS CONVERSATION
In two sentences, plainly: [ ]
Be honest about how we got here. If the standard was never written down, say
so. A reset that starts by pretending the expectation was obvious teaches the
person that the rules appear after the fact.
2. WHAT I HAVE ACTUALLY SEEN
Dates and specifics. No adjectives, no summaries of character.
Date | What happened | Effect on the work
[MM/DD] | [ ] | [ ]
[MM/DD] | [ ] | [ ]
[MM/DD] | [ ] | [ ]
3. WHAT THE EXPECTATION IS GOING FORWARD
Duty or behavior | The standard from now on | Checked against
[ ] | [ ] | [ ]
[ ] | [ ] | [ ]
[ ] | [ ] | [ ]
Anything that has changed about the role itself: [ ]
Anything I am taking off your plate to make room: [ ]
4. WHAT MIGHT BE IN THE WAY (FILL IN TOGETHER)
Ask before you conclude. Half of what looks like an expectations problem is a
tools problem, a training gap, a workload problem, or an instruction the person
received from someone else.
What the employee says is getting in the way: [ ]
What I did not know until this meeting: [ ]
Anything I got wrong above: [ ]
5. WHAT I WILL DO
I will provide | By when
[ ] | [MM/DD]
[ ] | [MM/DD]
6. HOW WE CHECK (AGREED IN THE MEETING)
Check-in dates: [MM/DD], [MM/DD]
What we will look at: [ ]
What good looks like at the first check-in: [ ]
Employee comments, in their own words: [ ]
7. SIGN-OFF
Employee: Date:
Manager: Date:
Signing means the conversation happened and the employee received a copy. It is
not an admission of anything.
DISCLAIMER: This is a sample template for general information only and is not
legal advice. Where a conversation may lead to discipline or termination, the
record you create here can be read months later out of context. Write it the way
you would want it read aloud, and check your state rules before you rely on it.
Template 5: Filled-In Example, Service Coordinator
A complete sample for a fourteen-person heating and air company: real times, a real spending limit, six duties with checkable standards, and a manager section with three dated commitments. Use it to calibrate how specific your own version needs to be.
Filled-In Example: Service Coordinator
EMPLOYEE EXPECTATIONS
Northline Heating and Air
Employee: Dana Whitfield Role: Service Coordinator
Manager: R. Okonkwo, Owner
Date written: 03/09/2026 Covers period: 03/09 to 06/30
First review date: 04/06/2026
1. WHAT THIS ROLE IS FOR
The Service Coordinator keeps four technicians booked and the customer informed,
so the owner is not dispatching from a truck.
Owns outright:
•The daily and next-day dispatch board
•Customer communication from first call to invoice sent
•Parts ordering for scheduled jobs, against the monthly budget
Does not cover:
•Pricing changes and quotes above $2,500 belong to the owner
•Technician performance and training belong to the lead technician
•Payroll and timesheet approval belong to the owner
Who to ask when the answer is not obvious: the owner, by phone, any time before
6:00pm.
2. DUTIES AND THE STANDARD FOR EACH
Duty | How often | The standard | Checked against
Dispatch board | Daily | Next day fully booked by 4:00pm, no gaps | Dispatch board
| | longer than 60 minutes between jobs |
Customer callbacks | Daily | Every voicemail returned the same working | Call log
| | day, before 5:00pm |
Arrival windows | Daily | Customer told a 2-hour window, and called | Call log, complaints
| | if the technician will miss it |
Parts ordering | Weekly | Scheduled jobs have parts on site the day | Purchase log
| | before, no same-day emergency orders |
Invoicing | Daily | Invoiced within one working day of the | Accounting export
| | technician closing the ticket |
Weekly report | Weekly | Jobs completed, callbacks, and open parts | Shared sheet
| | in the shared sheet by Friday noon |
3. DECISIONS THIS PERSON MAKES
Decides alone: daily scheduling, technician assignment, rescheduling a customer,
parts orders under $400 for a booked job.
Decides, then tells me: waiving a trip charge on a repeat visit.
Recommends, I decide: overtime on a Saturday, adding a new supplier.
Always ask first: quotes above $2,500, anything a customer is angry about.
4. BEHAVIOR EXPECTATIONS
•Tell a customer bad news yourself, the same day you learn it, rather than
letting them find out when nobody arrives.
•If a technician disagrees with the board, the conversation happens with me,
not by quietly swapping jobs.
•Mistakes get raised the day they happen. Nothing here gets worse from being
reported early and most things get worse from being reported late.
In front of customers: never diagnose a repair or estimate a price. Say we will
have the technician confirm, and follow up the same day.
5. COMMUNICATION EXPECTATIONS
Phone: anything that stops a job or involves an unhappy customer. Immediately.
Chat: coordination with technicians during the day. Within 2 hours.
Email: customers, suppliers, quotes, anything on record. Same working day.
One-to-one: Tuesdays, 8:00am, 20 minutes.
Hours: Monday to Friday, 7:30am to 4:30pm. No reply expected after 4:30pm except
the on-call week, which rotates monthly and is paid.
Late or sick: text the owner before 7:00am so the board can be covered.
6. WHAT YOU CAN EXPECT FROM ME
I will provide | By when
Dispatch software access and two hours training | 03/13/2026
The supplier account list and credit limits | 03/16/2026
A decision on the Saturday overtime policy | 03/31/2026
Check-in: Tuesdays, 20 minutes, booked by me.
You will hear from me if something is not working within 5 working days, not at
the end of the quarter.
7. HOW THIS GETS REVIEWED
Next review: 06/30/2026, or sooner if the role changes.
8. AGREED
Employee: Date:
Manager: Date:
DISCLAIMER: This is a sample filled in with fictional details to show the level
of specificity that works. It is general information only and is not legal
Three tabs: every role standard with its evidence source and decision right, a dated check-in log recording what was actually observed and what got in the way, and a reset log with a column for whether the standard had ever been written down before. Pre-filled with a worked example you can clear.
Employee Expectations Tracker
A
B
C
D
E
F
G
H
I
1
Employee
Role
Duty
How often
The standard
Checked against
Decision right
Agreed on
Next review
2
D. Whitfield
Service Coordinator
Dispatch board
Daily
Next day fully booked by 4:00pm, no gaps over 60 minutes
Dispatch board
Decides alone
2026-03-09
2026-06-30
3
D. Whitfield
Service Coordinator
Customer callbacks
Daily
Every voicemail returned the same working day, before 5:00pm
Call log
Decides alone
2026-03-09
2026-06-30
4
D. Whitfield
Service Coordinator
Invoicing
Daily
Completed jobs invoiced within one working day of ticket close
Accounting export
Decides alone
2026-03-09
2026-06-30
5
M. Alvarez
Front Desk
Insurance verification
Daily
Eligibility checked before every appointment, patient told their share at check-in
Practice system
Decides alone
2026-02-17
2026-05-29
6
M. Alvarez
Front Desk
Supply ordering
Monthly
Ordered against the monthly budget, invoices reconciled within 5 days
Purchase log
Under $400 alone
2026-02-17
2026-05-29
7
S. Nakamura
Warehouse Lead
Pick accuracy
Daily
Errors logged the day they happen, weekly rate published to the team
Error tracker
Recommends
2026-04-06
2026-07-06
8
9
10
11
Making a PDF of the Filled Form
There is no separate expectations template PDF here on purpose, because a PDF cannot be typed into without extra software and these forms exist to be filled in. Complete the Word file first, then use Save As and choose PDF as the format.
The signed copy is the one worth converting. Give the employee the PDF, keep the editable original, and store both under the person rather than by date, so next quarter you are reading the version they actually signed.
Running the Expectations Conversation
The meeting takes thirty to forty-five minutes and it runs in a fixed order. Get the order wrong and you spend it negotiating the wording of a document neither of you has read out loud.
Draft it before the meeting, alone
Write your version first so you find out what you actually think. Handing someone a blank form and asking them to define their own job is not collaboration, it is homework you did not want to do.
Read the duties out loud, one at a time
Reading them aloud catches the ones that sound fine on paper and land badly in the room. It also slows the meeting down enough that the person can disagree with a specific line rather than the whole document.
Ask what they think the job is
Before you finalize anything, have them say in two sentences what they believe their job is most about. Where that answer and yours do not overlap is the reason you are holding this meeting.
Sign it and book the first check-in
Both signatures, both copies, and the first check-in in the calendar before anyone leaves. A document signed with no date attached to it is a document nobody opens again.
Hold it in week one for a new hire, alongside the onboarding checklist and the paperwork. That week is when someone forms their picture of the job, and whatever they conclude then is what they will work to for months. Applicant tracking is coming soon to FirstHR.
For someone already on the team, book it as its own meeting rather than adding it to a regular one-to-one. Attaching it to the usual weekly slot sends a signal you did not intend, in both directions: either it looks like an ambush, or it gets rushed in the last five minutes and treated as filler.
Behavior and Communication Expectations
Write behavior expectations as things a person could be observed doing, and communication expectations as a channel with a response time attached. Traits are unenforceable and unfair; actions on specific days are neither.
The communication half is the part that pays for itself fastest at a small company. Most of what gets called an attitude problem turns out to be an unstated rule about which channel is for what and how fast a reply is expected.
Channel
What it is for
Expected response
What not to use it for
Phone
Work has stopped, a customer is on site, a safety issue
Immediately, during shift hours
Anything that could wait until the morning
Team chat
Day-to-day coordination and quick questions
Within two working hours
Decisions that need a record
Email
Customers, quotes, anything that goes on record
Same working day, even if only to acknowledge
Anything urgent
One-to-one
Feedback, workload, anything about the person
Booked weekly, fifteen minutes minimum
Status updates that would fit in chat
After hours
Genuine emergencies, by phone only
No reply expected on chat or email
Normal work saved up and sent at 10:00pm
State the after-hours rule explicitly even when the answer is that nothing is expected. Silence on that line does not read as freedom, it reads as an unwritten test, and the most conscientious person on your team is the one who will answer at 10:00pm and quietly resent it.
Do Not Write a Rule Against Discussing Pay
This is the line small businesses drop into a conduct section without thinking about it. The National Labor Relations Board states that employees have the right to communicate with their coworkers about wages, whether or not they are represented by a union, and an employer that interferes with that right can face an unfair labor practice charge. The same caution applies to broadly worded rules about loyalty, negativity, or talking about the company. Keep behavior expectations tied to specific work situations, and if pay conversations worry you, the fix is a pay structure you can explain rather than a rule. This is general information, not legal advice.
Resetting Expectations With a Current Employee
Open by saying whether anything is on the line. The person is working that out in the first thirty seconds regardless, and leaving it ambiguous means they spend the rest of the meeting decoding you instead of listening.
Then be honest about how you arrived here. If the standard was never written down, say that out loud and put it on the page. A reset that opens by implying the expectation was obvious all along teaches the person that rules at your company appear after the fact, which is a more expensive lesson than whatever the original problem was.
Bring dated observations rather than adjectives. Three lines with dates and effects beat a paragraph about attitude, and they hold up if the situation ends badly. Then state the standard going forward, with its evidence source, and stop talking.
The next question is the one that changes outcomes: what is getting in the way? A large share of what looks like an expectations problem turns out to be a missing tool, a training gap nobody closed, a workload that quietly doubled, or an instruction from somebody else in the business. If none of those apply and the standard still is not met after the agreed check-ins, that is when a performance improvement plan or a written warning becomes the honest next step rather than a surprise.
Where Expectations Documents Go Wrong
Three failure modes account for nearly all of it, and none is about the template. All three happen to managers who did the paperwork correctly, which is what makes them hard to see from the inside.
It first appears the week you are unhappy
The most common version, and the most damaging. A document that shows up for the first time in the middle of a problem does not read as clarity, it reads as paperwork being built. The person stops listening to the content and starts reading the subtext, which is usually accurate. Write expectations at the start of a role, at the start of a quarter, or on a day when nothing is wrong. If the timing is unavoidable, say so out loud in the first minute and write it on the page.
Standards nobody could check
Take ownership. Be professional. Communicate proactively. Every one of those is a value, not a standard, and none of them can be verified by two people looking at the same evidence. They feel productive to write because they cover everything, which is exactly the problem: a standard that covers everything decides nothing, and at review time it becomes whatever the manager felt that quarter. Replace each with a behavior somebody could witness on a specific day.
Only one side of the agreement is written
The form lists what the employee will do and stops. Then the training never happens, the access takes three weeks, the decision sits with the owner for a month, and the person misses a standard for reasons that were never theirs. Write what the manager provides, with a date beside each item, and treat a missed manager item the same way you would treat a missed employee one. It costs four lines and it changes how the document is received.
There is a fourth, quieter one: the document that is written well, signed, filed, and never opened again. Nothing on a signed page changes behavior by itself. The check-in date is what turns it from a statement into an agreement, which is why the tracker has a log tab and why the form asks who books the meeting.
Doing This Without an HR Department
Without a dedicated HR person the honest version is much smaller than what the large template libraries describe. One page per role, forty minutes to write it, a signature, and a fifteen-minute check-in on a recurring calendar slot. No calibration process, no cycle owner, no software that nags anyone.
Start with the roles where you are actually unhappy or actually confused, not with every seat in the company. Two documents that exist and get reread beat eight that were written in one weekend and never opened. Roles drift faster at twelve people than at a thousand, because everyone absorbs whatever falls on the floor, so plan to revisit rather than to finish.
Write it badly enough to finish. A rough page with six real standards on it is worth more than a polished document you are still editing next month, and the person waiting to know what good looks like gets nothing out of your draft.
Where the Signed Version Should Live
A signed expectations form is only useful if the next person to need it can find it. That is the part FirstHR handles: the form sits on the employee profile beside onboarding, training records, and the rest of the documents, sign-off comes back e-signed with a date attached, and the actions agreed in a check-in become assigned tasks with owners and due dates instead of notes in a file nobody reopens. Because it is attached to the person rather than to a folder, the manager writing next quarter's review is reading the same version the employee signed. Applicant tracking is coming soon to FirstHR.
One last argument for doing this in week one rather than month six. The expectations conversation is the cheapest part of the entire employment relationship: half an hour, one page, no cost. Everything downstream of it, the review, the improvement plan, and eventually a replacement hire with its own advertising, interviewing, and onboarding, costs multiples of that and lands on the same small team. Applicant tracking is coming soon to FirstHR.
Key Takeaways
An expectations document states what the role owns, the standard for each duty, and how the person is expected to behave and communicate.
A standard is the version of a duty two people could check independently and agree on, which rules out traits like professional or proactive.
Write what the manager provides, with dates, or the document reads as a list of demands rather than an agreement.
State the after-hours rule explicitly, because silence on that line reads as an unwritten test rather than as freedom.
On a reset, say whether anything is on the line, bring dated observations, then ask what is getting in the way before you conclude anything.
Both sign it, the employee keeps a copy, and the first check-in goes in the calendar before anyone leaves the room.
Frequently Asked Questions
What is an employee expectations template?
An employee expectations template is a fill-in document a manager and an employee complete together, stating what the role owns, the standard attached to each duty, and how the person is expected to behave and communicate. Both people sign it and it gets a review date. A useful one has four layers: the purpose of the role and what it does not cover, the duties with a checkable standard beside each, the behavior and communication rules including response times and after-hours availability, and what the manager provides in return with a date on every item. That last layer is the one most templates leave out, and it is the one that decides whether the document reads as an agreement or as a list of demands.
What should an employee expectations document include?
Seven things. Why the role exists, in one sentence. The two or three things this person owns outright, plus what the role does not cover and who owns that instead. Six to eight duties, each with a standard that says what good looks like and where the evidence comes from. Decision rights, including what they can spend without asking. Behavior expectations written as things somebody could witness. Communication expectations covering channels, response times, working hours, and what is expected after hours. And the manager side: training, tools, access, and decisions, each with a date. Finish with two signatures, a copy for the employee, and a review date. Keep the whole thing to two pages or it will not be reread.
How do you set expectations with a new employee?
Write your draft before the meeting rather than handing over a blank form, then go through it together in the first week. Read the duties aloud one at a time so the person can disagree with a specific line instead of the whole document. Before you finalize it, ask them to say in two sentences what they think the job is most about, because the gap between their answer and yours is the reason the meeting exists. Fill in what you owe them, with dates. Then both sign, give them a copy, and put the first check-in in the calendar before anyone leaves the room. Thirty minutes in week one saves the conversation you would otherwise have in month four.
What is the difference between an employee expectations document and a job description?
A job description defines the role. An expectations document defines how well the role has to be done, and by whom, starting now. The description is written before you advertise a job and covers the title, reporting line, classification, essential and marginal functions, and qualifications, which makes it a hiring and record-keeping document. The expectations form is written for one person in one period and adds the parts the description deliberately leaves out: the standard for each duty, the decision rights, the communication rules, the check-in cadence, and what the manager provides. The two must not contradict each other. If the expectations form says the person owns something the description assigns elsewhere, fix the description too.
How do you reset expectations with an existing employee?
Start by saying whether anything is on the line, because the person is trying to work that out in the first thirty seconds either way. Then be honest about how you got here: if the standard was never written down, say so, since a reset that pretends the expectation was obvious teaches people that rules arrive after the fact. Bring dated observations rather than adjectives, state the standard going forward with its evidence source, and then stop talking and ask what is in the way. A large share of what looks like an expectations problem turns out to be missing tools, missing training, a workload nobody rebalanced, or an instruction from somebody else. Agree the check-in dates in the meeting and write down what you will do.
Should employees sign an expectations document?
Yes, and both parties should sign it. A signature is not there to trap anyone. It marks the fact that the conversation actually happened and that the person received a copy, which matters later, because the usual dispute is not about whether someone met a standard but about whether the standard was ever communicated. Say plainly on the page what signing does and does not mean: that you read it together and agree it describes the job, that it is not an employment contract, and that it does not change at-will employment. Give the employee a copy and file the same version in their record, so the manager writing a review next quarter is reading the document the person actually signed.
What are examples of behavior and communication expectations?
Good ones describe something a person could be observed doing on a specific day. Call the customer yourself on the day a job slips, rather than letting them find out when nobody arrives. Bring a disagreement to your manager within one working day instead of to the rest of the crew. Reply on chat inside two working hours during shift hours, and move anything that needs a record onto email. Nothing is expected after the scheduled shift ends unless the paid on-call rotation is yours that week. Send a text before the shift starts if you will be late, so the schedule can be covered. Compare those with be professional, take ownership, or communicate proactively, none of which can be checked by two people looking at the same evidence, and all of which become whatever the manager felt that quarter.
Are these employee expectations templates free to download?
Yes. All six download free with no email form and no account: five as editable Word documents and one as an Excel workbook with three tabs. Downloading all six at once produces a single zip file containing each of them as a separate file, so you can open only the ones you need. Free does not mean finished, though. Fill in the brackets, replace the example numbers with your own, and cut any section that does not match how your business actually runs. Two of the six are worked examples rather than blank forms for that reason: the value of an expectations document is entirely in how specific it is, and a blank form gives you no calibration for how specific that has to be.