Performance reviews are one of the highest-leverage activities a leader does — and one of the most dreaded. Not because the conversation is hard, but because the preparation is a slog. You're digging through Slack messages, project notes, and your own memory trying to reconstruct six months of someone's work.
Claude turns this from a weekend project into a 30-minute workflow.
The Performance Review Workflow
Here's the process that works:
Dump your raw notes
Paste in everything — Slack highlights, project outcomes, 1:1 notes, peer feedback, metrics. Don't organize it. Just dump it.
Ask Claude to identify themes
Claude will find patterns across your notes — recurring strengths, areas that come up multiple times, growth trajectory.
Generate a structured draft
Use the right template for your review format (annual, quarterly, 360). Claude fills in the structure with specifics from your notes.
Refine the language
Ask Claude to check for vagueness, bias, and balance. Then edit for your voice.
Prepare for the conversation
Generate talking points and anticipated questions so you walk in ready.
Quick check
What's the primary advantage of using AI to assist with performance reviews?
Step 1: The Raw Notes Dump
Don't spend time organizing your notes first. Claude is better at finding patterns in messy data than you are. Just paste everything.
I need to write a performance review for [employee name], [their role]. Here are my raw notes, observations, and data from the past [time period]. Please:\n\n1. Identify the top 3-5 themes that appear across these notes (both strengths and growth areas)\n2. Pull out specific examples for each theme — with dates or project names where possible\n3. Flag any contradictions in my notes (e.g., 'great communicator' in one note but 'needs to improve stakeholder updates' in another)\n4. Note any gaps — important areas of their role where I have no notes at all\n\nRaw notes:\n[paste everything here]
Pro Tip
Include quantitative data when you have it — revenue influenced, projects shipped, tickets resolved, customer satisfaction scores. Claude will weave these into the review naturally, which makes your feedback more credible and less subjective.
Step 2: Generate the Structured Review
Once you have themes, ask Claude to write the actual review in your company's format.
Annual Review Template
Write a formal annual performance review for [employee name], [role], based on the themes and examples we just identified. Use this structure:\n\n1. **Summary** (2-3 sentences — overall assessment)\n2. **Key Accomplishments** (3-5 bullet points with specific examples and impact)\n3. **Strengths** (2-3 strengths with evidence)\n4. **Areas for Development** (2-3 areas with specific, actionable suggestions — not vague 'improve communication')\n5. **Goals for Next Period** (3-4 goals that are specific and measurable)\n6. **Overall Rating** (suggest a rating on [your scale] with justification)\n\nTone: direct, fair, and specific. Avoid generic praise ('great team player') — every statement should be backed by an example. Avoid recency bias — weight examples from across the full review period.Quarterly Check-In Template
Write a quarterly performance check-in for [employee name], [role]. This should be lighter than a formal annual review — think 'focused conversation guide' not 'HR document.' Structure:\n\n1. **What's going well** (2-3 specific wins from this quarter)\n2. **What to adjust** (1-2 areas to focus on next quarter, with concrete suggestions)\n3. **Career development** (one observation about their growth trajectory and a question to discuss)\n4. **One thing I want them to know** (a direct, honest statement — positive or constructive)\n\nKeep it under 300 words total. This should feel like a thoughtful conversation, not a form.
360 Review Summary
I've collected 360-degree feedback for [employee name] from [number] people — including peers, direct reports, and cross-functional partners. Here is all the raw feedback:\n\n[paste all feedback]\n\nPlease:\n1. Synthesize into 3-4 key themes with supporting quotes (anonymized)\n2. Identify where feedback is consistent (everyone says the same thing) vs. divergent (some say strength, others say weakness)\n3. Separate perception issues from performance issues\n4. Draft a summary I can share with [employee name] that is honest and constructive\n5. Suggest 2-3 discussion questions I should ask in the review conversation\n\nImportant: maintain anonymity — do not attribute specific feedback to identifiable people.
Checking for Bias and Fairness
This is where Claude earns its keep. We all have blind spots.
Review this performance evaluation draft for potential bias:\n\n[paste your draft]\n\nCheck for:\n1. **Recency bias** — Are most examples from the last 4-6 weeks? Flag if so.\n2. **Halo/horn effect** — Does one strong positive or negative dominate and color everything else?\n3. **Vague language** — Flag any statement that isn't backed by a specific example ('great communicator' without evidence)\n4. **Comparison to others** — Am I comparing this person to a teammate instead of evaluating against their role expectations?\n5. **Attribution bias** — Am I crediting their effort for successes but blaming external factors for struggles (or vice versa)?\n6. **Language patterns** — Flag any adjectives that research shows are applied differently across gender, race, or personality type (e.g., 'aggressive' vs. 'assertive,' 'emotional' vs. 'passionate')\n\nFor each issue found, suggest a specific rewrite.Sarah is a great team player who always has a positive attitude. She sometimes struggles with the technical details but makes up for it with her people skills.
Preparing for the Conversation
The written review is only half the job. The conversation is where the impact happens.
I'm about to deliver this performance review to [employee name]:\n\n[paste review]\n\nHelp me prepare for the conversation:\n1. What questions might they push back on? How should I respond?\n2. What might they be feeling when they read this? (Especially the development areas)\n3. Suggest 3 open-ended questions I should ask to make this a two-way conversation, not a lecture\n4. If they get emotional or defensive, what's my best approach?\n5. Draft a strong opening sentence that sets the right tone — honest, supportive, not sugar-coated
Scenario
You have a team member who's been performing well technically but is terrible at collaboration. Multiple people have complained privately but nobody wants to be named. You need to address it without revealing sources.
Self-Review Support
Many companies ask employees to write their own self-reviews. Claude is great for this too.
Help me write my self-review for [time period]. I'm a [role] at [company]. Here's what I did this period:\n\n[paste your accomplishments, projects, metrics, challenges]\n\nWrite a self-review that:\n- Leads with impact, not activity (what changed because of my work, not just what I did)\n- Is confident without being arrogant\n- Honestly addresses 1-2 areas where I struggled or am still developing\n- Ties my work to team/company goals where possible\n- Is under 500 words\n\nDon't embellish or exaggerate. Use the specific data and examples I provided.
The Review Cycle System
If you manage a team of 5+, set up a Project in Claude with:
- Your company's review template and rating scale
- The role descriptions and leveling criteria for each person
- A running document where you paste notes about each person throughout the quarter
When review time comes, you start the conversation with: "It's review time. Generate reviews for everyone on my team based on the notes I've been collecting."
Note
Use CoWork if your team shares a workspace. You can build a shared review system where managers across the org use the same criteria, the same bias checks, and the same quality bar. This is especially useful if you're the CEO reviewing reviews — Claude can flag inconsistencies across managers.
Real example
“I used to spend an entire weekend writing six performance reviews. Now I spend 30 minutes dumping notes and an hour reviewing and personalizing what Claude generates. The reviews are better than what I used to write — more specific, more balanced, more fair.”
— Head of Engineering
Manager of a 12-person engineering team at a Series B startup
Common Mistakes
Don't let Claude write the review without your notes. If you just say "write a review for a senior product manager," you'll get a generic review that could apply to anyone. The value is in Claude structuring YOUR observations, not generating fictional ones.
Don't skip the bias check. We all think we're fair. We're all wrong. The two minutes it takes to run your draft through a bias check is the highest-ROI step in the process.
Don't copy-paste without editing. Claude writes the first draft. You bring the judgment, the relationship context, and the nuance. Always read every word and adjust for things only you know.