Performance Review Comments: 100+ Examples and Best Practices for Managers

Most managers know that performance review comments matter. Fewer know exactly what to write. You sit down with a general sense of how someone has performed — and then the blank page arrives.

This guide gives you a practical framework and 100+ ready-to-use performance review comments organized by competency, performance level, and situation. It is written for people managers and team leads who own their own review cycles, often without an HR team scripting the process for them. Whether you call them performance review phrases, performance appraisal examples, or simply review comments — the goal is the same: specific, fair language that reflects what you actually observed.

This article covers manager-written comments about direct reports. If you are looking for self-appraisal comments or peer review examples, those guides cover a different voice and relationship.

What Makes an Effective Performance Review Comment?

An effective performance review comment is specific, behavioral, and forward-looking. It 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 as a person
• 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 during 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 — specific, factual. ("...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.

Why SBI reduces bias:

When feedback is anchored to situations and behaviors rather than impressions, it is harder for recency bias, affinity bias, or grade inflation to distort the rating. Managers who use SBI consistently find it easier to differentiate between employees at the same level because the evidence becomes the anchor.

Performance Review Comments by Competency

Each section 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.

These performance review comments are organized by the seven competencies most commonly evaluated in structured review cycles. Treat them as performance review phrases to adapt — not copy verbatim. The language here is intentionally plain; it should sound like an attentive manager, not a form generator.

Communication

Positive:

• "Consistently provides clear, structured updates in team meetings. 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. Decisions made in meetings 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 navigated it constructively — you addressed it directly and kept the team focused on the shared goal."

Constructive:

• "Collaboration is stronger within 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 catch-able 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 one-on-one investment you have made."
• "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 — regular one-on-ones with 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]."

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.

A note on Exceeds Expectations: Reserve this rating for genuinely exceptional performance. When most of the team receives this rating, the signal loses value — to the individual, to the team, and to the organization. If someone truly exceeds expectations, say exactly why. If most people are exceeding expectations, the expectations may be set too low.

Performance Review Comments for Specific Situations

Some employees do not fit the standard review template. The performance review comments below adapt the framework for four common situations — new hires, distributed team members, promotion candidates, and employees on a formal plan — where the usual expectations need extra context.

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.

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 performance review 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 maintain higher participation in subsequent 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 without a dedicated HR platform, the follow-through often falls apart between reviews. Structured employee performance reviews with built-in check-in reminders reduce the gap between what was agreed in the review and what actually changes. To streamline performance reviews across your team — including mid-cycle check-ins and manager follow-through — FeedbackPulse builds this into the process so the review comment is the beginning, not the end.

The goal of continuous feedback is not more feedback — it is faster, more visible follow-through on the feedback that already exists.

Frequently Asked Questions

How long should a performance review comment be?

A useful comment is typically 2–5 sentences per competency area. It should be long enough to give a specific example and state the impact, but short enough to be read in 30 seconds. Comments that run beyond a paragraph often lose focus. The test: can the employee clearly understand what they did well or need to change after one read?

What is the SBI method for performance reviews?

SBI stands for Situation, Behavior, Impact — a framework developed by the Center for Creative Leadership. You describe the context (when and where), the specific behavior you observed (what the person did), and the impact of that behavior (the result). It is the most practical structure for writing performance review comments that are defensible, specific, and usable.

How do I write comments for underperforming employees?

Keep language behavioral and factual. Reference specific situations, documented conversations, and observable outcomes. Avoid language that describes the person's character or attributes the problem to attitude. State what the expected standard is and what the observed gap is. If the employee is on a formal plan, involve HR before finalizing the language.

Can I use the same comment template for everyone?

You can use the same structure — SBI, or the competency-by-competency format above — but the specific content must be individualized. Generic comments that could apply to anyone signal to the employee that the review was not carefully considered. Even brief, specific comments land better than polished generic ones.

How often should performance reviews happen?

Most research — including Gallup's State of the American Workplace — points to more frequent, shorter check-ins as more effective than annual reviews. A common practical approach: formal written reviews twice a year, with structured one-on-ones monthly or quarterly in between. Annual reviews that arrive without any intermediate conversations tend to surface surprises — which is a failure of the system, not just the review.

What is the right balance between positive and constructive comments?

Research published in Harvard Business Review found that 57% of employees prefer corrective feedback over praise alone. A useful ratio for most reviews is two areas of strength to one development area — but the balance matters less than the specificity. A single, well-constructed development comment is more valuable than three vague positives.

Conclusion

Effective performance review comments are specific, behavioral, and connected to what comes next. The framework is simple: anchor comments to real observations, use the SBI structure to give them shape, and calibrate language to the employee's actual performance level.

The performance review examples in this guide are starting points. 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, like the ones above, only work when they are grounded in what you actually observed.

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

If you want to streamline performance reviews and build the follow-through habit into your team's process, FeedbackPulse gives managers a simple, structured system without enterprise complexity. Start free and run your first structured review cycle this quarter.