back

120 Performance Review Examples by Rating

Last Updated on August 25, 2026 by Status.net Editorial Team

This complete guide brings together example paragraphs, sample sentences, and full sample reviews across every common rating, tone, and outcome, so you can find the language you need for the situation in front of you.

If you have not yet, start with our complete guide “Performance Reviews: The Complete Guide.”

Part 1The 5-Level Rating System

The most common rating framework runs from 1 to 5, or from “Unsatisfactory” to “Exceeds Expectations.” Each level carries its own tone, its own vocabulary, and its own writing challenges. Below is a walk through each level, with example phrases you can adapt.

Level 5: Exceeds Expectations

Reserved for the small number of employees who consistently deliver beyond the scope of their role. Language at this level should sound confident and specific, while avoiding the empty superlatives that make top ratings feel generic.

Example phrases:

  • Sarah consistently exceeds expectations in her role as Senior Customer Success Manager, delivering measurable results across every key performance area this cycle.
  • James has established himself as one of the strongest performers on the team, with three flagship projects delivered ahead of schedule and above quality expectations.
  • Priya continues to raise the bar for technical excellence, and her code reviews are widely regarded as a benchmark by peers across the engineering organization.
  • Diego’s leadership of the enterprise renewal motion produced a 14-point lift in retention, well above the team’s stated target.
  • Mia consistently delivers work of exceptional quality and has become the go-to resource for cross-functional stakeholders when precision matters most.
  • Alex demonstrates the judgment and independence typically associated with the next level, and has already been operating in that capacity across several initiatives.
  • Yuki’s influence extends well beyond her immediate scope, evidenced by her mentorship of two junior team members who were promoted this year.
  • Rob’s work on the platform migration set a new standard for cross-team coordination, and stakeholders across three departments cited his leadership in their own reviews.

Level 4: Meets and Occasionally Exceeds Expectations

A strong rating for employees who consistently deliver, with several moments of standout performance. Language should highlight the pattern of solid work while calling out specific highlights.

Example phrases:

  • Kim consistently meets expectations across all core competencies and exceeded them in the Q3 launch, where she led cross-functional coordination between design and engineering.
  • Marcus has been a reliable contributor throughout the year, with especially strong work on the client onboarding redesign.
  • Elena delivers steady, high-quality output and has taken on several stretch responsibilities beyond her role description.
  • Terrell demonstrates strong technical fluency and continues to deepen his subject-matter expertise through active participation in the internal engineering guild.
  • Nadia consistently produces work that meets team standards, with the Q2 reporting redesign standing out as a clear example of her ability to elevate quality when it matters most.
  • Owen brings a steady, collaborative presence to every project he touches, and his contributions to the pricing analysis were widely recognized by peers.

Level 3: Meets Expectations

The most common rating, and often the hardest to write well. Language should feel affirming without inflating, and specific without being harsh.

Example phrases:

  • Chen meets expectations across the responsibilities of his role and demonstrates consistent, reliable performance in his day-to-day work.
  • Amaya delivers dependable results across her portfolio, with stakeholder feedback consistently rating her communication as clear and timely.
  • Jordan meets performance targets for the role and has shown steady progress in stakeholder management over the year.
  • Sana fulfills the requirements of her role with reliability, and her weekly reporting has become an anchor for team planning conversations.
  • Luis meets the standards of his role and has demonstrated a growing willingness to take on additional responsibilities within the team.
  • Ravi consistently completes his assigned work on time and to quality, and continues to build his subject-matter depth through hands-on project work.
  • Blake meets expectations across the core areas of the role, with steady contributions to team rituals and reliable follow-through on commitments.

Level 2: Needs Improvement

A rating that surfaces real gaps, most often in one or two focused areas rather than across the board. Language should be direct and specific, while pointing toward a clear path forward.

Example phrases:

  • Casey’s performance this cycle has fallen short of expectations in the area of project delivery, with three cross-functional deadlines missed in Q2 and Q3.
  • Riley demonstrates strong subject-matter knowledge, though gaps in stakeholder communication have limited the impact of her recent work.
  • Cameron has struggled to meet performance targets for the role, particularly around consistency of output during the middle stretches of each quarter.
  • Reese has shown effort and initiative in several areas, though follow-through on longer projects remains an area requiring improvement.
  • Sam’s technical work is solid, yet his ability to influence cross-team decisions has developed more slowly than the role requires at this stage.
  • Devon has demonstrated pockets of strong performance, though inconsistency across quarters has prevented the year from reaching the level expected in this role.

Level 1: Unsatisfactory

The most serious rating, reserved for sustained performance concerns that have already been raised and documented. Language should be factual, non-emotional, and firmly grounded in specific evidence.

Example phrases:

  • Taylor’s performance this cycle has been unsatisfactory in relation to the core responsibilities of the role, with sustained gaps across delivery, communication, and follow-through.
  • Documented concerns raised in the Q1 and Q3 check-ins have persisted through the review period, with limited evidence of sustained improvement.
  • Attendance and reliability have fallen below the standards expected for the role, and have been the subject of ongoing feedback throughout the cycle.
  • Repeated missed deadlines on client-facing deliverables have created downstream impact for the team and the customer.
  • Quality of work has not met the baseline expectations of the role, with rework required on the majority of recent deliverables.

Alternative Rating Scales You Might Encounter

