How-To Guide · 2026

How to Write Performance Reviews with Claude - fair, specific, and actually useful.

Performance reviews are important and time-consuming - and most managers dread writing them. Claude can help you write reviews that are more specific, more balanced, and more useful for the person receiving them, while cutting the time from 2 hours per person to 30–45 minutes.

The Short Version

Gather your notes (projects completed, specific behaviors observed, ratings if applicable) before opening Claude. Tell it whether you're writing a manager review, self-assessment, or peer review. Paste your notes and ask Claude to structure them into balanced feedback: strengths with evidence, development areas with specifics, and forward-looking goals. Your edit pass: verify nothing was softened so much it lost its meaning, and add one personal acknowledgment that shows you know the person.

Manager review system prompt

You are writing a manager performance review for a direct report. Your goal is to write feedback that is specific, balanced, honest, and useful for the employee's development - not sanitized, and not generic. FORMAT: 1. Overall Summary (2–3 sentences - the essential truth about this person's performance) 2. Key Strengths (2–3 strengths, each with a specific example or evidence) 3. Development Areas (1–2 areas, described specifically and constructively - what behavior, what impact, what the better version looks like) 4. Goals for Next Period (2–3 specific, achievable goals tied to development areas and career trajectory) RULES: - Every strength must have a specific example - no unsupported praise - Development areas must describe behaviors, not personality traits - Don't soften feedback to the point where the message is lost - Don't use: "can sometimes," "occasionally," "could benefit from considering" - be direct - Length: 350–500 words total EMPLOYEE: [Name, role, tenure] REVIEW PERIOD: [Timeframe] RATING (if applicable): [Exceeds/Meets/Below expectations or your company's scale] YOUR NOTES: [Paste all your raw observations, project notes, specific incidents, 1:1 notes]

Self-assessment system prompt

You are helping an employee write their self-assessment for performance review. The tone is reflective and honest - not a brag sheet, not falsely modest. A strong self-assessment acknowledges real growth, names specific contributions, and shows self-awareness about development areas. FORMAT: 1. Key Contributions This Period (3–4 specific achievements with context and outcomes where possible) 2. Skills and Capabilities Developed (what you've learned or built this year) 3. Areas for Growth (honest reflection on where you want to improve - shows maturity and self-awareness) 4. Goals for Next Period (what you want to accomplish and why it aligns with the team or company) TONE: First person, professional but human - reads like the person wrote it, not HR RULES: - Use specific numbers and outcomes where available - Name projects and collaborators where appropriate - Don't hedge on accomplishments you genuinely own - Don't claim contributions you can't substantiate PERSON: [Name, role, team] PERIOD: [Timeframe] RAW NOTES: [Paste your self-notes: projects, wins, challenges, feedback received, goals you set]

Collecting your notes: what to gather

The quality of your review depends almost entirely on what you feed Claude. Spend 10–15 minutes pulling together:

Your calendar and project list from the review period - what did this person actually work on?
Any feedback you gave in 1:1s or Slack - look for patterns, not isolated incidents
Goals set at the last review - did they meet them, exceed them, or fall short?
Peer feedback if you have it
Any specific incidents (good or difficult) that stand out - these are your most credible examples
The person's career goals (if you know them) - development feedback lands better when it's connected to where they're trying to go

Common mistakes

Recency bias in your notes. Claude will reflect whatever you give it. If your notes only cover the last 2 months of a 6-month review period, the review will be biased toward recent performance. Pull your full-period notes before prompting.
Letting Claude soften difficult feedback. By default, Claude may soften difficult messages. Tell it explicitly: "Do not soften the feedback on [specific area] - the message needs to be clear." Then check that it came through.
Not reading for accuracy. Claude may infer things from your notes that are slightly off. Read every claim and verify it reflects your actual assessment.
Generic development goals. Claude will write "continue to develop communication skills" if you don't give it better direction. Be specific in your notes about what improvement looks like for this person.

Time savings

Most managers spend 1.5–3 hours per person on performance reviews - often more when they're writing for 5–8 direct reports during a compressed review window. Using this workflow, the drafting phase drops to 30–45 minutes per person. For a manager with 6 direct reports, that's 6–12 hours recovered during review season - enough to make the difference between thoughtful reviews and rushed ones.

The quality benefit is also significant: Claude produces structurally consistent reviews that don't accidentally give more detail to some people than others based on how tired the manager was when they wrote them.

Want Claude set up for your HR and people ops workflows?

We build Claude systems for HR teams, people managers, and operations leaders who want to spend less time on admin and more time on their people.

Book an AI Audit → Free AI Audit Tool →