Most performance review examples you find online cover the comfortable middle. The solid performer. The obvious star. The person who delivered, communicated well, and made your job easy. But the conversations that keep managers up at night are rarely about those people. They are about the employee who almost delivered. The one who is brilliant but brittle. The one who is burning out quietly while their numbers still look fine. Those conversations need different language, and most templates do not go there.
This guide does. It is built around the performance review examples that cover the hard cases, the edge cases, and the ones where the standard phrase bank leaves you stranded. Every example here is tied to a real management situation, grounded in what good employee feedback actually looks like, and structured so you can use it or adapt it without starting from nothing.
What makes a performance review example actually useful?
A useful performance review example is specific enough to feel real, structured enough to be adapted, and honest enough to open a conversation rather than close one. The best examples anchor every observation in behaviour, connect it to impact, and point toward a future action rather than just rendering a verdict.
The weakest performance review language is abstract. "Shows good leadership" means almost nothing without a specific example. "Needs to improve communication" is so vague it often makes things worse, because the employee does not know what to change and the manager cannot track whether they have changed it. The standard that separates a useful performance review from a forgettable one is this: every claim should be supportable with an example, and every gap should be paired with a direction.
Research from Gallup's work on manager effectiveness consistently shows that employees who feel their performance is managed fairly and clearly are more likely to stay engaged over time. The review document is not where performance management happens, but it is where the whole year's worth of conversations gets distilled. If those conversations have been happening through continuous feedback loops, the review should feel like a summary, not a shock.
The examples in this guide are organised by situation, not by rating tier. That is deliberate. The same employee might be a strong performer on one dimension and underperforming on another, and collapsing everything into a single rating hides more than it reveals.
How do you write performance review examples for underperforming employees?
Write underperformance reviews by anchoring every observation in a specific, observable behaviour, stating the expected standard clearly, and closing with a concrete action plan that gives the employee a real path forward. Avoid adjectives. Stick to what happened and what needs to happen next.
Here is the structure that works:
- Name the gap: What specifically was expected, and what was delivered instead?
- Give the example: One or two concrete instances, not a pattern statement you cannot back up.
- State the impact: Why does this matter to the team, the customer, or the business?
- Name the path forward: What does success look like in the next 90 days, and what support will the employee receive?
The single biggest mistake in underperformance reviews is writing around the problem. Phrases like "has room to grow in project delivery" are so softened they carry no information. The employee reads it as mild feedback. The manager intends it as a serious concern. That gap is where trust breaks down.
Example phrases for underperformance situations:
Missed delivery standards: "Over the past quarter, three of five project milestones were missed by an average of eight days. The expected standard for this role is on-time delivery with proactive flag-raising when risks emerge. The impact has been downstream delays for two other teams. In the next cycle, I want to see a weekly status update on any work with a deadline further than two weeks out, and I want us to build a risk log together."
Quality issues: "Work submitted for client review in Q2 required significant revision on four separate occasions. The standard is submission-ready work that reflects the client brief without needing a second review cycle. I want to understand what is getting in the way, and then I want us to build a checklist process you own before anything goes out."
Attendance or availability patterns: "You have been absent or unavailable for team stand-ups on 11 occasions in the past six weeks. I want to understand what is driving that before I draw any conclusions, because I want to support you if something is going on. At the same time, consistent availability is a requirement of this role, and I want us to find a way to make that sustainable for you."
Each of these opens a dialogue. None of them deliver a verdict. That is the point.
How do you write performance review examples for high performers who are showing signs of disengagement?
Write these reviews by separating results from engagement clearly, acknowledging both honestly, and creating space for the employee to tell you what is actually going on. High performer disengagement is one of the most expensive problems a team can have, and it almost always has a cause that the manager can either address or at least acknowledge.
McKinsey research on employee experience has consistently flagged that high performers who disengage do so not because of money but because of a felt lack of meaning, autonomy, or recognition. They rarely say this out loud. They just start doing less.
A performance review for a high performer who is quietly disengaging needs to do three things. First, recognise the results clearly and specifically. Skipping recognition because you want to get to the concern is a mistake. Second, name what you have observed without diagnosing why. Third, invite the conversation rather than delivering a judgment.
Example phrases for this situation:
"Your delivery on the [specific project] this year has been exceptional, and the client feedback from that engagement has been some of the best we have seen on the team. I also want to be honest with you about something I have noticed over the past two quarters. You are contributing less in strategy sessions, and a few of your colleagues have mentioned that you seem less available for the kind of collaboration you were known for before. I am not drawing any conclusions from that. I want to understand it. What is making work feel the way it currently feels for you?"
That last question is where real performance management begins. The review is the opening, not the conclusion.
Pulse surveys can play an important role here. When HR teams are tracking employee sentiments between formal cycles using pulse surveys, managers can arrive at a review conversation with data about how the team has been feeling, not just numbers on what they have been producing. That context changes everything.
What do performance review examples look like for employees with high potential but inconsistent results?
For high-potential employees with inconsistent results, the review needs to hold both truths simultaneously without letting one cancel the other. These employees are often the most sensitive to how feedback lands, because they already know they have underdelivered in some areas, and they are watching to see whether the organisation sees their ceiling or their floor.
Name the potential with specificity. Then name the inconsistency with the same specificity. Then offer a theory about what is getting in the way - and ask whether your theory is right.
Example phrases:
"The work you did on [specific situation] in Q1 showed exactly the kind of thinking this team needs at the next level. You built a framework that nobody asked for, and it solved a problem we had been ignoring for two years. That is real capability. At the same time, the delivery on [specific project] in Q3 did not reflect that same level, and I want to understand what was different. Was it the scope? The support you had? Something else? I have a theory, but I would rather hear yours first."
The phrase "I have a theory, but I would rather hear yours first" is one of the most useful tools in any feedback conversation. It signals that the manager has thought about the situation, is not going to lecture, and is genuinely interested in the employee's perspective.
For these employees, action plans matter more than ratings. A development-focused action plan that links their potential to a specific near-term opportunity gives them something to aim at. Vague encouragement without a concrete path is actually demotivating for high-potential employees, because they hear it as "we think you could do more, but we have not thought about what."
How do performance review examples connect to company culture?
Performance reviews reflect company culture whether they are designed to or not. The language managers use, the behaviours they reward, and the gaps they name all signal what the organisation actually values, as opposed to what it says it values. If a company claims to value collaboration but reviews only mention individual output, employees notice the gap.
Research published in Harvard Business Review on performance management systems has repeatedly found that the credibility of a performance review depends heavily on whether employees trust that the process is fair and consistent. That trust is built or destroyed at the team level, not the organisational level.
For HR teams, this means that reviewing the language across the organisation - using real time analytics on review content, rating distributions, and completion rates - is not bureaucratic overhead. It is a signal about whether company culture is being lived or merely described. When review language is vague, rushed, or systematically positive in a way that defies reality, it tells you something important about workplace culture on that team.
A performance review is a cultural document as much as it is an evaluation tool.
Communication tools matter here too. When managers have access to templates that embed the organisation's values into the structure of the review, they produce better reviews. Not because they are smarter, but because the scaffolding reflects the right priorities.
Example phrases that tie review language to culture:
For a culture that values psychological safety: "One thing I have valued this year is your willingness to name problems before they become crises. That is exactly the kind of behaviour that makes this team better, and I want to call it out explicitly."
For a culture that values learning: "The way you responded to the setback in Q2 - owning what went wrong, rebuilding the approach, and bringing the team along - is exactly the learning posture we are trying to build here."
For a culture that values customer focus: "Every decision you made this year had the customer as a reference point. That is visible in the work, and it is the standard we are trying to hold across the team."
What should performance review examples include for remote or distributed employees?
For remote or distributed employees, performance review examples need to make visibility explicit. Remote work creates a proximity bias problem: managers tend to recall what they have seen most recently and most directly, which disadvantages people who are not in the room. Good remote performance reviews counteract that by building evidence collection into the cycle, not just the review moment.
Example phrases for remote employees:
"Working across time zones, you have consistently delivered to a standard that requires no hand-holding and very little follow-up. That reliability is genuinely valuable and I want to be clear that it does not go unnoticed just because we are not in the same place."
"One area I want to develop with you this year is visibility. Not because I think you are hiding, but because your thinking and your contributions deserve a wider audience, and we should build some deliberate ways to create that."
For HR teams using continuous feedback tools, the distributed team context makes employee feedback collection even more important. When managers cannot observe people directly, the feedback loop has to be more intentional. Pulse surveys, structured peer feedback, and regular one-on-one documentation all feed the annual review with evidence that proximity alone cannot supply.
How do action plans fit into performance review examples?
An action plan is not an appendix to a performance review. It is the part that makes the review matter. Without a clear, time-bound action plan, a review is a judgment. With one, it is a development conversation.
Every performance review that identifies a gap should contain an action plan that specifies what will change, how, by when, and what support the employee will receive.
A weak action plan looks like this: "Will work on improving presentation skills." A strong action plan looks like this: "Will attend one presentation skills session before end of Q1, will present at the next all-team meeting in February, and will debrief with manager within a week of that presentation using the feedback collected."
The difference is accountability without blame. The strong version gives the employee a clear track to run on and builds in a follow-up conversation that neither party can conveniently forget.
For performance management systems to work, the action plan has to live somewhere the employee can return to between review cycles. That is where digital tools earn their place. When HR teams can see whether action plans are being progressed, not just created, the review process has a feedback loop. Without that visibility, action plans are aspirational documents that expire the moment the review is filed.
Frequently Asked Questions
What are good performance review examples for underperforming employees?
Good examples for underperforming employees are specific, observable, and paired with a forward path. Avoid vague labels like "needs improvement." Instead, name the behaviour, quantify the gap where possible, state the expected standard, and close with a concrete action plan and a timeline for reassessment.
How do you write a performance review for a high performer who is disengaged?
Acknowledge the results clearly, then name what you are observing without diagnosing motivation. A phrase like "your output has stayed strong, but I have noticed less initiative in team discussions over the past quarter - I want to understand what is driving that" opens the conversation without accusation.
What should a performance review say about an employee with high potential but inconsistent results?
Name both sides honestly. Something like "you have demonstrated real capability in [specific situation], and the results in [other area] have not yet matched that potential - here is what I think is getting in the way, and here is what I want us to build together."
How long should written performance review comments be?
Long enough to be specific, short enough to be read. Aim for three to five sentences per competency or theme. Bullet points help skimmability, but every bullet should contain a concrete observation, not a vague label. Reviews that take longer than ten minutes to read are rarely read in full.
What is the difference between a performance review and continuous feedback?
A performance review is a structured, periodic summary of performance over a defined window, typically tied to ratings, compensation, or development plans. Continuous feedback is the ongoing, informal exchange of observations between managers and employees throughout the year. Reviews should contain no surprises if continuous feedback has been happening.
How do HR teams ensure performance reviews are consistent across managers?
Calibration sessions are the most reliable mechanism. Before reviews are shared with employees, managers compare ratings on a common set of people or competencies to surface scoring drift. Structured templates and real time analytics on rating distributions also help HR teams catch outliers before they become legal or morale problems.
Can performance review examples be used word for word?
They can be used as a starting framework, but effective reviews always include role-specific observations. A phrase bank gives you the structure and the opening; the specific behaviour, project, or outcome you insert is what makes it credible. Employees notice when language is generic, and it signals that the review was not taken seriously.
How do pulse surveys connect to performance reviews?
Pulse surveys capture employee sentiments between formal review cycles. When managers review that data before a performance conversation, they arrive with context about how an employee has been experiencing the work, not just how they have been performing it. That context changes the quality of the conversation significantly.
The reviews you avoid writing are the ones that cost you most
Every manager has a review they drafted at midnight, softened until it was barely recognisable, and filed with relief that it was done. Those are the reviews that do the most damage. The employee does not know where they stand. The manager has not had the conversation they needed to have. And the gap between what is written and what is real widens by another year.
The performance review examples in this guide are designed to make those conversations possible, not easier in the sense of more comfortable, but easier in the sense of having language ready when you need it. The hard conversations are the ones that change careers. They are also the ones that, when done well, make people feel genuinely seen by the people who manage them. That is not a soft outcome. It is one of the strongest drivers of employee engagement research has found, and it starts with a single well-constructed sentence.
If your team is trying to make performance review conversations more consistent, more grounded in evidence, and less dependent on individual manager skill, Kodecrew gives HR teams the infrastructure to make that happen - from continuous feedback collection and pulse surveys to real time analytics on how review cycles are actually running across the organisation.
