Take usable meeting notes and give a business update
Writing every word can hide the decision
- In a fictional student print shop, a meeting covers an order, a deadline and a possible supplier delay. Notes listing every sentence may still fail to identify who must do what. Listen or read for decisions, owners and conditions.
- This original GAC007-aligned practice uses a printed meeting script and partner rehearsal. The checks concern text comprehension, not recorded listening proficiency. Your formal update will use a simple action table as its visual aid.
What is the requested output?
Maya specifies forty posters and Thursday afternoon readiness. Wednesday is only a conditional start.
Distinguish a decision from a possibility
- Read the exchange, then have partners speak the two roles while a third person takes notes. Will marks the agreed checks here; if makes the printing start conditional. Do not record every proposed time as a confirmed commitment.
- Make headings for task, owner, time, condition before the rehearsal. Leave a question mark beside a detail you did not catch. The aim is a usable record that can be checked, not a complete transcript reconstructed from guesses.
Maya: We need forty event posters ready by Thursday afternoon. Arun, please confirm the final text with the organiser by Tuesday noon. I will check the paper delivery with the supplier on Tuesday morning. Arun: Can we promise to start printing on Wednesday? Maya: Only if the paper arrives and the text is approved. If either is delayed, I will contact the organiser before four on Tuesday to discuss a smaller run or a later delivery. Arun: So I confirm the wording, and you check the paper and contact the organiser if needed. Maya: Exactly. We have not promised a Wednesday start yet.
The meeting confirms that printing will start on Wednesday regardless of the checks.
The start requires both paper arrival and approved text; the script explicitly says it is not yet promised.
Turn speech into an action table
- Keep the owner beside the action. Arun confirms wording; Maya checks the supplier and handles a delay message. “Confirm everything Tuesday” loses both responsibility and the different times.
- Record the conditional start separately from the required delivery. Wednesday is a possible printing start, not a confirmed promise. Thursday afternoon is the requested readiness deadline. A useful table preserves uncertainty rather than hiding it.
| Action | Owner | Time or condition |
|---|---|---|
| Confirm final wording | Arun | Tuesday noon |
| Check paper delivery | Maya | Tuesday morning |
| Discuss alternatives if needed | Maya | Before Tuesday 4 pm |
| Start printing | Not yet confirmed | Paper received and text approved |
{callout:example} “Two checks are due Tuesday: Arun confirms the text by noon, and Maya checks delivery in the morning. A Wednesday start remains conditional. Maya will contact the organiser before four if either check reveals a delay.” {/callout}
Who confirms the final wording with the organiser?
Arun owns the wording check. Maya checks the paper and communicates any delay.
Build a formal update around what matters
- For a one-minute update, state the requested output and deadline, the two checks, the start condition and the backup discussion. Show the action table rather than a slide containing the whole script. Explain its meaning instead of reading every cell twice.
- Use accurate language: “is requested,” “will check,” “remains conditional” and “will discuss if needed.” Do not strengthen “discuss a smaller run” into “a smaller run has been approved.” Permission and possibilities have different business consequences.
{callout:warn} An internal planning suggestion is not automatically a customer promise. Check the actual decision before reporting a delivery or start date as guaranteed. {/callout}
Which TWO details must remain conditional in the update?
Wednesday depends on the checks, and a smaller run is only something to discuss. The two checks are agreed actions.
Check the summary with the speakers
- Ask, “Have I recorded the owners correctly?” and “Is Wednesday still conditional on both checks?” These questions target the parts that could affect the work. A confident tone cannot compensate for a wrong task owner.
- If corrected, revise the note and tell anyone who received the earlier version. Keep a simple date or version label on the table. A polished old table remains wrong after a decision changes.
Rehearse with a useful audience question
- Give the update and let a partner ask, “What happens if the text is late but the paper arrives?” Answer that either delay triggers Maya's discussion with the organiser before Tuesday four. Do not invent a new printing decision.
- Self-check output, deadline, owners, conditions and backup. Revise one unclear sentence, then give the update without reading the full script. These skills support oral reporting; a reviewed recording would be needed for a recorded listening assessment.
{callout:key} Useful meeting notes retain actions, owners, times and conditions. A formal update communicates those decisions without turning proposals into promises. {/callout}
The paper arrives but the text approval is delayed. What does the stated plan require?
Either delay triggers the discussion. No start or smaller run is automatically authorised.