Write Balanced Performance Review Comments from Your Manager Notes

Turns your rough manager notes into fair review comments where every point cites a behavior and its impact, and each gap gets one measurable next step.

You getSummary, strengths and development areas

Prompt

Prompt
You are an experienced HR business partner who coaches managers on writing fair, evidence-based performance reviews.

Job: Turn the manager notes I paste right after this prompt into balanced review comments for one employee. If the notes do not state the review period, the employee's role, or the rating scale, ask me those in one numbered message and wait before writing.

Rules:
1. Every point names a specific behavior (what the person did, when or where) and its impact on the team, customers or results. Drop notes that have neither.
2. Pair each development gap with exactly one next step that is measurable and has a time frame.
3. Remove personality judgments and labels (lazy, abrasive, great attitude). Rewrite them as observable behavior or flag them as unsupported.
4. Keep strengths and gaps roughly balanced. Do not invent achievements, numbers or examples that are not in my notes.
5. Use plain, neutral language without softening phrases that blur the message.

Output format:
- Summary (2-3 sentences)
- Strengths (3-5 bullets, each: behavior, then impact)
- Development areas (table: Behavior | Impact | Next step | Measure | By when)
- Removed or reworded notes (list with reason)
- Questions to verify before submitting

End with one line on what evidence is missing or which points an employee could reasonably dispute.

Example output

At a glancePriya's review: key evidence citedBehavior-based figures from the January-June review
CSAT on outage escalations
4.6
vs 4.2 team average, 41 tickets in 3 days
Monthly repeat API tickets
30 to 18
after rewriting 12 knowledge base articles
Audited tickets with one-line notes
9 of 20
next step: 4-field checklist by end of Q3
P3 first response average
31 hours
SLA is 24 hours; target by end of Q4

Example for: a support team lead reviewing Priya, a Tier 2 support specialist, for January-June, on a 1-5 rating scale.

Summary

Priya resolved complex escalations reliably and improved the team's knowledge base during the period. Her main gaps are ticket documentation and response time on low-priority queues. Both have clear, measurable next steps for the second half of the year.

Strengths

  • Owned the March billing outage escalations (41 tickets in 3 days) and wrote the customer reply template the team reused; CSAT on those tickets held at 4.6 versus a 4.2 team average.
  • Rewrote 12 knowledge base articles on API errors in April; repeat tickets on those topics fell from about 30 to 18 per month.
  • Ran two onboarding shadow sessions for new hire Marco in May; Marco closed his first Tier 2 ticket unaided in week 3 instead of the usual week 5.
  • Flagged a recurring login bug to engineering with reproduction steps, which led to a fix shipped in June.

Development areas

BehaviorImpactNext stepMeasureBy when
Closed tickets with one-line internal notes on 9 of 20 audited casesColleagues reopening tickets had to re-ask customers for detailsUse the 4-field internal note checklist on every closed ticket90% of monthly audit sample meets checklistEnd of Q3
First response on P3 queue averaged 31 hoursSLA is 24 hours; 3 customer complaints cited delaysBlock 45 minutes each morning for P3 triageP3 first response under 24 hours for 8 consecutive weeksEnd of Q4

Removed or reworded notes

  • "Can be a bit dismissive in standups" - personality label with no example. Removed; add a dated example if you want to keep it.
  • "Great attitude, always positive" - reworded into the onboarding and escalation behaviors above.
  • "Probably burned out" - speculation about health. Removed; raise wellbeing in a private 1:1, not the review.

Questions to verify before submitting

  1. Is the 4.6 CSAT figure from the outage tickets only, or the whole month?
  2. Did Priya know about the 4-field note checklist before the audit?
  3. Were P3 delays affected by her time on outage escalations in March?

Missing evidence: the P3 response gap may be disputed if her escalation workload was not adjusted; check queue assignments for March before finalizing.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Requiring behavior plus impact for every point turns vague impressions into evidence an employee can understand and act on.
  • One measurable next step with a deadline per gap makes the review a plan, not just a judgment.
  • A separate list of removed labels shows the manager what was cut and why, reducing bias and dispute risk.

Use before writing a mid-year or annual review. Paste your raw notes, examples and any metrics into ChatGPT, Claude or Gemini right after the prompt. Remove full names or ID numbers first if your company requires it.

Common edits

  • Ask for a shorter version that fits a 1,000-character field in your HR system.
  • Add a line asking for a suggested rating on your scale with a one-sentence justification.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in HR & Management