Performance Review Examples: Templates and Phrases That Actually Work

Performance Management · Templates & Examples Performance Review Examples: Templates and Phrases That Actually Work

Most performance reviews fail before the first word is written. Here are real examples, frameworks, and language that turn awkward evaluations into honest conversations that drive actual growth.

Performance review examples are the fastest way to rescue a broken review process. A good example shows a manager what "specific and actionable" actually looks like in practice - not in theory. This guide covers templates for every common scenario: strong performers, underperformers, people mid-development, and roles that are hard to measure. Use these directly. Adapt the language. And read the sections between the templates, because the words only work if the thinking behind them is right.

Why Do Most Performance Reviews Fail to Change Anything?

Most performance reviews fail because they are written in generalities, delivered once a year, and filed in a system nobody opens again. The feedback is vague. The employee leaves the room unsure whether they are valued or quietly being managed out. Nothing changes - not behaviour, not output, not engagement.

Gallup's research on performance reviews has found consistently that fewer than one in four employees strongly agree their manager provides meaningful feedback. That is not a rounding error. It means the majority of people in the workforce are going through a performance management process that they themselves describe as unhelpful. The ritual continues. The outcomes do not improve.

The root problem is rarely the manager's intent. Most managers want to give useful feedback. The problem is they do not have concrete examples to anchor their words to, and nobody showed them what a good review actually looks like on the page. So they default to phrases they have heard before: "a great team player," "could improve communication," "meets expectations." Phrases that are true of almost everyone and useful for almost no one.

That is the gap this article fills. Not theory. Examples. Real sentences. Frameworks you can use today.

"Meets expectations" is not feedback. It is a ceasefire. It tells the employee nothing about what they did well, nothing about where to grow, and nothing about how you actually see them.

The Core Problem With Generic Reviews

What Makes a Strong Performance Review Example?

A strong performance review example does four things. It names a specific behaviour or outcome. It connects that behaviour to a business result. It is honest about where improvement is needed, without cruelty. And it points somewhere - toward a next step, a development goal, or a clear expectation going forward.

That is it. Four things. The problem is that most review templates do not scaffold for any of them. They ask "Rate this employee on communication: 1-5." A rating of 3 with no context tells the employee nothing and exposes the organisation to risk if that rating is ever questioned.

Harvard Business Review's analysis of performance evaluation research points to one consistent finding across decades of studies: specificity is the single biggest predictor of whether feedback actually changes behaviour. Generic praise produces warm feelings. Specific praise produces better work.

The structure that works is simple: situation, behaviour, impact. What was happening, what did the person do, and what did that produce? Build your performance review examples around that spine and they will be useful regardless of the rating scale or template your organisation uses.

What Are Good Performance Review Examples for High Performers?

High performers are the most commonly under-reviewed category. Managers assume strong results speak for themselves and move on. They do not. Exceptional employees need to understand precisely what they are doing well - and why it matters - or they start wondering whether anyone is paying attention. Recognition tied to specifics is what builds loyalty. Vague praise builds nothing.

Example 1 - Exceeds Expectations (Individual Contributor)

"Over the past six months, [Name] has consistently delivered work that exceeds the scope of the brief. On the Q3 product launch, she identified a gap in the go-to-market plan before it reached the client, proposed a revised timeline, and coordinated across three departments to execute it without escalation. The launch came in four days ahead of schedule. This is not an isolated incident - it is her pattern. She does not wait to be asked. She sees the problem and moves."

Why it works: Specific project, specific outcome, observable behaviour, pattern noted.

Example 2 - Exceeds Expectations (People Manager)

"[Name] manages a team of seven across two time zones. His team's engagement score sits 14 points above the company average, and two members of his team were promoted internally this year - both of whom he had explicitly developed for those roles over the prior 12 months. He schedules monthly development conversations separate from operational check-ins. He uses continuous feedback as a tool, not a formality. His output numbers are strong, but his multiplier effect on others is what makes him exceptional."

Why it works: Uses a quantified benchmark, names retention and development impact, distinguishes individual output from team impact.

Notice what both examples avoid. They do not say "a pleasure to work with." They do not say "goes above and beyond" without explaining what above looks like. Every sentence earns its place by pointing to something real.

What Are Performance Review Examples for Underperformers?

Underperformance reviews are where most managers retreat into vagueness - because being specific feels unkind. The opposite is true. Vague criticism is the unkind move. It leaves the employee anxious and confused, without any clear path to improve. Specific, honest feedback - delivered without cruelty - is the most respectful thing a manager can do.

It is also, legally, the safer move. A documented, specific record of performance concerns and agreed action plans protects both parties far better than a rating of 2 with no narrative.

Example 3 - Below Expectations (Delivery and Reliability)

"Over the past quarter, [Name] has missed three agreed deadlines on the Meridian account. In each case, the delay was flagged by the client rather than communicated proactively. We discussed this pattern in our August check-in and agreed on a revised workflow with milestone check-ins. The pattern has continued. The core issue is not capability - his technical work, when delivered, meets standard - the issue is follow-through and proactive communication when he hits an obstacle. The focus for Q4 is: flag issues within 24 hours of identifying them, do not wait for the deadline to pass."

Why it works: Three specific instances, names prior conversation, distinguishes capability from behaviour, closes with a concrete expectation.

Example 4 - Below Expectations (Quality of Work)

"[Name]'s output this half-year has required significant rework before it can progress to the next stage. Of the 11 reports submitted since January, seven required revisions that went beyond formatting - they involved structural or analytical gaps that had to be corrected before the client received anything. We have discussed quality expectations twice in this period. The next step is a structured 30-day plan with weekly review points. If we do not see sustained improvement by the end of that period, we will need to have a different conversation about fit for this role."

