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

Stop staring at a blank page. Here are real performance review examples, honest phrases, and ready-to-use templates for every type of employee - and every difficult conversation you've been putting off.

Performance review examples are the most searched-for resource in HR - and the least well served. Most templates online read like they were written by a compliance department in 1997. Vague. Safe. Useless. A good performance review is specific, honest, grounded in real behaviour, and connected to what happens next. This guide gives you concrete examples across every performance level, explains the structure behind effective reviews, and shows you how to turn a once-a-year ritual into something that actually improves performance management across your organisation.

What makes a performance review example actually useful?

A useful performance review example is specific to a behaviour, tied to an outcome, and points toward a future action. It names what the person did, describes the impact it had, and gives the reader a clear sense of what "more of this" or "less of this" looks like in practice. Vague praise and vague criticism both fail the employee equally.

Most managers default to adjectives. "Sarah is a strong communicator." "James needs to improve his time management." These sentences feel like feedback. They are not. They describe a trait without grounding it in anything real. The person reading them learns nothing they can act on.

The research is not subtle on this point. Harvard Business Review's analysis of performance management reform found that companies replacing vague annual ratings with specific, behaviour-based feedback saw measurably stronger engagement and retention. The structure matters. The words matter. And frequency matters too - but we'll get to that.

A useful review example follows a simple pattern: Situation - Behaviour - Impact - Forward direction. Not every review needs all four in every sentence. But every section of a review should contain at least one element of each across the whole document.

What are good performance review examples for high performers?

For high performers, specific examples should name the behaviour, the context it happened in, and the concrete impact it delivered. Avoid generic praise - it signals you weren't paying attention. Instead, write something like: "During the Q3 product launch, Maya identified a critical integration gap two weeks before release, coordinated across three teams without being asked, and delivered a fix that prevented an estimated four-day delay. This is the kind of initiative that raises the bar for the whole team."

High performers are often the most poorly served by generic reviews. They already know they're doing well. What they want to know is whether their organisation sees how and why they're doing well - and what comes next. A review that doesn't answer those questions is a missed retention opportunity.

Here are additional examples for high performers across common competencies:

Leadership

"Tom consistently creates space for quieter team members to contribute in planning sessions, which has visibly improved the quality of decisions and increased psychological safety across the group."

Behaviour named. Impact on team described. No adjectives masquerading as evidence.

Delivery

"Anya delivered the client migration project on time despite two significant scope changes mid-cycle. She proactively updated stakeholders at each pivot, which maintained trust and avoided contract escalation."

Demonstrates resilience and stakeholder management with a named business outcome.

Growth & Learning

"Since completing the data visualisation training in January, Carlos has redesigned the monthly reporting pack, cutting preparation time by roughly 40% and improving leadership's ability to act on the data."

Learning tied directly to a business improvement. This is how you make development feel real.

What are performance review examples for employees who need improvement?

For employees who need to improve, the most common mistake is burying the concern in qualifications until it disappears. A review that spends three paragraphs on positives before one vague sentence about "areas to work on" does not constitute honest feedback - it just protects the manager's comfort. Be direct and be kind. These are not opposites.

Here is what honest, constructive looks like in practice:

Missed Deadlines

"Three of the five deliverables this quarter were submitted after the agreed deadline. In two cases this caused downstream delays for other team members. We need to understand whether this is a workload issue, a planning issue, or something else - and build a clear plan together."

Factual. Non-accusatory. Opens the door to a real conversation and connects to action plans.

Communication

"On several occasions this quarter, project status wasn't communicated until issues had already escalated. Proactive updates - even brief ones - would reduce friction for the wider team and give you more control over how problems are perceived."

Describes the gap, explains why it matters, and offers a practical path forward.

Quality of Work

"The reports submitted in Q2 required significant revision before they could be shared with clients. This adds workload for the team and risks client confidence. Let's agree a peer-review step before external submission for the next cycle."

Concrete example, business impact, and a proposed structural fix - not just a criticism.

A review that doesn't tell someone the truth about their performance isn't kind. It's a delay - and the employee pays the price for it later, usually with less time to course-correct.

On Honesty in Feedback

What does a complete performance review template look like?

A complete performance review template has five core sections: a summary of the review period, an assessment of goals and outcomes, an evaluation of behaviours and competencies, a development section, and a forward-looking goals section. Each section should contain space for both manager input and employee self-assessment. Reviews work best when they are conversations, not verdicts.

Below is a template structure that HR teams can adapt. The sections are deliberately lean - long templates get abandoned mid-way through.

Section 01

Period Summary

A brief, factual summary of the review period. What was the context? Were there significant changes in role, team, or business conditions that affected performance? This section grounds everything that follows and prevents the review from existing in a vacuum.

Section 02

Goals and Outcomes

List the goals set at the last review. For each one: Was it achieved? Partially achieved? Not achieved? What were the contributing factors? This section should be factual, not evaluative. Save the interpretation for the next section. Example: "Goal: Launch the partner portal by end of Q2. Outcome: Launched in week 1 of Q3 following API delays outside the employee's control."

