How to Write a Performance Review (With Examples)

A performance review's most common failure isn't harshness or excessive praise — it's vagueness. "Doing great, keep it up" and "needs to be more proactive" are both nearly useless to the person receiving them, because neither is anchored to anything specific enough to act on.

The fix isn't a longer review. It's a more evidenced one.

The structure that actually helps

Start with specific accomplishments, not general praise. "Consistently hit every deadline this quarter" is weaker than "led the Morrison account transition with zero disruption, including catching a scheduling conflict two weeks out that would have cost us the relationship." Specificity is what makes praise feel earned rather than performative.

Tie each point to an expectation that was set in advance. A review is much stronger when it references a goal or standard the employee already knew about, rather than introducing a new expectation for the first time inside the review itself.

Address growth areas with the same specificity as strengths. "Could improve communication" tells someone nothing actionable. "Status updates on the Chen project came in after the deadline three times this quarter, which left the team without visibility going into client calls" describes exactly what happened and implies exactly what needs to change.

End with forward-looking, specific goals. Not "continue doing great work," but two or three concrete things to focus on before the next review, ideally something the employee had input into rather than something purely handed down.

Phrasing that replaces vague language

Instead of "great communicator," try: "Consistently flags risks to the team before they become problems, which came up specifically during the Q2 rollout."

Instead of "needs to be more of a team player," try: "Hasn't yet volunteered to help teammates during crunch periods, even when their own workload has room — worth discussing what's getting in the way of that."

Instead of "has a great attitude," try: "Volunteered to take on the onboarding documentation nobody else wanted, without being asked, which made the next two hires noticeably smoother."

Instead of "struggles with deadlines," try: "Missed the stated deadline on four of the last six deliverables, most recently by two days on the client report due August 14th."

The pattern in each: name the specific behavior, with an example, rather than the trait it implies.

Why nothing in the review should be a surprise

If a regular cadence of 1:1s is already happening — weekly or biweekly — very little in an annual review should be genuinely new information. A performance issue raised for the first time in an annual review, months after it started, isn't really being addressed — it's being filed. The review works best as a summary and a formal record of things that were already being discussed as they happened, not as the only moment feedback gets delivered all year.

Handling a review for someone who's struggling

The mechanics don't change — specific evidence, tied to expectations, forward-looking goals — but the stakes of getting the specificity right are higher. A vague, softened review for someone genuinely underperforming does them a disservice twice over: it doesn't give them what they'd need to actually improve, and if the situation eventually leads to a termination, a history of overly generous reviews directly undermines the documentation trail that termination would need to be defensible.

If a review is arriving for a struggling employee and it's the first real documentation of the issue, that's worth naming honestly as a gap in how the situation was managed up to that point — not something to paper over by making the review vaguer to avoid an uncomfortable conversation.

Self-assessments

Having the employee write a brief self-assessment before the review conversation — what they're proud of, where they think they fell short — surfaces genuinely useful information, particularly where it diverges from the manager's own view. A large gap between how someone rates their own performance and how their manager sees it is itself worth discussing directly, since it often points to a mismatch in expectations rather than a performance problem.

A simple structure to reuse

Key accomplishments this period: [2–4 specific examples]

Areas for growth: [1–3 specific examples, with evidence]

Progress against previous goals: [What was set last time, and where it stands]

Goals for the next period: [2–3 specific, ideally collaboratively set]

Overall summary: [A few sentences connecting the above, not a new rating pulled from nowhere]

Calibrating across multiple managers

At a small business with more than one manager conducting reviews, it's worth checking that the same standard is being applied across teams — one manager's "meets expectations" shouldn't quietly mean something different from another's. A brief calibration conversation before reviews go out, comparing a few examples across teams, catches this kind of drift before it becomes a fairness issue that employees notice by comparing notes with each other.

Connecting the review to compensation, carefully

If performance reviews influence raises or bonuses, it's worth being explicit about that connection rather than leaving employees to guess whether a review is purely developmental or has real financial stakes attached. Ambiguity here tends to make employees more anxious about the review than the actual content warrants, and it can also make managers softer in their written feedback than the situation calls for, out of discomfort with the compensation implications riding on it. Stating plainly how the review relates to compensation decisions, even if the answer is "these are considered separately," removes a layer of unspoken tension from the conversation.

The short version

A performance review earns its value through specificity — real examples tied to expectations that were already known, not general impressions assigned after the fact. If regular 1:1s are happening throughout the year, the review should feel like a summary of an ongoing conversation, not the first time anything substantial gets said.