Calibration prep for a manager who's never done it before: a 5-day worksheet

60-Second Summary

Calibration prep done in the meeting is the #1 reason new managers get rolled. Five days, 30-60 min each, gets you to defensible.
Stack-rank before you assign ratings. The ranking forces honesty; the rating is just a label.
For each report, prep three sentences: signature strength, sharpest gap, the data behind the rating.
Anchor against last cycle's ratings to surface inflation/deflation drift before someone else does it for you.

Calibration is a room full of managers arguing about people they don't manage. The new manager who walks in unprepared gets their ratings adjusted by stronger voices, and their team pays the cost six months later in promotions and comp. The good news: 5 days of structured prep is the difference between getting rolled and holding your stack.

Day 1 — Stack-rank without ratings (60 min)

Write every direct report on a separate index card or row.
Rank them top to bottom on overall impact this cycle. Do not assign ratings yet.
If you can't decide between two, ask: 'Which one would I fight harder to keep if both quit tomorrow?' That's the higher one.
Sit with the ranking for 12 hours. Re-do it cold the next morning. The two versions should match within one swap.

Why ranking before rating

Ratings are anchors. The moment you write 'Exceeds Expectations' next to someone's name, you'll defend it. Ranking first removes the label and forces you to compare humans to humans.

Day 2 — Three sentences per report (45 min)

The three-sentence script

1
Signature strength
One specific thing they did this cycle that nobody else on the team could have done. With evidence.
2
Sharpest gap
The one thing that, if it were fixed, would move them up a level. Not a list — the one that matters most.
3
Rating rationale
Two pieces of evidence that justify the rating. Not feelings. Numbers, artifacts, or peer feedback.

Day 3 — Anchor against last cycle (30 min)

Check	What to look for	If true, prep for
Inflation drift	More than 40% of your team rated above expectations	Someone in the room will challenge — bring evidence
Deflation drift	Nobody rated above expectations	You will be asked: 'Is nobody on your team excellent?'
Persistent low	Same person below expectations 2 cycles running	Be ready for: 'Why are they still on the team?'
Promo readiness gap	Two people at the top of stack, neither promoted last cycle	Be ready to advocate or explain the wait

Day 4 — Pre-align with your skip (20 min)

Script — manager to skip-level pre-cal

'I want 15 minutes before calibration. I'll walk you through my stack and ratings. I need three things from you: tell me where you'd push back so I can prep, tell me where you'll back me when others push back, and flag anyone whose rating you've heard concerns about from outside my team — I'd rather hear it now than in the room.'

Day 5 — Rehearse the hard ones (30 min)

Pick the two reports whose ratings you're least sure about. Out loud, defend each one in 90 seconds. If you can't get through 90 seconds without saying 'um, well, kind of' — that's the rating that will get adjusted in the room. Either tighten your case or change the rating now.

In the room — defending your stack

Lead with your top of stack and your bottom — the middle takes care of itself.
If challenged, ask 'what evidence would change your mind?' before defending.
Never concede a rating change because someone is louder. Concede only when they bring evidence you didn't have.
If your skip flips on a pre-aligned position, name it: 'I want to flag — we aligned on this Tuesday. What changed?'
Take notes on every rating that gets adjusted. That's your feedback to deliver back to the report — in your words, not the room's.

After the room

If a rating gets adjusted against your case, you still own the conversation with your report. Don't say 'calibration overruled me' — that erodes trust in the whole process. Say 'here's the rating and here's what would change it next cycle.'

Written by Pawan Joshi.Sources cited inline.

First published 16 Jun 2026See site changelog →