Performance Review Examples and Comments: 100+ Phrases for Managers

Good performance review examples are specific, behavioral and forward-looking: they name a real situation, say what the person did, state the impact, and point to what comes next. Below are 100+ manager-written performance review examples, comments and phrases, plus a complete sample performance review and eight performance review summary examples you can adapt.

This guide is written for people managers and team leads who own their own review cycles, often without an HR team scripting the process. Whether you call them performance review comments, performance appraisal examples or review phrases, the goal is the same: fair language that reflects what you actually observed.

Key takeaways

• A strong comment is specific (a named project or period), behavioral (what the person did, not who they are) and forward-looking (it connects to a next step).
• The SBI structure (Situation, Behavior, Impact) is the fastest way to turn an impression into a defensible comment.
• Use the competency table for quick wording by rating, and the sample performance review to see every part of a review filled in.
• A performance review summary is four sentences: overall result, strongest evidence, main development area, and what happens next.
• Write one follow-up action for every development comment, and confirm it in writing within seven days.

A performance review comment is a short written statement in an employee's review that describes how they performed against role expectations, backed by observable evidence and a next step.

This article covers comments a manager writes about a direct report. If you need the employee's side, see our self-appraisal comments and self-evaluation examples. For input from colleagues, use the peer review examples.

#What Makes an Effective Performance Review Comment?

An effective performance review comment references a real situation or observable behavior, explains the impact that behavior had, and points toward what comes next, whether that is continued growth or a concrete change. Vague praise and vague criticism both fail employees, in different ways.

Three criteria to apply to every comment you write:

• Specific: Names a real project, period or observable moment, not a general impression
• Behavioral: Describes what the person did, not who they are
• Forward-looking: Connects past performance to a development path or next goal

Before and after comparison:

The right side of that table requires preparation before the review. Keep a running document of observations through the cycle, one or two sentences per notable moment. When review time arrives, you have evidence, not just impressions.

#The SBI Framework for Performance Review Comments

The SBI model (Situation, Behavior, Impact) was developed by the Center for Creative Leadership and remains one of the most effective structures for performance feedback because it is observable and specific. It also makes feedback more defensible if the review is ever revisited in a development conversation or formal process.

How to use SBI:

1. Situation: Set the context. When and where did this happen? ("During the Q3 sales planning cycle...")
2. Behavior: Describe what you observed, factually. ("... you identified a gap in the territory mapping and proactively raised it with the sales director...")
3. Impact: State the result. ("... which allowed us to reassign two accounts before targets were finalized, preventing a missed quota situation.")

Full worked example:

"During the November client crisis, you stayed available across a three-day period, coordinated communication between our team and the client's VP, and produced a clear incident summary that the client's team used in their own internal review. That response protected the relationship and directly supported our renewal."

This comment is written entirely from observable events. It does not attribute personality traits or make claims the employee cannot verify. That specificity builds trust and signals that the review is based on real observation. Anchoring comments to situations and behaviors also makes it harder for recency bias, affinity bias or grade inflation to distort the rating.

For a printable worksheet that walks you through Situation, Behavior and Impact in five minutes of review prep, download the free SBI feedback template (PDF) from our full SBI guide.

#Performance Review Examples for Managers

Here is what a manager writes about a direct report, by competency and by rating. Each cell is one comment you can adapt. Replace the details with your own evidence; the structure (situation, behavior, impact) is what carries over.

For more wording by type of feedback, the next section lists three positive and three constructive comments for each competency.

#Performance Review Comments by Competency

Each competency below includes three positive examples and three constructive examples. Positive comments recognize effective behavior and reinforce it. Constructive comments address development needs without blaming or labeling the person. A useful rule of thumb is two strengths for every development area, but the balance matters less than specificity: research published in Harvard Business Review found that 57% of employees prefer corrective feedback over praise alone, so one well-built development comment is worth more than three vague positives.

Treat these as performance review phrases to adapt, not copy verbatim. The language is intentionally plain; it should sound like an attentive manager, not a form generator.

#Communication

Positive:

• "Provides clear, structured updates in team meetings every week. Stakeholders rarely need to follow up for clarification because the communication anticipates their questions."
• "When the product roadmap changed in April, you proactively scheduled a 15-minute update with your cross-functional partners before they had to ask. That reduced confusion and kept delivery timelines intact."
• "Written communication is consistently accurate and well-organized. Client-facing documents produced this cycle required minimal revision, which saved significant review time."

Constructive:

• "Updates to the broader team on project status are inconsistent. On two occasions this quarter, adjacent teams were unaware of changes that affected their planning. A weekly project status note would address this directly."
• "In-meeting communication is confident, but written follow-up is sometimes missing or delayed. Meeting decisions are occasionally not documented, which creates confusion later. A habit of brief meeting notes would help."
• "When delivering difficult news, such as the Q2 delay, the communication was factual but left some team members uncertain about next steps. Practice framing changes with a clear 'what this means for you' section."

