A good performance review example names what the person did, what it changed, and what they should do next. The examples below are organized the way managers actually get stuck: by rating level, by situation, and by the role being reviewed. Every one ends with a next step, because a review without one is just a report card. And since most gaps in a review are skill gaps, the strongest next steps come with training attached.

What Makes a Performance Review Example Useful?

A performance review example is a model comment that shows a manager how to describe someone's work in specific, fair terms. The useful ones share three parts.

• Behavior: what the person did, with a real instance. "Ran the vendor transition" beats "takes ownership."
• Impact: what it changed for the team, the customer, or the numbers.
• Next step: one thing to keep doing or start doing, with the training or support to do it.

Here's the difference in one line. Weak: "Needs to communicate better." Useful: "Status updates on the billing project arrived after decisions were made, so finance planned around old numbers twice. Next quarter, send a Friday update to the project channel, and we'll review the first two together in our one-on-one."

The second version is longer. It's also the only one the employee can act on.

Why the Wording Matters

Vague comments leave employees guessing, and most of them notice. In a Gartner survey of 2,947 employees and managers published in April 2026, only 39% of employees agreed their manager is effective at providing clear developmental feedback.

Managers tend to see it differently. Gallup reported in May 2024 that only 20% of employees say they receive feedback weekly, while about half of managers say they deliver it weekly. The review is where that gap shows up in writing.

That gap rarely comes from bad intent. It comes from managers who were promoted and never trained to write one, working from a blank box at 9pm the night before it's due.

Performance Review Examples by Rating Level

Rating labels mean nothing until the words behind them are consistent. These examples follow a common five-point scale. Rename the levels to match yours, and keep the logic: the higher the rating, the more the comment should name scope and influence, and the lower the rating, the more it should name a standard and a date.

Exceptional (far exceeds expectations)

• "Rebuilt our onboarding checklist without being asked, and new hires now reach full workload two weeks sooner. Next step: present the approach to the other team leads in March so it spreads past our team."
• "Became the person other teams call when a launch is at risk. Three cross-team launches shipped on time this year with your coordination. Next step: let's scope a formal program lead role for next year."
• "Coached two junior analysts until they could run the monthly forecast alone. Next step: write down how you did it so we can repeat it with the next hires."

Exceeds expectations

• "Hit every quarterly goal and closed the year 12% over target, with the cleanest pipeline notes on the team. Next step: take the lead on one renewal negotiation next quarter to build deal strategy experience."
• "Your written project briefs are the clearest we have, and people now reuse them as templates. Next step: run one planning meeting a month so the clarity shows up live, too."
• "Flagged the data quality problem in August, before it reached the board report. Next step: propose a monthly check so it doesn't depend on you spotting it."

Meets expectations

• "Delivers assigned work on time and to standard, and customers rate your tickets well. Next step: pick one recurring problem you see in tickets and bring a fix to our next one-on-one."
• "Reliable in team meetings and easy to work with across departments. Next step: lead the next retro so you build facilitation experience."
• "Your reports are accurate and complete. Next step: add a short 'what this means' summary at the top of each one, so leaders can act on them faster."

Partially meets expectations

• "Your analysis is strong, but four of nine deadlines this half slipped by more than a week. Next step: two coaching sessions on planning and prioritization this month, then we'll set deadlines together in Monday one-on-ones and check progress midweek through March."
• "Customers like working with you, but follow-up notes are often missing from the CRM, so handoffs break. Next step: notes logged within one business day of every call, which we'll review every two weeks."
• "You've learned the new system quickly, but you still route most decisions back to me. Next step: you own approvals under the team's spending limit starting this month. We'll practice the calls you're unsure about in our one-on-ones and debrief the first five together."

Does not meet expectations

• "The role requires closing support tickets within two business days. Over the last quarter, 40% of yours took longer than five. By April 30, the standard is 90% within two days, and we'll review the numbers weekly."
• "Three client deliverables this quarter went out with errors the client found first. Starting now, every deliverable gets a checklist review before it ships, and we'll check the error rate together at the end of each month."
• "Team members have raised concerns about dismissive comments in meetings, and I saw two of them myself in September. The expectation is respectful disagreement in every meeting. You'll work with a coach on handling disagreement in meetings, and we'll talk through specific situations in our weekly one-on-ones."