Not every company uses this five-level structure. Depending on where you work, you might be writing against a three-level scale, a numeric scale of 1 to 10, a letter-grade system, or a rating-free model built entirely around narrative feedback and goal completion.

  • Three-level scales (often “Exceeds,” “Meets,” “Below”) compress the middle of the five-level system. The phrases in the “Meets Expectations” and “Meets and Occasionally Exceeds” sections above tend to collapse into one middle tier here, so the specificity within that tier carries more weight than trying to draw finer distinctions.
  • Numeric 1-10 scales usually map roughly onto the five-level system in pairs (1-2, 3-4, 5-6, 7-8, 9-10), though the exact cutoffs vary by company. Ask your HR partner or calibration lead for the mapping before you draft, since a “7” at one company can mean “solid performer” and at another can mean “exceeds expectations.”
  • Letter-grade systems (A through D, or A through F) borrow the emotional weight of academic grading, which means employees often react to a “C” more strongly than the equivalent “meets expectations” label. Adjust the surrounding narrative to soften that emotional gap if your evidence supports a genuinely solid year.
  • Goal- or OKR-based scoring ties the rating to percentage completion against stated objectives, for example, 0.7 out of 1.0. These systems reward specificity even more than traditional scales, since the narrative needs to explain exactly which goals were hit, partially hit, or missed.
  • Rating-free or narrative-only systems remove the number entirely and rely on the written review, a compensation recommendation, and a development conversation. If you work within one of these, the phrase patterns in the tone calibration section later in this guide become your primary calibration tool, since there is no number to anchor the message.

Whatever scale your organization uses, the underlying discipline stays the same: gather the evidence first, draft the narrative, and let the rating follow from what you have actually written.

For more, see “500 Performance Review Comments (by 5-Level Rating)” and “14 Examples of Performance Reviews (Good, Satisfactory, Poor).”

Part 2Positive Performance Reviews

An all-positive review is appropriate for a small number of employees in any given cycle. The bar should be high. When the year truly warrants it, positive language should feel earned and specific.

Example positive paragraphs:

  • Sarah has had a standout year as a Senior Customer Success Manager. She consistently exceeded her retention targets, delivered the enterprise health-score rollout ahead of schedule, and became a trusted mentor for two newer team members. Stakeholder feedback has been uniformly positive, with peers frequently describing her as calm, clear, and reliable under pressure.
  • James has established himself as one of the strongest technical contributors on the team. His leadership on the platform migration produced measurable performance gains and set a new benchmark for cross-team coordination. Colleagues consistently cite his code reviews as a model for constructive, growth-oriented feedback.
  • Priya continues to deliver work of exceptional quality across every project she owns. Her contributions to the pricing analysis are already shaping the company’s go-to-market strategy for the next fiscal year, and her mentorship of newer team members has been widely recognized.
  • Diego has emerged as a natural leader within the team. His willingness to take on stretch responsibilities, combined with his steady, calm presence during the reorganization, has made him a stabilizing force during a period of significant change.
  • Mia has delivered outstanding results across every quarter, most notably in the redesign of the reporting suite, which reduced average dashboard load times by 42 percent. Her attention to detail and craftsmanship are widely regarded as a benchmark by peers.
  • Alex has demonstrated the judgment, ownership, and influence typically associated with the next level of the career track. His work across the analytics function has consistently exceeded expectations in both depth and delivery.

Additional short positive phrases:

  • Consistently exceeds expectations across all core responsibilities of the role.
  • Delivers exceptional quality of work with a consistently high level of attention to detail.
  • Demonstrates strong ownership and follow-through on every commitment.
  • Trusted by peers and stakeholders across multiple functions as a reliable partner.
  • Sets a benchmark for professionalism and calm under pressure.
  • Shows strong strategic thinking and a clear ability to translate vision into execution.
  • Widely recognized for elevating the standards of the team through his own example.
  • Continues to invest in her professional growth and shares her learnings generously with the team.
  • Consistently produces work that requires little to no revision from stakeholders.
  • Regularly steps into leadership moments before being asked, and does so with humility.

A word of caution: the strongest positive reviews resist the pull toward generic praise. If a paragraph could be copied into any top performer’s review without changing a word, it has drifted too far from the specifics of this person’s year. Before finalizing a positive review, check it against a few questions:

  • Could this paragraph be mistaken for someone else’s review if the name were removed?
  • Does at least one sentence name a specific project, metric, or moment?
  • Would a colleague who worked closely with this person recognize the description?
  • Does the praise map to something the employee can point to and repeat next year?

Calibration conversations also tend to scrutinize top ratings more closely than any other tier, since they usually carry the largest compensation and promotion implications. A positive review backed by specific, verifiable evidence holds up far better in that conversation than one built on enthusiasm alone.

For more, see “10 Examples of Positive Employee Performance Reviews,” “195 Great Examples of Positive Performance Reviews Phrases,” and “60 Smart Examples: Positive Feedback for Manager in a Review.”

Part 3Negative Performance Reviews

Delivering hard feedback in writing calls for care. The most useful negative reviews are firm and specific, with the tone of a fair, respectful account rather than a personal indictment. Focus on behavior and impact. Avoid character labels.

Documentation matters more at this end of the rating scale. Every claim should be supported by a specific example, a date range, or a measurable pattern. If the review may inform a performance improvement plan or a termination decision, work closely with HR on the language.

Example negative paragraphs:

  • This cycle has been a challenging one for Casey. Three cross-functional deadlines were missed in Q2 and Q3, and the resulting rework was absorbed by the broader team. These patterns were raised in the Q2 and Q3 1:1 conversations, and progress in the second half of the year has been limited.
  • Riley’s technical skills remain a strength of the role, though gaps in stakeholder communication have significantly limited the impact of her recent work. Two of her most important projects this year stalled because updates were not shared with sponsors on the cadence the projects required.
  • Cameron has struggled to sustain the quality of work expected for this role. Q2 and Q3 deliverables required substantial revision from stakeholders, and pattern feedback from three peers has flagged concerns about consistency of output.
  • Reese has shown initiative in taking on new projects, though follow-through on longer commitments remains an area requiring significant improvement. Four projects opened in the first half of the year remained incomplete at the end of Q3.
  • Sam’s written work continues to meet the standards of the role, though his ability to influence cross-team decisions has developed more slowly than the seat requires. Two important initiatives this year proceeded without his active input during key decision points.
  • Devon has demonstrated pockets of strong performance during the year, though sustained inconsistency across quarters has prevented the year from reaching the level expected. Multiple 1:1 conversations have raised these concerns without a corresponding shift in behavior.
  All Job Interview Types & Formats: The Complete Guide

