Most managers cover the job description in the first week. Fewer explicitly discuss how they like to communicate, what good performance actually looks like in this team, what the working pattern and flexibility expectations are, how decisions get made, and what the development path looks like. The result is employees who work hard at the wrong things, make assumptions about norms that turn out to be wrong, feel surprised by feedback that should have been predictable, and disengage from a role that was never clearly defined for them. Gallup’s 2025 research found only 21% of employees worldwide were engaged — and unclear expectations are consistently identified as a primary driver. A structured expectations checklist ensures every dimension of what is expected of a new employee is explicitly discussed, agreed, and documented during onboarding — so the expectations set at the beginning become the shared foundation for every performance conversation that follows.
When an employee underperforms, the first question is whether they were given the tools, training, and support to perform well. The second — and often the more important — question is whether the performance standard was clearly defined and communicated in the first place. Performance management conversations that surface a problem after six months without evidence that expectations were set clearly at the outset are not just ineffective — they are often legally indefensible and almost always unfair. A structured expectations-setting process is not just a management tool. It is the foundation of fair and effective performance management.
The scope of what needs to be communicated is broader than most managers recognise. Role responsibilities and KPIs are the obvious ones. Working pattern expectations, communication norms, decision-making authority, professional conduct standards, and development expectations are the ones that go unspoken — and that cause friction when they turn out to have been misunderstood. A checklist that covers all of these dimensions ensures nothing is left to assumption, regardless of which manager is running the conversation or how busy the team is when the new hire joins.
This checklist covers seven areas of expectations that should be discussed, agreed, and documented with every new employee — ideally during the first week, reviewed at the 30-day milestone, and revisited at every performance review thereafter.
Start with the role — but go deeper than the job description. The job description describes the role in the abstract. The expectations conversation describes what the role looks like in this team, at this stage, with these specific priorities.
Working pattern expectations are among the most commonly unspoken — and the most commonly misunderstood. A new employee who assumes 9-to-5 when the team culture is 8-to-6 will create friction before the end of the first week. Discuss this explicitly.
Expectations documented at the start of employment become the reference point for every performance conversation that follows. Expectations that were never written down cannot be fairly enforced or meaningfully reviewed.
This checklist is available as a free, runnable template in CheckFlow — with tasks assigned to the hiring manager, a shared view for the employee, and a complete documented record of expectations set and acknowledged for every new hire.
Use this template freeMost managers cover job duties. Few cover all seven of these — and the ones left unspoken are usually the ones that cause friction.
Most commonly unspoken: What decisions the employee can make independently, where their role ends and a colleague’s begins, and which responsibilities are immediate versus phased in.
Most commonly unspoken: What “good” actually looks like in practice (not just the KPI number), how quality is assessed, and what the standard for a high performer in this team is.
Most commonly unspoken: Whether the contracted hours reflect the actual cultural expectation, what flexibility really means in practice, and whether availability outside hours is expected or optional.
Most commonly unspoken: Response time expectations, when to email versus message versus meet, and how much proactive status updating is expected versus assumed.
Most commonly unspoken: The specific behaviours that are valued and those that would cause concern, how disagreements are handled in this team, and what the confidentiality expectations are beyond the obvious.
Most commonly unspoken: Whether the organisation genuinely supports development or pays lip service to it, what progression really looks like from this role, and how closely performance is linked to advancement.
Most commonly unspoken: How often the manager gives feedback, whether they prefer direct or diplomatic delivery, and what the employee should do when they disagree with or do not understand feedback they have received.
Expectation-setting quality should not depend on which manager a new employee gets. CheckFlow runs the same structured expectations checklist for every new hire — ensuring every dimension is covered for every employee, regardless of the manager’s experience or the busyness of the team when the hire joins. Every employee gets the same thoroughness of expectation-setting as the first hire the organisation ever made.
CheckFlow’s secure sharing feature lets the manager assign expectations-setting tasks while giving the new employee visibility into what was discussed, agreed, and documented. Both parties have the same reference point for the conversation — removing the “but I thought you said…” dynamic that erodes trust in early performance conversations. What was agreed is written down and visible to both.
Every expectation documented in CheckFlow is timestamped and retained. When a performance review, a performance improvement plan, or an employment dispute requires evidence of what was communicated and when, the record is complete. Expectations that were set clearly, documented promptly, and acknowledged by the employee create a fair and defensible foundation for all subsequent performance management conversations.
Setting clear expectations is most effective when it is embedded within a structured onboarding process. CheckFlow’s Employee Onboarding Checklist places the expectations conversation within the broader 30-60-90 day framework — at the right point in the new hire’s journey, with the right context already in place. See the Employee Onboarding Checklist →
The expectations documented during onboarding become the reference point for performance reviews. CheckFlow’s recurring checklist feature can schedule expectation reviews at 30, 60, and 90 days automatically — ensuring the expectations conversation doesn’t stop after the first week. Learn more about recurring checklists in CheckFlow →
Employee Onboarding Checklist
Employee Offboarding Checklist
Employee Development Plan Checklist
Disciplinary Procedure Checklist
Roles, Responsibilities & Expectations Checklist
Describe the process in a sentence and the AI checklist generator drafts the phases and tasks for you.
A comprehensive employee expectations template covers seven areas: role responsibilities and scope (including decision-making authority and immediate priorities); performance standards and success criteria (KPIs, quality standards, and what good looks like in practice); working pattern and availability expectations (hours, flexibility, remote working, and out-of-hours availability); communication and collaboration norms (channel preferences, response times, update frequency, and meeting expectations); professional conduct and values alignment (behavioural standards, culture expectations, and confidentiality); development and growth expectations (development goals, progression pathway, and learning support); and a documented and reviewed expectations record (written summary, acknowledgement, and scheduled review dates). Each area should be discussed and agreed with the employee — not presented as a fait accompli — and documented for reference throughout the employment relationship.
The initial expectations conversation should take place in the first week of employment — ideally across two or three focused conversations covering different dimensions rather than one overwhelming single session. Role and performance expectations are typically discussed in the manager one-to-one during week one. Working pattern, communication norms, and conduct expectations are often covered as part of team orientation. Development expectations are best discussed when the new hire has had a few days to settle in and can have a more genuine conversation about their goals. Expectations should then be formally reviewed at 30 days (adjusted in the light of early experience), at 90 days (as part of the probationary review), and at every annual performance review thereafter.
Gallup’s 2025 research found that only 21% of employees worldwide were engaged — and unclear expectations are consistently identified as a primary driver. Employees who do not know clearly what is expected of them cannot prioritise their time effectively, do not know whether they are performing well or not, cannot ask for help or resources at the right moment, and feel anxious rather than confident in their role. Over time, this ambiguity produces either defensive under-contribution (avoiding failure by attempting less) or disengaged over-accommodation (working hard at the wrong things to avoid feedback). Neither produces the performance the role requires or the experience the employee deserves. Clear expectations are not just a management nicety — they are the prerequisite for both engagement and performance.
The content of expectations is the same for remote employees — role, performance, conduct, and development expectations apply equally. The emphasis and communication approach should differ in two areas. Working pattern expectations need more explicit agreement for remote employees, because the informal cues that communicate norms in an office (when people arrive, when they leave, how responsive they are to messages) are absent. Communication norms also require more explicit discussion — the default channel, response time expectations, and how to signal availability or unavailability need to be stated clearly rather than discovered informally. Remote employees who are unclear on these norms often over-communicate anxiously or under-communicate in ways that create concerns — both of which a clear expectations conversation prevents.
A job description describes the role — its purpose, key responsibilities, required qualifications, and how it fits into the organisational structure. It is typically written before the hire is made and describes the role in general terms. Expectations are the specific, contextualised version of the job description in practice — they answer the question “what does good look like in this role, in this team, at this moment?” rather than “what is this role responsible for?” They cover dimensions the job description does not address — working norms, communication preferences, decision-making authority, and development goals — and they are agreed with the specific employee rather than described generically. Both are necessary; neither substitutes for the other.
You can start a free 14-day trial with no credit card required, giving you full access to all features including this template. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.
14-day free trial, no credit cardFull refund in your first 30 daysUS hosting, EU on request
