Evidence-Based Performance Review Writer
Added Sep 29, 2026
About This Prompt
This prompt turns a manager's notes into a fair, specific performance review. It ties every strength and growth area to evidence from the review period, frames development feedback as observable behavior rather than personality, and sets measurable goals for the next cycle. The built-in bias check flags vague language, recency bias and unsupported claims, which are the most common ways reviews go wrong, and suggests a rewrite for each. It will not invent accomplishments the notes do not contain. Ideal for managers writing reviews, and for HR teams who want more consistent, defensible reviews across the company.
Variables to Customize
[EMPLOYEE_ROLE]
The employee's role and level (leave their name out)
Example: Senior Backend Engineer, Payments team
[REVIEW_PERIOD]
The period the review covers
Example: January to June 2026
[EVIDENCE]
Your notes, accomplishments, metrics and feedback from the period
Example: Led the migration of card processing to a new provider with zero downtime; cut p95 checkout latency from 900ms to 450ms; mentored two junior engineers through their first on-call rotations; missed the Q2 fraud-rules deadline by three weeks after underestimating the vendor API work
[GROWTH_AREAS]
Where they need to develop
Example: Estimating work that depends on outside teams; writing a design doc before starting large changes
[RATING_SCALE]
The rating scale your company uses
Example: 1 Below expectations, 2 Partially meets, 3 Meets, 4 Exceeds, 5 Exceptional
Tips for Best Results
- Keep a running log of specific examples during the period; reviews written from memory in the final week drift toward whatever happened most recently
- Leave the employee's name and personal details out of the prompt and add them when you finalize the review
- Treat the draft as a starting point: read every sentence as the employee will, and cut anything you could not back up in the conversation
Example Output
**Performance Review: Senior Backend Engineer, Payments — January to June 2026** **Summary** A strong half anchored by a zero-downtime migration of card processing and a halving of checkout latency. The main development area is estimating work that depends on other teams, which contributed to a three-week slip on the fraud-rules project. **Strengths** - *Delivering high-risk changes safely.* Led the card-processing migration with zero downtime, sequencing the cutover to protect checkout during peak hours... **Bias check** - "Is a natural leader" (Strengths, paragraph 3) describes a trait, not evidence. Suggested rewrite: "Mentored two junior engineers through their first on-call rotations." - The estimation concern rests on a single project; note that one example is thin evidence for a pattern...
Quick Info
- Tool
- ChatGPT
- Category
- Business
- Difficulty
- intermediate
- Variables
- 5
- Type
- text