How to Write a Performance Review That Is Fair and Specific (2026): Evidence, Strengths, Growth Areas and Goals

Full disclosure: my team built a tool for this, so I'm biased. The method below works in a plain doc.

TL;DR

A fair review is built from specific evidence, not from the last month's impression. Collect examples all year, then write four parts.

• Strengths, each backed by an example.
• Growth areas, framed as what to do next.
• An overall assessment that matches the evidence.
• Goals for the next cycle that can be checked.

The review at a glance

Why this goes wrong

• Recency bias. The last few weeks dominate the memory.
• Vague praise and vague criticism. "Great attitude" and "needs to communicate more" give nothing to act on.
• Rating first, evidence later. The write-up gets bent to fit a number already in your head.
• Invented specifics. A made-up metric damages trust if the employee disagrees.

Step 1: Collect your notes

Gather wins, misses, feedback from others and examples across the whole period. Rough bullets are fine.

Step 2: Write strengths with evidence

For each strength, write what happened and what it changed. If you have no example, say the strength is an impression and look for one.

Step 3: Frame growth areas as next steps

Describe the behavior, the effect, and what better would look like. Avoid judging character.

Step 4: Write the overall assessment last

Check it against the evidence. If your lean rating doesn't match your notes, fix one or the other.

Step 5: Set goals that can be checked

Use a clear outcome and a time frame. Check your company's rules for rating scales and what must be included.

A made-up example

This example is invented for illustration.

Strength: Takes ownership of handoffs. In [project], wrote a handoff note that let the next team start without a meeting.

Growth area: Raise blockers earlier. On [project], a dependency issue surfaced a week after it started. Next cycle: flag blockers in the weekly update as soon as they appear.

Goal: Lead one cross-team project by [date].

What I'd do today

1. Open a doc and list every example you can recall, with dates.
2. Draft strengths and growth areas from the examples only.
3. Write the overall assessment after, and compare it with your rating.
4. Share a draft with HR or your manager if your process requires it.

FAQ

How long should a review be?
Long enough to cover the four parts with examples. Check your company's template.

What if I have no examples for a point?
Leave the point out or mark it as a gap to collect evidence on.

Should the review contain surprises?
Ideally not. Raise issues during the period, not first in the written review.

Can AI draft a review?
It can help with structure and wording, but you must verify the facts and keep private data in line with your company's policy.

Drafting faster with Performance Review Writer

If you'd like a first draft, my team built a chat agent called Performance Review Writer. It runs on Capafy, an AI agent marketplace.

What you send: rough notes on the employee's work, such as wins, misses, examples and a rating you are leaning toward.

What you get back, according to the listing:

• strengths backed by your examples,
• growth areas framed constructively,
• a clear overall assessment,
• next-cycle goals.

The listing says it works for annual reviews, quarterly check-ins and promotion write-ups, and that it doesn't invent an achievement or metric you didn't mention; gaps are flagged instead. You still own the final text, so read it and follow your company's policy on sharing employee data.

Pricing on the listing is $1.99/week or $5.99/month.

Wrap-up

• Write from evidence collected across the period.
• Frame growth areas as next steps.
• Write the assessment last and set goals that can be checked.

Disclosure: my team built Performance Review Writer and sells it on Capafy.