Performance Review Examples: Phrases That Say Something Real

The sentence that ruins most performance reviews is not a harsh one. It is this: "Continues to be a strong contributor and is well regarded across the team."

Nobody can argue with it. Nobody can do anything with it either.

You wrote it that way for a reason. A review gets read by HR, by your manager, by a calibration panel, possibly by a lawyer two years from now. So you write for the reader who might dispute it, and the person it is about ends up holding a page that contains no information.

The fix is not writing harsher. It is writing checkable. Here are the phrases, band by band, hollow version next to real one, and the conversation that has to carry them.

A review is either defensible or useful, and most people pick wrong

There is one test. Read a sentence and ask: if this is true, what does the person do differently on Monday? "Strong communicator" fails it. "Sends the weekly client update on Thursday with the revenue numbers filled in" passes.

Three tells that you are writing for the record instead of the person:

The hedge verb. "Continues to," "at times," "could benefit from." Each one shrinks a claim below what you actually think. If you would not say "at times" out loud to their face, do not write it.

The missing owner. "Deadlines were missed on the Hendricks account." By whom, and what did you do at the time? Passive voice in a review is a manager hiding from their own sentence.

The unfalsifiable compliment. "Great team player." No behavior underneath it, so nothing to repeat.

Nothing in the written review should be a surprise

A performance review is a summary. It is not a reveal, and it is not the moment you finally say the thing.

Break that rule and you lose the meeting twice. The person spends it litigating the process instead of the content, which is fair. And they lose the year: they cannot fix in December a problem you noticed in June.

If there is something in the draft they have never heard, do not soften the document to make the gap smaller. Say it out loud first, in a separate conversation, before the document exists.

Apologize once and move on. A second apology turns it into a meeting about your discomfort. If the pattern is bigger than one deliverable, that is the underperforming employee conversation, and it belongs before the review, not inside it.

Phrases by rating band, hollow and real

Every real version does three things: names the behavior, gives the evidence, states the effect. The band changes the news, not the structure.

Exceeds expectations

High ratings get written lazily, because vagueness is cheap when the news is good. Then this paragraph becomes the evidence in a promotion case and says nothing.

Hollow. "Devon is a rock star who consistently goes above and beyond for the team." Real. "Devon took over the payments migration when Priya left, three weeks in, and shipped it before the December freeze. That was a scope above his level, and it is why the freeze was not an incident."

Meets expectations

The hardest band to write, because people read "meets" as "disappointing" and managers write it apologetically, which confirms the fear. Say that the standard is the standard.

Hollow. "Solid year. No real complaints." Real. "Riley ran the monthly reporting cycle twelve times this year with no missed dates and no escalations from finance. That is the job, done reliably."

Write the growth line as the next band up, not as a flaw in this one: "What would move Riley up a band is owning something end to end that touches another team, the way the pricing refresh did. That is a scope gap, not a quality one." People hear the difference.

Needs improvement

Hollow. "Needs to improve communication and be more reliable with deadlines." Real. "Three of the last eight deliverables shipped after the agreed date. In each case I learned about it on the due date, not in advance. What the role requires is a flag as soon as a date is at risk."

Hollow. "Work quality has been inconsistent this year." Real. "Four of the last six client decks came back with numbers that did not match the source report. Two reached the client, and I rebuilt them the same night."

Does not meet expectations

This band should never be the first time, and it has to be unambiguous. The consequence is real, and hedged language hides it.

Hollow. "Performance has not been where we would like it to be this year, and there is work to do." Real. "Marcus did not meet the standard for this role this year. Four of his six accounts went into escalation, three for the same reason: renewals started inside the last two weeks. We opened a formal improvement plan on October 3, and this rating covers the period before it."

Behavior, results, and the thing you should not write about

Two of the three things you can write about are safe.

Behavior is what a camera would have recorded. Sent the update Thursday. Interrupted twice. Escalated before the client did.

Results are what changed because of it. Failed payments down from 4% to 1.2%. Two accounts saved. Renewal missed.

The third is personality, and it is where reviews go wrong. "Abrasive." "Lacks executive presence." "Not a culture fit." "Attitude problem."

Three reasons to keep those out. They are unfalsifiable: there is no version of next quarter in which someone demonstrates they are no longer abrasive. They are where bias lives, because the same behavior gets called "direct" in one person and "abrasive" in another. And review files get read later, in a dispute or a severance negotiation. This is not legal advice, but a file full of traits and empty of incidents tends to support the employee's account, not yours.

The translation is always the same: replace the trait with the incident that made you think it.

Instead of "Alex can be abrasive in meetings." Write "In the October planning meeting, Alex cut Dana off twice and called the estimate nonsense. Two people told me afterwards that they held back concerns for the rest of the session."

The second is harder to write, much harder to argue with, and the only one that can be fixed. More patterns for those sentences are in constructive feedback examples.

Running the meeting so the document is not the whole event

Send the written review 24 to 48 hours ahead. Handing it over in the room means the person reads and reacts at once, in front of you, and most people cope by going quiet. You will read that silence as agreement. It is not.

Then be quiet. The pause after a rating lasts as long as it takes them to decide to be honest. Fill it and you get agreement instead of information.

Aim to talk a third of the time. Close with one thing that changes and a date to check it, and carry that into the one-on-one that follows, not a folder you reopen next December.

Delivering a rating they will disagree with

People collapse two moves: listening, and changing your mind. You can do the first without the second, and this conversation depends on that.

Never soften the rating verbally while it stays the same on paper. Do that and the document says one thing while their manager says another, and when the consequence lands with no raise attached, they will quote you, correctly.

If you argued for a higher rating and lost, say so, without disowning the outcome.

When the self-review is two bands above yours

Someone rates themselves Exceeds. You are writing Meets. The instinct is to read that as ego. Read it as data.

They are measuring effort, you are measuring outcome. Hardest year of their career, ordinary results. Both true.

They are counting work you never saw. Support, unblocking other teams, the thing they fixed quietly in March. This is where you might be wrong.

You never told them. The most common, and the easiest to check. If nothing you said this year contradicts their self-rating, the gap is yours, and you say that before anything else.

Listen for whether the answers are about scope or effort. If the scope is real and you missed it, change the rating in writing. That costs nothing and buys a rating they believe next year. If the answers are all effort, say the harder sentence: "I believe how hard that was. The rating is about what changed, not about what it took."

Most of this is avoidable at the source. Tell people what a self-review is for before they write it: three things you owned, what changed because of each, what you want to own next year. That makes the gap visible in October, not December. The real fix is feedback all year, not a better form.

This does not work if the rating is decided by calibration and you are writing after the fact. In companies where the number comes out of a room full of managers, the review is a record of a decision, not the decision, and the honest version says which parts you argued for and lost. We did not measure how common that is: ask how your own cycle works before the writing starts.

The phrases are the easy half

Everything above can be written at your desk with the door closed. That is not the hard part.

The hard part is the four seconds after you say "the rating is Needs Improvement" to someone you have worked with for three years, while they look at you and say nothing. Or the moment they call it unfair and you feel yourself starting to agree just to end the discomfort. No phrase bank prepares you for that, because on the page nobody reacts.

Reading a sentence and saying it while your pulse is up are different skills. The second only comes from saying the words out loud, more than once, to someone who pushes back.