How to Run a Performance Review: A Practical Guide
Performance reviews have a bad reputation because most of them are bad: a rushed form filled in the night before, a vague conversation, and a rating nobody believes in. Done properly, a review is one of the few structured moments where a manager and employee align on what’s working, what isn’t, and what happens next. The form is just the container, this guide is about making the contents worth having.
When to Use This
Run formal performance reviews on a fixed cycle, annually at minimum, twice a year is better. Annual-only reviews mean feedback arrives twelve months too late to act on. If someone’s struggling in March, telling them next January helps nobody.
Use the form also for ad-hoc reviews when something significant changes: a role change, a return from long leave, or the midpoint of a performance improvement plan. The template works for any structured performance conversation, not just the calendar cycle.
Schedule reviews well in advance and protect the time. A review squeezed between meetings signals that it doesn’t matter, and the employee will treat it accordingly.
How to Fill It Out
Section 1: Review period and role context. Record the period under review, the employee’s role, and any changes during the period (new responsibilities, team changes, manager changes). This matters because people get reviewed against expectations that shifted mid-year without anyone writing it down. If the role changed in June, the January-to-June expectations were different, say so explicitly.
Section 2: Objectives and results. List the objectives set at the start of the period (or the last review) and assess each one honestly: achieved, partially achieved, or not achieved, with evidence. “Exceeded expectations” should require specifics, not a warm feeling. Tie each assessment to observable outcomes: numbers, deliverables, feedback from others.
If objectives were never formally set, common in smaller companies, be honest about that in the form rather than inventing retroactive goals. Then set proper ones for the next period. A review that admits “we didn’t set clear objectives, here’s what we’re fixing” is more useful than one that pretends.
Section 3: Strengths. Name two or three genuine strengths with examples. Generic praise (“great team player”) is forgettable. Specific praise (“your client presentation in September won us the Meridian account, the way you handled their pricing objection was excellent”) reinforces the behaviour you want repeated and shows the employee you’re paying attention.
Section 4: Development areas. One or two areas, framed as growth rather than failure. “Needs to improve time management” is a criticism. “Would benefit from structuring project timelines more explicitly, let’s look at a planning framework together” is a development plan. The difference isn’t softness; it’s usefulness. The first leaves the employee defensive, the second gives them something to do.
Section 5: Forward objectives. Set three to five objectives for the next period. Each needs to be specific enough that you’ll both know whether it was met. Include at least one development objective (a skill to build, not just a target to hit). Agree them in the meeting, don’t present them as a done deal. Objectives the employee helped shape get more commitment.
Section 6: Overall rating and comments. If your system uses ratings, apply them consistently and be prepared to justify them. The most corrosive thing in performance management is rating inflation, when everyone gets “exceeds expectations,” the rating means nothing and your top performers notice. Both the manager and employee should have space for free-text comments.
Common Mistakes
1. The recency trap. Managers overweight the last six weeks and forget the previous ten months. Keep brief notes throughout the period, even a monthly one-liner per direct report. Without notes, you’re reviewing December, not the year.
2. No surprises rule violated. If the employee hears a serious criticism for the first time in the formal review, the manager failed. Difficult feedback belongs in the moment, not saved up. The review should summarise a year of ongoing conversation, not ambush.
3. Confusing the review with a pay discussion. Performance and compensation are related but separate conversations. Merging them turns the review into a salary negotiation, and the development discussion dies. Hold the pay conversation separately, even if it’s the following week.
4. The form becomes the point. Some managers spend more energy on getting the ratings “right” in the system than on the conversation. The form is documentation. The conversation is the review. If you only have time to do one well, choose the conversation.
Who Needs to Sign Off
The direct manager completes the assessment and leads the meeting. The employee signs to acknowledge the discussion happened, not necessarily to agree with every word; provide space for their comments. The manager’s manager (or HR) should review for consistency across the team, this is where you catch the manager who rates everyone “exceptional” and the one who never gives above “meets expectations.”
How Often to Review and Update
The review cycle itself should be annual or biannual. But supplement it with quarterly check-ins, fifteen minutes to revisit objectives and adjust. Objectives set in January are often irrelevant by July; a form that can’t accommodate that reality gets ignored.
Review the template annually. If managers consistently leave a section blank, the section is wrong, redesign it.
Download the free Performance Review Form template.
Note: employment law varies by country and region. This guide covers general best practice only, check your local requirements for anything related to dismissals, discrimination, or employee rights.