Most performance review advice focuses on what to measure. This post focuses on what to say. There is a significant difference. Choosing the right framework or rating scale matters, but the words a manager types into a review form are what the employee actually reads, re-reads, and remembers. These performance review examples are organised by conversation type, because the stakes, the tone, and the language all shift depending on whether you are reviewing a high performer, someone who is struggling, or someone who needs a completely different kind of honesty.
Getting this right is not a soft skill. It is a management competency. Gallup's research on the State of the Global Workplace consistently shows that how managers communicate directly affects employee engagement, retention, and whether people feel their work has meaning. The words in a review are a signal. Employees read them the way you read a contract.
What makes a performance review example actually useful?
A useful performance review example is specific, evidence-based, and connected to a real outcome. It avoids adjectives like "great" or "poor" without backing them up. The best examples follow a simple structure: what the person did, what the result was, and what it means going forward.
Generic phrases are the enemy of a good review. "John is a team player" tells John nothing about what he did that was valuable or what he should keep doing. "John restructured the weekly stand-up format after noticing the team was consistently running over time. Meeting duration dropped by 40% in the following month, and the team reported clearer priorities in the post-sprint pulse survey" tells John exactly what behaviour had an impact. That specificity is what makes employee feedback land. It is also what makes a review defensible if performance management decisions are ever questioned.
The single most important quality of any review example is that it names a specific behaviour, not a personality trait. You are reviewing performance, not personhood. That distinction protects the employee's dignity, the manager's credibility, and the organisation's legal position.
HR teams often supply templates to create consistency across the business. Those templates have value. But templates are scaffolding, not substance. The examples below are designed to sit inside whatever structure you already use.
How do you write performance review examples for high performers?
For high performers, the risk is not saying too little - it is saying nothing specific. Vague praise feels hollow to people who know their own output is strong. They are looking for evidence that you noticed the details, not just the headline.
Here are examples calibrated for high-performance conversations.
On results and delivery: "You closed 127% of your sales target for the half-year and maintained the lowest churn rate on the team. More significantly, you built a referral pipeline that accounted for three net-new enterprise accounts in Q4. That is not a coincidence; it reflects a consistent approach to client relationships that the rest of the team can learn from."
On leadership and influence without authority: "You stepped into the gap when the product roadmap shifted unexpectedly in March. Without being asked, you convened a cross-functional working group, clarified the revised priorities, and kept three dependent workstreams from stalling. That kind of initiative is the reason the quarter landed as well as it did."
On culture and company values: "Your approach to onboarding the two new analysts demonstrated exactly what we mean when we talk about our company culture. You spent time you didn't have to spend, shared context that isn't written down anywhere, and set them up to contribute meaningfully inside their first month."
Recognition that is this specific serves two purposes. It motivates the person receiving it. It also signals to everyone around them, because performance management is never truly private in an organisation, what the business actually values. Vague praise teaches people nothing about what to repeat.
High performers also need honest challenge. The most powerful reviews for this group combine recognition with a genuine development question. "Where do you want to go next, and what would need to be true to get there?" is a sentence that opens a conversation that generic performance templates never reach.
How do you write performance review examples for someone who is underperforming?
This is the conversation most managers avoid, and avoidance is its own kind of management failure. An underperforming employee who receives a neutral review is being set up to fail. The kindest thing a manager can do for someone who is struggling is name the gap clearly, link it to evidence, and build a concrete action plan together.
Here are examples structured for underperformance conversations.
On missed targets with context: "Over the past two quarters, delivery on the agreed project milestones has been inconsistent. Of the six checkpoints we set in January, three were met on time, two were delayed by more than a week without prior communication, and one required handover to another team member to complete. I want to understand what is getting in the way, because the pattern suggests something systemic rather than isolated."
Notice the last sentence. It opens the door rather than closing it. Underperformance has causes. Managers who skip to consequences without exploring causes make poor diagnoses and worse action plans.
On communication and conduct: "In the last performance cycle, there have been three occasions where a client escalated because they hadn't received an expected update. I'm not raising this to criticise your intent; the feedback from clients is that they value working with you when they do hear from you. The gap is in proactive communication when a deadline shifts. We need to close that gap in this next quarter."
On effort and engagement: "Your output during the second half of the year was noticeably below what you produced in the first. I want to be direct about that because I think you deserve honesty rather than ambiguity. I've noticed the change and I want to understand it before we talk about what comes next."
Each of these examples avoids character judgements. They describe observable patterns and invite dialogue. That is what separates performance management from performance punishment.
The action plan that follows a conversation like this needs to be specific. It should name what changes, how progress will be measured, what support the manager is committing to provide, and what the timeline is. A vague commitment to "improve" is not an action plan. It is a deferred disappointment.
How do you write performance review examples for mid-range performers?
Mid-range performers are the invisible middle of most organisations. They are rarely praised because they aren't exceptional enough to stand out. They are rarely developed because they aren't struggling enough to trigger concern. They churn quietly, and companies only notice the loss after the fact.
This is where continuous feedback between review cycles matters most. If a manager has been having real conversations throughout the year, the review for a solid mid-range performer is not a surprise. It is a summary.
On consistent, reliable contribution: "Your work on the client reporting process this year was not flashy, but it was consequential. The reports ship on time, the error rate has dropped significantly since you standardised the template, and two clients have specifically mentioned the quality in their quarterly business reviews. That kind of reliable delivery is the foundation the team builds on."
On development and growth edge: "You have a clear strength in analytical thinking, and I'd like to see you bring that into more visible settings this year. You've been hesitant to present findings directly to senior stakeholders. That's the next step. I'm going to create opportunities for you to do that with support, and I want you to take them."
On collaboration and team dynamics: "Your colleagues consistently describe working with you as straightforward and supportive. In a year where the team faced significant restructuring, that stability mattered. The next challenge is to bring more of your ideas into the room earlier, rather than after the decisions have been made."
These examples treat mid-range performers as people with a growth trajectory, not a fixed position. That shift in framing is one of the most powerful things a manager can do for employee engagement in this group.
How do you write review language that survives a legal or HR challenge?
Performance reviews occasionally feed into formal processes - disciplinaries, redundancy consultations, or grievance hearings. When they do, the language in the review matters in a different way. Vague, impressionistic writing becomes a liability.
Reviews that hold up are specific, factual, and free of personality language. "David is lazy" is a character judgement that cannot be verified and cannot be defended. "David missed four of the six deadlines agreed in the performance plan, without prior communication on three of those occasions" is a fact. Courts, employment tribunals, and HR directors know the difference.
This is where real time analytics from your performance management system become genuinely useful. If your system logs when goals were set, when reviews were completed, and what ratings were assigned, that data is contemporaneous evidence. It exists independent of memory and is far harder to dispute than a manager's recollection.
HR teams often underestimate how much the quality of written review language affects their own workload. When reviews are vague, employees challenge them. When reviews are specific and fair, challenges are rarer and easier to resolve. Investing time in review quality is not just a people matter, it is a risk management matter.
Communication tools that allow managers to log real-time notes throughout the year, not just at review time, also reduce the risk that reviews are written from memory rather than evidence. Memory is selective and biased. Notes taken in the moment are neither.
What do effective review phrases look like for specific competencies?
Competency-based reviews require language that connects observable behaviour to the competency being assessed. Here are examples across five common competency areas that appear in most frameworks.
Problem-solving: "When the API integration failed three days before the product launch, you mapped the failure path within two hours, proposed two viable workarounds, and communicated the options to the stakeholders without being asked. We launched on time. That is problem-solving under pressure."
Communication: "Your written updates to the project board were consistently clear, appropriately concise, and free of the jargon that made previous reports hard for the board to act on. Two board members specifically mentioned the quality of your Q3 summary. The skill is visible, and it has had an effect."
Adaptability: "The scope of this project changed four times in six months. You adjusted each time without visibly losing momentum or morale. More importantly, you helped the people around you recalibrate when they were struggling with the uncertainty. That is a form of leadership that doesn't show up in a job title."
Technical skill: "Your proficiency in the new data pipeline architecture went from zero to operational in six weeks. You documented your learning process in a way the whole team could use, which shortened the onboarding curve for the rest of the squad significantly."
Initiative: "Without being directed to, you identified a recurring process gap in the client handover workflow, designed a checklist to address it, piloted it with two accounts, and presented the results to the team. The fix is now standard. That is what initiative looks like."
Employee sentiments about performance reviews are often shaped by whether they feel the review was personalised to them. These kinds of examples, grounded in real events, create that feeling. A review that reads like it could have been written about anyone is worse than no review at all.
Frequently Asked Questions
What are good performance review examples for a high performer?
For high performers, focus on specific results and their broader impact on the team. Examples include: "You delivered the Q3 migration two weeks ahead of schedule, which unblocked three dependent teams and prevented a costly delay. The quality of your handover documentation set a new standard for the department."
How do you write a performance review for an underperforming employee?
Be specific, factual, and forward-looking. Name the gap, cite evidence, and attach a clear action plan. Avoid vague language like "needs improvement" without explaining what improvement looks like and by when. Link consequences to outcomes, not character judgements.
What is the difference between a performance review and continuous feedback?
A performance review is a structured, typically annual or semi-annual evaluation of an employee's contributions. Continuous feedback is ongoing, informal, and given close to the moment. Reviews summarise; continuous feedback shapes. Both serve different purposes and work best together, not as substitutes for each other.
How long should a written performance review comment be?
Between 50 and 150 words per competency or goal is a practical range. Long enough to be specific, short enough to be read. The goal is precision, not volume. Vague praise padded to fill space is worse than a short, honest, well-evidenced observation.
How often should performance reviews happen?
Research from Gallup suggests that meaningful performance conversations should happen at least quarterly, with many high-performing organisations moving to monthly check-ins supplemented by an annual summary review. Annual-only reviews are now widely considered insufficient for driving real development.
Can performance review examples be used as copy-paste templates?
They can be a starting point, but direct copying without personalisation signals to employees that the review was not genuinely considered. Use examples to calibrate tone and structure, then adapt every phrase to the specific person, role, and evidence in front of you.
What role do pulse surveys play in preparing for a performance review?
Pulse surveys surface employee sentiments between formal review cycles, giving managers a richer picture of morale, blockers, and engagement trends before they sit down for a review. They reduce the risk of a review feeling like a surprise by surfacing issues continuously rather than only at year-end.
What should a performance review action plan include?
A good action plan names the specific behaviour or skill to develop, the support the employee will receive, a measurable milestone, and a target date. It is a working document, not a punishment. The manager and the employee should both sign off on it and revisit it at the next check-in.
The thing no template can give you
Performance reviews are not a documentation exercise. They are a moment in the working relationship between a person and the organisation that employs them. Done poorly, they confirm every cynical thing employees already believe about workplace culture - that the feedback is generic, the ratings are political, and the conversation exists to protect the company, not to help the individual. Done well, they do the opposite.
The examples in this article work because they treat people as intelligent adults who deserve honesty and specificity. They assume that the reader of the review is going to sit with those words. They are written for the person, not the file. That is not a style choice. It is an ethical one.
The shift from reviewing performance to genuinely developing people starts with the language. Every manager who writes a better review this cycle makes a slightly better workplace for the people in it. Multiply that across a hundred managers and you start to shift company culture in a direction that compounds.
Explore Kodecrew to see how continuous feedback, real time analytics, and structured action plans can give your managers the context they need to write reviews that are honest, specific, and worth reading.