Additional short constructive phrases:

  • Delivery has fallen short of the standards expected for this role during the review period.
  • Consistency of output has been a recurring concern raised across multiple check-ins.
  • Stakeholder feedback has surfaced concerns regarding communication cadence and clarity.
  • Quality of work has required regular revision from managers and peers.
  • Follow-through on commitments has slipped on several high-visibility deliverables.
  • Cross-team collaboration remains an area with significant room for growth.
  • Response to feedback has been slower than the role expects at this stage.
  • The pattern of missed deadlines has created downstream impact for teammates and customers.
  • Ability to prioritize under pressure remains a documented area of concern.
  • Written communication with senior stakeholders has fallen short of the clarity the role requires.

A negative review lands better when every concern is paired with a next step. Naming the problem without naming the path forward leaves the employee with nowhere to put the feedback except discouragement. Consider structuring each concern with three parts:

  1. The pattern. What happened, how often, and over what period.
  2. The impact. Who or what was affected, in concrete terms.
  3. The support available. Coaching, resources, check-in cadence, or a formal improvement plan.

It also helps to read the draft aloud before sending it. Sentences that sound harsh when spoken usually read even harsher on the page. If a sentence would be difficult to say directly to the employee’s face in a calm tone, it probably needs another pass.

For more, see “10 Examples of Negative Employee Performance Reviews” and “30 Examples of Constructive Criticism: Negative Performance Review.”

Part 4Balanced Performance Reviews

Most employees land in balanced territory. Strengths and growth areas coexist in real proportion, and a well-written balanced review reflects both honestly.

The structure of a balanced review usually follows the six-section shape: opening, accomplishments, strengths, areas for improvement, goals, and summary. The key is calibration. If a strong performer has one honest growth area, the review should reflect the pattern of the year, with more weight on strengths and a clear, specific note on the growth area. A struggling performer with genuine bright spots deserves a review that names them while remaining clear about the concerns.

Example balanced paragraphs:

  • Jamie has had a solid year as an individual contributor. Her strongest work has been the reporting redesign, which shaped how the leadership team now reviews weekly metrics. The area with the most room to grow is stakeholder communication, where updates have sometimes been shared later than sponsors expected.
  • Marcus has delivered dependable work throughout the year, with especially strong contributions to the client onboarding project. Growth opportunities exist around scope management, where several projects expanded past their original boundaries and stretched the team’s capacity.
  • Elena has met expectations across the responsibilities of her role and shown a growing willingness to take on additional scope. The clearest area to keep building is verbal communication in larger meetings, where her ideas often surface later in writing rather than in the room.
  • Terrell continues to demonstrate strong technical fluency and steady output. The most important growth area for the year ahead is influence beyond his immediate team, particularly in shaping decisions across the broader engineering organization.
  • Nadia has delivered consistent work across her portfolio and shown standout contributions during the Q2 reporting redesign. The clearest growth area is time management under pressure, especially during quarter-end.
  • Owen has been a steady, collaborative presence throughout the year, with strong contributions to the pricing analysis and the client segmentation project. The area with the most room to grow is proactive leadership, particularly stepping into moments where the team would benefit from a clearer voice on the direction.

Additional short balanced phrases:

  • Delivers steady, reliable results across the responsibilities of the role, with clear opportunities for growth in stakeholder communication.
  • Demonstrates strong subject-matter expertise, with continued room to grow in cross-functional influence.
  • Consistently meets performance targets, and continues to build depth in strategic thinking.
  • Shows solid ownership of individual responsibilities, and is developing the ability to guide broader team direction.
  • Delivers dependable output, with several moments of standout performance in the Q3 launch and the year-end reporting cycle.
  • Balances speed and quality effectively in most projects, with room to sharpen prioritization under pressure.
  • Contributes meaningfully to team rituals and is developing the confidence to lead them.
  • Meets the standards of the role reliably, and shows early signs of readiness for greater scope.
  • Demonstrates strong collaborative instincts, with growth ahead in giving more direct written feedback to peers.
  • Consistently delivers thoughtful work, with continued opportunity to deepen strategic framing on complex projects.

Sequencing matters as much as word choice in a balanced review. Leading with strengths and closing with growth areas tends to help the employee stay open to the feedback that follows. Leading with the growth area and closing with strengths can work when the concern is the most important message of the review and you want it to land first, though this ordering carries a higher risk that the employee remembers only the criticism.

A useful gut check: read the review as if you were the employee receiving it for the first time. Does the overall impression match the rating you assigned? If the review reads as mostly critical but the rating says “meets expectations,” the proportion of strengths to growth areas probably needs adjusting.

For more, see “280 Examples of Balanced Performance Review Comments,” “100 Positive & Constructive Feedback Examples (Performance Review Phrases).”

Part 5Satisfactory or Meets Expectations Reviews

This is the most common rating on a healthy team, and it is often the hardest to write well. The trap is repetition. When every paragraph reads as some variation of “meets expectations” or “is a solid contributor,” the review becomes background noise. The employee finishes reading and cannot recall a single specific line about their year.

The way through is specificity. Even a “meets expectations” review can be memorable when each paragraph carries at least one concrete moment. The employee’s year had a shape, and the writing should reflect it.

