Team Review-Writing Checklist

Writing five, ten, or fifteen reviews the same way you'd write one is how review season eats your weekend. The problem isn't that you don't know your team. It's that you're rebuilding the same evidence-gathering and drafting process from scratch for every single person. This is the system for doing it once and running it across the whole list.

The Checklist

Work through it in order. Tick things off as you go and your progress is saved on this device, so you can come back to it over the days before the conversation rather than doing it all in one sitting.

1. Build one evidence file per person, continuously, not at crunch time

   The single biggest time sink in review season isn't writing, it's trying to remember what happened eight months ago. If you're starting that search the week reviews are due, you've already lost the weekend.

   • Keep a running log per direct report throughout the cycle, even three or four bullet points added as things happen.
   • Pull from 1:1 notes, project retros, and any peer or stakeholder feedback you've been sent, and drop it straight into that person's file as it arrives.
   • If you're starting review season with no running log, spend one focused block reconstructing evidence for everyone before you write anything, so you're not doing it person by person mid-draft.

2. Batch the evidence-gathering step across the whole team first

   Doing all your reading and gathering for every person before you draft anything keeps you in one mode of work instead of constantly switching between recall and writing.

   • Set aside a single block, or a couple of half-days, purely for pulling evidence and jotting rough notes per person, no full sentences yet.
   • Request self assessments and any peer feedback early enough that they're in hand before this block starts, not trickling in while you're mid-write.
   • Resist the urge to fully draft the first review you gather evidence for. Finish gathering for everyone, then move to drafting.

3. Use one template, filled in per person

   A consistent structure is what lets you move fast without cutting corners, because you're not deciding what to cover each time, only what to say.

   • Fix your sections: accomplishments against goals, strengths with specific examples, growth areas with specific examples, and forward-looking goals.
   • Write the section headers and prompts once, then copy the shell for every report rather than starting each review from a blank page.
   • Keep the same section order and length expectations across the team. It also makes ratings easier to compare honestly when you sit down to calibrate.

4. Draft the rating and headline first, then back it with evidence

   Writing paragraph after paragraph of detail and only deciding the rating at the end means you're doing the hardest judgment call while already fatigued.

   • For each person, write the rating and a one-sentence summary of the year before you write anything else.
   • Then go back and pull two or three concrete examples per section that support that summary, rather than listing everything and hoping a pattern emerges.
   • If you can't write that one-sentence summary confidently, that's a sign you need more evidence for this person, not that you should skip ahead to writing around it.
   • If your team's logged evidence already lives somewhere like Perform Review's Achievement Log, its review generator can turn that into a first draft to edit instead of a blank page to fill.

5. Timebox every review to the same window

   Without a timebox, review writing expands to fill whatever time you allow it, and the last few reports on your list get written worse because you're exhausted, not because those people did less.

   • Set a fixed window per review, something like 45 to 60 minutes, and stick to it even when a review feels unfinished.
   • Order your list so the hardest cases, like a mixed year or a rating you expect pushback on, go first while you have the most focus.
   • If a review consistently runs over the timebox, that's usually a sign the evidence-gathering step was incomplete, not that the writing step needs more time.

6. Write the hard ones deliberately, not last out of avoidance

   The reviews that are hardest to write, a rating that will disappoint someone, or a borderline call, are also the ones most likely to get rushed if you save them for when you're out of energy.

   • Identify which reviews on your list are genuinely difficult before you start, and schedule those in your first sitting, not your last.
   • For anyone getting tougher feedback, make sure the specific examples are airtight, since this is the review most likely to be read closely and pushed back on.
   • Don't let a hard review sit half-drafted for days. An unfinished draft you're avoiding costs more mental overhead than the 45 minutes it would take to just finish it.

7. Run a final consistency pass across the full set

   Reviews written one at a time over several days tend to drift in tone, length, and generosity. A short pass across all of them together catches what you can't see review by review.

   • Read all the ratings side by side before submitting anything, and check that similar performance got similar language and similar numbers.
   • Check that reviews written earlier in the process aren't noticeably thinner than ones written later, once you'd found your rhythm.
   • Confirm every rating has specific evidence behind it, not just adjectives. A review with no concrete examples is the one that gets challenged.

That is the whole checklist

Everything above is general by design, so it holds for most people in most companies. The specifics of your own case are the part it cannot cover.