How to Write a Performance Review with Claude
You'll finish with a fair, structured performance appraisal you're confident sending — even if your notes are a mess, you have no template, and you've got 20 minutes before the deadline. Paste your raw input, run one prompt, refine twice. That's the whole thing.
TL;DR
- You'll have a complete draft in under 60 seconds — even from bullet-point notes.
- Free plan works fine; one conversation is enough for a full review.
- Claude writes, you fact-check and sign off — the judgment stays yours.
- What used to take two hours takes 20 minutes, including your edits.
Before you start
- A Claude.ai account — free plan works fine here; upgrade to Pro if you're running several reviews back to back.
- Whatever notes you actually have: 1-on-1 scribbles, a Slack thread, project outcomes, a self-assessment form — even messy bullet points work. Don't clean them up first; paste them raw.
- The review format your client or company expects. If you don't know it off the top of your head, spend 30 seconds checking before you open Claude — this single detail shapes the whole output.
- The employee's job title and the review period. Two fields. Without them, Claude defaults to generic phrasing that you'll spend time deleting.
How to do it — step by step
Collect your raw notes and evidence
Start by opening a blank doc and dumping everything in: 1-on-1 notes, project outcomes, peer feedback, self-assessment answers, any numbers you tracked. Don't edit — paste it all raw. The reason this matters: Claude can only find evidence that's actually there. Spend an extra two minutes retrieving one more specific example — a project name, a metric, a piece of feedback — and that usually saves three rounds of follow-up edits later. If you're pulling from an HR workflow system you've kept through the year, this step takes 90 seconds instead of ten minutes.
Define the review format and tone you need
Before moving on, lock in two things: the section headings your client or company expects (Overall Summary, Key Achievements, Areas for Development, Goals for Next Period — whatever their template says), and the tone (formal and evaluative, or coaching-focused and direct). You're doing this now, not inside Claude, because if you skip it you'll get a well-written review in the wrong structure and spend more time reformatting than you saved. If you work with multiple clients who each have their own format, the HR Prompt Builder is worth bookmarking — it's built for exactly this kind of reuse.
Run the prompt and get a first draft
Now open Claude and paste the prompt below — fill in the green placeholders, then paste your notes at the bottom. Hit send. This is where Claude usually shines: it reads across all your notes at once, pulls out the recurring themes, and returns a structured draft in professional language in under a minute. Don't try to perfect the prompt before sending — a rough first pass gives you something to react to, which is always faster than writing from scratch. The goal here is a working skeleton, not a final document.
Refine tone, evidence, and balance
At this point, read the draft once through and ask yourself two things: does every claim trace back to a real example in your notes, and does the balance between positive and constructive feedback actually match how this person performed? If the output feels generic — phrases like "consistently demonstrates strong communication skills" with nothing behind them — that's your cue to push back in the same conversation. Be specific: "The development section is vague — rewrite it using only the feedback from the design team in my notes" gets you a better result than "make it more specific." The AI for HR Teams hub has more examples of how to phrase these follow-up requests if you get stuck.
Final check and personalise before sharing
Now check every factual claim against your original notes — not because Claude is unreliable, but because it occasionally blends two similar examples or slightly misattributes a detail, and you're the one signing this off. Replace any leftover generic phrases with the employee's actual name, real project names, and specific dates. Don't worry if this takes five minutes; it's the step that makes the review feel written by a person who actually knows the employee, not generated from a template. Then paste into your HR platform or document. Start to finish, you should be done in 20 minutes.
The prompt
You are helping me write a professional performance review for one of my employees or team members. Context: - Employee name and job title: [e.g. Sarah Chen, Senior Marketing Coordinator] - Review period: [e.g. January–December 2024] - Review format: [e.g. Overall Performance Summary / Key Achievements / Areas for Development / Goals for Next Period] - Desired tone: [e.g. professional and coaching-focused, not punitive] - Rating scale (if applicable): [e.g. Exceeds / Meets / Below expectations, or leave blank if no rating] Raw notes and evidence: [Paste your notes here — bullet points are fine. Include specific examples, project outcomes, feedback received, metrics, and anything relevant to this employee's performance during the review period.] Using only the evidence in my notes above, write a structured performance review for this employee. Follow the format I specified. For each section, include specific examples drawn from my notes rather than generic statements. Balance positive observations with honest, constructive feedback. Keep the language professional, clear, and direct — avoid jargon and filler phrases like "goes above and beyond." Do not invent details that are not in my notes. If a section of the format has no supporting evidence in my notes, say so briefly rather than padding with generic content. Please produce a draft performance review that I can refine and personalise before sharing with the employee.
What the output looks like
Overall Performance Summary
Sarah delivered a strong year in the Marketing Coordinator role, taking clear ownership of the Q3 product launch campaign and demonstrating consistent reliability across recurring responsibilities. Her performance meets expectations in most areas and exceeds them in project coordination and cross-team communication.
Key Achievements
Led the end-to-end coordination of the Horizon product launch, managing timelines across four departments and delivering all deliverables on schedule. The campaign generated 2,400 qualified leads in its first month — 20% above the target set in January. Additionally, Sarah redesigned the internal content calendar process, reducing missed deadlines across the team by approximately 30% in H2.
Areas for Development
Sarah's written communication is strong in internal documents but less consistent in external-facing copy, where tone can occasionally drift from the brand voice. A structured review step with the brand team before publishing would address this. She has also flagged a desire to build more confidence in data analysis; enrolling in the Q1 analytics workshop would be a practical next step.
Claude vs Gemini for this workflow
| Dimension | Claude | Gemini |
|---|---|---|
| Tone nuance and sensitivity | Better | Good |
| Sticking to your notes only | Better | Good |
| Following a custom format | Better | Good |
| Integration with Google Docs | Good | Better |
| Speed on free plan | Good | Better |
| Overall recommendation | Recommended | Solid alternative |
How to customise this workflow
For small business owners with no HR background
You'll get a more usable first draft if you add one line to the prompt: "Assume I have no HR background — use plain language and avoid jargon." Then, before pasting your notes, ask Claude in a separate message: "Suggest a simple review format for a 10-person company with no formal appraisal process." It'll give you a structure in 20 seconds that you'd otherwise spend 30 minutes trying to build from a blank doc. The AI for HR Teams hub has more guides written specifically for non-specialists doing HR work on their own.
For independent HR consultants working with multiple clients
If you're doing this for three clients a month, don't rewrite the prompt each time — save a version per client format in your notes tool and just swap in their specific sections, rating scale, and competency framework before pasting the employee notes. That drops the setup from five minutes to under one. The HR Prompt Builder is built for exactly this: you configure the prompt once per scenario and reuse it without starting from scratch.
For 360-degree or peer-inclusive reviews
Don't worry if your input is a mix of sources — paste it all in and label each block clearly: "Peer feedback from design team:", "Self-assessment:", "My observations:". Claude handles multiple sources well and will synthesise across them. More usefully: tell it to flag any significant gaps between how the employee sees themselves and how peers described them. That discrepancy is often the most important thing to bring up in the actual review conversation.
For remote or distributed teams
Remote reviews tend to be thinner because you don't have the informal observation data you'd pick up in an office. Before moving on to the prompt, pull in whatever written trail exists: Slack threads where the person communicated well (or didn't), async retro notes, written project updates. Then add this instruction to your prompt: "Pay specific attention to collaboration quality and async communication — these matter most for remote roles." Otherwise Claude defaults to achievements-and-goals structure and misses what actually matters for distributed work.