#Collaboration and Teamwork

Positive:

• "Reliably steps into collaborative work without needing to be asked. During the product relaunch, you took on tasks outside your scope to help the team meet the deadline, and did so without complaint."
• "Actively builds positive relationships across teams. Other team leads have mentioned that working with you is straightforward because you follow through on what you commit to."
• "When conflict emerged between two team members in March, you addressed it directly and kept the team focused on the shared goal."

Constructive:

• "Collaboration is stronger within the immediate team than across departments. Two cross-functional projects this cycle hit friction points because communication with the partner team lagged. Setting up a shared status channel early would help."
• "There is a tendency to solve problems independently before involving teammates who may have relevant experience. This sometimes leads to rework. Checking in earlier would be more efficient."
• "In group settings, participation in discussion is limited. Other team members would benefit from hearing your thinking more regularly, especially in planning sessions where you have relevant context."

#Quality of Work

Positive:

• "Output is consistently accurate and complete. In six months of project delivery, there were no major errors requiring rework. That reliability has made it possible to assign you to higher-stakes projects."
• "Applies strong attention to detail without slowing the process. You catch issues early and flag them clearly, which reduces problems downstream."
• "The customer research framework you built in Q2 became a team standard. The quality was high enough that other managers adopted it for their own planning cycles."

Constructive:

• "Three deliverables this cycle required significant rework after submission. The issues were catchable in a self-review step before handoff. A consistent quality check before sending work on would raise the standard."
• "Speed is good, but accuracy has been inconsistent at times. The pattern suggests that final-check steps are being skipped under time pressure. It is worth slowing down slightly if it removes the rework loop."
• "The work meets the minimum bar but has not yet demonstrated the quality expected at the next level. Specifically, strategic recommendations lack the supporting rationale that would make them more persuasive to senior stakeholders."

#Accountability and Reliability

Positive:

• "Delivers what you commit to, on time. Over this review period, you met every major deadline and flagged potential risks early enough that we could course-correct without disruption."
• "When an error occurred in the August client report, you identified it, disclosed it to the client directly and proposed a remedy, all before the client raised it. That accountability is rare and valuable."
• "Takes clear ownership of both outcomes and process. When something goes wrong on your projects, the response is diagnostic and solution-focused, not defensive."

Constructive:

• "Deadlines have been missed on three occasions this cycle. When delays are anticipated, earlier communication would allow the team to adjust rather than discover the problem at the due date."
• "Ownership of tasks is strong at the start of a project but tends to drift near completion. Handoffs sometimes happen without the necessary documentation or context, which creates work for others."
• "When things go wrong, the first response is sometimes to redirect responsibility. Taking ownership clearly, even in ambiguous situations, would strengthen trust with peers and senior stakeholders."

#Initiative and Proactivity

Positive:

• "Identified a process gap in the client onboarding flow that was causing a consistent delay, built a fix independently and presented it to the team. That initiative saved approximately two hours per new client account."
• "Does not wait for perfect information before acting. In a fast-moving situation in October, you assessed the available data and made a defensible call that kept the project on track."
• "Regularly brings solutions alongside problems. When you flag an issue, there is usually a proposed answer attached, which makes the management conversation much more productive."

Constructive:

• "When roadblocks appear, the tendency is to pause and wait for direction rather than exploring options independently. For issues within your scope, taking an initial step, even a provisional one, builds momentum and demonstrates readiness for more senior work."
• "Several opportunities to improve team process went unaddressed this cycle. Pointing out problems is useful; the next step is proposing or piloting a fix."
• "Proactivity is high when the task is well-defined, but lower in ambiguous situations. Developing comfort with acting on incomplete information, with clear reasoning, is a key step for the next level."

#Leadership and People Management

Positive:

• "Your team delivered consistently high performance this cycle, and direct feedback from team members reflects a clear and fair management approach. That outcome does not happen by accident; it reflects the investment you have made in your people."
• "Developed two team members significantly this year. Both have taken on responsibilities that were outside their scope at the start of the cycle, and both credit your coaching conversations."
• "Handled a difficult performance situation with a direct report carefully and appropriately. You documented the issues, communicated them clearly and gave the employee a realistic path to improvement."

Constructive:

• "Team engagement signals (participation in meetings, response to feedback requests, general morale) have been lower than expected this cycle. This warrants a structured conversation with the team about what is working and what is not."
• "Delegation is improving, but there is still a tendency to take work back from direct reports rather than coaching them through it. This limits their development and puts pressure back on you."
• "Feedback to direct reports is given informally and inconsistently. A more structured approach, with regular check-ins and documented development points, would accelerate your team's growth and give you a clearer record."

