4 exercises — the essential phrases for clarifying, agreeing, buying time, and closing meetings. The building blocks of every English-language meeting.
0 / 19 completed
1 / 19
You didn't understand a colleague's point in a meeting. Which phrase best asks for clarification without sounding rude?
Option B is the standard professional clarification phrase. Let's break it down:
"Could you clarify…" — This is a soft modal. More polite than "Can you explain" or "What do you mean?" The word "clarify" implies the issue might be your own lack of understanding, not that the speaker was unclear.
"…what you mean by that" — Targets the ambiguous part without repeating it (which can sound sarcastic).
"I want to make sure I follow correctly" — This clause signals good intent. It reframes the request as you working to understand, rather than challenging the speaker.
Other useful clarification phrases: • "Sorry, I didn't quite catch that — could you repeat?" • "Could you give an example of what you mean?" • "When you say [X], do you mean [Y]?" • "I just want to confirm I understand — are you saying [paraphrase]?"
What to avoid: • "What?" alone — sounds impatient • "That makes no sense" — sounds dismissive • "So basically you're saying [oversimplification]?" — misrepresents the speaker and can start a debate
2 / 19
A colleague suggests a solution. You genuinely agree with their idea. Which phrase shows the most engaged, professional agreement?
Option C is active, engaged agreement — the kind that builds good team dynamics and shows you were actually listening:
"That makes a lot of sense to me" — clear, confident affirmation (not passive like "I suppose") "especially the part about [specific detail]" — proves you were listening; you can name the specific element that resonated "I think that solves [specific problem]" — connects the idea to the actual problem, adding value to the discussion
Why the others fail: "Yeah, sure" — too casual in professional meetings; sounds like you're not really engaged "OK" — minimal; gives no signal about whether you support, oppose, or are neutral "I suppose that could work" — actually signals weak or reluctant agreement; it sounds like "I'll accept it but I'm not convinced"
Agreement phrases by strength: Strong: "Exactly." / "That's a really solid approach." / "Fully agree — especially because…" Moderate: "That makes sense." / "I'd support that." / "I think that works." Weak (avoid unless true): "I suppose…" / "Maybe…" / "If you think so…"
3 / 19
The meeting is moving to a vote on a technical decision. You're not sure yet and need more time to think. Which phrase is most appropriate?
Option C is the professional way to request more time in a meeting:
States a reason: "I want to think through one dependency" — not just "I'm not ready" Makes a specific request: "come back to me on this one" — tells the facilitator exactly what you need Offers a constructive bridge: "Could we take the other items first" — doesn't delay the whole meeting; provides a path forward
Why this works: Meetings have momentum. Saying "I'm not ready" without a path forward stalls everyone. Saying "let's take the other items and come back to me" keeps the meeting moving while protecting your right to give a considered response.
Why "I don't have an opinion" is often wrong: In technical decisions, "no opinion" is rarely true — it usually means "I don't want to take responsibility for the decision." If you genuinely have no opinion after thinking about it, "I defer to the team" is more honest and professional than "no opinion."
Buying time phrases: • "I'd like to think through [X] before I commit — can we revisit me at the end?" • "I need 2 minutes — can we move to the next topic and come back?" • "I'm on the fence — let me hear the remaining perspectives first."
4 / 19
The meeting is wrapping up. You're the last person in the agenda. Which phrase closes a meeting professionally?
Option C is the professional meeting close that actually ensures the meeting produced something:
Signals completion: "I think we've covered everything on the agenda" — context for the close Summarises the decision: "we agreed to [decision]" — critical; this is what the meeting was for States the next step with owner and deadline: "[name] is owning that by Thursday" — the meeting's output is a commitment, not just a discussion Acknowledges the people: "Thanks for the focused discussion" — not generic, acknowledges the quality of participation Final check: "any final questions before we close?" — prevents follow-up emails about things that could have been said in the meeting
The test of a good meeting close: If someone who missed the meeting asks "what did you decide?" — can you answer in one or two clear sentences? If yes, you closed well. If you say "well, we discussed a few things…" — the meeting didn't produce a clear output.
Meeting close checklist: ✓ One summary sentence of the decision or output ✓ Named action item(s) with owner and deadline ✓ Any outstanding items moved to parking lot or follow-up ✓ Thanks + final questions
5 / 19
John from the QA team just posted this comment on your code review: 'This logic seems a little convoluted. Can you explain it more clearly?' Which response is most appropriate and professional?
The key here is acknowledging the feedback and offering to explain your approach. Option 1 directly addresses the concern and demonstrates willingness to clarify. Options 2 and 3 are too dismissive or noncommittal. Option 4 completely misses the point of the comment.
6 / 19
You're in a Slack channel discussing potential improvements to the API endpoint for user authentication. A junior developer suggests using OAuth 2.0 instead of JWT. Which phrase best conveys your support for this suggestion?
This scenario requires you to show positive engagement. Option 1 is critical and negative. Option 2 demonstrates openness and encourages further discussion. Options 3 and 4 are dismissive and unhelpful. Framing the suggestion as 'interesting' adds a layer of politeness.
7 / 19
During your daily standup, you're asked about the progress on Task X. You want to briefly explain that you encountered an unexpected error during testing but haven't yet resolved it. Which statement is most effective for this context?
Standups are about quick updates. Option 1 is misleading. Option 2 provides a concise summary of the situation – acknowledging the problem without dwelling on it. Options 3 and 4 are overly optimistic or seek help directly, which isn't appropriate for standup format.
8 / 19
You've drafted a PR description for your code changes. A reviewer comments: 'Could you add more detail about the performance implications of this change?' Which phrase would be most appropriate to include in your response?
This requires you to acknowledge a valid concern and demonstrate willingness to address it. Option 1 is too vague. Option 2 shows awareness of the request while still maintaining control over the process. Options 3 and 4 are dismissive or shift responsibility.
9 / 19
The team is about to conclude a meeting discussing the rollout of the new feature. You want to formally end the discussion. Which phrase best summarizes this situation?
This is a standard closing phrase. Option 1 is informal and lacks clarity. Option 2 directly signals the transition to the next item. Options 3 and 4 are unnecessary or disruptive at this stage.
10 / 19
John from the QA team just posted this comment on your code review: 'This logic seems a little convoluted. Can you explain it more clearly?' Which response is most appropriate and professional?
The key here is acknowledging the feedback and offering to explain your approach. Option 1 directly addresses the concern and demonstrates willingness to clarify. Options 2 and 3 are too dismissive or noncommittal. Option 4 completely misses the point of the comment.
11 / 19
You're in a Slack channel discussing potential improvements to the API endpoint for user authentication. A junior developer suggests using OAuth 2.0 instead of JWT. Which phrase best conveys your support for this suggestion?
This scenario requires you to show positive engagement. Option 1 is critical and negative. Option 2 demonstrates openness and encourages further discussion. Options 3 and 4 are dismissive and unhelpful. Framing the suggestion as 'interesting' adds a layer of politeness.
12 / 19
During your daily standup, you're asked about the progress on Task X. You want to briefly explain that you encountered an unexpected error during testing but haven't yet resolved it. Which statement is most effective for this context?
Standups are about quick updates. Option 1 is misleading. Option 2 provides a concise summary of the situation – acknowledging the problem without dwelling on it. Options 3 and 4 are overly optimistic or seek help directly, which isn't appropriate for standup format.
13 / 19
You've drafted a PR description for your code changes. A reviewer comments: 'Could you add more detail about the performance implications of this change?' Which phrase would be most appropriate to include in your response?
This requires you to acknowledge a valid concern and demonstrate willingness to address it. Option 1 is too vague. Option 2 shows awareness of the request while still maintaining control over the process. Options 3 and 4 are dismissive or shift responsibility.
14 / 19
The team is about to conclude a meeting discussing the rollout of the new feature. You want to formally end the discussion. Which phrase best summarizes this situation?
This is a standard closing phrase. Option 1 is informal and lacks clarity. Option 2 directly signals the transition to the next item. Options 3 and 4 are unnecessary or disruptive at this stage.
15 / 19
John from the QA team just posted this comment on your code review: 'This logic seems a little convoluted. Can you explain it more clearly?' Which response is most appropriate and professional?
The key here is acknowledging the feedback and offering to explain your approach. Option 1 directly addresses the concern and demonstrates willingness to clarify. Options 2 and 3 are too dismissive or noncommittal. Option 4 completely misses the point of the comment.
16 / 19
You're in a Slack channel discussing potential improvements to the API endpoint for user authentication. A junior developer suggests using OAuth 2.0 instead of JWT. Which phrase best conveys your support for this suggestion?
This scenario requires you to show positive engagement. Option 1 is critical and negative. Option 2 demonstrates openness and encourages further discussion. Options 3 and 4 are dismissive and unhelpful. Framing the suggestion as 'interesting' adds a layer of politeness.
17 / 19
During your daily standup, you're asked about the progress on Task X. You want to briefly explain that you encountered an unexpected error during testing but haven't yet resolved it. Which statement is most effective for this context?
Standups are about quick updates. Option 1 is misleading. Option 2 provides a concise summary of the situation – acknowledging the problem without dwelling on it. Options 3 and 4 are overly optimistic or seek help directly, which isn't appropriate for standup format.
18 / 19
You've drafted a PR description for your code changes. A reviewer comments: 'Could you add more detail about the performance implications of this change?' Which phrase would be most appropriate to include in your response?
This requires you to acknowledge a valid concern and demonstrate willingness to address it. Option 1 is too vague. Option 2 shows awareness of the request while still maintaining control over the process. Options 3 and 4 are dismissive or shift responsibility.
19 / 19
The team is about to conclude a meeting discussing the rollout of the new feature. You want to formally end the discussion. Which phrase best summarizes this situation?
This is a standard closing phrase. Option 1 is informal and lacks clarity. Option 2 directly signals the transition to the next item. Options 3 and 4 are unnecessary or disruptive at this stage.
What will I practise in "Meeting Phrases & Vocabulary"?
This module focuses on Meetings & Collaboration — real workplace phrasing you'll use on the job. It contains 19 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 19 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Meetings & Collaboration exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around meetings & collaboration — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Meetings & Collaboration exercises?
See the Meetings & Collaboration hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.