Asking for Clarification in English Without Losing Face
Six lines that ask for clarification without sounding like you were not listening, plus a readback script, a three-line written follow-up, and a rehearsal routine that shows how to learn english quickly for work.
On this page
Why "sorry?" three times costs more than one precise question
At the end of a video call your manager runs through a handover. The deadline is clear. Who owns the second half, and what exactly has to be delivered, are not. You say "sorry?" once and she repeats the sentence a little louder. You say it again and she starts over from the beginning, faster. By the third time the room has decided something about you, and it is not about your English.
The problem is not the word. It is that "sorry?" carries no information about what failed. It asks for the whole message again, so the speaker has to guess which part you missed, and the guess is usually wrong. It also costs the listener more than it costs you: they repeat themselves, they lose their place, and they start to wonder whether the meeting could have been an email.
A better frame exists, and it comes from places where misunderstanding is expensive. In hospital teams the standard tool is not a louder repetition but a check-back: the receiver repeats the instruction in their own words, and the sender confirms. AHRQ's TeamSTEPPS programme calls this closed-loop communication, and it notes that check-backs are used specifically to support patients with limited English proficiency. The professional move when you are unsure is to say what you did hear, not to ask for everything again.
Four clarification targets: a word, the task, the priority, the deadline
Most half-heard instructions fail in one of four places, and each place has its own question.
| What is unclear | What it sounds like | The line to use |
|---|---|---|
| A word or an acronym | "the QBR deck" | Sorry, when you say QBR, do you mean the quarterly review pack? |
| The task itself | "own the migration" | Can I check what own means here: the plan, or the execution too? |
| The priority | two things, both urgent | Of these two, which should I drop if I run out of time? |
| The deadline | "by end of week" | Is that Friday your time or mine, and does it include the review? |
Naming the target is the whole trick. Sorry, I didn't catch the deadline is a complaint. Is that Friday your time or mine? is a question with an answer. The second version also proves you were listening, because you can only ask it if you caught the rest.
The readback: repeat the request in your own words
The readback replaces the third "sorry?", and it takes about five seconds.
- Signal what you are doing.
Let me play that back so I'm sure I have it. - Restate the request with owner, output and time.
So I send the revised deck to the client by Thursday, and Priya handles the numbers. - Ask for a correction, not a repetition.
Is that right, or did I mix up the day?
The third line matters most. Is that right? invites a yes or a fix. Did you say Thursday? invites a repeat of the one fact you already have. AHRQ's own example works the same way: a nurse taking a telephone order reads it back in full, and the doctor closes the loop with one word, Correct.
Two rules keep a readback from sounding like an exam. Keep it to one sentence with three facts; four sentences is a performance. And read back only what you will act on. If an instruction has five parts and you are sure of three, confirm the three and ask about the two.
The three-line written follow-up
Some instructions arrive at the worst moment: in a lift, in the last thirty seconds of a call, in a language you were not braced for. A short written follow-up is not an admission that you failed. It is the written half of the same loop.
- What you heard:
Quick note on the handover: I have the client deck due Thursday and Priya on the numbers. - The one thing you are unsure about:
The part I want to confirm is whether you want the pricing section in this version. - What you are doing next:
I'll send you the draft on Wednesday morning so you can correct me before it goes out.
Three lines sent within the hour beat a perfect memory, and they leave a record. That is why teams spread across time zones write them even when everyone shares a first language.
Tone control: polite, neutral, blunt
The same request can sound like a favour, a procedure or an accusation. Three things change: whether you give a reason, whether you take the blame, and whether you ask or tell.
| Register | Example | Where it works |
|---|---|---|
| Soft | Sorry, I think I missed part of that. Could you run through the owner again? | first weeks, senior stakeholders, phone calls |
| Neutral | I want to make sure I have the owner right: is it Priya? | most meetings, most colleagues |
| Direct | Which of the two is the priority if I can only finish one? | tight deadlines, established teams |
The soft version works twice and then stops working: repeated self-blame reads as uncertainty about the job rather than politeness. The direct version is not rude if it contains a real constraint, because I can only finish one is a fact. What makes a line blunt is an imperative with no reason attached: Repeat that.
Three scenarios to rehearse
- The end of a call. Your manager gives a two-part instruction and you caught only the deadline. Play back owner, output and time, then ask one targeted question.
- The acronym. A colleague says the report goes to "the RMT" and you do not know what that is. Ask what the letters stand for, then confirm the action rather than the word.
- The conflict. Two people hand you urgent work in the same hour. Name both pieces of work, ask which one to drop, and put the answer in writing.
Rehearse each scenario out loud with a partner or an AI speaking partner. One person gives the instruction at normal speed; the other uses only the lines above; both stop when the loop closes. Then swap roles. The listener's checklist has three questions. Did you name the target? Did you restate instead of re-asking? Did you leave the conversation with a next action?
How to learn english quickly for work by rehearsing six lines
Most people try to learn workplace English by widening their vocabulary. The faster return is narrower: six sentences you can say without thinking, aimed at the six moments where conversations actually break.
- one line to slow a fast speaker down without stopping them
- one line to ask about a word
- one line to ask what a task includes
- one line to ask which of two things comes first
- one line to confirm a deadline and a time zone
- one readback frame you can fill with any three facts
Fifteen minutes a day is enough if the fifteen minutes are the same six lines against different prompts. Write your own version of each in the words you would actually use; a sentence you would not say is a sentence you will not produce under pressure. Then use one of them in a real conversation the same week, and notice that the conversation continues instead of restarting.
Frequently asked questions
How do I ask my manager to repeat something politely in English?
Ask for the part, not the whole message. Sorry, I missed the part after the deadline, could you say that again? gives your manager something specific to repeat, and it costs her five seconds rather than a minute. Add a readback when the instruction has more than one part, and keep the reason short: I want to get the owner right is enough. Politeness in English comes mostly from the form of the question, so could you and would you mind do the work that a softer tone of voice might do in your first language.
What is a readback and why does it help at work?
A readback is a closed-loop check: you repeat the request in your own words, and the person who gave it confirms or corrects you. It helps for three reasons. It catches the one detail that was wrong before you act on it, it shows that you were listening rather than guessing, and it gives the other person permission to correct you without criticising you. The form is deliberately plain, which is why it works in a noisy meeting and in a written message.