Notice what the lowest ratings do. They state the standard, the gap, the date, and how progress gets checked. Vague words at this level are unfair to the employee and leave no paper trail if things don't improve.

Performance Review Examples by Situation

Ratings don't cover the reviews that keep managers up at night. These do.

A new hire's first review

"You've picked up our tools and process faster than most new hires, and the team already trusts your work. In the next six months, I'd like you to own one project end to end. Let's choose it together this month."

A strong performer who wants a promotion

"Your results are clearly at the next level. The gap for a senior role is influence beyond our team: right now, other departments go through me to reach you. Next step: you'll represent us in the quarterly planning meeting, and we'll revisit the promotion case in six months against that goal." If the conversation turns to longer-term growth, use a career path conversation instead of a promise.

A steady performer who has plateaued

"Your work is dependable, and that matters. It's also the same scope as last year. What would you want to be better at a year from now? Let's put one stretch goal in your individual development plan and check it monthly."

Someone coming back from a hard quarter

"The first half of the year was hard, and I know some of it was outside your control. Since July, your on-time delivery is back to where it was last year. Next step: keep the weekly planning habit we started, and tell me early if workload starts to slip again."

A remote employee you rarely see work

"Your written updates are the best view I have of your work, and they're consistently clear. What I see less of is your input in live discussions. Next step: bring one recommendation to each team call this quarter."

An employee heading toward a performance improvement plan

"We've discussed response times in four one-on-ones since June, and they haven't improved. This review documents the expectation: 90% of client emails answered within one business day. If that standard isn't met by the end of next quarter, the next step is a formal performance improvement plan. I'll support you with weekly check-ins starting next Monday."

This post isn't legal advice. If a review may lead to a performance improvement plan or termination, have HR review the wording before it's shared.

Performance Review Examples for Managers

Reviewing a manager means judging how their team performs, not only their own output. These examples cover the people side of the job.

• Coaching: "Your team's skills grew this year because you made time to coach. Two of your reports were promoted. Next step: share your one-on-one format with the two newest managers."
• Delegation: "You're still doing work your team could own, and it shows in your late nights before deadlines. Next step: two coaching sessions on delegation, then hand off the weekly report and the vendor calls by the end of next month."
• Feedback: "Your team says they hear about problems at review time, not when they happen. Next step: complete feedback training this quarter, then give one piece of specific feedback to each person every two weeks, and we'll check in on how it's going."
• One-on-ones: "Your one-on-ones are consistent, and your team says they're useful. Next step: add a standing development question, using a simple one-on-one template, so growth doesn't wait for the annual review."
• Hiring: "Your last three hires are all ramping well, and your interview notes are the most thorough we receive. Next step: join the hiring panel for the new team lead role."
• Follow-through: "Development goals from last year's reviews were set and never revisited. This year, every goal on your team gets a checkpoint at the halfway mark, and we'll review progress in our one-on-ones."

If several managers would get that last comment, the problem isn't one manager. It's how your company trains them.

Rewrite Weak Comments: Before and After

Most weak comments are fine instincts with the specifics missing. Here's how five common ones change.

• Before: "Great team player." After: "Stepped in to cover two colleagues' accounts during the June leave without a drop in response time."
• Before: "Needs to be more proactive." After: "Flags problems once they've already affected the client. Next step: raise risks in our Monday check-in, even if you're unsure."
• Before: "Good attitude." After: "Took the reorganization in stride and helped two newer teammates adjust to the new process."
• Before: "Should work on time management." After: "Three of five Q3 reports were late. Next step: block two hours each Thursday for report work, starting this week."
• Before: "Not a leader yet." After: "Your peers rely on your expertise, and you haven't yet led a group decision. Next step: run the next tool evaluation from kickoff to recommendation."

Turn Every Growth Area Into a Training Plan

Most low ratings point to a skill, not a character flaw. Name the skill, and the next step becomes training instead of a warning.

Here's how common review findings map to the skill behind them and the training that builds it.

