Claude for HR: Preparing a Performance Review Conversation
6 min read
The hard part of a performance conversation is rarely the delivery. It is the preparation: a year of scattered impressions, three emails, a half-remembered project and a feeling that someone is "not quite there." Walk into the room with that and the feedback comes out vague, or colored by whatever happened last month. The employee leaves unsure what to do differently.
Claude is useful in the preparation step, as a partner that asks for evidence and notices when your language is vague. It is not useful as the judge. This article shows how to use it for the first and keep it out of the second. For the basics of working with Claude, start with the Complete Beginner's Guide to Claude.
Before anything else: what not to paste
Review material is personal and often sensitive. Before you put any of it into an assistant, decide what to leave out.
- Replace the employee's name with a role or an initial.
- Leave out health, family and other personal information, and anything legally protected.
- Follow your organization's rules about AI tools and personnel data. If you are unsure, ask HR before you paste.
- Check your privacy settings. Claude Privacy Settings: A Real Walkthrough covers the controls, including incognito chats.
Claude prepares, you decide
Ratings, pay and promotion decisions are yours, made under your company's process and the law. Use Claude to organize your own evidence and to improve how you say things, not to make or justify the decision.
Step one: turn impressions into evidence
Start by dumping what you have, in any order: notes, dates, outcomes, quotes from feedback you were given. Then ask Claude to sort it.
Below are my raw notes about one team member over the last twelve months. Sort them into three groups: things that are specific and observable (what happened, when, with what result), things that are impressions or opinions, and things that are missing details. For each impression, tell me what example I would need to back it up. Do not add anything that is not in my notes.
”The "do not add anything" line matters. An assistant will happily invent a plausible example. You want a list of gaps, not filled ones.
Step two: use the behavior, impact, request pattern
Useful feedback names a behavior, its effect and what you want next. It does not label the person.
| Vague or loaded | Specific |
|---|---|
| "Not a team player" | "In the March release, you did not share the test results with QA until the day before launch, so QA had one day instead of five." |
| "Great attitude" | "When the vendor changed scope in June, you rebuilt the plan in two days and told the team what changed and why." |
| "Needs to communicate better" | "I would like status updates on Friday by noon, even when nothing has changed." |
Ask Claude to do this conversion with you:
Rewrite each of the following statements as behavior, impact and request. If a statement has no example behind it, do not invent one. Instead, ask me one question that would get the missing detail.
”Step three: check the language for bias
Review language drifts in predictable ways. Different standards creep in for different people, and loaded words stand in for evidence. A second read helps.
Read this draft review as a neutral third party. List any word or phrase that is vague, personality-based or likely to mean different things to different readers, such as "abrasive," "emotional," "not a fit," or "lacks presence." For each, suggest a replacement that describes an observable behavior. Then tell me whether the strengths and the development areas are backed with a similar level of detail.
”The last question is quietly powerful. If the strengths are one line each and the criticisms have three examples, the review is lopsided whether or not you meant it to be.
Tip
Ask the same question in reverse: "If this feedback were about someone else on my team with the same results, would I have written it differently?" Claude cannot answer for you, but you can.
Step four: plan the conversation, not just the document
A review document is not the conversation. Ask Claude to help you plan the second.
- 1
Open with the purpose and the structure
"I want to cover what went well, one or two areas to grow, and what support you need." Two sentences, so nobody spends the first ten minutes guessing.
- 2
Lead with specific strengths
Specific praise is believable. Generic praise followed by "but" is not.
- 3
Name a small number of development areas
One or two, each with the behavior, the impact and the request. A long list feels like a verdict.
- 4
Prepare three questions that invite their view
"What got in the way on that project?" "What do you want to be doing more of next year?" The conversation should have more than one voice.
- 5
Close with agreed next steps and a date
Write them down together. A vague ending undoes a good conversation.
Rehearse the hard part
If one point worries you, rehearse it. Describe the situation and ask Claude to play the employee who disagrees.
Play a team member who is surprised by this feedback and pushes back with "no one ever told me this before." I will give the feedback and you respond the way a real person might. After each exchange, give me one note on what helped and what did not. Keep your replies short.
”Do this once, then put it away. Rehearsal helps you find the sentence you are afraid to say. It does not predict the person in front of you, who will not read the script.
A short checklist before you walk in
Every point has a specific example I could explain out loud.
Strengths and development areas have a comparable level of detail.
I removed labels about the person and described behaviors instead.
I know what I am asking for, and what support I can offer.
The decision about the rating is mine and follows our process.
Other assistants can help with similar HR tasks, with different strengths: ChatGPT for HR: Writing Job Descriptions That Attract the Right People and Copilot for HR: Job Descriptions and Screening Notes cover the hiring side.
Official sources
- Prompting best practices | Claude Developer Docs
- Is my data used for model training? | Claude Privacy Center
Checked on October 24, 2026. This is a preparation method, not legal or HR advice; follow your organization's policies. Features, plans and names change often, so the vendor's own pages are the final word.