Example satisfactory paragraphs:

  • Chen has met expectations across the responsibilities of his role this year. His weekly reporting has become a dependable anchor for team planning conversations, and his contributions to the Q3 onboarding refresh were consistently on time and on scope.
  • Amaya delivers reliable results across her portfolio. Stakeholder feedback has consistently rated her communication as clear and timely, and she took on the client segmentation refresh in Q2 without disrupting her existing commitments.
  • Jordan has met performance targets throughout the year and shown steady progress in stakeholder management. His handoffs on the platform migration were widely cited as smooth, particularly across the sales and product teams.
  • Sana fulfills the requirements of the role with reliability. Her contributions to the annual planning cycle stood out for their clarity, and her willingness to pick up small requests without friction has been a real support to the team.
  • Luis has met the standards of his role and demonstrated a growing willingness to take on additional responsibilities within the team. His work on the internal onboarding guide freed up meaningful capacity for the rest of the group.
  • Ravi consistently completes his work on time and to quality. His subject-matter depth has continued to grow through hands-on project work, and his contributions to the technical office hours have supported several newer team members.

Additional short satisfactory phrases:

  • Meets performance expectations across the core responsibilities of the role.
  • Delivers reliable, on-time work across the standard portfolio of responsibilities.
  • Consistently demonstrates the judgment and ownership expected of the role at this level.
  • Fulfills the requirements of the position with steady, dependable output.
  • Shows solid follow-through on commitments and reliable communication with stakeholders.
  • Continues to build strong working relationships across the team.
  • Demonstrates a clear understanding of the priorities of the role and the team.
  • Contributes meaningfully to team rituals and cross-functional projects.
  • Maintains a professional and collaborative approach in all interactions.
  • Delivers quality work within expected timelines and to expected standards.

A quick specificity check works well for this rating tier specifically, since it is the one most prone to sounding interchangeable across employees. For each paragraph, ask:

  • Is there a project name, a date, or a number somewhere in this paragraph?
  • Does the sentence describe something this employee did, rather than a trait they possess?
  • If I removed the employee’s name, would a teammate still be able to guess who this is about?

If a paragraph fails all three, it likely needs one more pass before it goes into the final review.

Part 6Unsatisfactory Performance and Documentation

Unsatisfactory ratings carry weight beyond the review itself. They often support difficult decisions later, including performance improvement plans, role changes, or termination. The writing needs to hold up to careful reading by HR, legal, and, sometimes, external counsel.

The tone should stay factual. Language should describe patterns rather than character, and every claim should be grounded in a specific example, date, or measurable outcome. Emotional or accusatory phrasing rarely survives a second read.

Example unsatisfactory paragraphs:

  • Taylor’s performance during this cycle has been unsatisfactory across the core responsibilities of the role. Concerns raised in the Q1 and Q3 check-in conversations, documented in the shared 1:1 notes, have persisted through the end of the review period with limited evidence of sustained improvement.
  • Sustained gaps in attendance and reliability have been raised in multiple written communications during the review period, most recently on August 4 and October 12. The pattern has continued past the timelines discussed in each conversation.
  • Repeated missed deadlines on client-facing deliverables during Q2 and Q3 created downstream impact for both the internal team and the customer. Specific instances were documented in the June and September performance conversations.
  • Quality of work has consistently fallen below the baseline expectations of the role. Deliverables required substantial revision by stakeholders in the majority of recent projects, including the June client review, the August strategy readout, and the October rollout.
  • Response to written feedback during the review period has been limited. Concerns raised in the mid-year conversation on July 9 were not addressed in the following quarter, and similar patterns emerged again during the October review.

Additional short documentation phrases:

  • Performance during this cycle has fallen short of the documented expectations of the role.
  • Concerns raised in prior check-ins have persisted through the review period.
  • The pattern of missed commitments has been documented across multiple written conversations.
  • Quality of work has required substantial revision on the majority of recent deliverables.
  • Stakeholder feedback has surfaced consistent concerns about follow-through and reliability.
  • Timelines and expectations set in prior performance conversations have not been met.
  • Progress against improvement targets outlined in the last check-in has been limited.

Strong documentation reads like a timeline rather than an argument. When you can, anchor each concern to a date, a specific conversation, or a written record that already exists, such as a prior review, a 1:1 note, or an email. This approach keeps the tone factual, and gives the employee a clear, verifiable account of what was raised and when.

A few habits make this easier over the course of the year, rather than scrambling to reconstruct it at review time:

  • Keep a running note after every 1:1 where a concern comes up, even briefly.
  • Note the date and the specific example, not just the general impression.
  • Record what support or coaching was offered at the time, alongside the problem itself.
  • Revisit the note at the next check-in to confirm whether the pattern continued or improved.

For more, see “5 Examples: Unsatisfactory Performance Letter to Employee.”

Part 7End-of-Year Reviews

End-of-year reviews carry the weight of the full arc of the year. They usually pair with compensation decisions and calibration across the organization, which raises the bar for specificity and fairness.

The strongest end-of-year reviews walk through the whole year, not just the recent months. They surface the shape of the year: the strongest quarters, the hardest stretches, the through-line that defined the twelve months.

Example end-of-year paragraphs:

  • Sarah closes the year having delivered against every one of her stated goals. Enterprise retention rose from 78 percent to 91 percent, the new client health-score model launched two weeks ahead of schedule, and two of her direct mentees have already been promoted into stretch roles.
  • James enters the new year having significantly deepened his technical influence. The platform migration, the reliability rework, and the mentorship of two junior engineers have collectively raised the technical bar of the entire team.
  • Priya’s year is best captured in the shift she has led across the analytics function. Her contributions to the pricing project alone are projected to lift ARR by 6 percent, and she has left the reporting function in stronger shape than she found it.
  • Diego closes the year having steadied the team through a difficult reorganization. His steady presence, combined with strong operational delivery, has contributed directly to the strongest engagement scores the team has recorded in three years.
  • Casey ends the year with real progress in the second half. After a difficult Q2 and Q3, her Q4 delivery met every stated goal, and her final project of the year was widely cited as a model for scope management.

