Employee Evaluation Examples and How to Write Them

Employee evaluation examples show how to describe a person’s work with specific evidence, balanced feedback, and clear next steps. A useful evaluation connects observed behavior and results to job expectations; it avoids vague judgments such as “great attitude” or “needs to improve” without explaining what happened.

What employee evaluation examples show

An employee evaluation, also called a performance review or appraisal, is a structured assessment of an employee’s work over a defined period. Organizations use different schedules and formats, but the purpose is generally to discuss performance against role expectations, recognize contributions, identify development needs, and agree on priorities. Examples help managers turn broad impressions into clear statements that an employee can understand and act on.

A strong comment usually includes three elements: the expectation, evidence from the review period, and the impact or next step. For instance, “Jordan is dependable” is difficult to assess because it does not say what dependable work looks like. “Jordan submitted all six monthly inventory reports by the agreed deadline, allowing the team to complete its reconciliation on schedule” gives a specific, work-related example. If the evaluation covers a concern, it should be equally concrete and explain what improvement is expected.

Examples are starting points, not ready-made judgments. Adapt them to the employee’s role, actual work, agreed goals, and the organization’s review process. A sentence that accurately describes one person may be unfair or misleading when copied onto another person’s evaluation.

Examples by performance area

Choose examples that match the responsibilities of the role. A useful evaluation does not need to comment on every possible skill; it should focus on the expectations that matter for the employee’s work.

• Quality of work: “The client summaries were clear and required few corrections. In the next cycle, check figures against the source records before submitting the monthly report.”
• Productivity and organization: “You completed the weekly scheduling tasks on time throughout the quarter. When urgent requests arrived, you updated the shared task list so colleagues could see which deadlines had changed.”
• Communication: “You explain project risks early and give colleagues enough context to respond. One area to develop is summarizing decisions at the end of meetings so responsibilities are unmistakable.”
• Teamwork: “During the handoff between shifts, you shared the status of open customer cases and answered follow-up questions. This helped the next shift continue work without repeating the initial checks.”
• Customer or stakeholder service: “You listened to the resident’s concern, confirmed the details, and followed up after the repair request was assigned. Continue documenting the next action and expected timing in each case record.”
• Initiative and problem-solving: “After noticing repeated delays in collecting project inputs, you proposed a reminder schedule and tested it with the team. Review whether the process is still useful at the next planning meeting.”
• Learning and development: “You completed the required orientation and applied the new procedure during supervised assignments. A suitable next goal is to handle routine cases independently, with support available for unusual situations.”

When using an example, check that it reflects something the manager observed or can verify. Replace generic words such as “always,” “never,” or “excellent” with a timeframe, task, or outcome. If a result depended on several people, describe the employee’s contribution without assigning them credit for the entire team’s work.

Examples for different performance outcomes

Evaluations need not sound uniformly positive or negative. The wording should fit the evidence and the employee’s level of responsibility. These examples illustrate different situations without prescribing a rating scale:

• Consistently meeting expectations: “You completed the assigned weekly checks accurately and on schedule during this review period. You also flagged two missing records before they affected the handoff. Continue using the checklist and share any recurring gaps with the team lead.”
• Exceeding a particular expectation: “You volunteered to document the revised intake steps and gathered feedback from colleagues who use them. The guide made the process easier to follow. Next, confirm that the instructions remain accurate after the planned workflow change.”
• Progress after feedback: “At the start of the period, status updates were sometimes late. Since agreeing on a Friday update, you have submitted the last eight on time. Keep the routine in place and raise scheduling conflicts as soon as they arise.”
• Performance needing improvement: “Three of the last five weekly summaries were submitted after the agreed deadline, delaying review by the next team. Starting next week, send the summary by noon each Thursday or notify me in advance if a blocker makes that impossible. We will review progress in four weeks.”

For a difficult evaluation, distinguish a performance concern from a personal judgment. “The last three handoffs did not include the open-item list” is more useful than “You are careless.” State what standard applies, when the gap occurred, and what support or follow-up will be provided. Do not imply that a single incident represents an ongoing pattern unless the evidence supports that conclusion.

How to write a useful evaluation

Preparation improves accuracy and makes the discussion more constructive. A manager can use the following sequence:

1. Confirm the scope. Identify the review dates, role responsibilities, goals, and any instructions in the organization’s evaluation process.
2. Gather relevant evidence. Review work products, agreed targets, project outcomes, and notes from the period. Use examples from across the review window rather than relying only on the most recent event.
3. Separate observation from interpretation. Record what happened first, then explain why it matters. “The response was sent two days after the deadline” is an observation; “the employee does not care” is an unsupported conclusion.
4. Describe strengths and gaps. Include meaningful contributions as well as areas to improve. Be direct, respectful, and specific in both.
5. Set a practical next step. Define the expected behavior or result, any needed support, and a reasonable point to check progress. Make sure the goal is within the employee’s influence.
6. Invite the employee’s perspective. Ask what helped, what got in the way, and what support would make the next period successful. Correct factual misunderstandings before finalizing the record.

