Most managers spend far more time on performance reviews than the actual value they deliver warrants. The challenge is rarely a lack of knowledge about the employee — it is translating that knowledge into clear, balanced, professional written language that is fair, specific and legally defensible.
Claude does not replace your judgement about an employee. It helps you express that judgement clearly. You bring the observations, the context and the final decision. Claude structures them into language that works.
Key insight: The hardest part of a performance review is not knowing what to say — it is saying it in a way that is specific, fair and actionable. Claude excels at exactly that translation task.
Managers typically spend 2–3 hours per review on wording alone
Vague feedback is the most common employee complaint about reviews
Inconsistent language across reviews creates legal and fairness risk
Blank page paralysis
Starting from scratch for every employee, every cycle — even when you know exactly what you want to say.
Inconsistent tone
Reviews written at different times of day, in different moods, end up feeling inconsistent across the team.
Risky language
Poorly worded feedback — especially on underperformance — can create employment law exposure without proper care.
These three prompts cover the most common performance review tasks. Each one is designed to give Claude enough context to produce a first draft that is specific, balanced and ready to edit — not a generic template.
Key insight: The more specific context you give Claude, the better the output. Do not just say "good performer" — say what they did, how it performed against expectations and what the impact was. Claude turns your notes into language. You provide the substance.
Prompt 1 — Full performance review draft
Act as an experienced HR Business Partner. Draft a balanced, professional performance review for the following employee. Use specific, behaviour-based language throughout. Avoid generic phrases.
Employee name: [Name]
Role: [Job title]
Review period: [e.g. Q1 2026 / Annual 2025]
Overall rating: [e.g. Meets expectations / Exceeds expectations]
Key achievements this period:
[List 3–5 specific achievements with context]
Areas for development:
[List 1–3 development areas — be specific about the behaviour, not the person]
Goals for next period:
[List agreed goals]
Format: 3 sections — Achievements, Development Areas, Goals. 150–200 words per section. Professional tone. Suitable for UK / US employment context.
Prompt 2 — Constructive feedback on underperformance
Act as an HR Business Partner. Help me write a section of a performance review that addresses underperformance in a specific area. The language must be clear, factual and constructive — not personal or emotive.
Employee role: [Job title]
Area of underperformance: [Describe the specific behaviour or gap]
Impact of the underperformance: [What has it affected — team, clients, output?]
Previous support given: [What has already been provided — coaching, training, feedback?]
Expected standard: [What does good look like in this area?]
Write a 100–150 word paragraph suitable for inclusion in a formal performance review. Flag if any of this language should be reviewed by a legal or HR specialist before use.
Prompt 3 — Feedback conversation prep
Help me prepare for a performance review conversation with an employee. I want to deliver the feedback clearly, constructively and in a way that motivates them to improve.
Employee context: [Brief description of the employee, their role and tenure]
Main positive messages to deliver: [List 2–3 strengths]
Main development messages: [List 1–2 areas to address]
Any sensitivities to be aware of: [e.g. employee has been struggling, recent personal issues, etc.]
Produce: a suggested conversation structure with key talking points for each section, and 3 example phrases I can use to deliver the development feedback constructively.
Claude is a powerful drafting tool for performance reviews — but there are clear boundaries around how it should and should not be used in an HR context. Every HR professional using Claude for this work needs to know them.
Key insight: Claude drafts — you decide. The performance rating, the development decision and the conversation all require human judgement. Claude makes the documentation faster and clearer. It does not make the call.
Do this
Give Claude specific behaviours and examples — not just ratings
Edit every draft before it goes on record — Claude produces a starting point, not a final document
Use behaviour-based language: what the employee did, not who they are
Have your HR or legal team review underperformance language before it is used formally
Avoid this
Uploading employee names, personal data or salary details to Claude
Using Claude's output verbatim without reading and editing it first
Letting Claude make the performance rating decision — that stays with the manager
Using AI-generated language in a formal disciplinary or dismissal context without legal review
Vague feedback
"Sarah has a good attitude and generally meets expectations. She could improve her communication skills going forward."
Specific feedback
"Sarah consistently met her Q1 targets and proactively flagged two project risks before they escalated. Development focus for H2: structuring written updates for senior stakeholders — her verbal communication is strong but written summaries need more concision."
Important: Every performance review drafted with Claude must be read, edited and approved by the responsible manager before it is shared with the employee or placed on record. Claude is your drafting assistant — the accountability for the review remains entirely with you.