Additional short year-end phrases:

  • Closes the year having exceeded every stated performance target.
  • Enters the new year having significantly deepened his technical influence.
  • The year is best captured in the shift she has led across her function.
  • Concludes the review period having met every core commitment.
  • Ends the year with real, measurable progress in the second half.
  • The year’s work has left the team in stronger shape than it began.
  • Consistent delivery across all four quarters set a benchmark for the team.
  • Enters the new year having grown visibly in stakeholder communication and cross-team leadership.
  The Complete Guide to Manager Performance Reviews

End-of-year reviews also tend to arrive during calibration season, when ratings across a team or department get compared and sometimes adjusted before they are finalized. A review with specific, well-documented evidence survives calibration far better than one built on general impressions, since the manager advocating for the rating needs concrete examples to make the case in the room.

It also helps to review the employee’s self-evaluation, if one exists, before finalizing your draft. Employees often surface accomplishments a manager forgot about over twelve months, and reconciling the two documents before the meeting avoids surprises in the conversation itself.

For more, see “10 End of Year Employee Review Examples.”

Part 8Mid-Year and Quarterly Review Examples

Mid-year and quarterly reviews serve a different purpose than the end-of-year review. They function as checkpoints along the way, offering a read on trajectory well before the final rating arrives at year-end.

Two habits separate a useful mid-year review from a wasted one:

  • Reference the goals set at the start of the period as the anchor for the conversation. If quarterly goals were set in January, the July check-in should explicitly measure progress against them.
  • Leave room for the story to change. A mid-year review functions as a progress check, with the final rating still ahead at year-end. Language that sounds too conclusive (“this has been a disappointing year”) can box in both the manager and the employee before the year is even half over.

Example mid-year and quarterly paragraphs:

  • Halfway through the year, Priya is tracking well against her Q1 goals, with the pricing analysis already ahead of its original timeline. The second half of the year should focus on translating that early momentum into the go-to-market rollout.
  • Marcus’s first two quarters have been steady, with the client onboarding redesign as the clear highlight. The remaining two quarters are a good opportunity to build more visibility with senior stakeholders, an area worth prioritizing before the year-end review.
  • Casey’s Q1 was below the standard expected for the role, with two missed deadlines on cross-functional deliverables. The conversation at this checkpoint should focus on what support is needed to change that pattern before it becomes the story of the full year.
  • Riley is on pace to meet her goals for the year, and her Q2 work on the client segmentation project has been a clear strength. Continued focus on proactive stakeholder updates would strengthen the second half of the year further.

Additional short mid-cycle phrases:

  • Tracking well against the goals set at the start of the period, with room to build further momentum in the second half.
  • Halfway through the cycle, performance has been steady, with one area worth focused attention before year-end.
  • Early progress on the stated goals suggests the year is on track to meet or exceed expectations.
  • This checkpoint surfaces a pattern worth addressing now, before it shapes the full-year rating.
  • The first half of the year has shown clear improvement in the area flagged during the previous check-in.

Part 9Reviews by Outcome: Promotion, Lateral, Stay, Exit

Reviews rarely exist in a vacuum. Each one usually supports a specific outcome: a promotion decision, a lateral move, a decision to keep the employee in place, or a difficult transition. The language should reflect the outcome the review is building toward.

Reviews That Signal Promotion Readiness

A strong promotion review does more than confirm that the employee has done well in the current role. It shows that the employee has already been operating at the next level, with specific examples of the judgment, ownership, and influence expected there.

Example promotion-readiness phrases:

  • Alex has consistently demonstrated the judgment, ownership, and influence typically associated with the Senior Manager level, and has been operating in that capacity across several key initiatives this year.
  • Yuki’s work this year meets and exceeds the expectations of the next level, with clear evidence of strategic thinking, cross-functional influence, and mentorship of newer team members.
  • Rob has repeatedly stepped into decisions that shape the team’s direction well beyond his current scope, and has done so with the calm and clarity expected of a Director.
  • Mia has delivered work at a level of quality, autonomy, and impact that reflects the expectations of the Staff Engineer role.
  • Diego has established himself as a natural leader within the team, and his readiness for a formal leadership role has been evident in both his delivery and his influence.

Reviews That Signal Solid Performance in the Current Role

For employees who are performing well and staying in the current seat, the review should affirm the strong pattern while pointing toward continued growth within the role.

Example stay-in-role phrases:

  • Chen continues to deliver reliable, high-quality work in his current role, with clear areas of continued growth ahead within the scope of the position.
  • Amaya remains a strong contributor within her current seat, and the year ahead offers opportunities to deepen her subject-matter expertise and stakeholder trust.
  • Jordan is well-placed to continue building depth in the current role, with a clear runway for continued impact through the coming year.

Reviews That Signal a Lateral Move or Change in Scope

Some reviews surface a strong performer whose talents would be better applied in a different function. The language should honor the current work while pointing to the shift.

Example lateral-move phrases:

  • Elena has shown consistent strength in her current role, and the pattern of her most impactful work suggests she would flourish in a more strategy-facing scope.
  • Terrell’s recent contributions to cross-functional projects have surfaced a strong interest and clear talent for product-facing work that would benefit from a formal shift in scope.
  • Owen’s strongest work this year has consistently sat at the intersection of analytics and business strategy, and a move toward a strategy-focused role would allow him to build on that pattern.

Reviews That Signal Performance Issues or Termination Considerations

The most sensitive category. Language should stay factual, grounded in documented evidence, and focused on patterns rather than character. Work closely with HR on the phrasing.