Good documentation is not a collection of every minor mistake. Select evidence that is relevant to the role and proportionate to the point being made. If a review raises a matter involving legal obligations or another specialized professional issue, consult a qualified professional rather than relying on a general template.

Choosing ratings and setting goals

Some organizations use a rating scale; others use written summaries or a combination. A rating is useful only when the employee can understand what each level means. Define the scale in advance, apply it consistently to comparable roles, and explain the evidence behind the chosen level. A number or label should summarize the evaluation, not replace its reasoning.

A common source of confusion is treating “meets expectations” as a negative judgment. In a well-explained system, it means the employee is performing the role at the expected level; it does not mean that the work lacks value. Conversely, a high rating should be tied to results or behaviors that genuinely go beyond the stated expectations, not simply to popularity or effort.

Goals should describe a result or behavior the employee can work toward. “Improve communication” is broad. “For the next two project handoffs, send a written summary of decisions, owners, and due dates by the end of the meeting day” is more observable. Agree on how progress will be checked and whether the employee needs training, time, tools, or clearer priorities.

Common problems and how to avoid them

Vague feedback is one of the most common weaknesses in an evaluation. Labels such as “professional,” “not a team player,” or “lacks ownership” can mean different things to different people. Explain the behavior behind the label, provide a relevant example, and describe the expected alternative. If there is no specific evidence, reconsider whether the judgment belongs in the review.

Other problems include recency bias, inconsistent standards, and surprises. Recency bias occurs when a recent event overshadows earlier work; reviewing examples from the full period can help. Inconsistent standards arise when similar work is judged differently across employees; refer to role expectations and discuss how the scale is applied. A review should not be the first time an employee hears about a serious, ongoing concern. Timely feedback gives the person a chance to understand the expectation and respond during the review period.

Also avoid writing only about personality, comparing employees with one another instead of with job expectations, or setting goals that depend on factors outside the employee’s control. A balanced review is not necessarily one that gives equal space to praise and criticism. It is one that accurately reflects the evidence, identifies what matters, and gives the employee a fair understanding of what happens next.

Employee evaluation template

Use this generic form as a starting point and adjust it to the role and review process. Keep entries factual and concise; add rows or instructions if the organization requires them.

Making the review conversation useful

A written evaluation works best as part of a two-way conversation, not as a document delivered without explanation. Start by describing the purpose and asking the employee to reflect on accomplishments and challenges. Discuss evidence one point at a time, pause for questions, and make room for context the manager may not have known. Listening does not require agreeing with every interpretation; it helps ensure that the discussion is based on a fuller picture.

Close by confirming the main takeaways: what should continue, what needs to change, what support is available, and when progress will be revisited. Record agreed actions in plain language and share the completed evaluation according to the organization’s process. If the employee disagrees with a factual statement, clarify the evidence and follow the organization’s procedure for comments or corrections rather than turning the discussion into a contest of impressions.

Frequently Asked Questions

What is a good example of an employee evaluation comment?
A useful comment names a behavior or result, gives a concrete example, and explains its relevance. For example: “You sent the weekly status report by the agreed deadline for the past two months, giving the team time to address blockers before planning.”

How do I write a performance review for an employee who needs improvement?
Describe the specific expectation, the observed gap, and a clear next step with a follow-up point. Keep the wording respectful and factual, and identify any support or resources that will help the employee meet the expectation.

Should an employee evaluation include both strengths and weaknesses?
It should include the aspects of performance that are relevant to the review, which may include strengths, achievements, and development needs. Do not add criticism merely to make the review seem balanced, or omit a significant concern to keep it positive.

How often should employee evaluations be done?
There is no single schedule that fits every workplace. Organizations may use annual, periodic, project-based, or other review cycles, and managers can give timely feedback between formal evaluations. Follow the applicable workplace process and explain expectations to employees.

What should I avoid writing in an employee evaluation?
Avoid unsupported labels, personal attacks, exaggerated words such as “always” and “never,” and feedback unrelated to the job. Replace them with relevant observations, examples, and clear expectations. Do not copy a sample comment unless it accurately describes the employee’s work.

Related

• Job Application Template: What to Include and How to Use It
• Job Description Template: Build a Clear, Useful Posting
• Marketing Plan Template: Make a Practical Plan