Section 03

Behaviours and Competencies

Evaluate the how, not just the what. How did this person collaborate? How did they handle setbacks? How did they manage their stakeholders? Use specific examples for each competency - not a scale from 1-5 on its own. A rating without an example is almost meaningless. Continuous feedback collected throughout the year feeds directly into this section and makes it far more defensible.

Section 04

Development and Recognition

What has this person learned? What recognition have they received or earned? What skills are emerging that the organisation should invest in? Recognition here is not a token gesture - it is evidence that the organisation has been paying attention. Company culture is, in large part, built from moments like this one.

Section 05

Goals for the Next Period

Set between two and five goals. Each should be specific, time-bound, and owned by the employee - not assigned at them. Note any dependencies or support required from the organisation. These goals become the foundation of the next review cycle and the starting point for any action plans created in the interim.

How do pulse surveys and continuous feedback change the review process?

Pulse surveys and continuous feedback loops mean the annual review no longer has to carry the full weight of a year's worth of information. When managers collect employee feedback regularly, reviews become summaries of an ongoing conversation rather than a high-stakes revelation. This reduces anxiety for everyone and dramatically improves the quality of the examples managers can actually cite.

Gallup's State of the Global Workplace research consistently shows that employees who receive regular, meaningful feedback are significantly more engaged than those who receive it only at annual review time. The gap is not small. It is the difference between someone who is actively contributing and someone who is watching the clock.

Practically, this means building check-in rhythms into the cadence of work. Weekly or fortnightly one-to-ones. Quarterly goal check-ins. Pulse surveys deployed after significant organisational changes, project completions, or leadership transitions. The data gathered through these touchpoints feeds directly into the annual review and makes the manager's job of writing examples significantly easier - because the examples have already been documented in real time analytics dashboards and conversation notes.

It also changes the power dynamic. When employee sentiments are captured regularly - not just at review time - you catch disengagement before it becomes departure. The person who rates communication as deteriorating in October is giving you a three-month window to act before you lose them in January.

What phrases should you avoid in performance reviews?

Certain phrases actively damage the usefulness of a performance review. They are worth identifying explicitly because managers reach for them precisely when they are uncomfortable - and discomfort is usually a signal that something important needs to be said more clearly, not avoided.

Phrases to retire:

Avoid

"Meets expectations"

What expectations? Set by whom? Measured how? This phrase sounds like an assessment but contains no information. Replace with a specific example of what was met, and what the standard was.

Avoid

"Could improve in areas of communication"

What kind of communication? Written? Verbal? With whom? In what context? "Communication" is a category, not a behaviour. Get specific. "Tends to send lengthy emails where a two-line summary would serve better" is actionable. "Communication" is not.

Avoid

"A real team player"

This is the review equivalent of "nice to meet you." It signals nothing. If someone is genuinely collaborative, describe a moment where that collaboration produced something. Name the team. Name the outcome. Otherwise it reads as filler and the employee knows it.

Avoid

"No major issues this year"

Absence of problems is not performance. It also creates a false signal - the person reads this as an endorsement when it may simply mean they weren't observed closely enough. If there are no major issues, describe what was actually accomplished instead.

How does a strong review process affect employee engagement and workplace culture?

A strong review process builds employee engagement by demonstrating that the organisation sees people clearly. When a manager can describe what someone did, why it mattered, and what it says about their future potential, it creates a sense of being genuinely known. That is rare. It is also disproportionately powerful for workplace culture.

Research published in Harvard Business Review on the feedback fallacy argues that the most effective feedback is not corrective instruction but attention to what is already working well - communicated with specificity. This doesn't mean avoiding hard conversations. It means that recognition and honest assessment are not opposites. Both require the same thing: paying close attention.

The implications for company culture run deeper than any single review. When people know the review process is honest, rigorous, and connected to real consequences (good and bad), they trust it. When it's perceived as a paperwork exercise with no bearing on anything real, they disengage from it entirely. And the line between those two outcomes is often just the quality of the examples managers write down.

HR teams that invest in manager training on how to write and deliver reviews, that gather employee feedback continuously through communication tools like pulse surveys, and that make action plans a visible output of every review cycle - those teams build something that compounds. The reviews get better. The culture gets stronger. The data gets richer. And the conversations get easier.

The annual review is not the problem. Treating it as the only moment when performance is discussed - that is the problem. Reviews work when they confirm what both parties already know, not when they reveal surprises.

On the Purpose of the Review Cycle

How should self-assessments work in a performance review template?

Self-assessments work best when they mirror the structure of the manager's review - same sections, same prompts, completed independently before the two parties meet. This forces both sides to prepare and creates a natural agenda for the conversation: where do assessments align, and where do they differ? The divergences are almost always the most important part of the discussion.

Self-assessment prompts that actually generate useful responses:

Prompt 01

"Describe one moment this year where you feel you did your best work. What made it possible?"

Better than "what were your achievements?" because it asks for context and conditions - the stuff that helps managers understand what this person needs to repeat their best work.