How to Write a Performance Review as a Manager (Fair, Clear, Usable)
Review season lands, and your brain fills with last month’s wins, last week’s fire drill, and the person who sits nearest your desk. That is not a process. That is memory theater.
Managers who write strong performance reviews do not wait for the form to open. They gather evidence early, draft in plain language, check themselves for bias, prepare for calibration, and run a conversation that turns the rating into a plan. This guide is for people managers and directors writing reviews and running the meeting, especially if this is your first cycle.
You will get a draft structure, an anti-bias pass, a meeting script, a calibration prep sheet, and examples that turn vague phrases into usable coaching. For everyday feedback between cycles, see giving and receiving feedback at work. For hard talks that should not wait until the annual form, use difficult conversation scripts at work.
Core rule: Write the review as if the employee will use it to change next quarter’s behavior. Every critical paragraph needs a concrete example and a forward-looking ask. If a section could not guide a change, it is ranking theater, not coaching.
Gather input beyond your own memory
Do not draft from vibes. Build a thin evidence file before you open the official form.
Sources worth collecting:
- Goals and outcomes from the cycle (docs, dashboards, project notes)
- Your 1:1 notes and agreed action items (how to run a 1:1 meeting)
- Peer or cross-functional input (short, structured asks beat open-ended “any feedback?”)
- Customer or stakeholder notes when the role touches them
- The employee’s self-assessment, if your process includes one
Calibration prep sheet (fill one per person):
Employee / role / time in role:
Cycle goals (3-5):
Evidence bullets (outcome + date + your role / their role):
-
-
Peer / partner input (themes, not gossip):
-
Strengths with examples:
-
Development areas with examples + forward ask:
-
Proposed rating / summary language (draft):
Risks / open questions for calibration:
HR / process notes (if any):
Ask peers for scenes, not labels. “What is one thing they did that helped your team ship?” and “What is one thing that slowed collaboration?” beat “How would you rate them?” Cap each peer at two or three bullets so you get signal, not a second full review.
If the cycle was remote-heavy, lean harder on artifacts and written outcomes. Visibility bias hits quiet, distributed contributors first. A shared doc of shipped work often tells a fairer story than who spoke most in meetings.
When the employee submits a self-assessment, read it before you finalize your draft. Use it to catch wins you forgot and to prepare where your views diverge. Do not copy it into your review as a shortcut.
Manager review draft structure
Use the company form’s required fields, then fill them with this spine so the writing stays usable:
- Role and context (one short paragraph: scope, team changes, major constraints)
- Outcomes vs. goals (what landed, what slipped, why)
- How the work got done (collaboration, judgment, reliability, leadership if relevant)
- Strengths to keep (2-3, each with an example)
- Development areas (1-2, each with example + forward ask)
- Next-cycle focus (goals or themes, not a novel)
- Support you will provide (coaching, access, scope changes)
Skip personality essays. Skip comparing them to their loudest peer in the same paragraph. Stick to the job, the standards, and the next move.
Rewrite vague phrases into specific ones
| Vague | Specific |
|---|---|
| “Needs to be more strategic.” | “In Q2 roadmap reviews, proposals jumped to solutions before naming the customer problem. For next cycle, bring a one-page problem statement to every priority pitch.” |
| “Great teammate.” | “When Design slipped two weeks, they renegotiated the launch cut with Marketing the same day so Sales had a clear story.” |
| “Communication issues.” | “Status updates often arrived after standup, so blockers hit late. Ask: post blockers in the channel by 10 a.m. on meeting days.” |
| “Not ready for more scope.” | “Owns current queue well; has not yet led a cross-team dependency without escalation. Next step: lead one multi-team milestone with a shared decision log.” |
If you cannot name a scene, you are not ready to write that line.
Balance strengths and development areas
A fair review is not a sandwich of fake praise around a knife. It is a clear picture of contribution and a short list of growth that matters for the role.
Guidelines that keep tone honest:
- Lead with outcomes, then craft. People need to know what worked.
- Limit development themes. Two sharp asks beat six soft complaints.
- Match weight to role level. A senior IC’s bar for judgment is higher than a new hire’s.
- Separate “not yet” from “not meeting.” Stretch gaps and performance gaps need different language.
- Never invent balance. If the cycle was rough, say so with evidence. If it was strong, do not invent a fake flaw to look “tough.”
When ratings language is “meets,” “exceeds,” or similar, write the narrative first, then choose the label that fits the evidence. Do not write backward from a desired rating.
Companies differ on rating scales and calibration rules. Follow your process. This article does not claim one distribution is correct.
Calibration: what it is and how to prepare
Calibration is usually a meeting where managers align ratings and language across a group so similar performance gets similar labels. It is not a gossip hour, and it is not a place to invent stories you did not put in the draft.
How to prepare:
- Bring evidence bullets, not adjectives
- Know peer input themes in one sentence each
- Be ready to explain tradeoffs (“strong delivery, late stakeholder updates”)
- Flag time-in-role, scope changes, and inherited messes without using them as excuses
- Update your draft after the room lands. Do not leave the written review fighting the calibrated rating
If you disagree in the room, argue with examples. If you lose the argument, own the final message with the employee. Do not blame “calibration” as a shadowy villain in the live conversation.
Avoid bias: a quick anti-bias review pass
Run this pass on every draft before you submit:
Anti-bias checklist
- [ ] Recency: Did the last six weeks dominate a six- or twelve-month cycle?
- [ ] Visibility: Am I rewarding proximity, camera time, or Slack volume over outcomes?
- [ ] Similarity: Am I favoring people who work like me or share my background?
- [ ] Halo / horns: Did one win or one miss color everything else?
- [ ] Role clarity: Am I grading them on work that was never scoped or resourced?
- [ ] Compare-to-peer trap: Did I write relative rankings where absolute standards belong?
- [ ] Language scan: Any identity comments, accent jokes, “culture fit” vagueness, or parental-status assumptions? Remove them.
- [ ] Forward ask: Does every development paragraph tell them what to do next?
Bias checks do not replace your company’s DEIB or HR guidance. They are a manager hygiene step.
What goes in writing vs. said live
Put in writing:
- Outcomes and examples
- Rating or summary language your process requires
- Clear development asks
- Next-cycle goals or themes
- Commitments you make as the manager
Save for the live conversation (then summarize in writing if needed):
- Tone, empathy, and pacing
- Clarifying questions and their perspective
- Career hopes that need dialogue
- Sensitive context you should not over-document without HR guidance
Do not sandbag: if a concern is serious enough to affect the rating, it should not be a surprise invented in the room. Steady managers surface issues in 1:1s during the year. Reviews confirm and plan; they should not ambush.
For sensitive cases (possible PIP paths, integrity issues, leave-related complexity), partner with HR early. Bring facts and prior coaching notes. Ask what the process requires. This is process partnership, not legal advice. Employment rules vary by company and place.
Deliver the review conversation
Treat the meeting like a structured talk, not a reading of the form in a monotone.
Meeting script (adapt freely)
Opening (2 minutes)
“Thanks for making time. Goal today: walk through how I see the cycle, hear your view, land on clear strengths and one or two development focuses, then set next-cycle goals. You’ve seen the written review. I’ll summarize, then I want your take.”
Rating / summary discussion
“On outcomes, here’s what I weighted most: [2-3 examples]. That led me to [rating/summary language]. Where does that match or miss how you saw the year?”
Strengths
Name two with scenes. Ask which strength they want to lean on next cycle.
Development
“One area to improve: [example]. Impact was [impact]. Forward ask: [specific behavior or milestone]. What support do you need from me?”
Disappointing news without sugarcoating
“This rating is below what you were aiming for. I’m not going to soften the facts. Here is the gap in plain terms: [examples]. Here is what ‘on track’ looks like over the next 90 days: [signals]. I want you to succeed, and I will [support]. I also need you to own [ask].”
Do not pile on. Do not hide behind the form. Do not promise promotions or pay outcomes you do not control. If the news is hard, slow down and check understanding: “What are you taking away from what I just said?” Fix misunderstandings in the room when you can.
Close
“I’ll send a short follow-up with goals and check-in dates. Questions before we stop?”
If emotions spike, pause. Offer a short break or a follow-up meeting within a few days. Stay respectful. If the conversation moves into policy or legal territory, involve HR rather than improvising. Your job in the moment is clarity and dignity, not winning an argument.
Connect the review to next-cycle goals
A review without a forward plan is a grade with no syllabus.
Within a week of the meeting:
- Confirm 3-5 goals or outcome themes for the next cycle
- Tie each development ask to a visible milestone
- Put check-ins on the calendar (for example, 30/60/90 days, or your normal 1:1 cadence with a quarterly deep dive)
- Note what you will change as the manager (scope, access, coaching, stakeholder cover)
Keep goals measurable enough to discuss, not fake-precise. “Lead the Q1 launch decision log and land stakeholder alignment one week before ship” beats “be more cross-functional.”
Follow-up cadence after reviews
48 hours: Send a brief written summary: rating/summary language, strengths, development asks, agreed goals, support you committed to.
Next 1:1: Confirm they read it. Adjust wording if something was unclear. Do not reopen the whole rating fight every week; reopen progress.
Monthly (or your regular cadence): Track development experiments. Ask what is working. Course-correct early.
Mid-cycle: Do a lightweight progress review so the next formal cycle is not a cliff.
Managers who only talk performance once a year create surprise. Managers who coach in 1:1s make review day a checkpoint. If someone wants more coaching between formal cycles, point them to how to ask for feedback at work so the ask stays specific and easy to answer.
HR partner checklist (process, not legal advice)
Use this when a case feels sensitive or unclear:
- [ ] What does our policy require for documentation and timing?
- [ ] Have prior coaching conversations been documented in the right place?
- [ ] Is this a development gap, a role misfit, or a conduct issue?
- [ ] Who else needs to be informed (skip-level, HRBP)?
- [ ] What am I allowed to say about pay, promotion, or headcount?
- [ ] If performance may lead to a formal plan, what are the next process steps?
Do not invent timelines for termination or promise outcomes. Ask HR for the playbook your company uses.
FAQ
How long should a written performance review be?
Long enough to cover outcomes, two strengths with examples, one or two development asks, and next-cycle focus. Short enough that someone can act on it. Pages of adjectives help no one.
What if I disagree with the employee’s self-assessment?
Compare evidence side by side in the meeting. Acknowledge where they are right. Be clear where your view differs and why. Update your own draft if their evidence changes your mind.
How do I handle “meets expectations” when someone wanted “exceeds”?
Explain the standard in scenes, not slogans. Show what exceeded looked like this cycle in their role. Set a concrete path for the next cycle if growth is realistic.
Should I discuss compensation in the performance review?
Follow your company’s process. Some firms separate pay conversations. If pay is in scope and you are authorized, keep it factual. If you are not the decision maker, do not guess.
What if I inherited the employee mid-cycle?
Say so in the context section. Weight the period you managed, include prior-manager input if available, and avoid grading work you never saw.
Writing a performance review as a manager is a coaching document first and a ranking exercise second. Gather evidence, write scenes, pass for bias, calibrate with facts, deliver without theater, and lock the next quarter’s asks. If a paragraph cannot change next quarter’s behavior, cut it and write something that can.