Table of Content
KEY TAKEAWAY
7 steps to write a performance review that motivates change instead of just documenting performance. The most important rule: be specific about behaviors, not personality. Use the full review period, not just recent weeks. Treat the review as the start of a development conversation, not the end of an evaluation process.
Most managers dread writing performance reviews. Not because they do not care about their employees, but because they are not sure how to translate a year of observations into written feedback that is specific enough to be useful, fair enough to be credible, and clear enough to drive action.The result is reviews that are either so vague they say nothing ('John is a great team player') or so blunt they damage trust ('Sarah's communication needs significant improvement'). Neither version helps the employee grow or gives HR the documentation they need.
This guide walks through 7 steps to write performance reviews that are fair, specific, and genuinely useful to the employee receiving them.
Why Most Performance Reviews Fail
Before getting to the steps, it helps to understand what goes wrong. Research by Deloitte found that 58 percent of executives believe their current performance management approach drives neither employee engagement nor high performance. That is a damning finding from the organizations investing the most in HR.The most common failures:
- Recency bias: the review reflects only what happened in the last 4 to 6 weeks, not the full year
- Vague language: feedback that could apply to anyone ('collaborative,' 'hardworking') and tells the employee nothing specific
- Personality over behavior: commenting on who someone is rather than what they did and the impact it had
- No development path: a review that documents the past without connecting to a plan for the future
- One-way delivery: a manager reads their notes and the employee listens, rather than a two-way conversation
Step 1: Gather Your Evidence Before You Write a Single Word
The quality of a performance review is directly proportional to the quality of the evidence you gather before writing it. Do not open a review form and start typing from memory. Gather first.Sources to review before writing:
- The employee's stated goals and OKRs from the beginning of the period and their final scores
- Notes from every 1-on-1 and check-in conversation throughout the year
- Any feedback submitted by peers or cross-functional partners
- Project outcomes, deliverables, and metrics the employee was responsible for
- Any recognition or concerns raised during the review period
- The previous review to understand what development goals were set and how they progressed
In TraineryHCM, all of this evidence is available in one place: check-in notes, OKR scores, feedback submissions, and IDP progress are accessible directly within the review form. Managers who skip this step almost always produce reviews that overweight recent events.
Step 2: Start With Accomplishments, Not Personality
The first substantive section of your review should document what the employee achieved, using specific behavioral examples rather than personality assessments.The formula for a strong accomplishment statement: [Action] + [Specific context or project] + [Measurable outcome or business impact].
Step 3: Address Development Areas Without Weaponizing the Review
Development areas are the section most managers struggle to write well. The instinct is to either avoid them entirely (resulting in useless positive-only reviews) or to be so blunt that the employee shuts down.
The right approach: describe the specific behavior, explain the impact it had, and connect it to a development suggestion.
Step 4: Address Recency Bias Deliberately
Recency bias is the most common and least-discussed performance review failure. It happens when the review reflects what happened in the last 4 to 6 weeks rather than the full review period, because recent events are easier to recall than events from 10 months ago.The practical fix: before you finalize your review, ask yourself whether your evidence spans the full review period. If your three accomplishment examples all happened in the last quarter of the year, you have a recency bias problem. Go back through your check-in notes and look for achievements from earlier in the year that deserve documentation.In TraineryHCM, managers can filter check-in notes by date range directly within the review form, making it easy to identify accomplishments from the full year rather than relying on memory.
Step 5: Use the Self-Assessment Before You Write, Not After
If your review process includes a self-assessment (and it should), read the employee's self-assessment before writing your review, not after you have already formed your conclusions.The self-assessment tells you two important things: what the employee is proud of that you may not have been aware of, and where their perception of their performance diverges significantly from yours. Both are valuable inputs.A significant divergence in self-rating is not a problem to avoid. It is a signal that the upcoming review conversation needs to spend time on alignment, not just feedback delivery. Identifying that divergence before the meeting gives you time to prepare.
Step 6: Set Goals for the Next Period Before the Review Meeting
A review that documents the past without connecting to the future is a wasted opportunity. The most actionable part of any performance review is the goals section for the next period.Do not write these goals without the employee. Draft a proposal based on the development areas you have identified and the business priorities for the next period, then refine them collaboratively in the review meeting. Goals that employees helped shape generate significantly stronger commitment than goals handed down by managers.In TraineryHCM, goals set during the review can be turned into OKRs in the Goals module immediately, or connected to a new IDP with learning content assigned from Trainery Learn. The goal is not just documented. It is actionable from day one of the new period.
Step 7: Treat the Review Meeting as a Conversation, Not a Verdict
The written review is preparation for the meeting, not the meeting itself. The most important thing that happens in a performance review is the conversation between manager and employee.Guidelines for the review meeting:
- Share the written review at least 24 to 48 hours before the meeting so the employee has time to read and process it
- Open the meeting by asking the employee to share their reaction to the review, not by reading your notes
- Spend at least 40 percent of the meeting on the future: goals, development, and support needed
- Document any updates or agreements made during the meeting and add them to the review record
- End with a clear action: at least one development goal with a concrete next step
What to Never Say in a Performance Review
Certain phrases consistently appear in performance reviews that fail to drive development or, worse, create legal risk. Avoid these:
KEY TAKEAWAY
7 steps to write a performance review that motivates change instead of just documenting performance. The most important rule: be specific about behaviors, not personality. Use the full review period, not just recent weeks. Treat the review as the start of a development conversation, not the end of an evaluation process.
Most managers dread writing performance reviews. Not because they do not care about their employees, but because they are not sure how to translate a year of observations into written feedback that is specific enough to be useful, fair enough to be credible, and clear enough to drive action.The result is reviews that are either so vague they say nothing ('John is a great team player') or so blunt they damage trust ('Sarah's communication needs significant improvement'). Neither version helps the employee grow or gives HR the documentation they need.
This guide walks through 7 steps to write performance reviews that are fair, specific, and genuinely useful to the employee receiving them.
Why Most Performance Reviews Fail
Before getting to the steps, it helps to understand what goes wrong. Research by Deloitte found that 58 percent of executives believe their current performance management approach drives neither employee engagement nor high performance. That is a damning finding from the organizations investing the most in HR.The most common failures:
- Recency bias: the review reflects only what happened in the last 4 to 6 weeks, not the full year
- Vague language: feedback that could apply to anyone ('collaborative,' 'hardworking') and tells the employee nothing specific
- Personality over behavior: commenting on who someone is rather than what they did and the impact it had
- No development path: a review that documents the past without connecting to a plan for the future
- One-way delivery: a manager reads their notes and the employee listens, rather than a two-way conversation
Step 1: Gather Your Evidence Before You Write a Single Word
The quality of a performance review is directly proportional to the quality of the evidence you gather before writing it. Do not open a review form and start typing from memory. Gather first.Sources to review before writing:
- The employee's stated goals and OKRs from the beginning of the period and their final scores
- Notes from every 1-on-1 and check-in conversation throughout the year
- Any feedback submitted by peers or cross-functional partners
- Project outcomes, deliverables, and metrics the employee was responsible for
- Any recognition or concerns raised during the review period
- The previous review to understand what development goals were set and how they progressed
In TraineryHCM, all of this evidence is available in one place: check-in notes, OKR scores, feedback submissions, and IDP progress are accessible directly within the review form. Managers who skip this step almost always produce reviews that overweight recent events.
Step 2: Start With Accomplishments, Not Personality
The first substantive section of your review should document what the employee achieved, using specific behavioral examples rather than personality assessments.The formula for a strong accomplishment statement: [Action] + [Specific context or project] + [Measurable outcome or business impact].
Step 3: Address Development Areas Without Weaponizing the Review
Development areas are the section most managers struggle to write well. The instinct is to either avoid them entirely (resulting in useless positive-only reviews) or to be so blunt that the employee shuts down.
The right approach: describe the specific behavior, explain the impact it had, and connect it to a development suggestion.
Step 4: Address Recency Bias Deliberately
Recency bias is the most common and least-discussed performance review failure. It happens when the review reflects what happened in the last 4 to 6 weeks rather than the full review period, because recent events are easier to recall than events from 10 months ago.The practical fix: before you finalize your review, ask yourself whether your evidence spans the full review period. If your three accomplishment examples all happened in the last quarter of the year, you have a recency bias problem. Go back through your check-in notes and look for achievements from earlier in the year that deserve documentation.In TraineryHCM, managers can filter check-in notes by date range directly within the review form, making it easy to identify accomplishments from the full year rather than relying on memory.
Step 5: Use the Self-Assessment Before You Write, Not After
If your review process includes a self-assessment (and it should), read the employee's self-assessment before writing your review, not after you have already formed your conclusions.The self-assessment tells you two important things: what the employee is proud of that you may not have been aware of, and where their perception of their performance diverges significantly from yours. Both are valuable inputs.A significant divergence in self-rating is not a problem to avoid. It is a signal that the upcoming review conversation needs to spend time on alignment, not just feedback delivery. Identifying that divergence before the meeting gives you time to prepare.
Step 6: Set Goals for the Next Period Before the Review Meeting
A review that documents the past without connecting to the future is a wasted opportunity. The most actionable part of any performance review is the goals section for the next period.Do not write these goals without the employee. Draft a proposal based on the development areas you have identified and the business priorities for the next period, then refine them collaboratively in the review meeting. Goals that employees helped shape generate significantly stronger commitment than goals handed down by managers.In TraineryHCM, goals set during the review can be turned into OKRs in the Goals module immediately, or connected to a new IDP with learning content assigned from Trainery Learn. The goal is not just documented. It is actionable from day one of the new period.
Step 7: Treat the Review Meeting as a Conversation, Not a Verdict
The written review is preparation for the meeting, not the meeting itself. The most important thing that happens in a performance review is the conversation between manager and employee.Guidelines for the review meeting:
- Share the written review at least 24 to 48 hours before the meeting so the employee has time to read and process it
- Open the meeting by asking the employee to share their reaction to the review, not by reading your notes
- Spend at least 40 percent of the meeting on the future: goals, development, and support needed
- Document any updates or agreements made during the meeting and add them to the review record
- End with a clear action: at least one development goal with a concrete next step
What to Never Say in a Performance Review
Certain phrases consistently appear in performance reviews that fail to drive development or, worse, create legal risk. Avoid these:
.webp)
.webp)
.webp)
.svg)
.svg)
.svg)