• Missed deadlines: the skill is planning and prioritization. Train it with a weekly planning routine practiced alongside a coach, then review the plan in one-on-ones.
• Late or unclear updates: the skill is written communication. Train it by rewriting two real updates with feedback, then checking the next five.
• Tension with peers: the skill is handling disagreement. Train it by rehearsing the next hard conversation before it happens.
• Decisions routed upward: the skill is judgment and ownership. Train it with clear decision rights and a debrief after the first few calls.
• Managers who give vague feedback: the skill is feedback. Train it with practice on real situations from the manager's own team.
• Managers doing their team's work: the skill is delegation. Train it by choosing what to hand off, practicing the handoff, and checking the result.

Then write it into the review in three lines.

1. The skill: "Planning and prioritization."
2. The training: "Two coaching sessions this month, then a weekly plan reviewed in our Monday one-on-ones."
3. The check: "At our next check-in, we'll compare deadlines met against last quarter."

This is where most review processes break. The review names the gap, and nobody schedules the training to close it. Put the training on the calendar in the same meeting, and the next review has something real to measure.

Phrases to Avoid in a Performance Review

Some phrases sound harmless and cause real trouble. Cut these on sight.

• Personality labels such as "abrasive" or "not a culture fit." Describe the behavior instead.
• Comparisons to coworkers such as "not as fast as Dana." Compare to the standard.
• Absolutes such as "always" and "never." One counterexample undoes the whole comment.
• Comments on age, health, family or other personal traits. They're unfair, and they create legal risk.
• Praise with no evidence such as "rock solid" or "amazing." It feels kind and can't support a raise or promotion.
• Surprises. If the review is the first time someone hears about a problem, the comment isn't the issue. The year of silence is.

Give Managers a One-Page Guide, Not a Phrase Bank

A phrase bank helps one manager write one review. If you lead HR, the bigger risk is ten managers using the same rating to mean ten different things. A one-page guide fixes that. Here's a version you can copy into your review instructions.

1. Define each rating in one sentence. For example, "Meets expectations: does the full job to standard, with normal support."
2. Require one real instance per rating. A project, a date, or a number. No instance, no rating.
3. Require one next step per review. Who does what by when, and which training or coaching comes with it.
4. Ban the top five vague phrases you see most in your own reviews. Pull them from last cycle.
5. Check a sample before reviews go out. Read five reviews per manager and compare the language against the ratings.
6. Put the next steps on the calendar. Each one gets a checkpoint in the next three one-on-ones.

Step six is the one most companies skip, and it's the one that decides whether the review matters.

Better Wording Won't Save a Review Nobody Follows Up On

Better comments are worth the effort. Specific wording is fairer, easier to defend, and easier to act on.

But a well-written review that sits in a drawer still changes nothing. The comment is the start of the work, not the end of it. What matters is whether the next step happens, and whether the person gets the training to take it.

Running that kind of review is a skill too, for the manager. Skills improve with practice: across more than 5,000 Bundle session reviews, 81% of learners say they apply the skills. Reviews improve the same way. A manager rehearses the hard conversation, gets feedback, and tries again with a real employee.

Performance Review Examples FAQ

How many comments should a performance review include?

Three to five specific comments usually beat ten vague ones. Cover the person's biggest contribution, their most important growth area, and one next step. If your form has a box for every competency, keep the minor ones to a sentence.

How do you write "does not meet expectations" comments?

State the standard, the evidence, the date for improvement, and how progress will be checked. Keep it about the work, not the person. Have HR read it before it's shared.

Should the comments match the rating?

Yes. A "meets expectations" rating with glowing comments, or a high rating with only criticism, confuses the employee and weakens your records. Read the comments alone and ask whether they would lead someone to the same rating.

What should happen after a performance review?

Turn the main growth area into a training plan: name the skill, choose the format, such as coaching, a short course or practice with a peer, and book the check-in where you'll look for progress. Do it before the meeting ends, while both people agree on the gap.

Is it fine for managers to copy review phrases?

Copying a structure is fine. Copying the words without adding a real instance produces the same empty review in nicer language. Use the examples as a pattern, then fill in what actually happened.

Make the Next Step the Point

The best review comment is the one that changes what happens next week. Bundle connects what a review finds to the training that closes the gap, starting with live 1:1 manager training that helps managers run reviews like these, one real review at a time.