Why it works: Quantified, distinguishes types of errors, notes prior conversations, signals the next step without ambiguity.

The last sentence of Example 4 is one many managers avoid. They consider it too blunt. But ambiguity at this stage is a disservice. The employee deserves to know where they stand. So does the organisation.

What Are Performance Review Examples for Employees Who Meet Expectations?

The "meets expectations" band is where the most people sit, and it is where review writing is most commonly phoned in. Solid, reliable contributors get a paragraph of warm nothing. They notice. Over time, it erodes their sense of being seen - which erodes employee engagement, which erodes the company culture you have been trying to build.

Meeting expectations is not a mediocre outcome. For many roles, consistent, reliable, high-quality delivery is exactly what is needed. That deserves acknowledgment that is just as specific as what you would write for a high performer - it just points to different things.

Example 5 - Meets Expectations (Consistent Contributor)

"[Name] is one of the most reliable members of the team. Her work comes in on time, at the right level, with minimal rework required. That sounds like a baseline - but in a team that has been under consistent pressure this year, reliability has had real value. She stepped in to cover two projects during the summer staffing gap without being asked, and both were completed without dropping in quality. The area to develop in the next cycle is visibility: she does the work, but she is not yet shaping how others see it or contributing to the wider strategic conversation."

Why it works: Reframes "meets expectations" as a genuine value, gives a specific example of discretionary effort, names a clear development direction.

If your "meets expectations" review could apply to any of the 20 people in that band, you have not written a review. You have written a template for nobody.

On Specificity

What Phrases Should You Use - and Avoid - in Performance Reviews?

Certain phrases have become so overused they have been drained of meaning. Others are actively harmful because they are too vague to act on, or because they frame personality as the problem rather than behaviour. The following breakdown is based on what actually holds up when employee sentiments are measured post-review and when reviews are examined for legal defensibility.

Avoid

"Has a bad attitude"

This describes a judgement about personality, not an observable behaviour. Replace with: "In three team meetings this quarter, [Name] responded to proposed changes by dismissing them without engaging with the rationale, which has affected the team's ability to move forward quickly." Now there is something the employee can actually change.

Avoid

"Always goes above and beyond"

"Always" and "above and beyond" are both meaningless without specifics. What does above look like? When did they go there? What did it produce? Without answers, this phrase lands as well-meaning noise.

Avoid

"Needs to work on communication skills"

Which communication skills? Written? Verbal? Upward? Cross-functional? The gap is in explaining complex data to non-technical stakeholders? Then say that. "Communication" is a category, not a behaviour. Name the behaviour.

Use

"In [specific project], you did [specific behaviour], which resulted in [specific outcome]"

This is the backbone of every good performance review example. Situation, behaviour, impact. Three elements. Every time.

Use

"The focus for the next period is X, and we will measure progress by Y"

Close every development point with a direction and a measure. Not "improve time management." But: "The goal is to hit agreed deadlines without escalation on at least 90% of deliverables in Q1. We will check in monthly on this specifically."

Use

"Here is what I see, here is what I would like to see, and here is how I can support that"

This structure signals partnership rather than judgement. It also holds the manager accountable - what will you actually do to help? Good performance management is not one-directional.

How Should a Performance Review Template Be Structured?

A template that works is not a form with boxes to fill in. It is a thinking scaffold. It forces the reviewer to gather real evidence before they write a single word of evaluation. The following structure works across most roles and seniority levels. Adapt the sections to fit your context, but do not skip any of them.

Section 01

Key Contributions This Period

List two to four specific projects or outputs. For each: what was the goal, what did the person do, what was the result? No adjectives until you have the nouns and verbs. Results first, judgement second.

Section 02

Strengths (With Evidence)

Name two or three genuine strengths. For each, name the evidence. "Strong under pressure" - when? Which situation? What did they do that tells you that? If you cannot answer those questions, you do not know whether it is a strength or an assumption.

Section 03

Development Areas

Name one to two areas. Be specific about what the current state is and what the target state looks like. Avoid "needs to improve X" - use "currently, X looks like this: [specific behaviour]. The goal is for it to look like this: [specific behaviour]." Then name what support is available.

Section 04

Goals Review (Prior Period)

What were the agreed goals from the last review? Were they met, partially met, or not met? Do not skip this section. If you set goals and never return to them, you have taught the employee that goals are decoration. HR teams that embed this accountability loop see significantly better follow-through on action plans.

Section 05

Goals and Action Plans (Next Period)

Two to three goals maximum. Each with a measurable outcome and a timeline. This is where performance management becomes a forward-looking tool rather than a historical judgement. Close the review here: what does success look like in six months?

How Does Continuous Feedback Change the Performance Review Process?

If continuous feedback is working in your organisation, the annual or semi-annual review should contain no surprises. Everything in it has already been discussed. The review becomes a summary and a commitment document - not a verdict handed down after months of silence.

Research published in HBR on the feedback fallacy challenges some assumptions about how corrective feedback works neurologically - but it reinforces the case for frequent, specific, positive feedback as a driver of learning and performance. The most effective managers are not those who save up their observations for the year-end form. They are those who share observations in the moment, consistently, so that the formal review is a confirmation rather than a revelation.

This also changes what employee feedback in the formal review needs to do. When the relationship already contains ongoing dialogue, the written review can focus on patterns, growth, and forward-looking goals rather than spending half its length explaining events the employee has already processed. The review gets shorter and more useful at the same time.

Pulse surveys between review cycles give HR teams an early signal when something is off - when employee sentiments shift, when a team's engagement drops, when a manager's feedback scores diverge from their team's output. That signal gives leaders time to act before the formal review, rather than discovering a problem in the documentation of it.

The organisations that have moved to real time analytics on employee feedback are not replacing human judgement with data. They are giving managers more signal, earlier - so that