Biswashree Roy
BLOG / Performance Management
Performance Review Examples, Comments & Phrases
Written by:
Performance Review Calibrations Made Easy
Performance review calibration aligns manager ratings, prevents bias, and ensures consistent fairness across your organization.
Download Your Free Guide
August 27, 2026
TL;DR
- Every example on this page follows one structure: name the behavior, point to evidence, state the impact, set a next step.
- 72 phrases across nine competencies, each split into strong performance, meets expectations and needs improvement, so you can write a balanced review at any rating level.
- Five complete review summaries covering high performers, solid performers, improvement cases, new hires and managers.
- Twelve weak comments rewritten side by side, with the reason each original fails.
- Run every phrase through the 5-point personalization check before it goes in the form.
This is a working library of performance review examples, comments and phrases you can adapt in minutes. Every phrase below follows the same structure: name the behavior, point to evidence, state the impact, then set a next step. Copy the wording that fits, swap in the employee’s real work, and you have a review comment that holds up in a conversation. If you need the full review process rather than the wording, start with our guide to employee performance reviews. If you are looking for review terminology used in appraisal forms, the same phrases work for performance evaluation and performance appraisal examples.
Every example on this page follows the same four-part formula: name the behavior, point to the evidence, state the impact, then set a next step.
For example: “You rewrote the onboarding checklist (behavior) after three new hires missed the same two steps in Q2 (evidence), and no new hire has missed them since (impact). Take the same pass at the contractor onboarding flow this quarter (next step).”
Jump to a category
Examples by competency
Communication Goals & Results Leadership & Teamwork Accountability Problem-Solving Time & Productivity Quality of Work Job Knowledge & Initiative Customer Focus & Dependability
Other sections
How to Use These Performance Review Examples
Performance review examples are starting points, not finished reviews. A phrase becomes useful the moment you attach it to something the person actually did. Before you paste anything, pull up the evidence you already have: goal progress, project outcomes, peer feedback, support tickets, code reviews, deal notes, whatever your team produces.
Then work through each phrase in three passes. First, replace every generic noun with the real project, client or metric. Second, add a timeframe so the comment is anchored to the review period rather than to a general impression. Third, check that the comment ends with something the employee can act on. A review comment with no next step reads as a verdict, and verdicts are what make reviews feel like judgment instead of coaching.
Each competency below is split into three performance levels so you can write a balanced review across a rating scale: strong performance, meets expectations and needs improvement. Most managers only have language for the top and the bottom, which is why solid performers so often get vague reviews.
Performance Review Examples by Competency
Below are 72 performance review phrases across nine competencies. Each competency covers all three performance levels, so you can use the same page whether you are writing up your strongest engineer or documenting a performance concern.
Communication and Interpersonal Skills
Communication comments go wrong when they describe personality instead of behavior. Point to a specific message, meeting or handoff, then say what it changed.
Strong performance
- In the last two quarterly planning sessions, you turned a 40-page requirements doc into a one-page summary the sales team could act on, which cut the number of clarification requests to almost zero.
- You consistently flag blockers in the daily standup before they affect anyone else’s work, which has kept three dependent workstreams on schedule this quarter.
- When the client escalated in June, you restated their concern back to them before responding, and the conversation moved from complaint to solution within one call.
Meets expectations
- Your written updates are clear and land on time, and stakeholders rarely need to follow up for detail.
- You contribute in team meetings and answer questions directly, though you tend to wait for a prompt rather than raising items yourself.
Needs improvement
- Project updates in the last two launches arrived after dependencies had already changed, which caused rework for the design team. Send a short weekly status note every Thursday so downstream teams can adjust earlier.
- In cross-functional meetings you answer the question you expected rather than the one asked. Take ten seconds to restate the question before responding, starting with next month’s roadmap reviews.
- Three of your last five handoff documents left out the acceptance criteria, and the QA team had to reconstruct them. Use the shared handoff template for every ticket you pass on this quarter.
Goals and Results
Results comments should reference the goal as it was written at the start of the cycle, not as you remember it. If the target moved, say so.
Strong performance
- You closed the year at 118 percent of your pipeline target while keeping the average deal cycle flat, which means the growth came from throughput rather than from discounting.
- You broke the migration goal into four milestones with named owners, and all four landed within a week of their planned date.
- When the Q3 target was raised mid-cycle, you renegotiated scope with the stakeholder instead of quietly absorbing it, and the revised goal was still met.
Meets expectations
- You met four of your five goals for the year, and the fifth was blocked by a vendor delay outside your control.
- Your goals are clearly written and measurable, though progress updates tend to appear only near the deadline.
Needs improvement
- Two of your four goals this cycle had no measurable outcome attached, so it is hard to say whether they were met. Rewrite each goal with a number and a date before the next cycle opens.
- Goal progress was updated twice in six months, both times in the final two weeks. Update progress at the end of each month so blockers surface while there is still time to act.
- You take on new commitments before closing existing ones, and three goals carried over from the previous cycle. Before accepting new work, confirm with me which existing goal moves down the list.
Leadership and Teamwork
Leadership language applies to anyone who influences how work gets done, not only to people with direct reports. Teamwork comments should describe a specific collaboration, not a general disposition.
Strong performance
- You ran the incident review in May without assigning blame, and the two process changes that came out of it have prevented a repeat of the same failure.
- You handed the customer onboarding project to a newer teammate with a clear brief and a weekly check-in, and they delivered it on time while you stayed available rather than taking it back.
- You surfaced a disagreement between engineering and support early rather than letting it sit, and the shared triage rule you proposed is now used by both teams.
Meets expectations
- You support teammates when asked and share context readily, and your handoffs are reliable.
- You take part in team decisions and follow through on what is agreed, though you rarely put forward an alternative when you disagree.
Needs improvement
- Decisions on your project were made in one-to-one conversations and announced to the team afterwards, which left two engineers rebuilding work they had already started. Bring scope decisions to the weekly team sync before they are final.
- You take on the hardest parts of every project yourself, which limits how quickly the rest of the team develops. Assign one meaningful piece of the next project to someone else and coach them through it.
- Feedback to your reports has been positive but general, and two of them said they were unclear on what to improve. Use a specific example and a next step in every one-to-one this quarter.
Accountability and Ownership
Accountability comments are the easiest to make sound punitive. Describe what happened and what you expect next, and leave out words like ‘always’ and ‘never’.
Strong performance
- When the pricing page shipped with the wrong tier, you flagged it yourself within the hour, published a fix, and wrote up what went wrong before anyone asked.
- You own the reporting pipeline end to end, including the parts nobody assigned you, and it has not missed a delivery window in twelve months.
- You raised your own risk of missing the September deadline six weeks out, which gave us time to re-scope rather than slip.
Meets expectations
- You complete what you commit to and let people know when something is at risk, usually with enough notice to adjust.
- You follow the team’s process consistently, though you tend to wait for direction on work that sits between two owners.
Needs improvement
- When the reconciliation errors were found in July, the first response was to point to the upstream data feed. Even when the cause is elsewhere, own the outcome and bring the proposed fix to the conversation.
- Three deadlines slipped this cycle and I heard about each one after the date had passed. Raise a slipping date as soon as you know, not after it lands.
- Work that falls between your role and the analytics team’s has stalled twice this year. Where ownership is unclear, take the first step and name the gap rather than waiting for it to be assigned.
Problem-Solving and Adaptability
Adaptability is often written as a personality trait. Anchor it instead to a specific change and what the person did in the two weeks after it.
Strong performance
- When the vendor deprecated the API with four weeks’ notice, you mapped every affected integration, sequenced the migration by risk, and finished with a week to spare.
- You traced the checkout failures back to a caching rule rather than accepting the surface explanation, which fixed a problem that had been reappearing for months.
- After the team restructure in April you rebuilt your working relationships with the new stakeholders within a month, and delivery did not dip.
Meets expectations
- You handle changes to priorities without disruption and ask clarifying questions early.
- You work through routine problems independently and escalate the genuinely ambiguous ones, though you sometimes escalate later than would be useful.
Needs improvement
- Recurring issues get resolved individually rather than traced to a common cause, and the same export bug was fixed three separate times. When an issue repeats, write up the pattern before fixing the instance.
- Changes to the roadmap tend to stall your work for a week or more while you wait for full clarity. Start on the parts that are settled and flag the open questions in writing.
- You reach for the approach that worked last time even where the constraints have changed, as with the batch job design in Q2. Sketch two options before committing to one on your next significant piece of work.
Time Management and Productivity
Productivity comments should reference output and reliability, not hours visible online. These performance review phrases for productivity and quality of work focus on what shipped and when.
Strong performance
- You cleared 34 support escalations last quarter, the highest on the team, and your reopen rate was the lowest at under 4 percent.
- You restructured your week around two protected build blocks, and cycle time on your tickets dropped by roughly a third without any change in scope.
- You have hit every sprint commitment for three consecutive quarters, including the two sprints that lost a week to the office move.
Meets expectations
- You deliver your committed work within the sprint and give notice when something will carry over.
- Your output is steady and predictable, though the largest tasks tend to land in the final days of the cycle.
Needs improvement
- Four of the last six deliverables arrived on the deadline day rather than ahead of it, which left no room for review. Aim to have a reviewable version two working days before the due date.
- Time goes to whichever request arrived most recently, and two planned pieces of work slipped as a result. Rank your week on Monday and treat anything new as a trade against that list.
- You take on requests from other teams without checking capacity, and your own roadmap items slipped twice this cycle. Route inbound requests through me before committing to a date.
Quality of Work and Attention to Detail
Quality of work performance review phrases work best when they cite a defect rate, a rework count or a review outcome rather than an adjective.
Strong performance
- Your last eleven pull requests were merged without a correctness change requested, which is well above the team’s average and has sped up everyone’s review queue.
- The board deck you built in January needed no factual corrections from finance, which had not happened in the previous four quarters.
- You added validation to the intake form after spotting the pattern in bad records, and data quality complaints from the analytics team have stopped.
Meets expectations
- Your work meets the standard and rarely needs correction, and you check your own output before handing it over.
- Deliverables are accurate on the substance, though formatting and naming conventions are inconsistent across documents.
Needs improvement
- Three client-facing documents went out this quarter with figures that did not match the source report. Reconcile every number against the source before sending, and have a second reader on anything client-facing.
- Speed on your tickets is strong, but the rework rate is roughly one in four. Slow down on the final check and treat the reopen rate as part of the delivery, not as a separate issue.
- Edge cases are handled inconsistently across your modules, and two production incidents traced back to unhandled null values. Add the team’s standard input checks to every new function this quarter.
Job Knowledge, Initiative and Learning
Job knowledge performance review phrases should reference what the person can now do that they could not before, or what the team relies on them for.
Strong performance
- You became the team’s reference point for the billing logic after documenting it during the audit, and three other engineers now resolve billing questions without escalating.
- You learned the reporting stack outside your own remit and used it to answer the pricing question that had been open with finance for two months.
- You proposed the automated reconciliation check without being asked and built it in your own planning slack, and it now catches errors before month-end close.
Meets expectations
- You know your area well and answer questions accurately, and you keep up with the changes that affect your work.
- You complete required training on time and apply it, though you tend to wait for formal training rather than seeking out what you need.
Needs improvement
- Questions about the new API version still come back to the previous owner, six months after handover. Work through the integration guide and take the next three support questions yourself.
- You apply the process correctly but rarely question whether it still fits, and the manual export step has continued long after the tool that needed it was retired. Bring one process you would change to each monthly review.
- Your depth in your own area is strong, but gaps show at the handoff points with data engineering. Spend one hour a fortnight with that team this quarter and document what you learn.
Customer Focus, Dependability and Professionalism
These comments cover the behaviors that show up in how someone treats customers and colleagues day to day, including reliability and conduct.
Strong performance
- You held the renewal conversation with the unhappy enterprise account yourself rather than routing it to support, and the account renewed at the same value.
- Your response time on customer escalations has stayed under two hours for the full year, including through the two weeks your teammate was out.
- When the outage hit, you sent the first customer update within twenty minutes and kept the cadence hourly until resolution, and we received no complaints about communication.
Meets expectations
- Customers get accurate answers from you and escalations are handled within the agreed window.
- You are reliable on attendance and commitments, and colleagues can plan around you.
Needs improvement
- Customer replies are accurate but read as templated, and two accounts said they felt processed rather than heard. Open each reply by naming their specific situation before moving to the answer.
- You resolve the ticket in front of you without checking whether the underlying issue will bring the customer back. Add a root cause note to every escalation you close this quarter.
- In two cross-team discussions this year the disagreement became personal in tone. Keep the critique on the decision and raise anything about a person with me directly.
Complete Performance Review Summary Examples
Sentence-level phrases cover the individual boxes on a review form. The overall summary is a different job: it has to say where the person stands, why, and what happens next, in a paragraph the employee could read six months later and still act on. Below are five complete performance review summary examples covering the situations most managers write for. Each one runs 100 to 160 words, which is long enough to carry evidence and short enough that people actually read it.
High performer Senior product designer, annual review
Priya had the strongest year on the design team. She led the checkout redesign end to end, ran the usability sessions herself rather than delegating them, and shipped the final flow two weeks ahead of the committed date. The redesign reduced support tickets about payment errors by roughly half in the first month after launch. Beyond her own work, she rebuilt the component library documentation, which two new designers used to get productive in their first fortnight instead of their second month. The one area to push on is scope: Priya takes on adjacent problems that are not hers to solve, which is generous but concentrates knowledge in one place. Next cycle, I would like her to hand one significant workstream to a mid-level designer and coach it rather than run it.
Solid performer Account manager, mid-year review
Daniel delivered a consistent half-year. He retained all eleven accounts in his book, closed two expansions worth a combined 60,000 dollars in annual value, and kept his quarterly business reviews on schedule with every account. Clients describe him as responsive and straightforward, and there have been no escalations from his portfolio this period. Where there is room to grow is depth: his account plans document what the client asked for, but not what the client is trying to achieve behind the request. That limits how early he can spot an expansion or a risk. For the second half, Daniel will rewrite three account plans to include the client’s own business goals for the year, and bring one of them to our monthly review to talk through the difference it makes.
Improvement needed Operations analyst, annual review
Sam’s technical work is accurate, and the recurring monthly reports have gone out on time all year. The concern this cycle is scope and initiative rather than quality. Three of Sam’s five goals had no measurable outcome attached, so we cannot say whether they were met, and two pieces of analysis were delivered after the decision they were meant to inform had already been made. When priorities shifted in Q2, work paused for close to two weeks while full clarity was sought rather than starting on the settled parts. None of this is a capability question. For the coming cycle, every goal needs a number and a date, progress gets updated at month end, and any delivery at risk of slipping past its decision point gets raised the week it becomes visible. We will review progress monthly rather than quarterly.
New employee Software engineer, 90-day review
Aisha joined in May and has moved through onboarding faster than expected. She shipped her first production change in week two, and by week six she was picking up tickets from the general queue without needing them scoped for her. Her pull requests are small and well described, and reviewers have asked for correctness changes on only two of her fourteen submissions. She asks clarifying questions early, which has saved rework more than once. The natural next step is breadth: her work so far has stayed inside the billing service, and the handoff points with the data pipeline are where most of our incidents originate. Over the next quarter Aisha will take one cross-service ticket per sprint and pair with a data engineer on the first two.
Manager or team lead Engineering manager, annual review
Marcus took over a team of six mid-year during a difficult period and stabilized it. Voluntary attrition on his team went to zero after two departures in the preceding six months, and sprint predictability moved from roughly 60 percent of committed work delivered to consistently above 85. He runs one-to-ones weekly without cancelling them, and his reports say they know where they stand. Delivery decisions are the area to work on. Scope calls are still made in one-to-one conversations and communicated afterwards, which has twice led to duplicated work. Marcus also carries too much of the hardest technical work himself, which is why two of his engineers have not grown into it. Next year: scope decisions come to the team sync before they are final, and one significant technical workstream per quarter goes to a report with Marcus coaching rather than building.
Why the improvement-needed summary works
Read the Sam example again and notice what it does not do. It never uses the word underperformer, it opens by naming what is working, and every concern is tied to a countable fact: three goals without measures, two late analyses, two weeks paused. The closing paragraph is a set of instructions, not a warning. That structure is what makes a difficult review defensible if it is ever revisited, and readable enough that the employee can act on it the same week.
Writing 40 reviews from a blank page?
Peoplebox pulls each person’s goals, project updates and peer feedback into the review form, so you start from evidence instead of memory. And when a comment comes out vague, Nova AI rewrites it into specific, behavior-based feedback without you leaving the form.
Nova AI rewrites a half-written review comment in place, inside the review form.
Weak vs Better Performance Review Comments
Most weak review comments fail the same way: they describe the person instead of the work. The rewrites below apply the behavior, evidence, impact and next step structure to twelve comments managers write most often. Read the middle column first, because naming the problem is what stops the same phrase reappearing next cycle.
| Weak comment | What is wrong with it | Better comment |
|---|---|---|
| She has a great attitude. | Personality trait, no behavior, nothing to act on. | When the release slipped, you rewrote the customer comms yourself rather than escalating, and the account did not churn. Keep taking that first pass on customer-facing messages. |
| Needs to improve communication. | Names a category, not a behavior, and gives no evidence or next step. | Status updates on the last two launches arrived after dependencies changed, which caused rework. Send a weekly Thursday note so downstream teams can adjust earlier. |
| Consistently exceeds expectations. | Rating language repeated as a comment; adds no information the score did not carry. | You delivered all four milestones on the migration ahead of schedule and absorbed the vendor delay without moving the launch date. |
| Not a team player. | Judgment about the person rather than a description of what happened. | In the last two sprint plannings, decisions on your workstream were shared after they were made, and two engineers rebuilt work. Bring scope calls to the sync before they are final. |
| Is very detail oriented. | Adjective with no evidence; equally true of most people on the team. | Your last eleven pull requests merged with no correctness changes requested, against a team average of roughly six. |
| Struggles with time management. | Vague and slightly personal; the employee cannot tell what to change. | Four of six deliverables landed on the deadline day, leaving no review window. Have a reviewable version ready two working days early. |
| Great job this year. | No specifics, so it does not survive as a record or help at promotion time. | You closed the year at 118 percent of pipeline target with a flat deal cycle, so the growth came from throughput rather than discounting. |
| Sometimes drops the ball. | Hedged, unmeasurable, and reads worse than a direct statement. | Three deadlines slipped this cycle and each was raised after the date passed. Flag a slipping date as soon as you know it. |
| Needs to be more proactive. | Corporate shorthand that means something different to every reader. | The manual export step continued for four months after the tool that needed it was retired. Bring one process you would change to each monthly review. |
| Lacks confidence in meetings. | Describes an inferred internal state rather than an observable behavior. | In the last three roadmap reviews you raised concerns after the meeting rather than in it. Put one open question on the agenda before each review this quarter. |
| Work quality is inconsistent. | States a pattern without the evidence that would make it fair. | The rework rate on your tickets is roughly one in four while throughput is high. Treat the reopen rate as part of delivery and slow down on the final check. |
| A pleasure to work with. | Social comment in a performance record; carries no assessment. | Colleagues route ambiguous customer issues to you because your write-ups let them pick the work up without a handoff call. |
Performance Review Examples for Specific Scenarios
The library above is written from a manager’s point of view for a standard review cycle. Some reviews need a different voice or a narrower set of language. Use these when the situation calls for it.
When colleagues review each other in a 360 cycle and need language that assesses collaboration without sounding like a manager.
Self performance review examples
When you are writing about your own work and need to claim results without overstating them. This is also where employees find what to say in a performance review.
Positive performance review comments
When the review is strong throughout and you need recognition language that stays specific instead of turning into praise.
Areas of improvement in performance reviews
When the improvement section is the hard part of the review and you need wording that is direct without being discouraging.
Performance review competency examples
When your form is built around a defined competency framework and comments have to map to named competencies and levels.
Constructive criticism examples
When you need the delivery, not just the wording: how to open a difficult conversation and keep it on the work.
If you are still deciding what kind of review to run, or which questions to put on the form, see types of performance reviews and our list of performance review questions.
How to Personalize Performance Review Phrases
A copied phrase reads as copied. Employees can tell, and so can anyone reviewing the review later. The fix is not to write everything from scratch, it is to run each phrase through the same five checks before it goes in the form. This takes about ninety seconds per comment and it is the difference between a review that lands and one that gets nodded through.
The 5-point personalization check
- Name the real thing. Replace “a project” with the project’s actual name, “a client” with the account, “the metric” with the number. If you cannot name it, you do not have evidence yet.
- Anchor it in time. “In Q2” or “over the last three sprints” tells the employee which period you are assessing and stops one bad week from coloring a whole year.
- State the effect on someone else. Impact is what makes a comment matter. Who was unblocked, who had to redo work, which customer noticed.
- End with an action, not a verdict. Every comment should be answerable. “Send a weekly status note” can be done. “Be more communicative” cannot.
- Check the absolutes. Delete “always”, “never” and “consistently fails”. They are almost never accurate and they turn a conversation about work into a defense of character.
One more habit worth building: write the improvement comments first, while you have the most patience for precision, and write the praise second. Managers who do it the other way round tend to spend their best wording on the easy paragraphs and run out of care by the time they reach the part that actually changes behavior.
How Performance Review Software Helps
The hardest part of writing a review is not the wording, it is reconstructing eleven months of work from memory two days before the deadline. That is where generic comments come from. Performance review software keeps goal progress, project updates and peer feedback attached to each person as the year goes, so the review form opens with evidence already in it. It also standardizes the cycle itself: the same questions, the same rating scale and the same deadlines for everyone, which is what makes reviews comparable at calibration time.
See performance reviews in Peoplebox
Run review cycles in Slack or Teams, with goals, one-to-one notes and 360 feedback already attached to every form. Fifteen minutes, no slide deck.
FAQs
What is an example of a good performance review comment?
A good performance review comment names a behavior, points to evidence, states the impact and ends with a next step. For example: “Project updates on the last two launches arrived after dependencies had already changed, which caused rework for the design team. Send a short weekly status note every Thursday so downstream teams can adjust earlier.” Compare that with “needs to improve communication”, which names a category rather than a behavior and gives the employee nothing to act on.
How do I make performance review comments specific?
Replace every generic noun with a real one. Swap “a project” for the project’s name, “a client” for the account, “the metric” for the number. Add a timeframe such as “in Q2” or “over the last three sprints” so the comment is anchored to the review period. Then name who was affected: who was unblocked, who had to redo work, which customer noticed. If you cannot fill in those details, you do not have enough evidence to write the comment yet.
How long should a performance review comment be?
For an individual competency or rating box, two to three sentences is usually right: one for the behavior and evidence, one for the impact, one for the next step. Overall summaries should run 100 to 160 words. Longer than that and people skim past the part that matters. Shorter than a full sentence and the comment reads as a rating repeated in words, which adds nothing the score did not already carry.
What should I write in a performance review summary?
Open with where the person stands overall, then give two or three pieces of evidence that support it, then name the single area you want them to work on and what they should do about it. Keep it to 100 to 160 words. Avoid opening with a rating word like “exceeds” or “underperforms”, because the summary should explain the rating rather than restate it. See the five complete summary examples on this page for high performers, solid performers, improvement cases, new hires and managers.
How do I write constructive performance review feedback without demotivating someone?
Keep the comment on the work and off the person, cite something countable rather than a general impression, and end with an instruction the employee can carry out. Delete absolutes such as “always” and “never”, which are rarely accurate and push the conversation into a defense of character. It also helps to write the improvement comments first, while you still have the patience to be precise, and the praise second.
What can an employee say in their own performance review?
Use the same structure managers use: what you did, the evidence, the effect it had, and what you plan to do next. Claim outcomes rather than effort, and give numbers where you have them. Name one area you want to develop and what you are already doing about it, since a self review with no growth area reads as defensive. For wording written from the employee’s point of view, see our self performance review examples.
How do I avoid bias and generic wording in performance reviews?
Generic wording and bias tend to travel together, because vague criteria leave room for impressions to fill the gap. Write from evidence you collected during the period rather than from the last few weeks, use the same competency definitions for everyone on the team, and check that a comment could not be swapped between two employees without anyone noticing. If it could, it is describing a personality rather than performance.
TABLE OF CONTENTS
RELEVANT ARTICLES
Our Customers Love us