Example difficult-transition phrases:

  • Despite the support provided during the review period, including weekly check-ins and a written improvement plan initiated in July, the concerns raised in Q1 have persisted through the end of the cycle.
  • Sustained gaps across delivery, communication, and follow-through have created a clear pattern of performance below the baseline expectations of the role.
  • Progress against the improvement targets outlined in the July performance conversation has been limited, and the concerns raised at that time remain present at year-end.
  • Multiple written performance conversations during the review period have not produced sustained changes in the areas of documented concern.

Part 10Self-Evaluation Examples by Rating

Employees writing their own self-evaluations face a different challenge than managers. Understating accomplishments leaves a manager without the material needed to advocate for a strong rating. Overstating them risks a credibility gap once the manager’s view comes into the conversation. The strongest self-evaluations sit in between: confident, specific, and honest about growth areas without volunteering ammunition against the employee’s own case.

Self-Evaluation Language for a Strong Year

  • This year, I led the client health-score rollout from concept to launch two weeks ahead of schedule, and enterprise retention rose from 78 percent to 91 percent over the same period.
  • I took ownership of the platform migration end to end, coordinating across three teams and delivering the project with zero unplanned downtime.
  • I mentored two newer team members this year, both of whom have since taken on expanded responsibilities, which I see as a direct result of the coaching we did together.
  • My work on the pricing analysis is already shaping next year’s go-to-market strategy, and I would point to this as the clearest example of the impact I aim to have in this role.

Self-Evaluation Language for a Solid Year

  • I met the core goals set at the start of the year, with the Q3 onboarding refresh as the project I am most proud of.
  • My day-to-day work has stayed consistent and reliable throughout the year, and I have started taking on additional scope in the last two quarters.
  • I would describe this year as steady rather than standout, and I am looking for ways to take on more visible, higher-impact work in the year ahead.

Self-Evaluation Language for a Difficult Year

  • This year included some real challenges, particularly around meeting deadlines during Q2 and Q3. I have made changes to my workflow since our September conversation and want to build on that progress going forward.
  • I recognize that my communication with stakeholders was not consistent enough this year, and I am working on sharing updates earlier in a project’s life cycle.
  • I did not meet every goal I set at the start of the year, and I want to use this review to talk through what support would help me close that gap in the year ahead.

One habit worth building regardless of the year’s outcome: write the self-evaluation with the same discipline expected of a manager’s review. Name specific projects, use numbers where they exist, and avoid vague claims like “worked hard all year” that a manager cannot verify or act on.

Part 11Performance Review Examples by Role and Function

The core structure of a performance review stays consistent across roles, though the evidence that fills it looks different depending on the function. A sales review leans on numbers. An engineering review leans on code quality and system impact. A support review leans on resolution metrics and customer sentiment. A people-manager review has to account for the performance of an entire team, alongside individual output.

Sales Performance Review Language

  • Closed 118 percent of quota for the year, with the largest enterprise deal of the quarter closing two weeks ahead of the customer’s original timeline.
  • Pipeline generation has been consistently strong, though close rate on mid-market deals has room to improve relative to the team average.
  • Built a repeatable outreach process that two newer reps have since adopted, extending the impact of the work beyond individual quota attainment.

Engineering Performance Review Language

  • Shipped the reliability rework with zero regressions, and the resulting drop in on-call incidents has been noticed across the broader engineering organization.
  • Code review comments consistently model the kind of constructive, specific feedback the team aims to give one another.
  • Technical depth is strong, and the growth area for the year ahead is proactively surfacing architectural tradeoffs earlier in the design process, well before implementation begins.

Customer Support and Success Review Language

  • Maintained a customer satisfaction score above 96 percent for the third consecutive quarter, while handling a caseload above the team average.
  • First-response time has improved steadily throughout the year, and peer feedback consistently describes a calm, clear tone with frustrated customers.
  • Escalation handling remains an area for continued growth, particularly around looping in account teams earlier in at-risk situations.

People Manager Review Language

  • The team’s engagement score rose eight points this year, alongside two internal promotions that reflect the coaching invested in direct reports.
  • Delegation has improved visibly since the mid-year conversation, with three team members now owning workstreams that previously required direct involvement.
  • The growth area for the year ahead is giving more direct, timely feedback to underperforming team members as concerns arise, so problems surface well before formal review cycles begin.

Part 12New Employee and Probationary Period Reviews

Reviews written during the first 90 days, or during a formal probationary period, carry a different weight than an annual review. The employee has limited history, the evidence base is thin, and the review often informs a decision about whether the role is a fit at all. Language should acknowledge the short runway while still giving an honest read on trajectory.

Example new-employee review paragraphs:

  • In her first 90 days, Anya has ramped faster than the typical onboarding timeline for this role, already taking ownership of the weekly reporting process without close supervision.
  • Marcus has met the expectations set for a new hire at this stage, with strong early signs in his grasp of the product and his working relationships with the team.
  • The first quarter has surfaced a few gaps in technical readiness relative to what the role requires. A focused 30-day plan, with weekly check-ins, would give a clearer read on whether these gaps close with support and time.
  • Early performance has been mixed. Strengths in collaboration and communication are clear, while the core technical skills expected for this role have not yet been demonstrated at the level the position requires.

A few things to keep in mind when writing for this stage:

  • Compare the employee against a realistic ramp curve for the role, since holding them to a tenured peer’s output sets an unfair bar this early.
  • Name what “good” looks like at the 30, 60, and 90-day marks so the employee has a clear, concrete target to aim for.
  • If the review is informing a probationary decision, document specific examples with the same rigor expected of a year-end unsatisfactory review.

Part 13Peer Feedback and 360-Degree Review Examples

Many review cycles now include input from peers, direct reports, or cross-functional partners, alongside the manager’s own assessment. This peer, or 360-degree, feedback often carries a different tone than a manager’s review, since it usually comes from someone with a narrower, more specific view of the employee’s day-to-day work.

