How long does it take to write performance reviews for your team?

10 October 2026 · 6 min read

Longer than the calendar usually allows, and most of the time goes into gathering evidence and deciding what to say, not typing. The useful number is your own: time the first review of the cycle stage by stage, multiply by the size of your team, and block the hours before the deadline arrives instead of finding them in your evenings.

Why review season always runs over

Performance reviews are a rare task, which is exactly why they are hard to estimate. You write them once or twice a year, and by the next cycle you remember the deadline and the stress but not the hours.

They also look shorter than they are. The finished review might be a page per person. But a fair page needs:

• Months of evidence. Projects, feedback from peers, goals set last time, things that went well and things that did not.
• A judgment. Deciding what the overall message is, and whether the rating matches it.
• Careful wording. Feedback a person will read more than once, and that others may read later, deserves more care than an email.
• Calibration. Many organizations compare ratings across teams, which means preparing to explain each one.

Each of those is real work, and none of it shows up as words on the page until late.

The stages of one review

Break a single review into stages, and each one tends to live in a recognizable place on your Mac:

1. Gathering evidence. Past one-on-one notes, project documents, tickets, chat threads, peer feedback. Mostly the browser, your notes and your team’s chat.
2. Reading the self-review. If your company asks people to write their own first, reading it properly takes time.
3. Deciding the message. Three or four points you want the person to take away. Notes, or a scratch document.
4. Writing. Usually in the browser, in your company’s review system, or a draft in Pages first.
5. Revising. Reading it as the recipient will, checking the tone, matching examples to claims.
6. Calibration prep. A short summary per person for the meeting where ratings are compared.

The stages also tell you where to cut. If gathering evidence is the biggest stage, the fix is better notes during the year, not faster writing at the deadline.

Time the first review, then multiply

You do not need to time every review. Time the first one honestly.

1. Pick a typical person. Not the easiest review and not the hardest.
2. Do the whole thing. Every stage, including evidence-gathering, which is the one most often left out of estimates.
3. Note the stage changes. A line in Notes with the time: “2:40 evidence done, starting draft.”
4. Multiply by the team. Then add extra for the reviews you already know will be harder: someone struggling, someone up for promotion.
5. Add calibration and delivery. The meetings themselves, plus preparing for each conversation.

Here is how the arithmetic works, with made-up numbers. If the first review took three hours and you have seven reports, that is twenty-one hours of writing, before the harder cases and the calibration prep. Spread across two weeks, it is a couple of hours a day on top of everything else. Seeing that number in advance is the difference between blocking the time and losing evenings to it.

Let the Mac keep the count

Noting stage changes by hand is easy to forget once the writing absorbs you. Punchcard keeps the count without a timer. It notices which app is in front through the day and, at the closing time you set, prints a receipt: the top five apps with time on each, the rest as MISC, and a day total. On a review day, the browser line is usually the review system and the evidence-gathering; Notes and Pages are the thinking and drafting.

If you work in Chrome, Brave, Edge or Vivaldi, “Itemize websites” in Settings splits the browser line into the sites you used, so the review system and your team’s ticket tracker show as separate lines. It keeps only the site name, never the full address, the page title or anything you typed. Safari, Firefox and Arc are not itemized; their time stays on one line.

Two honest limits. Punchcard records app names only, so it does not know whose review you were writing; if you want a per-person figure, note it at the end of the day. And on a work Mac, check your company’s rules before installing anything. Can you run a personal time tracker on a work Mac? covers what to look for. What it tracks stays on the Mac, in one local file.

Make the next cycle shorter

The biggest saving comes before review season, not during it.

• Keep a running note per person. Two lines after each one-on-one: what they did, what you noticed. In review season, evidence-gathering becomes reading your own notes.
• Write the message before the review. Three bullet points of what you want the person to hear. Then write to those points.
• Use their self-review as a structure. Respond to what they raised before adding your own points.
• Block the time on the calendar. Use your measured hours, not a hopeful guess, and put the blocks in as soon as the cycle dates are known.

If review season is part of a broader squeeze on your own time, A manager’s week: how much time is left for your own work looks at the rest of the week. And when it is your turn to be reviewed, Writing your self-review when you cannot remember the year covers the other side of the table.

Questions

Is it normal for reviews to take this long?

It is common for them to take longer than planned, mostly because evidence-gathering is invisible until you do it. Your own measured time is the only figure that matters for your planning.

Should I write each review in one sitting?

The evidence and the message benefit from one focused block. Revision is better done the next day, with fresh eyes. Splitting a review across two sittings often produces a better result in the same total time.

Do templates make reviews faster?

A template helps with structure, but it does not gather evidence or decide the message, which is where most of the time goes. Running notes kept through the year save more.