Performance review phrases are short, ready-made lines that describe how someone performed on a competency such as communication or time management. Managers use them to write reviews faster and more consistently, and employees use the same lines, in the first person, to write a self-evaluation. Whether your company runs reviews in a shared document or in one of the talent management platforms we compare, the blank text box is the same.
The generator at the top of this page writes a full draft for either side of the desk. Below it you’ll find 200 phrases sorted by competency and rating level, self-evaluation examples for six roles, before-and-after rewrites of vague comments, and the wording that creates legal risk.
Treat every phrase as a starting point. On its own, “communicates clearly” gives the employee nothing to repeat or fix. With one real example attached, it becomes feedback. This guide is part of our free HR templates library.
Performance review phrases are pre-written statements that describe an employee’s performance on one competency at one rating level. Managers use them in reviews, and employees adapt them for self-evaluations.
Every phrase needs one concrete example, or it reads as filler. A short review with three real examples does more than a long one built from stock lines.
- 3 to 5competencies per review
- 1example for every rating
- 3rating levels in this guide
Quick Summary: Performance Review Phrases
How to Write a Performance Review in 6 Steps
To write a performance review, gather evidence from the whole review period, rate 3 to 5 competencies against the role’s expectations, support each rating with one example, and close with measurable goals. The same steps work for a self-evaluation, written in the first person.
Most weak reviews go wrong at the first step. The manager starts writing from memory in the week the review is due, so the review really covers the last six weeks and whatever went wrong most recently.
- Keep an evidence logNote wins, misses and feedback as they happen, with the date. Ten minutes a month is enough.
- Check the role’s expectationsRate against the job description, level framework or goals agreed at the start of the period, never against other people on the team.
- Pick 3 to 5 competenciesChoose the areas that mattered most this period. A designer and a support agent should not be reviewed on the same list.
- Decide each rating firstSettle the rating before you choose the wording. The phrase follows the rating, never the other way round.
- Add one example per ratingA project, a date or a result. The bracketed prompts in the generator are there as a reminder.
- Close with goals and a dateTurn each needs-improvement area into a measurable goal and agree when you will check progress.
For the goals in step six, use the same structure you use for team metrics. Our guide to KPIs for remote teams covers how to write targets people can track without a manager watching over them. If your company runs pulse surveys, recent results add useful context to teamwork and communication ratings.
200 Performance Review Phrases by Competency
Below are 200 performance review phrases for 10 competencies: 7 exceeds-expectations phrases, 7 meets-expectations phrases and 6 needs-improvement phrases for each one. They are written in the third person without a name, so they drop straight into a manager’s review. For a self-evaluation, start with “I” and switch to the past tense.
Use the filter to jump to one competency. The copy button on each card copies all of its phrases, and the panel beside them tells you which evidence to attach.
Communication: exceeds expectations
Explains complex work in plain language that non-specialists can act on.
Sends updates before anyone has to ask, so partners always know where work stands.
Flags risks early, with options, instead of at the deadline.
Writes documents the team reuses as the reference version.
Adapts the message to the audience, from an engineer to an executive.
Listens fully before responding, and people feel heard in meetings with them.
Runs meetings that end with clear decisions, owners and dates.
Exceeds ratings get questioned most in calibration, so back at least one of these with a specific update, document or meeting, and what changed because of it. A self-evaluation version: “I sent a written update every Friday, so stakeholders never had to chase me for status.”
Communication: meets expectations
Communicates clearly and keeps their manager informed about progress and blockers.
Writes updates that are accurate, complete and on time.
Responds to messages within the team’s agreed timeframe.
Asks clarifying questions when instructions are unclear.
Shares relevant information with the people who need it.
Presents work in a way colleagues can follow.
Records decisions in the agreed place so others can find them.
A meets rating still needs one line on what good looked like this period. Add a specific update, document or meeting, and what changed because of it, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Communication: needs improvement
Shares updates late or only when asked, which leaves partners unsure of status.
Leaves out context in messages, so others need follow-ups before they can act.
Raises blockers close to the deadline rather than when they appear.
Writes long messages where the key request is hard to find.
Talks over colleagues in meetings, which cuts discussion short.
Responds slowly to messages that others are waiting on.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Teamwork: exceeds expectations
Steps in to help teammates without being asked and without dropping their own work.
Shares knowledge freely, so the team depends less on any one person.
Gives credit to others publicly and specifically.
Settles disagreements calmly and keeps the discussion on the work.
Takes on the unglamorous tasks the team needs done.
Builds working relationships across teams that speed up shared projects.
Helps new colleagues become productive faster through informal onboarding.
Exceeds ratings get questioned most in calibration, so back at least one of these with a project where you helped a colleague or partner team, and the result. A self-evaluation version: “I covered two client accounts while a colleague was on leave and kept both renewals on schedule.”
Teamwork: meets expectations
Works well with others and does a fair share of team work.
Follows through on commitments made to teammates.
Stays respectful in discussions, including when disagreeing.
Supports colleagues when asked.
Shares information openly with the team.
Contributes in team meetings.
Commits to decisions once the team has made them.
A meets rating still needs one line on what good looked like this period. Add a project where you helped a colleague or partner team, and the result, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Teamwork: needs improvement
Works alone and brings others in late, which causes rework on shared projects.
Is hard to reach when colleagues need input.
Lets disagreements turn into delays instead of raising them openly.
Commits to shared tasks without always delivering them.
Holds on to information the team needs.
Rarely offers help to colleagues under pressure.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Leadership: exceeds expectations
Sets a clear direction and explains the reasons behind it.
Gives frequent, specific feedback that helps people improve.
Develops others into bigger responsibilities.
Takes ownership when things go wrong and shares credit when they go well.
Makes sound decisions under pressure with incomplete information.
Builds a team where people raise problems early.
Delegates real ownership, not only tasks.
Exceeds ratings get questioned most in calibration, so back at least one of these with a decision you made or a person you helped grow, and what happened next. A self-evaluation version: “I gave each person I manage written feedback every two weeks and agreed a development goal with each of them.”
Leadership: meets expectations
Takes ownership of their own work and outcomes.
Makes decisions within their scope and escalates the right issues.
Sets clear expectations on projects they lead.
Guides newer colleagues when asked.
Coordinates the team when the situation needs it.
Models the standards they expect from others.
Follows through on what they promise the team.
A meets rating still needs one line on what good looked like this period. Add a decision you made or a person you helped grow, and what happened next, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Leadership: needs improvement
Waits for direction on decisions that sit within their role.
Gives feedback rarely, so people are unsure where they stand.
Leaves goals and responsibilities unclear on projects they lead.
Avoids difficult conversations until problems grow.
Does work personally instead of delegating it.
Changes direction without explaining why.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Problem solving: exceeds expectations
Finds the root cause, so fixes stay fixed.
Spots problems before they reach customers or deadlines.
Breaks messy problems into clear options with a recommendation.
Stays calm in incidents and works through them methodically.
Uses data to test assumptions before acting.
Turns one-off fixes into process changes that prevent repeats.
Is the person colleagues go to with their hardest problems.
Exceeds ratings get questioned most in calibration, so back at least one of these with a problem you diagnosed and the outcome of the fix. A self-evaluation version: “I traced the recurring invoice errors to one import setting and fixed it, and the errors have not come back.”
Problem solving: meets expectations
Solves the problems in their area reliably.
Brings possible solutions, not only the problem.
Analyzes an issue before acting on it.
Asks for help at the right point.
Keeps work moving while a fix is found.
Weighs the options before choosing one.
Learns from mistakes and avoids repeating them.
A meets rating still needs one line on what good looked like this period. Add a problem you diagnosed and the outcome of the fix, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Problem solving: needs improvement
Escalates problems before trying a first step.
Fixes symptoms rather than causes, so issues come back.
Stalls when something unexpected happens.
Acts on assumptions without checking the facts.
Raises problems without suggesting a way forward.
Takes a long time to decide, even on low-risk choices.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Time management: exceeds expectations
Delivers on time even when priorities change.
Estimates accurately, so others can plan around their work.
Manages a heavy workload without dropping anything.
Says early, with a new date, when something needs to move.
Protects time for the highest-value work.
Finishes ahead of schedule without cutting quality.
Helps the team plan realistic timelines.
Exceeds ratings get questioned most in calibration, so back at least one of these with a deadline you met or moved, with the dates. A self-evaluation version: “I delivered all four quarterly reports on time and flagged the one date change a week in advance.”
Time management: meets expectations
Meets agreed deadlines.
Prioritizes sensibly when new requests come in.
Keeps several pieces of work moving at once.
Flags timeline risks before the deadline.
Manages their calendar so meetings do not crowd out delivery.
Gives estimates that are generally accurate.
Arrives prepared for meetings and handovers.
A meets rating still needs one line on what good looked like this period. Add a deadline you met or moved, with the dates, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Time management: needs improvement
Misses agreed deadlines and flags delays late.
Spends time on low-priority work while key deadlines slip.
Gives optimistic estimates that others cannot plan around.
Leaves work until the last moment, with no time for review.
Overcommits and then has to drop tasks.
Needs reminders to complete routine tasks on time.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Quality of work: exceeds expectations
Produces work that is accurate, complete and ready to use.
Catches errors others miss, including in other people’s work.
Holds the same standard on low-visibility work as on high-visibility work.
Builds checks or templates that raise the team’s quality.
Tests their own work before handing it over.
Produces work that others use as the example.
Turns feedback into lasting improvements.
Exceeds ratings get questioned most in calibration, so back at least one of these with a piece of work and how it was received, or an error rate before and after. A self-evaluation version: “I built a pre-release checklist for our reports, and none of them needed a correction after publishing this period.”
Quality of work: meets expectations
Produces accurate work that meets the role’s standard.
Checks work before handing it over.
Applies feedback from reviews.
Produces work that rarely needs major revision.
Follows agreed processes and standards.
Keeps work organized so others can build on it.
Asks for a review on work that carries risk.
A meets rating still needs one line on what good looked like this period. Add a piece of work and how it was received, or an error rate before and after, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Quality of work: needs improvement
Hands over work with errors that others have to correct.
Delivers inconsistent quality from task to task.
Repeats mistakes that came up in earlier reviews.
Skips agreed checks to save time.
Delivers work that is incomplete against the brief.
Needs close review on work that should be done independently.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Initiative: exceeds expectations
Spots what needs doing and does it without being asked.
Proposes improvements with a plan, and delivers them.
Takes ownership of problems outside their brief when no one else does.
Learns new skills ahead of when the team needs them.
Volunteers for stretch work and follows through.
Brings researched proposals rather than complaints.
Started improvements the team now relies on.
Exceeds ratings get questioned most in calibration, so back at least one of these with an improvement you started and what it changed. A self-evaluation version: “I set up the shared request form for design work, which replaced requests scattered across chat and email.”
Initiative: meets expectations
Takes ownership of assigned work.
Suggests improvements when they see them.
Follows up on open items without reminders.
Acts within their scope without waiting for approval.
Contributes ideas in team discussions.
Looks for answers before asking.
Takes on new tasks willingly.
A meets rating still needs one line on what good looked like this period. Add an improvement you started and what it changed, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Initiative: needs improvement
Waits for instructions, even on work clearly in their area.
Rarely suggests improvements despite knowing the work well.
Leaves open items until someone follows up.
Raises ideas but does not act on them.
Avoids tasks outside their usual routine.
Needs prompting to start work.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Adaptability: exceeds expectations
Adjusts quickly when plans change and helps others do the same.
Picks up new tools and processes fast and teaches others.
Stays productive during uncertain periods.
Treats feedback as information and changes course quickly.
Handles a change in role or scope without a drop in output.
Suggests practical ways to make a change work.
Works well across new teams, time zones and working styles.
Exceeds ratings get questioned most in calibration, so back at least one of these with a change you adapted to and how quickly you got back to full speed. A self-evaluation version: “When our team moved to a new project tool mid-quarter, I was fully set up in the first week and ran two training sessions for others.”
Adaptability: meets expectations
Adjusts to changing priorities without losing momentum.
Learns new tools at a reasonable pace.
Accepts feedback and changes approach when it makes sense.
Works effectively with new colleagues and teams.
Stays professional when plans change at short notice.
Follows new processes once they are agreed.
Recovers from setbacks and refocuses.
A meets rating still needs one line on what good looked like this period. Add a change you adapted to and how quickly you got back to full speed, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Adaptability: needs improvement
Takes a long time to adjust when plans change.
Is slow to adopt tools and processes the team has agreed on.
Pushes back on feedback before discussing it.
Falls back on old ways of working after a change.
Loses productivity for long periods during change.
Struggles to work with colleagues whose style differs from their own.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Customer focus: exceeds expectations
Understands customer needs before customers spell them out.
Turns customer feedback into changes and closes the loop.
Handles difficult customers calmly and leaves them feeling heard.
Builds relationships that lead to renewals or referrals.
Sets realistic expectations and then beats them.
Speaks up for customers in internal decisions.
Resolves issues on first contact wherever possible.
Exceeds ratings get questioned most in calibration, so back at least one of these with a customer outcome, such as a resolved case, a renewal or a satisfaction score. A self-evaluation version: “I replied to every customer within one working day and closed the loop on each feature request I passed to product.”
Customer focus: meets expectations
Responds to customers promptly and professionally.
Resolves customer issues within agreed timeframes.
Sets clear expectations and follows through.
Passes customer feedback to the right team.
Stays courteous under pressure.
Keeps customer records up to date.
Considers customer impact when making decisions.
A meets rating still needs one line on what good looked like this period. Add a customer outcome, such as a resolved case, a renewal or a satisfaction score, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Customer focus: needs improvement
Leaves customer issues open too long.
Lets customers chase for updates.
Makes promises to customers that the team cannot keep.
Ends difficult conversations without a clear next step.
Does not pass customer feedback on.
Responds to complaints defensively.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Technical skills: exceeds expectations
Solves technical problems others get stuck on.
Explains technical work so non-specialists can make decisions.
Keeps skills current and introduces better methods.
Produces technical work that holds up in review and in use.
Automates repetitive work, saving the team time.
Mentors colleagues on technical skills.
Is the go-to person for a key system or skill.
Exceeds ratings get questioned most in calibration, so back at least one of these with something you built, fixed or automated, and its effect. A self-evaluation version: “I automated the weekly data export, which saves the team about two hours every Monday.”
Technical skills: meets expectations
Has the technical skills the role requires.
Applies technical knowledge correctly in daily work.
Learns new tools when the work calls for it.
Follows technical standards and documentation practices.
Asks for help on technical questions at the right point.
Produces technical work that meets review standards.
Keeps documentation up to date.
A meets rating still needs one line on what good looked like this period. Add something you built, fixed or automated, and its effect, and keep the tone matter-of-fact. Meets is a solid rating, not a warning.
Technical skills: needs improvement
Has gaps in core technical skills that affect delivery.
Relies on others for tasks that are part of their role.
Has not kept up with the tools the team now uses.
Produces technical work that often fails review.
Skips documentation, which makes work hard to hand over.
Uses workarounds instead of learning the correct method.
Name the behavior and its effect, then agree one measurable goal and a date to check progress. Point to the specific cases behind the rating so the gap is a matter of record, not opinion.
Want these in a finished review instead? Pick the same competencies in the generator above and it will build the paragraphs, the development goals and the closing line for you.
Self-Evaluation Examples by Role
A good self-evaluation names specific results, admits one real growth area along with what you are doing about it, and proposes a goal for next period. The examples below follow that structure for six common roles, with placeholders for your own numbers and dates.
Self-evaluations usually fail in one of two ways. Some people undersell, listing duties instead of results. Others oversell, rating everything as exceptional with nothing to back it up. Both leave your manager to go looking for your evidence, and they may not find it.
Not sure which competencies to cover? Switch the generator at the top of this page to self-evaluation mode and pick the same 3 to 5 your manager is likely to rate.
Vague vs Specific Performance Review Comments
A vague comment describes a trait. A specific comment describes what someone did, when they did it and what happened as a result. The fix is the same for managers and employees: the behavior, one example and the impact.
Here are four manager comments and two self-evaluation lines, before and after the rewrite.
None of the stronger versions needs an adjective like “great” or “poor”. The example carries the judgment, and the reader can check it.
Phrases to Avoid in a Performance Review
Avoid personality labels, comparisons with coworkers, absolutes such as “always” and “never”, vague hedging, promises about pay, and any comment that touches a protected characteristic. These comments are hard to act on, and the last group can turn a review into evidence in a discrimination claim.
In the US, the Equal Employment Opportunity Commission’s guidance on performance evaluations tells employers to communicate performance standards to employees, apply them consistently and include factual details in evaluations. In Great Britain, the Equality Act 2010 protects nine characteristics at work, including age, disability, pregnancy and maternity, race, religion or belief, sex and sexual orientation, as listed on GOV.UK. Other countries have their own equality laws, so if you manage people in several countries, check the local rules with HR or an employment lawyer.
Personality labels
Words like “abrasive”, “lazy” or “not a culture fit” describe the person, not the work. They give the employee nothing to change and are easy to challenge.
Describe what the person did and the effect it had.Comparisons with coworkers
“Not as strong as Kenji” turns a review into a ranking and puts a colleague’s name in someone else’s file.
Compare performance against the role’s expectations.Protected characteristics or protected leave
Comments such as “great energy for a young hire”, remarks about an accent or health, or ratings that fall after parental leave can read as discrimination.
Rate only job-related behavior and results, and remove anything else.Absolutes
“Always late” and “never listens” invite an argument about the one exception instead of the pattern.
Give counts and dates: three of five deadlines missed.Hedging
“Maybe a little” and “kind of” soften the message until the employee doesn’t realize there is a problem.
State the rating and the reason plainly.Promises about pay or promotion
“You’ll definitely be promoted next year” commits the company to something a manager rarely controls alone.
Explain the criteria and the process instead.
Ratings and Calibration: What Meets Expectations Means
“Meets expectations” means the person did the job the role requires, to the standard agreed at the start of the period. It is a good rating. On a healthy team most people should get it in most competencies, which is why ratings cluster there.
That clustering is often treated as a problem. We don’t think it usually is. A rating scale exists to separate the unusual from the expected, and on most teams most work is the expected kind. The real trouble comes from inflation on one side and avoidance on the other: managers who rate everyone as exceeding to skip a hard conversation, and managers who never use needs improvement until the person is already on the way out.
Exceeds expectations
AboveResults clearly beyond the role’s expectations, across the whole period. One great month is not enough.
Meets expectations
AtThe job done well and consistently. This should be the most common rating on a healthy team.
Needs improvement
BelowA gap the person can close with a clear goal and support. It should never be the first they hear of it.
Calibration is the meeting where managers compare ratings across a team or department, so the same rating means the same thing for everyone. Bring your examples. A rating backed by a date and a result rarely moves in calibration. A rating backed by an impression often does.
If your company treats meets expectations as a warning, the problem is the scale, not the employee.
Most HR platforms with a performance module let you collect self-evaluations and manager reviews in the same cycle, including HiBob, BambooHR and Rippling, which we review in detail.
Manager Review vs Self-Evaluation
A manager review judges performance against the role and decides the rating. A self-evaluation puts the employee’s evidence and view on record before that decision is made. Both cover the same competencies, but they do different jobs.
Manager review
Written about the employee- Written by
- The direct manager
- Voice
- Second person (“you”)
- Main job
- Rate performance and set goals
- Common mistake
- Writing from memory of the last few weeks
- Best evidence
- Notes and results logged across the period
Self-evaluation
Written by the employee- Written by
- The employee
- Voice
- First person (“I”)
- Main job
- Put your results on record before ratings are set
- Common mistake
- Listing duties instead of results
- Best evidence
- Metrics, dates and feedback from others
Regular feedback between cycles makes both documents easier to write. The tools in our employee engagement software guide handle recognition and check-ins, and most HRIS platforms keep the review history in the employee’s record.
Read nextHow to Measure Culture in Global Teams: 8 Key Metrics 2026→Frequently Asked Questions
What are good performance review phrases?
Good performance review phrases describe a specific behavior at a clear rating level, such as “flags risks early, with options, instead of at the deadline.” They avoid personality labels and absolutes. The best ones are followed by one example from the review period, which turns a stock line into feedback the employee can act on.
How do I write a self-evaluation?
List your main results for the period with numbers and dates, pick 3 to 5 competencies, and write two or three sentences on each. Include one honest growth area and what you are already doing about it, then propose a goal for next period. Use the first person and the past tense.
What should you not say in a performance review?
Avoid personality labels, comparisons with named coworkers, words like “always” and “never”, promises about pay or promotion, and anything related to a protected characteristic such as age, disability, pregnancy, race, religion or sex. Stick to job-related behavior and results you can show with an example.
How long should a performance review be?
For most roles, 300 to 600 words is enough: a short summary, two to four sentences per competency, development goals and a closing line. Length matters less than evidence. A 300-word review with three real examples is more useful than 1,000 words of stock phrases.
What does meets expectations mean in a performance review?
It means the employee did the job the role requires, to the standard agreed at the start of the period. It is a positive rating, and on most teams it should be the most common one. It is not a warning.
How do you write a review for an underperforming employee?
State the gap plainly, with the specific cases and dates behind it, and explain its effect on the team or customers. Then set one or two measurable goals with a check-in date and say what support you will provide. If this is the first time the person hears about the problem, the feedback came too late, so start regular check-ins now.
Can I use a generator or AI to write my performance review?
Yes, as a first draft. The generator on this page builds the structure and wording from our phrase bank and runs in your browser, so nothing you type is sent anywhere. Before you submit any draft, replace the prompts with real examples and read it once as the person receiving it.
How many competencies should a performance review cover?
Three to five is the right range for most reviews. Fewer can miss an important part of the role, and more dilutes the message and makes the review harder to discuss in one meeting.
How do you review remote employees fairly?
Rate results and agreed behaviors rather than visibility or hours online. Written updates, delivered work and feedback from partner teams are better evidence for remote staff than impressions from meetings. Our remote work statistics and our guide to building culture in distributed teams cover what tends to go wrong.
What should I do if I disagree with my performance review?
Ask for the specific examples behind the rating, then respond in writing with your own evidence, keeping to facts and dates. Most companies let you add comments to the review record. If you decide the role is no longer right for you, our resignation letter generator helps you leave on good terms.
Running reviews in documents and email threads? Compare the talent management platforms that handle goals, self-evaluations, manager reviews and calibration in one place.