The most useful peer feedback avoids two common failure modes: vague praise that could apply to anyone, and vague criticism that gives the manager nothing to act on. Specificity matters here as much as it does in the manager’s own review.

Example peer feedback phrases:

  • Working with Jordan on the client segmentation project, I consistently found his updates clear and his timelines reliable, even under a tight deadline.
  • Elena is one of the easiest people to collaborate with on this team. She responds quickly, flags risks early, and never makes a handoff feel dropped.
  • I would love to see Sam bring his ideas into the room earlier in a project, ideally before key decisions are finalized. His input is always valuable once it surfaces.
  • Nadia’s documentation on the reporting redesign made it possible for our team to build on her work without needing a separate walkthrough, which saved real time.
  • In cross-functional meetings, Owen tends to defer to others even when he has the strongest technical read on the room. Encouraging him to speak up earlier would benefit the whole group.
  How to Create and Write a Work Plan

When compiling 360-degree feedback into a review, look for patterns across multiple respondents. One peer mentioning a communication gap might reflect a specific project friction. Three peers mentioning the same gap independently signals a pattern worth naming directly in the review.

Part 14Common Mistakes That Weaken Performance Reviews

Even experienced managers fall into a handful of predictable traps when writing reviews. Recognizing them before you draft saves a round of rewriting later.

  • Recency bias. The last six weeks of the year tend to dominate the memory, crowding out a strong Q1 or Q2. Pull up old 1:1 notes, project trackers, or prior check-ins before drafting to make sure the full period is represented.
  • The halo or horn effect. One standout project can make every other paragraph read more glowingly than the evidence supports, and one visible mistake can do the opposite. Evaluate each area of the role on its own evidence, so one strong or weak impression does not color the rest.
  • Vague praise or vague criticism. Phrases like “great attitude” or “needs to step up” sound like feedback but give the employee nothing concrete to repeat or fix. Every positive and every concern should be traceable to a specific example.
  • Copy-pasted language across employees. Reusing the same sentence structure for multiple people on the team is efficient, though it often produces reviews that feel interchangeable. Employees compare notes more often than managers expect, and generic language is usually the first thing they notice.
  • Burying the message. A review that hides a serious concern in the middle of a long paragraph, softened by several sentences of praise, risks the employee walking away without understanding the real message. If a concern matters enough to include, it deserves to be stated plainly.
  • Writing the review the night before it is due. Reviews drafted under time pressure tend to lean on generic language and skip the research needed to find the strongest example for each point. Blocking dedicated time earlier in the cycle produces noticeably better writing.
  • Choosing the rating before drafting the narrative, then writing to justify it. Deciding on a rating first and then hunting for evidence to support it tends to produce a lopsided, unconvincing review. Draft the evidence first, and let the rating follow.

Part 15Tone Calibration: Matching Language to Rating

The words you choose carry as much signal as the rating itself. A “meets expectations” review written in glowing language will confuse the employee. A “strong performer” review written in cautious language will undersell them. Matching tone to rating is one of the subtle marks of a well-written review.

Positive-Tone Phrase Patterns

Reserved for standout performance. Uses confident verbs and specific descriptors. Avoids overuse of superlatives.

Positive-tone verbs: delivered, exceeded, established, led, elevated, shaped, mentored, championed, drove, produced.

Positive-tone phrases:

  • Consistently exceeds expectations across the core responsibilities of the role.
  • Has established herself as one of the strongest performers on the team.
  • Delivered outstanding results in every quarter of the review period.
  • Continues to raise the bar for technical excellence across the team.
  • Widely regarded as a benchmark by peers across the organization.
  • Emerged as a natural leader during a period of significant change.
  • Sets a standard for professionalism and calm under pressure.
  • Drove measurable improvement in retention across the enterprise segment.

Neutral-Tone Phrase Patterns

Reserved for solid, dependable performance. Uses steady, professional verbs and clear descriptors of consistency.

Neutral-tone verbs: meets, delivers, fulfills, maintains, contributes, demonstrates, supports, follows through, completes, participates.

Neutral-tone phrases:

  • Meets performance expectations across the core responsibilities of the role.
  • Delivers reliable, on-time work across the standard portfolio of responsibilities.
  • Fulfills the requirements of the position with steady, dependable output.
  • Maintains a professional and collaborative approach in all interactions.
  • Consistently follows through on commitments and communicates clearly with stakeholders.
  • Contributes meaningfully to team rituals and cross-functional projects.
  • Demonstrates a clear understanding of the priorities of the role and the team.

Constructive-Tone Phrase Patterns

Reserved for growth areas that appear in an otherwise solid review. Uses developmental verbs that keep the door open for change.

Constructive-tone verbs: continues to develop, is building, is growing, has room to grow, is working toward, is strengthening, is deepening, is refining, is expanding.

Constructive-tone phrases:

  • Continues to develop stronger written communication with senior stakeholders.
  • Is building depth in strategic thinking as the scope of the role grows.
  • Has room to grow in giving more direct feedback to peers.
  • Is refining her ability to prioritize under pressure during quarter-end.
  • Is strengthening cross-functional influence beyond her immediate team.
  • Is deepening subject-matter expertise through active participation in the internal community of practice.
  • Is working toward delegating earlier in high-stakes projects.

Critical-Tone Phrase Patterns

Reserved for documented performance concerns. Uses factual, non-emotional verbs and grounds every claim in specific evidence.

Critical-tone verbs: has fallen short of, has not met, has failed to sustain, requires improvement in, has been the subject of concern regarding, has been documented as, has slipped in.

Critical-tone phrases:

  • Performance during this cycle has fallen short of the documented expectations of the role.
  • Sustained gaps in delivery have been documented across the review period.
  • Concerns raised in prior check-ins have persisted through the end of the cycle.
  • The pattern of missed deadlines has been the subject of ongoing feedback throughout the year.
  • Quality of work has required substantial revision from stakeholders on the majority of recent deliverables.
  • Progress against improvement targets outlined in the mid-year conversation has been limited.
  • Response to written feedback during the review period has been slower than the role requires.

