Performance Review Checklist
Nothing in a review should be new information, recency bias beats memory, and whatever was promised needs writing down. Covers manager and employee.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Performance Review Checklist?
Reviews fail in two specific ways. Nothing is written down, so the conversation becomes an argument about memory, and the difficult feedback appears for the first time in the review, which is both unfair and useless because there was no chance to act on it.
This list covers both sides, because the preparation is symmetrical: each party brings specific examples with numbers, and each leaves with the same written record. The sections for manager and employee are separate so you can delete the half that is not you.
- Covers both sides, with separate sections you can delete the irrelevant half of
- Names recency bias as the main distortion and gives the fix
- Flags review language that falls unevenly across groups
- Insists on a written record of anything promised
- Editable and exportable as PDF, CSV, Markdown or a Google Form
Updated
How to use the Performance Review Checklist
- As a manager, make sure nothing in the review is new, gather examples across the whole period, and share your assessment in advance.
- As an employee, write your own list of what you delivered with numbers, and decide what you want from the conversation.
- In the meeting, talk about specific behaviour and its effect, listen for half of it, and ask what is getting in the way.
- Disagree plainly where you disagree, and do not make decisions in the moment if the news is bad.
- Afterwards, get the outcome and any promise in writing, make objectives measurable with dates, and diarise a mid-point check.
Worked examples
Review next week, as an employee
Input
Employee section
Output
Delivered work listed with numbers, a specific ask prepared
Reviews without an ask produce nothing.
First time as a manager
Input
Manager section
Output
Evidence across the year, assessment shared in advance
Surprise causes most defensive reactions.
A rating you disagree with
Input
Afterwards section
Output
Record corrected in writing, appeal route checked
An uncorrected record becomes next year's baseline.
Background and insight
The strongest distortion in reviews is recency: without notes across the whole period, you rate the last fortnight. That applies to managers assessing and to employees recalling their own year, which is why a running note beats reconstruction in review week for both.
Sharing the written assessment in advance changes the conversation. Reading it live means the other person is processing rather than responding, and most defensive reactions come from surprise rather than disagreement. The same logic underlies the first item: serious feedback first heard at a review is a failure of the preceding six months.
Separating development feedback from a pay decision matters because mixing them makes both worse. If they are separate processes, saying so, and saying when the other happens, removes a lot of unnecessary anxiety from the conversation.
The language check is both a fairness and a legal matter. Vague praise, criticism aimed at personality rather than outcomes, and comments about style fall unevenly across groups, and they are also the parts of a review that cannot be evidenced if challenged. Specific behaviour and its effect can be discussed; "you are disorganised" cannot.
Afterwards, the written record is the thing that survives. Verbal commitments about promotions, pay reviews, projects and training do not survive a reorganisation or a change of manager, and an uncorrected inaccurate record is the one that gets read in any later dispute. Objectives need to be judgeable as true or false on a date, or the next review repeats this one.
Common use cases
Preparing as an employee
The evidence to bring and the ask to make.
Running your first reviews
No surprises, evidence across the period, and language that can be evidenced.
After a difficult review
Correcting the record, and what to do rather than resign in the meeting.
Writing objectives
Making them judgeable on a date rather than aspirational.
Tips and limitations
- Keep a running note through the year. Thirty seconds after a win beats three hours in review week.
- Share the written assessment before the meeting so they can respond rather than process.
- Talk about behaviour and its effect, not character. One can be discussed; the other cannot.
- Ask what is getting in the way. The honest answer is often process or another team.
- If the news is bad, ask for time. Decisions made in a difficult review are rarely right.
Sources and further reading
- Performance management, Acas. Running fair appraisals and handling poor performance
- Disciplinary and grievance procedures, Acas. What to do when a review leads to a formal process
- Performance Management, US Office of Personnel Management. Objective setting and appraisal cycles
Frequently asked questions
Should anything in a performance review be a surprise?
No. Serious feedback first heard at a review is a failure of the previous six months, because there was no opportunity to act on it. If something significant has not been raised, the review is the wrong place to raise it for the first time.
How should I prepare as an employee?
Write your own list of what you delivered, with numbers, because your manager has genuinely forgotten most of it. Be honest in any self-assessment including about what went badly, and decide what you want out of the conversation before it starts.
How do I disagree with a review?
Say so plainly in the meeting and point at specific evidence rather than arguing about impressions. If the written record is still wrong afterwards, correct it in writing, politely and once, because the uncorrected version is what gets read later.
What makes a good objective?
Something that can be judged true or false on a date. "Improve communication" cannot be. A specific, measurable outcome with a deadline and a mid-point check can be, and the mid-point check is what stops it being remembered in the final fortnight.
What should I do after a bad review?
Do not resign or accept a plan in the meeting; ask for time. Get the written record, correct anything inaccurate, find out what specifically would change the assessment and by when, and check what the appeal route is if the process itself was unfair.
Is there an in-depth guide to the Performance Review Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.