Business Meeting English Shadowing: Updates, Decisions and Next Steps
Practise business meeting English shadowing: separate updates from decisions, make the next action clear, name ownership and recap what happens after the meeting.
Separate what is new from what is decided, then name the next action and owner before the meeting closes.
“That sounds good” can be genuine agreement. It can also be the meeting equivalent of smiling at a menu. “We should…” is useful too—but it is not yet an owner.
Don’t leave with vibes; leave with a decision: Update → Decide → Assign → Confirm.
Start with the update: what changed?
A useful update gives the meeting new information without turning immediately into a recommendation or decision.
Original practice example
The supplier replied this morning, and delivery has moved to Friday.
This is information. It changes the meeting context, but it does not yet say what the team will do.
Useful when a date, dependency or external condition changes.
Meeting state: Update.
Change the supplier/date details and keep the line informational.
Explore more language-learning guides in Media-Based Language Learning.
A proposal is not automatically a decision
British Council meeting guidance recommends clarifying and checking agreement. That matters because positive language can still leave the decision state fuzzy.
Original practice example
We should move the review meeting.
This proposes a response to the update. It does not by itself prove that the group has decided to move anything.
Useful when suggesting a next move after new information arrives.
Meeting state: Proposal.
Replace move the review meeting with another possible response.
Original practice example
So, are we agreeing to move the review to Thursday?
This checks whether the discussion has crossed the line from suggestion to decision.
Useful when several people sound positive but the final choice is still not explicit.
Meeting state: Decision check.
Keep So, are we agreeing to…? and replace the decision.
Turn the decision into an owned action
British Council recommends recording action points with tasks and who will do them. Current work-management guidance also treats a clear owner as part of making an action trackable. But the language still needs one more step: the owner must actually accept.
Original practice example
Maya, can you update the calendar invite?
This proposes ownership. It is not yet the same as Maya accepting the task.
Useful when a decision creates a specific follow-up action.
Meeting state: Proposed owner.
Change the name and task, then wait for an acceptance line.
Original practice example
Yes, I’ll update it this afternoon.
Now the task has an owner and a stated timing commitment.
Useful when accepting a meeting action item clearly.
Meeting state: Accepted action.
Replace the action and timing with a realistic work example.
Close with one shared version
The final recap should match what was actually decided and accepted—not what somebody merely suggested earlier.
Original practice example
Great—review on Thursday, and Maya updates the invite today.
The recap compresses the decision and owned next step into one shared version.
Useful near the close of a meeting.
Meeting state: Confirmed recap.
Build a recap with one decision and one accepted action.
Meeting State Board
Before opening the model, label each line by state. The goal is to track commitment, not just language.
Round 1
“The supplier says delivery is now Friday.”
See the state
Update. New information only.
Round 2
“We should move the review meeting.”
See the state
Proposal. A possible response, not yet a decision.
Round 3
“That sounds good.”
See the state
Positive reaction, but potentially ambiguous. If the decision matters, ask: “So, are we agreeing to move it to Thursday?”
Round 4
“Maya, can you update the invite?”
See the state
Proposed ownership. Wait for Maya to accept or decline.
Round 5
“Yes, I’ll update it this afternoon.”
See the state
Accepted action.
Correction lab: commitment language matters
“We decided to moving the review.”
Classification: wrong in standard English.
What a listener will probably understand: the team decided to move the review.
Likely learner intent: report a decision.
Natural alternative: “We decided to move the review.”
Context note: decide to + base verb fits this pattern.
“Maya will update the invite.” before Maya accepts
Classification: grammatically valid, but contextually overcommitted if ownership has not been accepted.
What a listener understands: Maya owns the task.
Likely learner intent: assign the next step.
Natural alternative: “Maya, can you update the invite?”
Context note: move to a firm recap only after ownership is actually agreed.
“We should do this.”
Classification: grammatically valid.
What a listener understands: the speaker recommends an action.
Likely learner intent: either suggest or state a decision.
Natural alternative: none required if it is a proposal; if you need a decision, ask “So, are we agreeing to do this?”
Context note: the same sentence can be useful without proving commitment.
“That’s decided.” when the group has not clearly agreed
Classification: grammatically valid, but contextually premature.
What a listener understands: the matter is closed.
Likely learner intent: summarise agreement.
Natural alternative: “Are we agreed on that?”
Context note: use decision language only when the group’s agreement is genuinely clear.
The 20-second close
Practise one closing line with exactly three pieces: decision → owner → next step. If any one piece is unknown, say that instead of inventing it.
Don’t leave with vibes; leave with a decision
Business meetings get clearer when you track the state of the talk. Updates change the context. Proposals suggest options. Decisions close choices. Actions need owners. A good recap tells everyone which of those states the meeting actually reached.