HR
Performance Review Writer
Staring at a blank performance review is one of the least enjoyable parts of management. Describe your employee's year and get a structured, professional review — specific, fair, and ready to deliver.
AI-generated output
Fill in the employee details above and click Write to get your performance review.
How it works
Enter the employee's name, role, and the review period. Then describe their key achievements and any areas where they need to develop — bullet points work perfectly here, no need to write prose.
Select the overall performance rating that reflects your assessment. The AI will write a review that is consistent with that rating — neither inflating mediocre performance nor understating strong performance.
You get a complete performance review with an opening summary, a strengths section, a development areas section, and forward-looking goals — all in professional language ready to deliver or submit to HR.
Practical example
For example, a mid-level software engineer who shipped three major features but struggled with estimation accuracy might get a review that opens with a specific, outcome-focused summary of their impact, acknowledges the estimation issue honestly without blame language ("this is an area to develop" rather than "repeatedly failed to"), and closes with specific development goals for the next cycle.
The review avoids the common pitfall of vague language ("good team player", "needs to improve communication") and replaces it with specific examples and observable behaviours.
Frequently asked questions
What makes a performance review legally defensible?
Specificity and consistency. Reviews that rely on vague observations ("attitude problem", "doesn't fit the culture") are both less useful and legally riskier than reviews grounded in specific, observable behaviours. Document what happened, when, and the business impact — not your interpretation of character. Consistent application of standards across comparable employees also matters: if one employee is rated differently for the same behaviour as another, that inconsistency can become a liability.
How do I write about performance issues without causing a grievance?
Focus on behaviour and impact, not personality. "The documentation delivered for the Q3 release was incomplete, requiring two rounds of revision and delaying the QA team by 3 days" is factual and specific. "You are disorganised" is a character judgement. The former is appropriate to write; the latter is not. Managers often avoid documenting performance issues to be kind — but an accurate, professional record protects both the employee and the company.
Should I share the review with the employee before the meeting?
Best practice is to share the written review 24–48 hours before the review meeting — so the employee can read it without reacting in front of you, and so the meeting can focus on discussion rather than just information delivery. Ambush reviews (where the employee reads the review for the first time in the meeting) create defensiveness and undermine the development conversation.
How specific should development goals be?
As specific as possible. "Improve stakeholder communication" is a direction, not a goal. "By Q2, deliver monthly written updates to the two senior stakeholders on the platform project, in the agreed format, with no requests for follow-up clarification" is a goal. Good development goals include what success looks like, how it will be measured, and when it is expected — so there is no ambiguity at the next review.
Thingy Tools