What to Say When You Don't Understand in an English Meeting

Every professional using English at work eventually hits the same moment: a sentence goes by too fast, an idiom doesn't land, or an unfamiliar accent throws you off, and you have no idea what was just said. What to say when you don't understand in an English meeting is not a fluency problem — it's a skill with its own vocabulary, and fluent speakers use it constantly too. The fix isn't silence or a guilty nod. It's a small set of reusable phrases for three situations: asking someone to repeat, confirming what you think you heard, and requesting written follow-up when the stakes are too high to trust your ear alone.

What should you say when you don't understand something in an English meeting?

Say so directly and point at what you missed, rather than announcing that you're lost in general. "Sorry, could you repeat the last part?" or "I didn't catch the number you mentioned" both work because they name a specific gap, which keeps the exchange short and lets the speaker fix exactly the right thing instead of re-explaining everything.

Three short phrases cover most situations:

• "Sorry, could you say that again?"
• "I missed the part about the deadline — could you repeat it?"
• "Could you slow down slightly? I want to make sure I get this right."

None of these apologize for your English level. They apologize for missing one detail, which is a completely normal meeting event — audio cuts out, someone talks over a colleague, a name gets mumbled. Native speakers ask for repeats constantly; the difference is they don't attach any meaning to it. Treat the request the same way: a one-line technical correction, not a confession.

In practice, this sounds like: a colleague says "we're pushing the launch to next Thursday," you catch "pushing" and "Thursday" but not which one, and you ask "Sorry, pushing it to Thursday — this Thursday or next week?" The exchange takes five seconds and moves the meeting forward, which is the real goal — not perfect comprehension of every sentence, but the correct information landing in your notes.

Why do professionals pretend to understand instead of asking?

Most people pretend to understand because they read a clarifying question as a sign of weakness, not because the question itself is hard to form. Research on meeting behavior describes this kind of pretend participation as "commonplace" in workplace meetings, according to a 2026 study in Group & Organization Management.

That pattern shows up across roles and seniority levels, not only among newer or junior staff.

For non-native speakers, the same instinct gets amplified by language-specific anxiety on top of the ordinary version. A study of multinational companies found that foreign-language anxiety pushes employees toward communication avoidance and withdrawal — staying quiet, nodding along, switching to their first language with anyone who shares it — even when their actual English proficiency is high enough to follow the conversation, according to Aichhorn and Puck's 2017 research on language barriers in MNCs.

The cost of pretending is higher than the cost of asking. A missed number becomes a wrong invoice. A misread instruction becomes a deliverable built to the wrong spec. Reframing the moment as technical — a gap in the audio, not a gap in your competence — is what makes asking easier the second and third time. It's the same reframe that helps with jumping into a fast-moving discussion in the first place; see how to speak up in an English meeting without interrupting for the phrases that get you into the conversation before this moment even comes up.

How do you ask someone to repeat themselves without sounding lost?

Ask for the specific piece you missed and offer a guess if you have one, so the other person corrects rather than repeats from scratch. "Did you say the client meeting is Tuesday or Thursday?" gets answered in three words, while "sorry, what?" forces the speaker to reconstruct the whole sentence and makes you sound further behind than you are.

This works because a targeted question signals that you followed most of the discussion and only lost one thread. It also respects the room's time, which matters in meetings running on a tight agenda. A few patterns to keep ready:

• "Did you say [X] or [Y]?" — for anything you half-caught
• "Sorry, one more time on the last point — I want to write it down correctly"
• "Quick check: when you said 'push it back,' did you mean the deadline or the whole project?"

That last pattern matters more than it looks. Understanding every word but not the intended meaning is a different problem from missing words outright, and naming which one it is helps the other person answer faster.

If the same gap keeps recurring with one person — an accent you're still tuning into, a habit of trailing off mid-sentence — it's fair to say so directly: "I sometimes miss the end of your sentences on calls — would you mind pausing slightly before moving on?" That's a request about audio, not about them.

How do you confirm you understood correctly?

Summarize what you heard in your own words and ask a single yes/no question at the end, rather than repeating the sentence back verbatim. "So the plan is we ship the beta Friday and email the client Monday — is that right?" turns a fast exchange into something both people can check before it leaves the room.

This paraphrase-and-confirm pattern is worth building into a habit for anything with a number, date, owner, or dollar amount attached, since those are the details that are both easy to mishear and expensive to get wrong.

Situation	What to say	Why it works
You missed a word or phrase	"Sorry, could you repeat that last part?"	Points to one specific gap, not general confusion
You missed a number or date	"Can you confirm — was that the 12th or the 20th?"	Numbers are the costliest thing to mishear in a meeting
You heard the words but not the intent	"When you say 'fast-track it,' do you mean skip the review stage?"	Separates vocabulary from meaning
You want to confirm before the meeting ends	"So to confirm, I'm sending the draft to Priya by Friday — is that right?"	Turns a spoken agreement into a checkable commitment
The topic is too important to rely on memory	"Could you drop that in the chat, or follow up by email, so I have it in writing?"	Removes the risk of misremembering spoken English later

Paraphrasing also buys you a few extra seconds to process what was said, which is often the real problem — not the vocabulary itself, but the speed at which it arrives.

What do you say when you need written confirmation instead of verbal?

Ask for the detail in writing when a mistake would be costly. "Could you send that in an email so I have the exact wording?" or "Mind putting the numbers in the chat? I want to double-check before I forward them" both frame the request as ordinary due diligence, not as a language gap.

This matters most for anything a third party will see: a client-facing figure, a budget line, a legal term, a deadline that goes into a shared calendar. Relying on your memory of spoken English for these is a risk regardless of your level, because meetings move fast for everyone and audio quality varies. A short, specific written-confirmation request protects you and the person who spoke, since it catches their slip of the tongue as readily as your mishearing.

Two versions to keep ready, depending on formality:

• Formal: "Would you mind sending a quick summary after the call? I want to make sure I have the action items right."
• Informal / same team: "Can you drop the key numbers in Slack? I'll pull them from there."

This habit costs nothing socially and saves real time later, since a written record means nobody has to reconstruct the meeting from memory a week on.

Is it unprofessional to ask for clarification in an English meeting?

No — in most English-language business meetings, asking for clarification is standard practice, not a mark against you. Roughly 1.75 billion people speak English at a useful level, about one in four of the world's population, so most English used in global business happens between people for whom it is a second or third language, not a native one.

That framing matters because the alternative — staying quiet to avoid looking uncertain — is the more visible risk. A wrong deliverable or a missed deadline traced back to a misheard instruction reads as far less professional than a five-second clarifying question ever could, and colleagues in mixed-language teams expect and plan for these checks as a normal part of how meetings run.

The professionals who come across as most capable in English meetings aren't the ones who never miss a word — they're the ones who recover from a missed word in one clean sentence and keep the meeting moving. That recovery is a specific, learnable skill, which is exactly what a structured method drills: Worklish builds it into scenarios at the sentence level, working through Vocabulary, Translate, Word Bank, Fill In, and Role Play for your actual job function, so the phrases above are already rehearsed before you need them live in a meeting.