Opening and Closing Line Patterns

The first and last sentences of a review carry outsized weight, since they are often what an employee remembers most clearly after the meeting has ended. A strong opening line sets the tone for everything that follows, and a strong closing line leaves the employee with a clear sense of where they stand and what comes next.

Opening line examples by tone:

  • Positive: “This has been one of the strongest years I have seen from a member of this team.”
  • Neutral: “This year reflects a consistent, dependable pattern of performance across the core responsibilities of the role.”
  • Constructive: “This year included real strengths alongside a few clear areas worth focused attention.”
  • Critical: “This review addresses a pattern of performance concerns that has been raised and documented throughout the cycle.”

Closing line examples by tone:

  • Positive: “I am glad to have you on this team, and I am looking forward to seeing what you take on next.”
  • Neutral: “I appreciate the consistency you bring to this role, and I look forward to building on it together next year.”
  • Constructive: “I see real strengths to build on here, and I am confident that focused attention on the areas above will make next year even stronger.”
  • Critical: “I want to see meaningful change in the areas outlined above, and I am committed to providing the support needed to make that possible.”

Frequently Asked Questions

How do I decide which rating to give?

Start with the evidence, then choose the rating. Managers who choose the rating first often end up writing to justify it, which weakens both the rating and the review. Once the evidence is gathered and the paragraphs are drafted, the rating usually becomes clear.

Can I give a “meets expectations” rating and still call the year strong?

Yes. On many teams, “meets expectations” is the healthy default for a solid contributor. The narrative can still recognize excellent work in specific areas. The rating reflects the overall pattern; the writing reflects the shape.

How do I write a negative review without discouraging the employee?

Focus on behavior rather than character. Ground every claim in a specific example. Pair every concern with a path forward and the support that will be provided. Honest feedback delivered with care is far kinder in the long run than soft feedback that leaves the employee unable to change.

Should I share the rating before the review meeting?

This depends on the company’s process. Many teams share the written review and the rating 24 to 48 hours before the meeting. Others reveal it in the conversation. Either approach can work as long as the employee has time to sit with the feedback before making decisions.

How do I handle a review where the rating and the narrative feel disconnected?

Rewrite one of the two until they align. If the rating feels too high for the narrative, either the narrative is missing something positive or the rating is too generous. If the rating feels too low, either the narrative overstates the concerns or the rating is unfair. Trust the evidence, and revise until the two parts tell the same story.

What if the employee’s self-evaluation and my draft rating are very different?

That gap is one of the most useful signals in the whole review process. Treat it as a conversation starter. Bring specific evidence for your view, invite the employee to share theirs, and use the difference to sharpen the picture. Sometimes the manager adjusts. Sometimes the employee sees something they had not. Either outcome is a good use of the moment.

How long should a performance review be?

Length should match the complexity of the role and the rating more than any fixed word count target. A solid “meets expectations” review often runs a few tight paragraphs per section. A review supporting a promotion or a serious performance concern usually needs more length to carry the necessary evidence. The goal is to include everything the reader needs, and nothing that only pads the page.

How often should performance reviews be conducted?

Most companies run one formal annual or semi-annual review, often supplemented by lighter quarterly or mid-year check-ins. The formal review carries the most weight for compensation and promotion decisions, while the more frequent checkpoints keep surprises out of that final conversation.

What is the difference between a self-evaluation and a manager’s review?

A self-evaluation gives the employee’s own account of their year, written from their vantage point and their memory of what mattered most. The manager’s review adds the broader view: how the work landed with stakeholders, how it compared across the team, and how it maps to the company’s rating framework. The strongest review cycles use both documents together, since either one alone offers only part of the picture.

Should I write a review differently for a remote or hybrid employee?

The substance of the review should not change based on location, though the evidence-gathering process often needs more intention. Without the casual visibility of an office, it helps to lean more heavily on written artifacts: shared documents, project trackers, chat threads, and meeting notes. Checking in with cross-functional partners who work closely with a remote employee can also fill in gaps that a manager might otherwise miss.

Can I reuse phrases from last year’s review for the same employee?

Reusing a phrase makes sense if the underlying pattern genuinely continued, though the review should still point to fresh evidence from the current period. An employee who reads the same sentence two years in a row, with no new example attached, may reasonably wonder whether the manager paid close attention this year.

What rating scale is most common across companies?

The five-level scale covered earlier in this guide remains the most widely used framework, though three-level scales and numeric scales are common as well, and a growing number of companies have moved toward rating-free, narrative-only systems. Check with your HR team on the specific framework in place, since the underlying writing principles carry across all of them.

How specific do examples in a review need to be?

Specific enough that someone with no other context could picture what happened. A date, a project name, a metric, or a direct quote from feedback all raise a vague statement into a credible, useful one. If a sentence could describe several different people on the team, it likely needs one more layer of detail.

How do I write a review for an employee who changed roles mid-year?

Address both roles explicitly. Blending them into one narrative that neither manager could fully verify tends to weaken the review’s credibility. Note the transition date, evaluate performance in each role against the expectations that applied at the time, and, where possible, coordinate with the employee’s prior manager to fill in the earlier part of the year accurately.

Conclusion

The right words carry a review. Whether the rating is positive, balanced, or unsatisfactory, the strongest language is specific, calibrated to the situation, and grounded in real evidence. The example phrases in this guide are starting points. Adapt them to your team, your employees, and the year each of them has had.

When you are ready to go deeper, return to our complete guide “Performance Reviews: The Complete Guide” for the full system, or explore “2000+ Performance Review Phrases: The Complete List” for the largest phrase library across every competency.

Posted in: Complete Guides