The performance review comment is one of the most consequential paragraphs a manager ever writes. It shapes how an employee understands their own work. It informs compensation decisions, promotion cases, and, in hard cases, the grounds for termination. It lives in HR systems for years, read by future managers trying to understand who they just inherited. Yet most performance review comments are written the night before the deadline, in language that neither praises effectively nor gives feedback the employee can act on.
The gap between a useful performance review comment and a vague one is not talent. It is a set of habits and templates that any manager can learn. The goal of this guide is to move you from comments that satisfy the HR system to comments that actually help the person receiving them.
What Performance Review Comments Are For
A performance review comment has three jobs. It records what the employee did in a specific review period. It communicates how that work measured against expectations. And it gives the employee a foundation for doing better in the next period.
Most weak performance review comments fail at the third job. They describe what happened and give a rating, but leave the employee wondering what to do with the feedback. A comment that says "strong performer, exceeded expectations on the Apex launch" is pleasant to read and operationally useless. The employee does not know what to repeat, what to refine, or what to stop doing.
A strong comment gives the employee a clearer map of their own work. It names specific examples. It separates what the employee controlled from what they did not. It identifies patterns the employee can act on. It does all this in a voice the employee will recognize as their manager's own rather than in HR boilerplate.
"Feedback is information about the past delivered in a form that is useful for the future. If it does not meet both criteria, it is not feedback. It is commentary." Kim Scott, Radical Candor
The Four-Part Comment Structure
Strong performance review comments follow a predictable internal structure regardless of the length required by the HR system.
Part 1: Context. One or two sentences setting up the scope of the employee's role this period. What were their primary responsibilities and priorities.
Part 2: Specific evidence. Three to five concrete examples of work. Named projects, specific metrics, particular moments. This is the section that distinguishes serious feedback from vague feedback.
Part 3: Pattern. What the examples add up to. A behavioral, skill, or impact pattern the employee can recognize.
Part 4: Forward direction. What would make this employee even stronger in the next period. One or two specific development areas or stretch opportunities.
This structure works for strong performers, average performers, and struggling performers. The content changes. The structure does not.
Template 1: High Performer Comment
Use this for employees who consistently exceeded expectations in the review period.
[Name] had a standout [year/quarter/period] in [role/team]. Their primary responsibilities were [list 2-3 main areas], and they moved each of them forward meaningfully.
Specific highlights:
- [Project name]: [specific outcome with metric]. [One sentence on what made this notable beyond the outcome itself, such as difficulty or stakeholder feedback.]
- [Project or contribution]: [specific outcome with metric]. [One sentence on the employee's role in it.]
- [Project or contribution]: [specific outcome]. [One sentence on ripple effects or team benefit.]
Across these, a consistent pattern emerges: [Name] is strongest when [observed skill or behavior]. This shows up in [brief example of the pattern across multiple projects].
For the next period, the growth edge is [specific stretch area]. This is not a weakness. It is the next level of impact [Name] is ready for. Concretely, this would look like [specific stretch example]. I will support this by [specific manager commitment].
Overall, [Name] operated well above expectations for the [role level] and is a strong candidate for [promotion / expanded scope / whatever specific next step applies].
A strong performer comment does not just list accomplishments. It names a pattern that gives the employee a frame for their own strengths, and it identifies the stretch opportunity that turns "exceeds expectations" into "is ready for more." Comments that stop at praise fail the third job of feedback.
Template 2: Solid Performer Comment
Use this for employees who met expectations consistently, without obvious excellence or concerning gaps.
[Name] delivered consistently this [period] on the core responsibilities of [role]. The work was reliable, on time, and at the quality bar expected for the level.
Representative contributions:
- [Project]: [outcome]. [One sentence of texture.]
- [Project]: [outcome]. [One sentence of texture.]
- [Ongoing responsibility]: [Name] maintained [metric or state] across the period.
The strength pattern I see is [specific observation, e.g., strong execution once direction is clear, reliable cross-functional partner, deep subject matter expertise in area X]. This is a genuinely valuable profile on our team.
The growth opportunity I see is [specific area]. Examples where this showed up: [1-2 specific moments where stretching in this direction would have produced a stronger outcome]. Developing here would move [Name] from consistent performer to someone whose work catalyzes the work of others.
My specific suggestion for the next period: [one concrete development action, tied to a project or behavior that is already on the calendar]. I will check in on this at our [specific time, e.g., mid-period one-on-one].
Solid performer comments often get written most poorly because managers feel less pressure than with stars or strugglers. But these employees make up the bulk of most teams, and a generic comment wastes the rare opportunity to give them something to work on.
Template 3: Underperformer Comment
Use this for employees who did not meet expectations in material ways. These comments require more care, more specificity, and more clarity about the path forward.
[Name]'s performance this [period] did not meet the expectations for [role level] in several areas.
Specific observations:
- On [project or responsibility]: expected outcome was [X]. Actual outcome was [Y]. Key gap: [specific behavior or skill issue, not character judgment].
- On [project or responsibility]: expected outcome was [X]. Actual outcome was [Y]. Key gap: [specific issue].
- On [pattern area]: [description of recurring issue and how it showed up across multiple situations].
I have discussed each of these with [Name] at the time they occurred. This review reflects a pattern, not a single incident.
The underlying issues as I see them are [one or two specific named issues, e.g., inconsistent follow-through on committed deadlines; difficulty with cross-functional collaboration when tensions arise]. I acknowledge that [any mitigating factors, e.g., this was [Name]'s first period in the role, or specific circumstances that affected the work].
What needs to change: [specific, observable behaviors with timeline]. I will support [Name] with [specific resources or check-in cadence]. If this pattern continues through [specific date], we will need to have a further conversation about fit for the role.
[Name] has the ability to close this gap. What has been missing is consistency in [specific area]. I am committed to working with [Name] on this, and I need to see specific progress by [date].
Underperformer comments serve a distinct purpose: they create a clear, documented basis for development, performance improvement plans, or if necessary, separation. Vague comments that soften the message do the employee no favors. They delay the hard conversation and, if termination eventually becomes necessary, they leave the manager without documentation.
Specific Versus Vague Language
The single biggest quality difference in performance review comments is specificity. Vague comments are less useful, less actionable, and less defensible.
| Vague Language | Specific Language |
|---|---|
| Great team player | Mentored three junior team members, two of whom took on stretch projects this quarter |
| Strong communicator | Presented the Q3 strategy to the executive team, handled pushback on the budget question directly and without deflection |
| Needs to improve communication | On the Gamma project, stakeholders learned of the 3-week delay from a client, not from [Name], creating a trust issue we are still recovering from |
| Delivers quality work | Shipped 4 releases in the period, each with less than 2% defect rate in the first two weeks post-launch |
| Could be more proactive | When the partner team missed their deliverable in July, [Name] waited for them to reach out rather than flagging the risk upward, which cost us two weeks on the critical path |
| Good leadership skills | Ran the incident response for the Nov 3 outage, coordinated across four teams, and authored the post-mortem within 48 hours |
| Room for growth in strategic thinking | On the Portfolio Review, [Name] produced strong tactical recommendations but did not surface the longer-term question about platform investment that emerged later |
| Exceeds expectations | Delivered the Acme renewal at 140% of target, negotiated against [competitor], and added two multi-year clauses that lock in the account through 2027 |
Specific language takes longer to write but is the entire point of the exercise. A manager who writes specific comments is a manager who has been paying attention.
"The difference between a review that changes someone's career and one they forget in a week is specificity. Vague praise and vague criticism both slide off the memory." Marcus Buckingham, First, Break All the Rules
Comments for Different Rating Outcomes
Performance review systems vary in structure, but most rating outcomes fall into a few categories. Matching comment tone to rating is important. A "meets expectations" comment that reads like "exceeds expectations" confuses the employee about their own standing.
| Rating | Tone | Focus of Comment |
|---|---|---|
| Exceeds expectations | Warm and specific | What they did, what the pattern is, what's next |
| Strongly meets expectations | Warm and specific | Reliability and strengths, specific growth edge |
| Meets expectations | Direct and specific | Consistent delivery, one clear development area |
| Partially meets | Clear and development-oriented | Specific gaps, specific plan, resources offered |
| Does not meet | Formal and documented | Specific failures, pattern, required change, timeline |
| Too new to rate | Contextual | Onboarding progress, what "ready to rate" looks like |
| On performance improvement plan | Formal and documented | Exactly matches the PIP language, no softening |
The tone shift between "meets" and "partially meets" is the most important to get right. Employees read "meets expectations" as fine and "partially meets" as a problem. Writers who soften the partially meets comment to preserve the relationship create confusion about where the employee actually stands.
The Bias Problem
Performance review comments are subject to several well-documented biases. Managers tend to remember recent events more than earlier ones in the period. They tend to rate employees who are similar to them more favorably. They tend to write more vague comments for employees they are uncomfortable with, which disproportionately affects employees from underrepresented groups.
Counteracting these biases requires a few habits. Keep notes throughout the review period, not just in the final weeks. Review the specific project outcomes before writing, not just general impressions. Check the distribution of comment length and specificity across your team: if one group is consistently getting shorter, less specific comments, look at why.
The cognitive research at What's Your IQ on how memory distortions affect judgment applies directly to performance reviews, and the documentation patterns discussed at When Notes Fly on continuous notes provide the running record that counteracts recency bias.
"The feedback you give employees is a record of how much you have actually observed. Managers who cannot write specific feedback have usually not been watching specifically." Josh Bernoff, Writing Without Bullshit
Phrases to Avoid
Some phrases appear in so many performance review comments that they have lost all meaning. Others mean something different to the writer than to the reader. A running list of phrases to avoid:
| Phrase to Avoid | Why |
|---|---|
| Rockstar, ninja, superhero | Sounds like a startup ad, says nothing specific |
| Goes above and beyond | Meaningless unless you specify what the base is |
| Has a lot of potential | Reads as a euphemism for "has not delivered yet" |
| Good attitude | Often used for employees from groups the manager does not know how to describe otherwise |
| Team player | Vague; prefer specific examples of collaboration |
| Strong work ethic | Often code for "worked long hours," which may not be the right metric |
| Always available | Should not be praised; indicates poor boundaries |
| Hardworking | Specify the work rather than the effort |
| Very intelligent | Subjective; specify decisions or insights |
| Needs to develop soft skills | Vague; name the specific skill and the specific example |
| A joy to work with | Nice sentiment; replace with one concrete thing they did |
| Does not take feedback well | Name the specific incident, and ask whether the feedback was specific enough to be actionable |
These phrases tend to cluster in reviews written in the last hour before the deadline. Notes kept during the period make them easier to replace with specifics.
Writing Reviews Under Time Pressure
Most managers write performance review comments under heavy time pressure. A few practices make the writing go faster without sacrificing quality.
Keep a running notes file per direct report. A simple document with dated entries whenever something notable happens, good or concerning. At review time, the raw material is already there. This takes five minutes a week and saves hours at review time.
Draft the specific examples first, then the framing. The temptation is to write the opening line ("X had a strong quarter") and try to fill in from there. Start with the three to five specific examples. The framing writes itself once the examples are on the page.
Write underperformer comments first. They are the hardest and benefit from the most care. Writing them early, when energy is high, improves quality. Writing them last, at midnight the day before the deadline, produces the vague comments that create problems later.
Read each comment as if you were the employee. Would you know what the writer is telling you? Would you know what to do differently? If not, rewrite.
Review Meetings: What the Written Comment Should Do
The written comment and the review conversation are different artifacts. The comment is a durable record. The conversation is an exchange. They should reinforce each other, not duplicate each other.
The written comment should carry the specific evidence and the pattern observation. The conversation should let the employee respond, ask questions, and discuss the forward direction. If the conversation ends up being the first time the employee hears critical feedback, the review system is broken: feedback should have been delivered during the period, not saved for the review.
The written comment should also not surprise the employee. Everything in it should be something they have heard before. The review is a summary, not a reveal.
Legal and Documentation Considerations
Performance review comments can become legal documents. In employment disputes, promotion appeals, and termination cases, the written record is heavily scrutinized. Comments that were vague or overly positive for employees the manager later tried to separate create serious problems for the employer.
A few practices help. Use specific, observable language rather than character judgments. "Missed deadline on the Gamma project" is factual. "Unreliable" is a character judgment. Document conversations about performance issues in writing, even briefly, at the time they happen. If you had to explain the review in court, would the comments match the record of ongoing feedback?
In regulated industries and in some jurisdictions, specific requirements apply to performance documentation. The employment law guidance at Corpy covers jurisdictional variations on documentation requirements for multi-country employers.
Comments Across the Year, Not Just At Review Time
The best performance review comments are a summary of feedback the employee has already received throughout the year. The worst are the first time the employee is hearing anything specific.
Building a rhythm of feedback through the year means the review comment is less loaded. It confirms what the employee already knows. It formalizes the record. It sets the stage for the next period. It does not try to compress a year of unspoken feedback into five paragraphs.
Mangers who invest in continuous feedback often find that the review comment itself becomes faster and more useful. The employee already knows where they stand. The manager already has the specifics. The document becomes a tool rather than a test.
Building a Review Comment Discipline
Teams where review comments are consistently useful share a few traits. Managers keep running notes through the year. A house template exists and is used. Comments are calibrated across the team before ratings are finalized. The manager's own manager reviews a sample of written comments for quality.
Teams where review comments are consistently vague also share traits. Feedback is ad-hoc rather than continuous. Templates are missing or ignored. Ratings are finalized without calibration. No one reads the manager's written comments except the employee and HR.
The most efficient improvement is to establish a house standard for comments, train managers on it once a year, and have senior leaders spot-check comments quarterly. Within two review cycles, the quality of written feedback across an organization can change visibly.
For related guidance on professional documentation, see our articles on how to write effective meeting minutes and how to write standard operating procedures.
References
Scott, K. (2017). Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin's Press. https://www.radicalcandor.com/
Buckingham, M., and Coffman, C. (1999). First, Break All the Rules. Simon and Schuster. https://www.marcusbuckingham.com/
Bernoff, J. (2016). Writing Without Bullshit. Harper Business.
Edmondson, A. C. (2019). The Fearless Organization. Wiley. https://doi.org/10.1002/9781119595663
Society for Human Resource Management. Performance Management Resources. https://www.shrm.org/topics-tools/topics/performance-management
Harvard Business Review. The Feedback Fallacy. https://hbr.org/2019/03/the-feedback-fallacy
Gallup. State of the American Workplace. https://www.gallup.com/workplace/
Kluger, A. N., and DeNisi, A. (1996). The effects of feedback interventions on performance. Psychological Bulletin, 119(2), 254-284. https://doi.org/10.1037/0033-2909.119.2.254
Frequently Asked Questions
How long should a performance review comment be?
Most effective comments run 150 to 400 words per review period, with longer versions for senior roles and shorter for entry-level contributors. Length matters less than specificity. A 100-word comment with three concrete examples outperforms a 600-word comment filled with generic praise.
Should I include negative feedback in a performance review?
Yes, when it is warranted, and it should never be a surprise. If the review is the first time the employee is hearing about an issue, the feedback loop has failed earlier. Name specific observed behaviors, not character judgments, and describe what good would look like going forward.
What is the biggest mistake managers make in review comments?
Vague language. Phrases like team player, strong communicator, and exceeds expectations carry almost no information. Replace them with specific examples, named projects, and concrete outcomes. Specificity is what separates useful feedback from commentary.
How do I write a review comment for an employee I am about to put on a PIP?
Align the review language exactly with the PIP language. Document specific, observable gaps with dates and examples. Avoid softening that will later make the PIP look inconsistent. The review and the PIP are part of the same record and need to tell a consistent story.
How do I avoid bias in performance review comments?
Keep running notes across the full review period to counter recency bias. Check whether comment length and specificity are consistent across your team. Review the specific project outcomes before writing rather than going on general impressions. Calibrate ratings across peer managers before finalizing.
Can performance review comments be used in legal disputes?
Yes. In employment disputes, promotion appeals, and termination cases, written comments are heavily scrutinized. Vague or overly positive comments for employees the manager later tried to separate create serious problems. Write in specific, observable language and document concerns when they occur, not at review time.
How do I give high performers useful feedback?
Go beyond praise to identify the pattern that makes them strong, and name the stretch opportunity that represents their next level. A review that only lists accomplishments does not help the employee grow. The most useful comments for top performers identify the growth edge they have not yet tackled.