How to Write Year-End Performance Reviews: A Manager's Prep Plan

When you sit down to write performance reviews, the hard part is remembering what happened in February.

Without notes, most reviews get built from the last six weeks and a general impression. That's how strong people end up with vague praise ("great team player") and struggling people get feedback they can't act on ("needs to communicate better"). Neither helps anyone, and both are hard to defend in calibration.

The fix is mostly timing. Start three weeks before reviews are due, gather evidence before you write anything, and check every statement against that evidence before it goes into your company's form.

A three-week timeline for writing performance reviews

If your deadlines are tighter, compress the timeline but keep the order.

Step 1: Gather evidence before you write a word

For each person, pull together what actually happened this year:

• Your one-on-one notes
• The goals you agreed on last cycle, and how each one turned out
• Project results, shipped work, and numbers your team already tracks
• Messages where someone thanked them, or where a problem was flagged
• Peer feedback, if your company collects it

Turn each item into a short dated note: what happened, what it led to, and where you saw it. "Mar 14: rebuilt the onboarding checklist after two new hires missed payroll setup. No misses since. Source: 1:1 notes." One line like that is worth more than a paragraph of impressions.

Then look at how the notes are spread. If one person has twenty notes and another has three, the gap may be in your notes. Find out what you missed before you start drafting.

Step 2: Ask each person for a self-review

Send it three weeks before reviews are due, while you gather notes, and ask for it back within a week. Five questions cover it:

1. What are you proudest of from this year?
2. What got in your way?
3. What would you do differently?
4. What do you want to learn or take on next year?
5. What do you need from me?

Self-reviews surface things you didn't see, and they show where your view and theirs differ. It's far better to learn that while you're drafting than in the meeting.

Step 3: Draft from the notes, not from memory

Work through one person at a time, with their notes and self-review open. A consistent structure keeps drafts fair across your team:

• Results against each goal, with the note that shows it
• Two or three strengths, each with an example
• One or two growth areas, each with an example and what "better" would look like
• The employee's view, from their self-review
• Goals for next cycle
• The rating, in your company's terms

The biggest improvement most drafts need is specificity. A common structure is situation, behavior, impact: what was going on, what the person did, and what happened as a result. In practice, the difference looks like this (the examples are made up):

Each specific version is something the person can recognize, repeat or fix.

Step 4: Check every statement before you send it

Before a draft goes into your company's system, read it once more with these questions in mind:

• Can I point to a dated note for each claim?
• Is each statement about behavior and results?
• Does it cover the whole review period, or mostly the last few weeks?
• Would I be comfortable saying every sentence to the person directly?
• Does the rating match the words? A glowing review with a middling rating, or the reverse, invites questions.
• Have I held everyone on the team to the same standard?
• Does anything mention health, family, leave, or a protected characteristic such as age, race, religion, pregnancy or disability? If so, take it out and talk to HR.

It's a short check, and it's the easiest step to skip when the deadline is close.

Step 5: Calibrate, then hold the conversation

Before calibration, line up your team's ratings side by side. Could you defend each one using the notes alone? If you change a rating, write down why.

For the conversation, follow your company's practice on whether people see the written review first. Open with a short summary, give the person room to respond, and spend the last part on next cycle's goals. The conversation goes better when it spends more time on next year than on last year.

When to bring in HR

Talk to HR before you write if a review could lead to an improvement plan or discipline, or if it touches leave, health, a complaint or an accommodation. Your company's process and your HR team's guidance come first. This guide covers preparation. It isn't employment or legal advice.

A kit that follows this plan

Our Review Cycle Kit for Managers ($29) is built around these steps. It includes an Excel evidence log with room for 15 direct reports and 500 dated notes, a self-review request, a review draft template, a writing guide with 60 sentence frames and 24 vague-to-specific rewrites, a calibration sheet, and an optional AI drafting guide for employers that allow it. It works in Excel and Word, or in Google Sheets and Docs.