How to Write a Performance Review
How to Write a Performance Review in 6 Steps
Gather Evidence Throughout the Year
The biggest mistake managers make is trying to recall 12 months of performance in a single sitting. Recency bias takes over and the review reflects the last 6 weeks, not the full year.
Start a running log for each direct report. Once per week, spend 2 minutes noting anything significant: a project delivered, a deadline missed, positive client feedback, a conflict handled well, or a skill gap observed. Use a private ClickUp Doc, a notes app, or even a spreadsheet. By review time, you will have 40 to 50 data points instead of trying to reconstruct the year from memory.
Review Goals and Expectations
Pull up the goals set at the beginning of the review period. For each goal, gather the measurable outcome: Was the target hit? By how much? If not, what was the actual result? Goals without measurable outcomes are unfair to evaluate because there is no agreed standard for success.
If goals were not set clearly at the start (a common problem), acknowledge this in the review and set clearer goals for the next period. Do not penalize the employee for ambiguous expectations you failed to define.
Rate Competencies With Evidence
For each competency (communication, problem solving, collaboration, etc.), assign a rating and cite at least one specific example. A rating without evidence is an opinion. A rating with evidence is a defensible assessment.
Use the SBI format for each example: Situation (when and where), Behavior (what the person did specifically), Impact (what resulted). “During the Q2 product launch (situation), Sarah identified a vendor dependency 2 weeks before it would have caused a delay (behavior), which saved the team an estimated 3 weeks of rework (impact).”
Draft Strengths and Growth Areas
Write 3 to 5 strength statements and 2 to 3 growth area statements. Each should be one to two sentences with a specific example. Test each statement: Could the employee read this and know exactly what behavior to continue or change?
For growth areas, include a recommended next step: “I recommend enrolling in the advanced SQL course by Q2 to close the data analysis gap” is actionable. “Needs to improve technical skills” is not. Growth areas without recommended actions create frustration, not development.
Write the Development Plan
Co-create 2 to 3 development goals with specific actions, timelines, and success measures. Development goals should connect the employee’s career aspirations to the team’s needs. “Complete the data analytics certification by June to take over the quarterly reporting dashboard” serves both the employee (skill building) and the team (capability gap filled).
Avoid development plans with more than 3 goals. People cannot meaningfully develop in 5 directions simultaneously. Prioritize the 2 to 3 that have the highest impact on both the person’s career and the team’s performance.
Prepare for the Conversation
The written review is not the review. The conversation is the review. Prepare by identifying the 2 to 3 most important messages you want the employee to walk away with. If they remember nothing else, what should stick?
Anticipate disagreements. If you rated a competency lower than the employee would expect, prepare your evidence and be ready to listen to their perspective. The goal is not to win an argument but to reach a shared understanding of performance and a clear plan forward. Request the employee’s self assessment 2 to 3 days before the meeting so you can identify alignment gaps in advance.
The difference between a useful performance review and a pointless one comes down to preparation. Managers who gather evidence throughout the year write specific, defensible reviews in 60 minutes. Managers who start from scratch the week reviews are due write vague, generic feedback that helps nobody and takes longer. Keep a running log of observations per employee (2 minutes per entry, once per week) and review writing becomes straightforward.
Common Questions About How to Write a Performance Review
How long should a performance review take to write?
60 to 90 minutes per employee if you have been keeping a running evidence log throughout the year. 3 to 4 hours per employee if you are starting from scratch and trying to recall the entire review period. The evidence log habit saves 2 to 3 hours per review per employee and produces significantly better quality feedback.
How do I handle a performance review for an underperformer?
Be specific, factual, and forward looking. Document the gap between expected and actual performance with evidence. Present a clear improvement plan with measurable milestones and a timeline (typically 30, 60, or 90 days). Avoid vague language like “needs to do better.” Instead: “Delivered 4 of 9 projects on time versus the expected 8 of 9. The improvement plan targets 7 of 9 over the next quarter with weekly check ins on blockers.”
Should I share the written review before the meeting?
Send the structure and your summary 24 hours before so the employee can prepare, but save detailed feedback for the live conversation. This gives them time to process the overall assessment without creating a situation where they fixate on specific wording before you can provide context. The conversation is where nuance, questions, and alignment happen.