English Phrases for Performance Reviews at Work: What to Say and How to Say It

Why performance reviews fail non-native speakers

Performance reviews are not really about your performance. They are about how well you can describe your performance in a short window, under pressure, while someone takes notes. That is a speaking task, and it is harder in a second language than almost any other workplace conversation.

The problem is rarely vocabulary. Most professionals at B2 level know the word "achievement" and can use "improve" correctly. The problem is framing. A native speaker says "I led the migration and cut response time by 40 percent". A non-native speaker, nervous and reaching for safe words, says "I worked on the migration, it was good". The second sentence is grammatically fine and professionally invisible.

There is also a cultural gap. Many learners come from workplaces where self-promotion is rude, and reviews reward humility. In an English-speaking office, the review is one of the few places where you are expected to describe your own value directly. Understating it reads as underperformance, not modesty.

The fix is not to become boastful. It is to learn a small set of sentence frames that let you state facts clearly, and to practise them until they come out without hesitation. The rest of this article gives you those frames.

The three-part structure that carries every answer

Almost every strong review answer has the same skeleton. First you state the result, then you name the evidence, then you connect it forward. Result, evidence, direction. That is it.

Here is the difference it makes. Weak answer: "I think I did a good job this year." Strong answer: "I closed the two largest client accounts this year, which brought in around 120,000 in new revenue, and I want to build on that by leading the expansion into the next region." Same person, same year, completely different impression.

The evidence step is where most people fall down. You do not need a spreadsheet. You need one concrete number, name, or event. A project name, a percentage, a client, a deadline you beat. If you cannot name one, the claim is not ready to be said out loud yet.

Write down your three biggest achievements before the meeting, each as a single sentence in this structure. You will find that the writing forces you to find the evidence, and the evidence is what your manager actually remembers.

English phrases for performance reviews at work: talking about your strengths

Here are the phrases that do the heavy lifting, grouped by what you want to convey. They are templates: swap in your own result and evidence.

For results you delivered: "I delivered X, which led to Y." "My main contribution was X, and it resulted in Y." "I took ownership of X and brought it in ahead of schedule." The key word is "led to" or "resulted in". It forces you to name the outcome, not just the activity.

For problems you solved: "When X happened, I stepped in and Y." "I identified the bottleneck in X and fixed it by Y." Managers hear problem-solving language as leadership, even at junior levels.

For collaboration: "I worked closely with X to deliver Y." "I brought together the X and Y teams to resolve Z." Be specific about who and what. "I am a team player" is the phrase that gets you marked down, because it is what everyone says and it proves nothing.

A common mistake is stacking verbs: "I helped, supported, and contributed to the project." Three weak verbs do not add up to one strong one. Pick the verb that is actually true, "led", "built", "delivered", "negotiated", and let the sentence stand on it.

How to talk about weaknesses without undermining yourself

Every review asks about weaknesses, and the question is a trap if you answer it literally. The goal is not to confess. It is to show that you can see your own gaps and have already started closing them.

The safe frame is: name a real but contained weakness, then show the action you have already taken. "I used to struggle with X, so I have been doing Y, and it has improved Z." The past tense matters. A weakness you are already fixing reads as self-awareness; a weakness you are still sitting in reads as a problem.

Pick something genuine but not fatal. "I can be too detail-oriented" is tired and transparent. Better: "I found it hard to push back in meetings, so I have been preparing one question or objection before each one, and I now speak up in most of them." That is honest, specific, and shows growth.

Avoid the false-humility phrases: "I work too hard", "I care too much", "I am a perfectionist". Managers in English-speaking workplaces have heard these so often that they now read as evasive. A real, fixed weakness earns more trust than a disguised compliment. If you are unsure how a phrase will land, saying it aloud to a tutor who responds the way a manager would, the way Tutoro's conversation practice does, is a quick way to hear it from the other side.

Phrases for asking for a raise or promotion

This is the part most learners skip because it feels confrontational. But a performance review is the one meeting where asking is expected, and not asking is often read as not wanting it.

The frame is: anchor to evidence, then state the request plainly. "Based on the results we have discussed, I would like to discuss a move to the senior role." Or "Given the revenue I brought in this year, I would like to talk about a salary adjustment." The word "given" or "based on" does the work: it ties the request to facts already agreed in the room.

Do not soften the request into a question about possibility. "Is there any chance of a promotion?" invites the answer "not right now". "I would like to discuss a promotion" starts the actual conversation. One is a hope, the other is a position.

If the answer is no, you still win by asking the follow-up: "What would I need to demonstrate over the next six months to get there?" That turns a rejection into a plan, and it is the single most useful sentence in this entire article.

How to practise before the meeting

Reading these phrases is not the same as being able to produce them when your manager is looking at you. The phrases have to live in your mouth, not on a page. That means saying them out loud, several times, in full sentences.

Start by writing your three achievement sentences in the result-evidence-direction structure. Then say them aloud, once slowly, once at normal speed. Then say them without looking. If you stumble on a phrase, that is the one to practise more, because it is the one you will stumble on in the room.

Better still, rehearse the whole conversation, not just your lines. The review is a dialogue: your manager will follow up, ask for detail, push on a number. You need to answer follow-up questions, not recite a script. That is a skill you can only build by actually having the conversation.

One practical way to rehearse is to run the conversation with someone who will push back, the way a real manager does. An AI English tutor can play that role: it asks the follow-up questions, listens to your answers, and lets you repeat a sentence until it comes out clean. That is the kind of pressure-free repetition that turns a script into speech.

Tutoro runs performance-review conversations as live speaking practice. You talk through your achievements and goals with a tutor who responds in character, and your pronunciation is scored word by word as you speak, so you hear exactly which phrases need another pass. It suits learners who want to rehearse a specific meeting before it happens; it does not replace the meeting itself, and it is not for anyone looking for a written phrase list they never have to say out loud.

What not to say in an English performance review

Some phrases do active damage, and they are worth naming so you can delete them. "I did my best" is the worst of them: it is an excuse with no information in it, and it signals that the result did not happen. "It was a team effort" is fine once, but if it is your answer to every question, your manager cannot tell what you contributed.

"I am not sure, maybe" as an opening to your own achievement is self-sabotage. You are the only person in the room who knows what you did. State it.

Also avoid the conditional hedge on things that already happened: "I think I might have helped with the launch." The launch happened, you were there, say "I helped with the launch". Hedging on past facts makes everything you say sound uncertain, including the parts that are true.

The pattern underneath all of these is the same: vague verbs, no evidence, no ownership. The fix is the same as everywhere else in this article. Name the result, name the evidence, say it plainly.

A short script you can adapt

Here is a complete answer you can reshape for your own review, built entirely from the frames above.

"This year my main contribution was leading the website redesign. It shipped in March, and it resulted in a 25 percent increase in sign-ups by June. The part I am most proud of is bringing together the design and engineering teams, who had not worked well together before, and getting the project delivered on time. One area I have been working on is delegating more. I used to try to review every detail myself, so I have been handing off smaller tasks and checking in weekly instead of daily. Based on these results, I would like to discuss taking on the product lead role next year."

Notice what is not there: no "I think", no "maybe", no "I worked hard". Every sentence has a fact in it. That is the whole skill, and it is learnable.

If you want to go deeper, the University of California's self-evaluation guidance offers a framework for writing honest, evidence-based self-assessments, and Harvard Business Review's advice on self-promotion explains why stating your results plainly is a skill, not arrogance. For the language itself, the British Council's business English resources list the standard phrases native speakers use in workplace conversations.