How to Write a Performance

Learning how to write a performance review starts with one rule: every important conclusion should be supported by evidence the employee can understand and discuss.

“Great attitude” is too vague to guide development. “Performance needs improvement” is too serious to leave unexplained. A useful review connects an agreed expectation to a result, shows the source and period behind that result, adds context, and defines what happens next.

That does not mean filling the document with screenshots or activity logs. Evidence should help explain performance, not overwhelm the conversation or turn the review into surveillance.

This guide provides an eight-step method, a worked example and a copyable employee review template.

Quick Answer: How to Write a Performance Review

To write a fair, evidence-based performance review:

1. Confirm the review period, role and agreed expectations.
2. Gather evidence from the full period.
3. Balance results, quality, timeliness, behaviour and context.
4. Separate facts from interpretation.
5. Support each rating with specific examples.
6. Discuss gaps without ignoring workload or process barriers.
7. Set measurable next-period actions.
8. Let the employee respond and record the final discussion.

The finished review should answer three questions: What happened? What evidence supports that conclusion? What should continue or change?

What Does “Evidence Attached” Mean?

Evidence attached does not require a literal file beside every sentence. It means each rating can be traced to a reliable source.

Useful evidence may include:

• agreed goals and success measures;
• completed projects or work samples;
• output, quality and timeliness metrics;
• customer or stakeholder feedback;
• attendance or schedule records where relevant;
• documented coaching and check-in notes;
• training, certifications or development progress;
• workload, task and process context;
• the employee's own examples and explanation.

TrackForce's guide to employee performance metrics explains why output, quality, timeliness, workload and business impact should be considered together. Hours, active time and application use may add context, but they rarely prove performance alone.

How to Write a Performance Review in 8 Steps

1. Reopen the Original Expectations

When learning how to write a performance review, begin with the job responsibilities, goals, standards and priorities that applied during the period. Do not rate an employee against expectations introduced later.

The Acas performance-management guidance recommends reviewing agreed objectives, workplace behaviours and development plans, while keeping a written record of the discussion. Its SMART framework also provides a useful test: objectives should be specific, measurable, achievable, relevant and time-bound.

Create a short review header containing:

• employee and role;
• manager;
• review dates;
• goals and weights, if used;
• rating definitions;
• major priority changes during the period.

This gives every later comment a shared reference point.

2. Build a Full-Period Evidence Pack

Recency bias occurs when the last few weeks dominate a review. Prevent it by collecting evidence across the full period before deciding on a rating.

Organise the evidence by goal or responsibility, not by data source. For each goal, capture the expected result, actual result, source, date range and relevant context.

If you are learning how to write a performance review for the first time, this table is the best protection against writing from memory.

3. Choose Balanced Measures

Understanding how to write a performance review means knowing that one number should not determine it. Quantity without quality rewards rushed work. Customer impact without workload context may punish someone assigned the hardest cases. Activity without outcomes rewards visible busyness.

The CIPD performance-management factsheet recommends choosing measures that are necessary, relevant and aligned with organisational strategy. It also distinguishes task, contextual and adaptive performance.

Select three to five measures that fit the role. TrackForce's guide to key performance indicators for employees offers role-based scorecards and explains why KPIs should follow the work rather than available software data.

4. Separate Fact, Interpretation and Decision

A manager applying how to write a performance review principles should separate three layers:

1. Fact: What verifiably happened?
2. Interpretation: What does the pattern suggest?
3. Decision: What rating or action follows?

Example:

Fact: 46 of 50 assigned cases met the service deadline, compared with the 90% target. Quality audit results averaged 96%.

Interpretation: Delivery was reliable and quality remained above standard across the review period.

Decision: Meets expectations for service delivery and exceeds expectations for quality.

Keeping these layers visible makes the reasoning easier to verify and challenge.

5. Write Each Rating as Claim, Evidence, Context and Impact

Use one repeatable structure for every important review comment:

• Claim: State the performance conclusion.
• Evidence: Provide two or three relevant examples or metrics.
• Context: Explain scope, constraints or changes.
• Impact: Connect the result to the team, customer or business.

Weak comment:

Jordan had a good year and was very productive.

Evidence-based performance review comment:

Jordan exceeded the delivery target by completing 24 of 25 planned milestones, with 23 accepted on the first review. Delivery remained consistent after the project scope increased in May. This reduced handoff delays and helped the team release two weeks earlier than forecast.

This is how to write a performance review that can support recognition, coaching and calibration.

