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.

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.

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.

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.

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.