An employee evaluation should include the review period, the employee’s responsibilities and goals, evidence of results, specific feedback on strengths and improvement areas, the employee’s perspective, and clear next steps. A useful review is job-related, balanced, based on examples rather than impressions, and specific about what success should look like going forward.
What an Employee Evaluation Is For
An employee evaluation is a structured conversation and record of how someone performed during a defined period. It can help an employee understand what is working, where expectations are not being met, and what support or development could help. It also gives a manager a chance to clarify priorities and recognize contributions that might otherwise go unmentioned.
There is no single format that suits every workplace. Some organizations use annual forms, while others hold shorter, more frequent check-ins. Whatever the schedule, the review should connect to the employee’s actual role and the expectations communicated during the period. It should not surprise someone with an entirely new standard at the end of the year.
Core Sections to Include
A practical evaluation covers both outcomes and the way the work was done. Include the following sections, adapting the wording to the role and the organization’s process:
- Review details: Record the employee’s name, role, manager, and dates covered. This makes the scope of the evaluation clear.
- Role expectations: Summarize the main responsibilities or standards being assessed. Refer to the current role description or agreed priorities rather than relying on vague assumptions.
- Goals and results: List relevant goals, describe progress against each one, and note important outcomes. Include goals that changed or became irrelevant, with a brief explanation.
- Key contributions: Identify completed work, improvements, collaboration, customer or internal service, or other contributions that mattered to the role.
- Strengths: Name capabilities the employee can continue to use, supported by an example.
- Improvement areas: Describe a specific gap, its effect on the work, and the expected change. Avoid labels about personality or character.
- Development and support: Record skills to build, learning opportunities, coaching, tools, or other support that could help.
- Next-period priorities: Set a small number of clear goals, define how progress will be recognized, and identify a target date or check-in point.
- Employee comments: Give the employee space to add context, achievements, concerns, or a response to the assessment.
Include a rating scale only if it helps the organization make expectations clearer. If the form uses ratings, explain what each level means and apply the definitions consistently. A number without a written explanation rarely tells the employee what to repeat or change.
Use Evidence, Not General Impressions
Specific evidence makes feedback easier to understand and discuss. It can include completed project milestones, work quality, agreed service measures, examples of collaboration, or documented progress on a goal. Choose evidence that is relevant to the job and the review period. A manager does not need to turn every task into a metric; some important work is best described with a concrete example and its effect.
Compare performance with communicated expectations, not with a colleague’s personality or working style. For example, “Your handoffs included the required status and next steps on the last three projects” is more useful than “You are very organized.” For an improvement point, “Two reports were submitted after the agreed deadline, which delayed review; please flag schedule risks as soon as they arise” gives a clearer path forward than “You need to be more reliable.” The examples should be accurate, proportionate, and drawn from the period being reviewed.
Consider the circumstances around results, too. A goal may have changed because priorities shifted, resources were unavailable, or the employee took on additional work. Recording that context does not erase accountability; it helps explain the outcome fairly and makes future goals more realistic.
Make Ratings and Feedback Clear
If you use a rating, define the scale in plain language. For instance, a scale might distinguish consistently meeting expectations from exceeding them in a sustained way, while also identifying performance that needs improvement. The precise labels are an organizational choice; the important point is that employees and managers understand them before the review is completed. Avoid changing the meaning of a rating from one person or team to another.
Pair every rating with a short explanation. A high rating should describe what the employee did and why it mattered. A low rating should identify the expectation, the evidence of the gap, and what needs to change. Do not let one recent success or mistake overshadow the rest of the review period. When a manager has limited direct observation, they should seek relevant input rather than present an assumption as a fact.
Keep feedback focused on behavior and work outcomes. “The meeting summary omitted owners for several follow-up tasks” describes something that can be addressed. “You do not care about details” assigns a motive that may not be known and is much harder to act on.
Include the Employee’s Perspective
An evaluation should not be only a manager’s verdict. Ask the employee to reflect on their achievements, challenges, goals, and support needs before or during the discussion. Their account may add context the manager did not see, such as behind-the-scenes coordination or a barrier that affected a deadline. Listening does not require agreeing with every interpretation; it helps both people discuss the same events.
Invite specific responses with questions such as: Which accomplishment are you most proud of? What made your work harder this period? Which skill would you like to develop? What support or clearer priorities would help? Leave room in the form for the employee’s comments and note any follow-up the manager agrees to provide. If the employee disagrees with part of the review, record their perspective respectfully and explain the organization’s process for adding a response or requesting clarification.
Employee Evaluation Template
| Review field | Employee response | Manager notes and examples |
|---|---|---|
| Employee, role, manager, and review period | ||
| Main responsibilities and expectations | ||
| Goals and progress | ||
| Key contributions and strengths | ||
| Improvement area and expected change | ||
| Development or support needed | ||
| Next-period priorities and check-in date | ||
| Employee comments or response |
Sample — fictional details: Jordan Lee, service coordinator, review period January–June. Contribution: “Created a shared handoff checklist that made task ownership clearer for the team.” Development area: “Confirm priority changes with the manager before moving scheduled work.” Next step: “Review workload and priorities together at the monthly check-in.”
Adapt the Evaluation to the Role
Keep the core structure consistent across a team, but choose examples and measures that fit each job. For a project-based role, the review might discuss milestones, quality, planning, and coordination. For a customer-facing role, it might address accurate information, follow-through, and the quality of interactions. For a role involving less visible work, consider reliability, documentation, risk awareness, or support provided to colleagues rather than counting only easily measured output.
When responsibilities changed during the period, state what changed and which expectations remain relevant. A new employee may need feedback on learning role basics, while an experienced employee may have agreed goals tied to broader responsibilities. In either case, the evaluation should not penalize someone for an expectation they were never given or a result outside their reasonable control.
Common Evaluation Problems to Avoid
- Vague wording: Phrases such as “have a better attitude” do not explain the action expected. Replace them with observable examples and a practical next step.
- Recency bias: A recent event can feel more important than work from earlier in the period. Review notes and examples across the full timeframe before deciding.
- Surprises: A formal review should summarize ongoing feedback, not introduce a serious concern for the first time. Raise problems promptly so an employee has an opportunity to respond and improve.
- Overweighting numbers: A target can be useful, but a single metric may miss quality, complexity, or changed conditions. Explain what the measure captures and what it does not.
- Uneven standards: Similar work should be assessed against comparable expectations. Managers can check whether their evidence and rating definitions are being applied consistently.
- Too many goals: A long list makes it difficult to identify the most important work. Prioritize a manageable set and revisit it when circumstances change.
Another common misconception is that a review must be either entirely positive or entirely critical. A balanced evaluation can recognize strong work and still describe a real improvement need. The purpose is not to soften every point; it is to make the assessment accurate, respectful, and actionable.
Turn the Review into Follow-Up
The evaluation is more useful when it leads to an ongoing plan. End the meeting by confirming the main takeaways, the employee’s next priorities, and what the manager will do. For example, if the employee needs practice with a new process, agree who will provide guidance and when progress will be discussed. If a goal depends on another team or a resource, identify that dependency rather than treating it as the employee’s responsibility alone.
Document agreed actions and schedule a check-in instead of waiting until the next formal review to revisit them. Keep records in the organization’s approved process and share the completed evaluation with the employee according to workplace policy. If a situation raises legal, tax, medical, or financial-planning questions, ask a qualified professional rather than treating the evaluation form as advice.
Frequently Asked Questions
What should an employee evaluation include?
Include role expectations, goals and results, specific examples, strengths, improvement areas, employee comments, development or support needs, and priorities for the next period.
How long should an employee evaluation be?
There is no universal length. It should be long enough to explain the assessment and agreed actions, but concise enough that the employee can identify the key points without searching through repeated or irrelevant comments.
Should employees write their own evaluations?
An employee self-assessment can be a useful part of the process, but it does not replace the manager’s assessment. It gives the employee a chance to document achievements, explain context, and identify goals or support needs.
How do you give constructive feedback in an evaluation?
Describe the expectation, cite a specific example of the gap, explain its work-related impact, and state the change or support needed. Keep the language focused on actions and outcomes rather than personal judgments.
Should an evaluation include a rating?
Only if the organization’s process calls for one and the scale is clearly defined. A rating should be accompanied by evidence and an explanation so the employee understands how it was reached.