#Learning and Adaptability

Positive:

• "When the company shifted to a new project methodology mid-year, you adapted quickly and helped two colleagues work through the change. Your learning curve was minimal, which reduced disruption to the team."
• "Actively seeks feedback and uses it. Three examples this cycle where you incorporated direct feedback within weeks: the report format, the client communication approach and the estimation process."
• "Takes on new challenges without requiring extensive support. When a new tool was introduced in Q3, you were proficient within a week and were informally training others shortly after."

Constructive:

• "Adapting to change has been a friction point this cycle. The transition to the new CRM prompted more resistance than expected, and the delay in adoption affected team productivity. Approaching process changes with more openness, even when the new approach is less familiar, will become more important as the team grows."
• "Feedback is received positively in the moment but does not always result in observable behavior change. The gap between hearing feedback and acting on it is the development focus for the next cycle."
• "Learning is happening, but primarily in areas of existing strength. The next step is deliberately building in exposure to areas where you are less comfortable, particularly [specific skill area relevant to role]."

#Sample Performance Review

A sample performance review shows every part of a completed review in one place: ratings with evidence, strengths, growth areas, goals and a summary. The example below is for a fictional employee, written the way a manager would complete an annual review. Names and numbers are invented; the structure is what you can reuse.

To write your own, download the review evidence worksheet (CSV). It keeps the agreed expectation, dated evidence, impact, employee perspective and next action together. Replace the illustrative row with verified evidence and use the blank rows for the rest of the review period; do not treat the example as a rating recommendation.

Review details

Ratings and evidence

Strengths

1. Consistent quality at volume. "You handled the highest ticket load on the team in Q2 and Q3 while keeping satisfaction above target. The cases I reviewed showed careful diagnosis, not just fast replies."
2. Systems thinking. "The tagging scheme you built turned ticket data into a monthly report that product now uses to prioritize fixes. That is work beyond the role description, and it changed how the company hears from customers."
3. Early risk flagging. "You raised the October backlog risk before it affected customers, with a proposed plan. That is the standard I would like the whole team to meet."

Growth areas

1. Cross-team handoffs. "Two billing escalations in Q3 lacked account history and needed extra rounds of questions. A short handoff checklist (plan, last invoice, what the customer already tried) would remove that friction."
2. Structured coaching. "Your informal onboarding worked, but it relied on your availability. Writing a simple two-week onboarding plan would make the coaching repeatable and prepare you for a team lead role."

Goals for the next cycle

1. Reduce billing-handoff follow-up questions to zero for tickets you escalate by March 31, using the handoff checklist.
2. Write and run a two-week onboarding plan for the next support hire, and collect feedback from them at day 30.
3. Present the first quarterly top-issues review to the product team by the end of Q1.

Overall summary

"Ngozi had an excellent year. She exceeded the satisfaction target, delivered a tagging scheme that now informs product decisions, and warned us about the October backlog before it hit customers. The main development areas are handoff quality with the billing team and turning her informal coaching into a repeatable process. Overall rating: 4, Exceeds expectations. We will review progress on the three goals in a check-in at the end of Q1."

Employee comments: a short section where the employee can respond, ask for support or disagree with a rating. Leave it in every review; it turns the document into a two-way conversation.

#Performance Review Summary Examples

A performance review summary is the short closing paragraph that states the overall result in a way the employee, their manager's manager and HR can all read in 30 seconds. Build every summary from four parts: the overall result, the strongest evidence, the main development area, and what happens next.

The eight examples below cover the range of performance levels. Each is written from the manager's point of view and includes the evidence, because a rating without evidence is only an opinion.

Reserve the top ratings for genuinely exceptional performance. When most of a team receives Exceeds Expectations, the signal loses value to the individual, the team and the organization. If most people are exceeding expectations, the expectations may be set too low.

#Performance Review Comments by Performance Level

Use this table to calibrate language to the employee's overall rating. These are sentence starters and framing anchors; combine them with the competency examples above.

#Performance Review Comments for Specific Situations

Some employees do not fit the standard review template. The comments below adapt the framework for four common situations: new hires, remote or hybrid team members, promotion candidates and employees on a formal plan.

#First-Year or New Employees

New employees should be evaluated against onboarding expectations and role ramp milestones, not fully against senior-level standards. Anchor comments to what was realistic in the ramp period.

• "In your first six months, you reached proficiency in [core skill] ahead of schedule and have started contributing independently to [type of project]. That is a strong foundation."
• "The onboarding period surfaced a few gaps in [area], which is expected at this stage. What matters is that you engaged with feedback and made visible progress."
• "For someone new to this role, your ability to navigate ambiguity and ask the right questions has been a clear strength. The development focus for year two is [specific area]."

