Performance Review Writer

A balanced, evidence-based performance review that gives employees clear feedback and actionable growth goals.

Best For

•A manager tracking goals against a formal rubric uses it to assess each stated goal as Met, Exceeded, or Missed with a specific example, instead of writing a vague narrative
•An HR team standardizing review quality across managers uses this structure to ensure every review includes evidence-backed strengths and SMART goals for the next period
•A manager who received mixed peer feedback on a report uses it to synthesize those themes into constructive, specific development areas rather than repeating hearsay

Prompt Template

Write a structured performance review for [EMPLOYEE_NAME], [EMPLOYEE_TITLE], covering the review period [START_DATE] to [END_DATE]. Use the following inputs: their stated goals for the period: [GOALS_LIST], notable accomplishments: [ACCOMPLISHMENTS], areas where they fell short: [GAPS], and peer feedback themes: [PEER_FEEDBACK]. Structure the review as: (1) Overall performance summary (3–4 sentences, lead with strengths), (2) Goal-by-goal assessment, for each goal state whether it was Met, Exceeded, or Missed and provide one specific example, (3) Strengths, 2–3 specific, evidence-backed strengths (no vague praise), (4) Development areas, 2 areas for growth framed constructively with a suggested action for each, (5) Goals for next review period, 3 SMART goals. Use direct, professional language. Avoid filler phrases like "rockstar" or "goes above and beyond." Keep the total under 600 words.

Pro Tip

Feed in the peer feedback as direct quotes or paraphrased themes rather than a single-word summary, since the prompt is built to turn scattered peer input into specific, attributable strengths and gaps.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

Goal-by-goal assessment: Reduce average ticket resolution time to under 4 hours - Exceeded, achieved 3.2 hours by Q2 through a new triage process the employee proposed. Strengths: consistently documents edge cases so the next person doesn't repeat the investigation, based on peer feedback from two teammates. Development area: delegating lower-priority tickets during high-volume weeks, suggested action: set a personal WIP limit of 5 open tickets.