How to prepare for a performance review (manager's side)

The quality of a review is decided before you write a word — in what you collected. Here is how to prepare for a performance review so you walk in with a year of evidence instead of a blank page and a fading memory.

Writing the review is the easy part once the preparation is done. The hard part is reconstructing what actually happened over twelve months for each person — and most managers try to do it in a single panicked evening. This guide is about the days and weeks before you write: how to gather real evidence, why cramming quietly produces unfair reviews, and a checklist to make sure you've covered the whole period before you start.

Gather evidence across the whole year

The goal of preparation is simple: arrive at the writing stage with a chronological record of what each person did, said, and delivered across the entire review period. Not impressions — artifacts. The further back you can see clearly, the fairer your review will be.

The best version of this isn't a frantic dig at the end; it's a habit. If you jot a line after each 1:1 and tag notable wins as they happen, "preparation" becomes assembly rather than archaeology. But even starting cold, you can reconstruct a lot. The point is to pull from sources that captured the moment, not your end-of-year recollection of it.

Avoid the cramming trap

Trying to summon a year of performance the night before is where reviews go quietly wrong. Three things happen when you cram:

• Recency bias takes over. You remember the last month vividly and the first nine through a fog, so people are judged on timing rather than performance.
• The vivid beats the important. One dramatic incident — a missed deadline, a great demo — crowds out months of steady, less memorable work that actually mattered more.
• You reach for adjectives. With no specifics in front of you, you fall back on "reliable" and "needs to be more proactive" because you can't recall the example that would have made the point land.

The antidote isn't a better memory. It's collecting the evidence over time, or at minimum giving yourself enough runway before the deadline to reconstruct it properly from records.

The review you write the night before isn't dishonest. It's just a review of whatever you happened to remember — which is rarely the same as what happened.

What to collect

For each person, pull together:

• Your 1:1 notes. The single richest source — themes, struggles, things they raised, commitments they kept. (If you don't keep these, our guide on running 1:1s is where to start for next time.)
• Shipped work and outcomes. What they delivered, and the actual impact — numbers where you have them, not just "worked on X."
• Goals from the last review. What did you agree they'd focus on, and what happened with each?
• Peer and cross-team input. A few quick notes from people who worked closely with them often surface things you never saw.
• Specific moments. The escalation they handled, the time they spoke up, the project they rescued — concrete scenes you can describe.
• Growth signals. Where they stretched, where they got stuck, what they're asking to do next.

A prep checklist

Before you start writing any single review, confirm you can answer yes to each:

1. I've reviewed evidence from the whole period, not just the last few weeks.
2. I have at least two or three specific, concrete examples for each person — wins and growth areas both.
3. I've checked their goals from last cycle and noted the outcome of each.
4. I've gathered input from at least one or two people who worked with them.
5. Nothing I'm about to write will be a genuine surprise — anything serious was already raised in a 1:1.
6. I've applied the same lens and the same bar to everyone on the team.

With those in hand, the writing goes fast and the result holds up. For the writing stage itself — structure, phrasing, and keeping it fair — see how to write a performance review.