#Remote or Hybrid Team Members

For remote or hybrid team members, evidence may come from async communication, project output and peer feedback rather than direct observation. Be explicit about this in comments.

• "Working asynchronously, you maintained strong project visibility. Daily check-ins were informative without being excessive, and you flagged blockers early enough that the team could respond."
• "Collaboration across time zones has been effective. You structured handoffs clearly, which is a measurable contribution for a distributed team."
• "Response time and availability have occasionally been unpredictable, which has created delays for teammates in other locations. A clearer async communication rhythm would help."

#Promotion Candidates

Comments for promotion candidates should explicitly connect performance to next-level expectations. Do not leave the promotion rationale implicit.

• "This cycle, you have demonstrated consistent readiness for [next level]. The evidence: [specific contribution 1], [specific contribution 2] and your handling of [situation]. The recommendation is to discuss a formal title transition in [quarter]."
• "You are operating at the top of your current level. What the next level requires that we have not yet seen consistently is [specific gap]. That is the development target for the next cycle."

#Employees on a Performance Improvement Plan

Comments for employees on a formal improvement plan require particular care. Keep language factual, specific and tied to documented conversations. Avoid language that characterizes the person rather than the behavior.

• "We have discussed [specific performance gap] in [month] and [month]. Progress toward [specific standard] has been [accurate assessment]. The expectation for the next 30 days is [specific, measurable outcome]."
• "This rating reflects that performance in [area] has continued to fall below expectations despite the support provided. The next step in this process is [clear, fair next step]."

If your organization has an HR function, involve them before finalizing language for employees on formal plans. For more on the wording of corrective conversations, see our negative feedback examples.

#What to Avoid in Performance Review Comments

The fastest way to weaken a review is to fall into one of these five patterns. Each one makes comments less specific, less fair or less useful to the employee, and each has a simple correction.

#1. Personality labels instead of behavioral descriptions

• Avoid: "Has a negative attitude."
• Instead: "In three team meetings, feedback from peers was met with visible skepticism and counterargument before the points were fully heard. This has reduced participation from others in those sessions."

#2. Vague positives that set false expectations

• Avoid: "Always goes above and beyond."
• Instead: "Took on the technical lead role during the product launch without being asked, and delivered it ahead of schedule. That is one example of consistently exceeding what the role formally requires."

#3. Recency bias

The most recent three weeks of a review cycle should not dominate six or twelve months of performance data. If you have kept running notes through the cycle, use them. If you have not, schedule 30 minutes before writing to reconstruct the full picture from calendar events, project logs and email threads.

#4. Absolute language

• Avoid: "Never meets deadlines." / "Always delivers great work."
• Instead: Use frequency qualifiers: "on [number] occasions," "consistently throughout Q3," "in most client-facing work this cycle."

#5. Comparative language

Comments should evaluate performance against role expectations, not against other team members. "Performs better than most of the team" is not a performance assessment. It is a ranking that can create unhealthy competition and does not tell the employee what they are being measured against.

#Turning Performance Review Comments into Action After the Review

This is where most performance review processes fail. The comment is written. The conversation happens. Then nothing changes, and the employee notices.

A performance review comment is not a summary. It is a commitment. When you write a development comment, you are implicitly agreeing to support the change you are describing. Without follow-through, the review becomes theater.

How to connect written comments to real follow-up:

For each development comment, write one action sentence before the conversation:

The 7-day follow-up:

Within one week of the review conversation, send one written note to the employee that confirms what you recognized, what the development focus is, and what the first concrete step is. This is not a formal document; it can be an email or a message. The value is in the visible commitment.

Teams that close the feedback loop within seven days tend to keep participation higher in later review cycles, because employees see that the process leads to real outcomes.

Using a system to stay consistent:

If you run your own review cycles from documents and spreadsheets, the follow-through often falls apart between reviews. That's where performance review software helps. FeedbackPulse's employee performance reviews bring self-assessments, peer input and manager review into one structured cycle, so you can see what is complete and keep the next conversation grounded in shared evidence. Performance reviews are part of the Pro plan; check the pricing page for current details. If you are still choosing a tool, our guide to the best performance review software compares the options.

#Conclusion

Effective performance review examples share three traits: they are anchored to real observations, structured with SBI, and calibrated to the employee's actual performance level. Use the competency table for quick wording, the sample performance review as a template for the whole document, and the summary examples to close each review with a clear result and a next step.

Every comment you write should ultimately reflect a specific person in a specific role at a specific point in their development, not a generic template. Strong performance appraisal examples only work when they are grounded in what you actually observed.

Most importantly: write the comment, then act on it. The follow-through conversation, the written confirmation and the mid-cycle check-in are where the review does its work.