6. Address Gaps Fairly and Specifically

For how to write a performance review fairly, describe the gap between the agreed standard and observed result. Avoid personality, attitude or motivation labels unless they refer to defined, observable behaviour.

Weak comment:

Priya is careless and needs to try harder.

Stronger comment:

Five of 38 monthly reports required correction because required validation fields were incomplete. The standard is no more than one avoidable correction per month. Beginning next month, Priya will use the review checklist before submission, and the manager will sample the first four reports.

Before assigning responsibility, check workload, unclear instructions, system failures, training and dependencies. The purpose is not to excuse a real gap. It is to identify the right cause and response.

7. Turn the Review Into a Forward Plan

A review that only judges the past has limited value. For every important strength or gap, add a next-period action.

Good actions define:

• the result to maintain or improve;
• the measure and target;
• support or resources;
• the owner;
• the check-in date;
• what success will look like.

The U.S. Office of Personnel Management recommends performance standards that are objective, measurable, realistic and clearly recorded in writing. Its performance standards guidance groups useful measures around quality, quantity and timeliness.

If the review identifies a genuine performance gap, link the employee to a focused plan. TrackForce's guide on how to improve work performance covers practical changes to expectations, focus, workload, processes and feedback.

8. Invite the Employee's Evidence and Record the Discussion

A good how to write a performance review process is a two-way conversation. Share the draft or evidence summary early enough for the employee to prepare.

Ask:

• Which result are you most proud of?
• What important work is missing from this evidence?
• Which blockers affected the outcome?
• Where do you disagree with the interpretation?
• What support would improve the next period?

Record agreed changes, unresolved disagreements, development actions and follow-up dates. Acknowledgement should confirm that the discussion occurred, not force agreement with every rating.

Copyable Employee Review Template

Use this structure whenever you need how to write a performance review guidance in a repeatable format:

1. Review summary

Overall result, review period and two or three headline findings.

2. Goals and outcomes

For each goal: expectation, result, evidence source, context, rating and business impact.

3. Strengths demonstrated

Two or three strengths supported by dated examples.

4. Improvement priorities

Specific gap, expected standard, evidence, contributing factors and required change.

5. Development plan

Skill or behaviour, action, support, success measure and review date.

6. Employee comments

Employee response, additional evidence and any disagreement.

7. Confirmation

Manager, employee, review date and next check-in.

Common Performance Review Mistakes

Avoid these errors:

• writing from recent memory;
• using one activity metric as the rating;
• comparing employees with different roles or workloads;
• describing personality instead of behaviour;
• including praise without explaining the impact;
• raising a serious issue for the first time in the annual review;
• attaching raw data without interpretation;
• ignoring employee evidence;
• setting goals without owners or dates.

Local employment, equality, privacy and record-retention rules vary. HR should review the process before monitoring data or ratings influence pay, promotion, discipline or termination.

How TrackForce Supports Reviews With Evidence

TrackForce employee performance management software is designed to help managers open the review with the full period in view instead of relying on recent memory.

Time, activity, application, workload and productivity trends can help explain changes in delivery or consistency. The value comes from connecting those signals to goals, quality and outcomes, then letting managers and employees add context.

Software should prepare evidence, preserve history and make reasoning visible. It should not replace a manager's judgement or turn screen activity into an automatic rating.

Write Reviews That Hold Up

The best answer to how to write a performance review is simple: make the reasoning inspectable.

Start with agreed expectations. Use evidence from the full period. Balance results with quality and context. State exactly why each rating was chosen, invite the employee's response and finish with measurable next steps.

That produces a review that is easier to explain, fairer to discuss and more useful for improving future performance.

Frequently Asked Questions

What should be included in a performance review?

Include the review period, agreed goals, results, evidence sources, strengths, improvement areas, employee context, ratings, development actions and follow-up dates.

How do you start writing a performance review?

Start by reopening the employee's role, goals and success standards. Gather evidence across the full review period before writing the summary or choosing ratings.

What counts as performance review evidence?

Evidence may include completed work, goal progress, quality results, deadlines, customer feedback, documented behaviours, coaching notes, development progress and relevant workload or activity context.

Should activity data be attached to a performance review?

Activity data can provide context when it is relevant, accurate and collected appropriately. It should be connected to actual work outcomes and should not become the sole basis for a rating.

How long should a performance review be?

Use enough detail to explain the important conclusions without repeating every event. Most reviews are clearer when each major goal has one concise evidence-based paragraph plus specific next steps.