An employee evaluation checklist template is a reusable form for reviewing an employee’s work, discussing examples, and agreeing on next steps. Use the blank template below as a starting point, then adapt its criteria and rating scale to the role, review period, and policies of your workplace.
What an Employee Evaluation Checklist Is For
A checklist helps a manager cover important topics consistently instead of relying on memory or letting one recent event dominate the conversation. It can prompt the reviewer to consider agreed goals, the quality and impact of the employee’s work, collaboration, development, and support needed from the manager. A written record also gives both people a shared reference after the meeting.
It is a framework, not a verdict or a substitute for ongoing feedback. A yearly or twice-yearly review should not be the first time an employee hears about a serious concern. Regular check-ins make it easier to clarify expectations, recognize progress, and address obstacles while there is still time to respond.
There is no single checklist that fits every organization. The form should reflect actual job responsibilities and be used in a way that is consistent with the employer’s review process. A checklist that is too generic can produce vague comments; one that is too long can turn a useful discussion into a box-ticking exercise.
Prepare Before the Review
Start by confirming the review period, the employee’s current role, and the expectations that applied during that period. If responsibilities changed, note when and how they changed rather than judging the whole period against a newer job description. Review previously agreed goals and any relevant work examples, such as completed projects, deliverables, customer feedback, or documented check-in notes. Choose evidence that is relevant to the role and available to the employee for discussion.
Ask the employee to complete a self-review or share topics they want to discuss. This does not mean the manager must agree with every self-assessment; it gives the conversation another perspective and can reveal work that was less visible to the manager. Allow enough time to read the responses and prepare specific examples. Avoid collecting personal information that is not needed to assess work or plan support.
- Tell the employee the review period and the topics the meeting will cover.
- Compare performance with communicated expectations, not with an unstated ideal.
- Bring examples of both effective work and areas that need improvement.
- Note relevant changes in workload, resources, priorities, or supervision.
- Set aside time for the employee’s questions and perspective.
Employee Evaluation Checklist Template
| Section or criterion | Notes and specific examples | Rating, if used | Agreed next step |
|---|---|---|---|
| Employee name | |||
| Role or team | |||
| Reviewer | |||
| Review period and meeting date | |||
| Goals and key responsibilities | |||
| Quality and accuracy of work | |||
| Timeliness and reliability | |||
| Communication and collaboration | |||
| Problem-solving or role-specific skills | |||
| Strengths and contributions | |||
| Development areas and support needed | |||
| Goals before the next review | |||
| Employee comments | |||
| Follow-up date |
Sample — fictional details: For a fictional project coordinator, the reviewer might write, “Strength: sent weekly project updates that helped the team identify a scheduling conflict early. Next step: use the shared handoff checklist on the next project and review progress at the monthly check-in.” This is an example of specific, work-related wording, not a rating standard.
Choose Relevant Criteria and Examples
Choose a manageable set of criteria tied to the job. Common categories include results against agreed goals, work quality, reliability, communication, teamwork, judgment, and role-specific knowledge. Not every category applies equally to every position. For example, a role with individual deliverables may emphasize accuracy and completion, while a role coordinating a team may also require clear handoffs and information sharing.
Define what each category means before applying it. “Communication” could refer to timely updates, clear documentation, or responding appropriately to colleagues; it should not become a vague judgment about personality or speaking style. “Reliability” should be connected to relevant expectations, such as agreed deadlines or following established processes, while considering whether priorities or resources changed.
Write observations that describe actions and outcomes. “Completed the monthly reconciliation accurately and submitted it by the agreed date” is more useful than “great attitude.” For an improvement area, identify the expectation, the observed gap, and its work impact: “Two handoff notes were missing required status details, so colleagues had to request clarification.” Leave room for the employee to explain context and discuss what would help.
Decide Whether to Use Ratings
A rating scale can make patterns easier to scan, but it is optional. If the organization uses ratings, define each level in plain language and apply the definitions consistently. A scale might distinguish work that is still developing, consistently meets expectations, or regularly exceeds clearly stated expectations. Avoid adding labels without explaining what evidence supports them.
Ratings can create a false sense of precision when criteria are unclear or reviewers interpret the scale differently. Do not treat a number as a replacement for examples, discussion, or context. If two people receive different ratings, the form should help explain the difference in role expectations and evidence rather than imply that the number alone tells the whole story. If your workplace has an established scale, use its definitions rather than inventing a competing one.
Keep the Review Fair and Useful
Evaluate performance across the full review period, not just the latest project or a memorable mistake. A simple way to check balance is to gather examples from more than one point in time and consider both results and the conditions in which the work was done. Be alert to recency bias, in which recent events receive too much weight, and halo or horns effects, in which one strong or weak impression influences unrelated judgments.
Use the same job-related standards for employees doing comparable work, while recognizing that roles, assignments, and available resources can differ. Do not infer motivation, ability, or commitment from a single event when the evidence does not support that conclusion. Keep notes factual, respectful, and limited to information relevant to work. A review should not introduce surprise allegations or rely on rumors as if they were established facts; concerns should be clarified through the appropriate workplace process.
Invite the employee to respond to examples and correct factual errors. A disagreement does not automatically mean either person is acting in bad faith. Record the employee’s perspective where it helps explain the discussion, and distinguish agreed facts from differing interpretations. If a review raises a legal, medical, or other specialized issue, ask a qualified professional rather than treating this checklist as advice.
Hold the Meeting and Agree on Next Steps
Open by explaining the purpose and review period, then recognize contributions before moving into challenges and goals. Discuss one topic at a time, using examples rather than broad labels. Ask open questions such as, “What helped this project go well?” or “What made that deadline difficult?” Listen without interrupting, and check that expectations are understood. The meeting is a conversation, not simply a manager reading aloud a completed form.
Turn development comments into practical actions. Instead of writing only “improve prioritization,” agree on a specific behavior, a source of support, and a time to check progress. For example, the employee and manager might agree to review competing deadlines together during a weekly check-in for the next month. The action should be realistic, within the employee’s influence where possible, and clear about what the manager will do.
Close by summarizing the main points, confirming any goals or support commitments, and setting a follow-up date. Give the employee a chance to add comments or note a disagreement according to the organization’s process. Clarify who will keep the completed document and who may access it, following workplace rules for handling personnel records.
Common Checklist Problems
- Vague feedback: Replace “be more proactive” with an observable expectation, an example, and a practical next step.
- Too many criteria: Focus on the responsibilities that matter for the role instead of rating every imaginable behavior.
- Surprise criticism: Raise performance concerns in timely check-ins, then use the formal review to summarize progress and remaining needs.
- One-sided documentation: Include the employee’s perspective and record relevant context, not just the reviewer’s conclusion.
- Goals without follow-up: Put a check-in date and responsible person beside each agreed action.
A common misconception is that a completed form automatically makes an evaluation objective. A form can improve consistency, but fairness still depends on relevant criteria, reliable examples, thoughtful judgment, and an opportunity for discussion. Another misconception is that every employee needs identical goals. Shared standards can support consistency, while goals should still reflect the individual’s role and responsibilities.
Adapt the Template to Your Workplace
Before using the form, remove criteria that do not fit and add role-specific expectations that employees already know or can discuss. If several managers will use it, agree on what each rating and category means, and compare interpretations before reviews begin. Keep the form short enough to complete carefully. A one-page checklist with meaningful examples is often more useful than a long form filled with generic comments.
Different review approaches can complement the checklist. A self-assessment gives the employee a structured voice; regular one-to-one notes help track progress between formal reviews; and project feedback can add details about work a manager did not directly observe. These are inputs, not automatic substitutes for a fair, role-based evaluation. Choose only methods that serve a clear purpose and fit the organization’s process.
Frequently Asked Questions
What should an employee evaluation checklist include?
A practical checklist usually covers employee and review details, goals, job-related criteria, specific examples, strengths, development needs, employee comments, and agreed follow-up actions. Tailor the criteria to the role rather than treating a generic list as mandatory.
How often should employee evaluations be done?
There is no universal schedule that fits every workplace. Follow the organization’s review cycle and pair formal evaluations with regular feedback, especially when priorities or responsibilities change.
Should an employee evaluation use a rating scale?
Only if ratings are useful and their definitions are clear and consistently applied. A rating should be supported by examples and discussion; it should not replace them.
How do I write a fair performance review?
Use expectations that were communicated for the role, consider the full review period, and describe observable work with specific examples. Invite the employee’s perspective and account for relevant changes in priorities or resources.
Can I use the same checklist for every job?
You can reuse the structure, but the criteria should reflect each job’s responsibilities. A shared template can support consistent conversations without requiring identical performance measures for very different roles.