Claude Prompt Templates for Performance Reviews

Research on performance management consistently shows that vague feedback -- the kind that fills most performance reviews -- is nearly as demotivating as no feedback at all. Employees who receive reviews with specific observations and concrete development paths retain at higher rates and improve faster than those who get competency-checkbox scores without contextual evidence. But most managers writing reviews have six to twelve direct reports, a two-week window, and limited writing bandwidth. The result is reviews that are legally compliant but developmentally useless.

A claude prompt template for performance reviews is valuable specifically because it can produce specific, evidence-based language quickly -- but only if the prompts are built around real observations, not generic competency scores.

What Makes a Good Performance Review Prompt?

The single most important input for any performance review prompt is specific behavioral observations -- what the person actually did, not what trait they have. "Strong communicator" is an assessment. "During the Q3 replatforming project, raised a cross-team dependency issue six weeks before it would have become a blocker, preventing a likely three-week delay" is an observation. The second is the one that holds up in a conversation, motivates improvement, and protects against legal challenge if a review is ever disputed.

Claude prompts for performance reviews work when they force that specificity from the inputs before drafting anything.

Manager Review Template

Write a performance review section for [employee name, role].

Review period: [dates]
Rating area: [competency being reviewed -- e.g., "Communication," "Technical Delivery," "Collaboration"]

My specific observations (these are what you MUST base the review on -- do not add observations I haven't given you):
- [Observation 1 -- specific behavior or outcome]
- [Observation 2]
- [Observation 3, if available]

Rating I've assigned: [your company's rating scale and where this person falls]

Write: 3-4 sentences that connect my specific observations to the rating, explain what the observations demonstrate about this person's performance in this area, and -- if not at the highest rating -- name one specific behavior that would move them to the next level.

Tone: direct and respectful, not corporate filler. No "meets expectations" language without evidence.

What this does: The instruction to base the review only on observations provided prevents the common failure mode where AI-generated review language sounds plausible but isn't actually accurate to the individual -- which is a legal and trust problem if challenged.

⚡ Pro tip: Before running this prompt, spend five minutes writing raw observation notes with no structure -- just everything you actually remember about this person's work in the review period. Even rough, unpolished observations produce dramatically better review language than starting with a trait rating and trying to reverse-engineer examples.

Why It Matters for Organizations

The business case for specific performance reviews is actually stronger than most HR teams communicate internally. Beyond retention, review quality correlates with improvement rate: employees who understand specifically what's working and exactly what to change develop faster than those who receive general ratings. And for managers of large teams, the time investment in quality reviews is real -- a tool that reduces the time to produce specific, useful review language means managers spend less time on review writing and more time on the conversations that reviews are supposed to prepare them for.

Self-Review Template

Help me write my self-review section for [competency area].

Review period: [dates]
Specific things I did this period that demonstrate this competency (even rough notes are fine): [paste notes]
Challenges or failures this period that I want to be honest about: [describe]
What I want to develop in the next period: [be specific]

Write a self-review section (150-200 words) that:
- Opens with the most significant contribution I made in this area
- Acknowledges one area where I fell short with one sentence of context (not excuse)
- Closes with a specific development goal for the next period that's realistic and measurable

Avoid: excessive self-promotion, excessive self-criticism, vague statements like "I hope to continue growing"

What this does: Asking for a specific, measurable development goal rather than a vague aspiration is what makes self-reviews useful to managers rather than performative -- "increase code review throughput to under 24-hour turnaround by Q2" is actionable; "improve in the technical area" is not.

⚠️ Common mistake: Using AI-generated review language for rating justifications without checking that the language accurately reflects the actual rating decision and the actual observations. Reviews that sound specific but don't match what the manager actually observed or the actual rating assigned create confusion in feedback conversations and can backfire if an employee escalates.

Three Real Scenarios

A people manager with eleven direct reports used the observation-first template to systematize her review writing process: for two weeks before review season, she kept a simple running document of behavioral observations for each report. The template then turned those rough observations into polished review language in about fifteen minutes per report -- compared to her previous forty-five-minute average.

An IC using the self-review template specifically chose to address a challenge section that most self-reviews soft-pedal: a project that had slipped due partly to their own estimation errors. Addressing it specifically -- what happened, what they'd do differently, what they'd already changed in their process -- was better received by their manager than the manager expected, precisely because it was genuine rather than the typical self-review optimism.

A startup going through its first formal review cycle used the template to bring consistency across eleven managers who'd never run formal reviews before -- each using the same observation-first structure meant the final reviews were comparable across teams, which made calibration conversations significantly easier.

Common Mistakes

⚠️ Writing the review then asking Claude to "make it sound less harsh" or "soften this." The goal of a performance review isn't softened language -- it's accurate, specific, and constructive language. Softening accurate specific feedback produces the vague reviews that cause the retention and development problems described above. If feedback feels harsh, the issue is usually in how it's framed (specific behavior vs. character judgment) not in its softness.

A Development Conversation Prep Prompt

The review document is preparation for a conversation, not a replacement for one. A prompt that helps structure that conversation is often as valuable as the review itself:

I have a performance review conversation with [employee, role] next week. Their review covers [brief summary]. The most important development point I need to discuss is: [specific behavior or gap].

Help me plan this conversation:
1. How do I open it in a way that's direct without being defensive-triggering?
2. What specific example should I use to ground the development feedback? (I'll provide the observation, you help me frame it)
3. What question should I ask them to get their perspective, rather than just delivering feedback at them?
4. How do I close with a concrete development commitment -- not vague "let's work on this" but a specific agreed action?

Don't write a script -- give me a conversation structure I can adapt in the moment.

What this does: Structuring the conversation rather than scripting it preserves the genuine responsiveness that makes performance conversations useful -- a scripted delivery tends to feel like an HR process the manager is getting through, not a conversation they're actually having. The structure gives direction; the adaptation keeps it real.

Conclusion

A claude prompt template for performance reviews that's built around specific behavioral observations produces reviews that are more useful, more defensible, and more likely to drive the development they're supposed to support. Once you've built the observation-gathering habit alongside the prompt structure, the combination is genuinely faster than writing reviews from a blank page -- making it a tool worth refining and storing in PromptABCD across review cycles.

The development conversation prep prompt is worth running before every significant review conversation, not just the difficult ones. Even for strong performers, the conversation structure -- specific opening, concrete example, their perspective, closing commitment -- produces more useful 30-minute conversations than an unstructured "you're doing great, keep it up" discussion that leaves no actionable direction for the next review period. The highest-performing employees often have the least specific development conversations because managers assume positive reviews don't need the same care. That assumption is what causes high-performers to eventually leave because they felt they had nowhere to grow -- a retention problem that shows up in exit interviews but rarely gets traced back to the quality of development conversations that happened twelve or eighteen months earlier.