Performance Review Prompt

What it does

Writes a performance review narrative that's grounded in specific behaviors and outcomes, not vague impressions. The output balances recognition of what the employee does well with clear, direct feedback on what needs to improve — in language that's professional, behavior-focused, and usable in a formal review document.

undefined

How to use it

The specific examples in your input are what make the review useful. "Great communicator" helps no one. "Consistently delivered clear meeting recaps that helped the team align on decisions faster — particularly valuable during the Q2 product launch" tells the employee exactly what to keep doing.

For development areas, use behavior-specific language: "tends to miss deadlines when managing multiple priorities without checking in" is actionable. "Needs to improve time management" is not.

Example output

Exceeds expectations:

"[Role] consistently delivered work that exceeded scope requirements this year. The standout example was the [project name] initiative, where they independently identified a process gap that was causing 3–4 hours of rework per week across the team, designed a solution, and implemented it before it was formally prioritized. The result was adopted immediately and is now a standard part of the team's workflow.

Communication quality is consistently strong — written updates are clear, well-structured, and distributed proactively rather than on request. Three times this quarter, their pre-meeting summaries prevented decisions from being made on incomplete information.

Development focus for the next period: [Role] should begin taking on cross-functional coordination responsibilities. The next growth lever is building influence outside the immediate team — specifically in how they present work to senior stakeholders where context and framing matter as much as content quality."

Variations

Self-review (employee writing their own): Add "This is a self-assessment the employee writes before the formal review. Write in first person. The tone should be confident and specific without overselling."

360 feedback input: Add "This is a 360 feedback comment from a peer, not a manager. The tone should be collegial and specific — focused on behaviors observed, not ratings or scores."

Underperformance / PIP support: Add "This review will accompany a Performance Improvement Plan. The language needs to be precise, behavior-focused, and legally defensible. No emotional language."

Common pitfalls

Halo effect. If the employee's overall performance is strong, reviewers tend to underrate their development areas. Make sure the growth section is specific even when the overall review is positive.

Recency bias. Performance reviews that only reflect the last 2 months miss 10 months of behavior. If you don't have notes from the full period, this is a reminder to keep a running document.

Vague development goals. "Improve communication skills" is not a goal. "Send a meeting summary within 2 hours for every project meeting attended" is a goal.

Who uses this prompt

Managers preparing annual or quarterly performance reviews. HR managers who write or edit reviews for multiple employees. Small business owners doing their first formal review cycle. Team leads writing peer feedback for 360 programs.