How to Write an Employee Performance Review
A good performance review is specific, balanced, and grounded in the whole period's evidence, not the last few weeks or a general impression. Done well, it helps people grow; done badly, it demotivates.
The performance review is one of the most common management tasks and one of the most commonly done badly. A good review helps an employee understand how they are doing, what they do well, and where to grow, and it strengthens the relationship between manager and employee. A bad one, vague, unbalanced, biased toward recent events, or a surprise, demotivates people and undermines trust. The difference comes down to preparation and honesty: a review grounded in real evidence from the whole period, specific and balanced in its content, focused on outcomes, and delivered as a genuine two-way conversation. This guide explains how to write an employee performance review that actually helps, covering preparation, specificity, balance, avoiding the common biases, and making the review a conversation rather than a verdict. It applies whatever review format your organization uses.
Prepare with real evidence
A good review starts long before it is written, with evidence gathered across the whole review period. The most common failure is writing a review from general impression or memory, which is unreliable, biased, and unfair, when it should be based on a record of what the person actually did, achieved, and struggled with over the entire period.
This means keeping notes and records throughout the period, not scrambling to remember at review time: specific accomplishments, concrete examples of both strong work and difficulties, and progress against goals. A review built on this ongoing evidence is accurate and fair, while one reconstructed from memory at the last minute is neither.
Preparation also means reviewing the goals and expectations set at the start of the period, so the review measures performance against what was actually agreed rather than a shifting or unstated standard. A review anchored to clear, pre-set goals is fair and meaningful; one measured against vague or after-the-fact expectations is not.
A structural problem worth naming is that the annual performance review, however well written, is a fundamentally limited tool, and expecting too much of it sets everyone up to fail. Compressing a whole year of a person's work into a single document and conversation asks that one event to carry an enormous load: recognition, correction, development planning, and often pay decisions all at once, which is more than any single conversation can bear well. The organizations that get the most from reviews are usually the ones that lean on them least, because they have made feedback continuous, a regular part of the working relationship, so that by the time the formal review arrives it holds no surprises and simply summarizes an ongoing dialogue. A well-written review is valuable, but it works best as the periodic summary of a year of good feedback, not as the substitute for it.
Be specific and balanced
Like any performance feedback, a review should be specific rather than vague. Great job this year and needs improvement are useless; naming exactly what the person did well, with concrete examples, and exactly where they can grow, with specifics, gives them something real to build on. Specificity is what makes a review useful rather than empty.
A review should also be balanced, covering both strengths and areas for growth honestly. A review that is all criticism demoralizes and misses the point of recognizing good work; one that is all praise fails to help the person grow and lacks credibility. Genuine, specific recognition of what is working, alongside honest, constructive guidance on what is not, is the balance that helps.
Balance does not mean forced symmetry or softening real issues, but honest proportion: reflecting the person's actual performance fairly, giving genuine credit where due and addressing real problems clearly. The goal is an accurate, useful picture the employee recognizes as fair, which requires honesty in both directions.
It is also worth being honest about the tension between the developmental and evaluative purposes of a review, because they pull in opposite directions and pretending otherwise weakens both. When a review is tied to pay and rating decisions, employees quite reasonably become defensive, downplaying difficulties and advocating for themselves rather than engaging openly with where they could grow, which is exactly the wrong posture for genuine development. Some organizations respond by separating the two conversations, holding the honest developmental discussion apart from the pay-and-rating one, so that each can be what it needs to be. Whether or not you separate them formally, being aware that the evaluative stakes can suppress the developmental value is what lets a manager handle the tension deliberately rather than letting the rating quietly hollow out the growth conversation.
Focus on outcomes
A review should judge performance by outcomes, what the person actually achieved and its quality, rather than by activity or how busy they appeared. Reviewing someone on hours worked or visible busyness rewards the wrong things and misses what actually matters, which is the value of what they produced.
This outcome focus keeps reviews fair and meaningful, especially for knowledge work where activity is a poor proxy for value. Judging a person on results, against the goals set for them, reflects their real contribution, while judging them on activity distorts both the review and, over time, their behavior toward looking busy rather than being effective, which our guide to measuring team performance develops.
Focusing on outcomes also makes reviews more objective and defensible. Results against clear goals are concrete and verifiable, while impressions of effort or attitude are subjective and contestable, so an outcome-based review is both fairer to the employee and more solid for the organization than one based on how hard someone seemed to be trying.
Evidence, Balance, Dialogue
What makes a review good
Review essentials
▲ A good review is specific, balanced, outcome-focused, free of recency bias, and a genuine two-way conversation.
Illustrative eMonitor dashboard.
Avoid the common biases
Performance reviews are prone to well-known biases, and avoiding them is much of what separates a fair review from an unfair one. Recency bias, weighting the last few weeks over the whole period, is the most common: a strong or weak recent stretch distorts the picture of a full year, which is exactly why evidence gathered across the whole period matters.
Other biases include the halo effect, letting one strong trait color the whole assessment; leniency or severity bias, rating everyone too high or too low; and similarity bias, favoring people like oneself. Being aware of these, and checking a draft review against the actual evidence rather than gut feeling, helps counter them and keeps the review accurate.
The best defense against all of these biases is grounding the review in documented evidence from the whole period rather than impression. When a review is built on a record of what actually happened across the full period, recency, halo, and personal biases have much less room to distort it, because the facts anchor the assessment. This is the practical value of preparing with real evidence.
Make it a two-way conversation
A performance review should be a conversation, not a verdict delivered from on high. The written review is one input; the review meeting should be a genuine dialogue where the employee can respond, share their perspective, discuss their goals, and be heard, which makes the review far more useful and better received than a one-way judgment.
Crucially, a review should contain no surprises. If genuine problems have arisen during the period, they should have been raised at the time, through regular feedback, not saved up for the review, where hearing serious criticism for the first time is both demoralizing and a management failure. The review should summarize an ongoing conversation, not start one.
Finally, a good review looks forward as much as back. Beyond assessing past performance, it should discuss goals, development, and how the manager can help the person grow, turning the review from a backward-looking judgment into a forward-looking plan. Done this way, as a fair, evidence-based, two-way conversation about past and future, the review does what it is meant to: help the person do better and feel supported, which our guide to improving performance reinforces.
Review the whole period, not the last week
eMonitor's records across the full period help managers ground reviews in evidence and avoid recency bias, judging real outcomes rather than recent impressions. $3.90 per user.
Best practices
How to write a performance review that helps:
- Prepare with evidence: from the whole period, not memory.
- Anchor to pre-set goals: measure against what was agreed.
- Be specific: concrete examples of strengths and growth areas.
- Be balanced: honest recognition and honest guidance.
- Judge outcomes: results and quality, not busyness.
- Avoid recency and other biases: check against the evidence.
- No surprises: serious issues were raised when they happened.
- Make it two-way: a conversation about past and future.
Writing a performance review that helps means preparing with real evidence from the whole period, being specific and balanced, focusing on outcomes, guarding against recency and other biases, and making the review a genuine two-way conversation with no surprises.
The thread through all of it is honesty grounded in evidence. A review built on a record of what actually happened, delivered as a fair dialogue about past performance and future growth, helps people improve and feel supported. One built on vague, recent, or biased impressions does the opposite.
Ground reviews in whole-period evidence
The biggest failing of performance reviews is basing them on recent impression rather than the whole period, and eMonitor helps fix that. Its records of work activity and outcomes across the full review period give managers evidence to prepare with, so a review reflects the entire period's real performance rather than the last few weeks or a general feeling, which is the single best defense against recency and other biases.
Used this way, the data supports fair, outcome-focused reviews: it grounds the assessment in what actually happened, helps judge results rather than busyness, and keeps the review accurate and defensible. It is read as trends and employees can see their own data. Trusted by 1,000+ companies and rated 4.8/5 on Capterra, eMonitor costs $3.90 per user with a 7-day free trial.
If your reviews run on recent impressions, ground them in whole-period evidence instead. Start a free trial.