Prompting Guide
How to Prompt Claude to Write a Performance Review
The hard part isn't the writing. It's remembering six months of specifics.
Anthropic's Claude is good at turning a list of half-remembered accomplishments into a review that reads like it was written by someone who was paying close attention all year. It is not good at knowing what actually happened on your team unless you tell it, which is why a one-line prompt like "write a performance review for my report" tends to come back generic enough to apply to almost anyone. The fix is giving Claude the same material a thoughtful manager would use anyway: concrete examples, the goals that were set, and a clear instruction to balance strengths with areas to grow, then checking the draft against your own memory of the year before it goes anywhere near HR.
To prompt Claude to write a performance review, give it the employee's role and the review period, a list of specific accomplishments and examples (not vague impressions), the goals that were set at the start of the period, and an instruction to cover strengths, growth areas, and next-period goals in a balanced, specific tone. Never paste confidential details like full names, salary, or HR system data unless your company's AI policy explicitly allows it; describe the person by role instead and add identifying details yourself afterward.
Published
Free lesson · no account neededMeet ClaudeWhy Claude?6 minStart the free lessonKey Takeaways
- Specific examples beat vague praise. "Led the migration project two weeks ahead of schedule" is useful; "did a great job this year" is not, and Claude can only write what you give it.
- Balance strengths with growth areas on purpose. A prompt that only asks for the good stuff produces a review that reads as dishonest the moment a reader compares it to the employee's actual year.
- Never paste names, salary, performance ratings, or other confidential HR data into Claude unless your company's AI policy explicitly allows it. Describe the person by role and add identifying details yourself afterward.
- Give Claude the goals that were set at the start of the period, not just what happened. A review that doesn't measure the year against its own stated goals reads as unmoored from what was actually expected.
- Read the draft against your own memory of the year before it goes anywhere near HR or the employee. A review is a document people remember; a wrong detail in it causes more damage than a late one.
Copy and Paste
Prompts You Can Use Today
A full annual review from your own notes
Write a performance review for a [job title] covering the past year. Here are the specific things they worked on and accomplished: [list your notes, examples, and any numbers you have]. Here were the goals set for them at the start of the year: [list goals]. Structure the review as a summary, three to five specific strengths with examples, two areas to grow with concrete suggestions, and goals for next period. Keep the tone direct and specific, not generic praise.
Describe the person by role, not by name, and keep anything confidential out of the prompt itself.
Turning rough notes into specific examples
Here are some rough notes I jotted down over the year about one of my reports: [paste your notes]. Turn these into three to five specific, concrete examples I could use in a performance review, written the way you'd describe an accomplishment to someone who wasn't there and needs the context to understand why it mattered.
Useful when your notes are fragments rather than full sentences; Claude can expand them without inventing details you didn't give it.
Checking a draft review for vague praise
Read this draft performance review and flag every sentence that is vague praise rather than a specific, checkable example: [paste your draft]. For each one you flag, suggest what kind of specific detail would make it concrete, without inventing an example yourself.
Run this on your own first draft, or on one Claude wrote, before it goes to the employee.
A self-review from your own accomplishments
Help me write my own self-review for the past year. Here's what I worked on and accomplished, in no particular order: [list your work]. Organize it into the categories my company's review form actually asks for: [list your form's sections, e.g. impact, collaboration, growth]. Keep my own voice; don't make it sound more corporate than I actually talk.
Paste your company's actual review form sections so the structure matches what you'll submit, not a generic template.
Softening harsh feedback without losing the substance
Here is blunt, unfiltered feedback I want to give about one area this person needs to grow: [paste your blunt notes]. Rewrite it so it's direct and still names the specific problem clearly, but lands as constructive rather than harsh, the way you'd want to hear it said to you.
Use this for the growth-areas section specifically; keep the strengths section in your own more generous voice.
The Structure
What a performance review prompt needs that a one-liner doesn't give it
The same four things separate a usable review from a generic one, no matter how the company's own form is formatted.
Role and period, stated plainly
Say what the person's job is and what time period the review covers. Without this, Claude has no way to judge whether an accomplishment was a big deal for the role or an ordinary part of the job.
Specific examples, not impressions
"Did good work on the redesign" and "shipped the redesign two weeks ahead of schedule after the original lead left mid-project" point Claude at completely different reviews. Give it the second kind.
The goals that were actually set
A review that doesn't reference the goals from the start of the period reads as disconnected from what the person was actually asked to do. Paste those goals in, even informally.
An explicit instruction to balance the picture
Ask directly for strengths and growth areas in the same review, with the growth areas framed as specific and actionable rather than as a formality tacked on at the end.
Before You Paste Anything In
What never goes into the prompt
Before any of the prompt structure matters, there is a line that comes first: don't paste an employee's full name, salary, performance rating history, medical information, or anything pulled directly from your HR system into Claude unless your company's AI policy explicitly says that kind of data is allowed there. This isn't a Claude-specific rule; it's the same rule that applies to pasting that information into any tool your company hasn't cleared for it, and a performance review is exactly the kind of document that tends to contain it without anyone pausing to notice.
In practice, this means describing the person by role in your prompt ("a mid-level backend engineer," not a name) and adding any identifying details yourself after you've got a draft back, not before. If your company has explicitly approved an AI tool for this kind of HR work through a sanctioned process, that changes the calculation, but the default assumption should be that a performance review contains data you shouldn't be typing into any general-purpose AI chat.
This is also the point to flag if you're not sure what your company's policy actually allows. A quick question to your manager or HR partner before you start drafting costs you two minutes; finding out afterward that confidential data went somewhere it shouldn't have costs considerably more, and it's not a mistake you can quietly undo.
Common Mistakes
What turns a review into something nobody trusts
These are the patterns that make a review feel written about a stranger rather than about the actual person.
Generic praise with no example attached
"Strong communicator" or "great team player" with nothing underneath it reads as filler the moment the employee notices it could describe anyone on the team. Every strength needs a specific moment behind it.
Growth areas with no path forward
Naming a weakness without a concrete suggestion for improving it reads as criticism without help attached. Ask Claude to pair every growth area with an actionable next step.
A tone that doesn't match how you actually talk
If the draft sounds nothing like you, the employee will notice, and it can read as impersonal at exactly the moment a review should feel like it came from someone who knows their work.
Treating the first draft as the final one
A first draft condenses whatever you gave it, which means something may be missing or overstated. Read it against your own memory of the person's year before it goes to them or to HR.
Keeping It Fair
Why specific examples protect you as much as the employee
A review built on specific, checkable examples is easier to defend later if anyone ever asks why a rating was what it was, and it's also simply fairer to the person being reviewed, who worked on real, specific things all year and deserves a document that reflects that instead of a template with their name swapped in. Asking Claude for examples with dates, numbers, or outcomes attached, rather than general impressions, produces a review that would hold up if someone else read it cold.
This matters more than it might seem for the growth-areas section specifically. A vague criticism like "needs to improve communication" is nearly impossible for an employee to act on, and it's also the part of a review most likely to feel unfair if it isn't backed by something concrete. Ask for a specific instance and a specific suggestion every time, and push back on the draft if either one comes back generic.
If you're reviewing someone whose year included a rough patch, a layoff on the team, a reorg, or anything else outside their control, say so in the prompt. Claude can account for context you give it; it can't account for context it was never told, and a review that doesn't acknowledge a genuinely hard year can land as out of touch even when every sentence in it is technically accurate.
Before It Goes Out
What to check before you send it
Read every strength and growth area against your own memory of the actual year, not just against whether the sentence sounds reasonable on its own. A confident-sounding example that didn't quite happen the way it's described is worse than an honest gap, because it damages trust the moment the employee reads something about themselves that isn't accurate.
Check that the growth areas are things you'd actually be comfortable saying to this person directly, in the same room. If a line reads harsher on the page than you intend it to land in conversation, that's the sentence to rewrite before it goes out, not after someone's upset by it.
These prompts are a starting structure, not a substitute for your own judgment about a document that follows someone through their career; the writing is the easy part, and the judgment about what belongs in it is still yours.
Writing the review is the easy part
The harder skill is knowing what belongs in it and what should never touch an AI chat in the first place. Nightschool AI's free lessons walk through real workplace writing tasks with Claude, including the judgment calls around sensitive material.
Frequently Asked Questions
Is it safe to paste an employee's name and details into Claude for a performance review?
Not by default. Don't paste a full name, salary, rating history, or anything from your HR system into Claude unless your company's AI policy explicitly allows it. Describe the person by role instead, and add identifying details yourself after you have a draft.
What should I give Claude so the review doesn't come out generic?
Specific, concrete examples with dates, numbers, or outcomes attached, plus the goals that were set for the person at the start of the review period. Vague impressions produce a vague review; specific input produces a specific one.
How do I make sure the review doesn't come out one-sided?
Ask directly for strengths and growth areas in the same prompt, and ask for every growth area to come with a concrete, actionable suggestion rather than just a criticism. A review that only lists good things reads as dishonest the moment it's compared to the actual year.
Can Claude help me write my own self-review?
Yes. List what you worked on over the period, paste in the actual sections your company's review form asks for, and ask Claude to organize your accomplishments into that structure while keeping your own voice rather than making it sound overly formal.
Should I send the review Claude writes without reading it first?
No. Read every example against your own memory of the person's actual year, and check that any growth-area feedback is something you'd be comfortable saying to them directly. A first draft is a starting point, not a document to send unread.
What if the person I'm reviewing had a genuinely difficult year outside their control?
Say so in the prompt. Mention a layoff, reorg, or other disruption explicitly so Claude can account for it. A review that doesn't acknowledge real context can read as out of touch even when the individual sentences are accurate.
How specific should the growth-areas section be?
Specific enough that the person could act on it this quarter. "Needs to improve communication" helps no one; a specific instance plus a concrete suggestion for what to do differently gives them something to actually work on.
Can I use this same prompt structure for a mid-year check-in instead of an annual review?
Yes. Just shorten the review period and the list of examples accordingly. The same four parts, specific examples, stated goals, and a balance of strengths and growth areas, apply at any check-in cadence.
A fair review starts with specific input
The prompt structure is reusable every cycle. Knowing what to keep out of it is the part worth getting right once.