🌕 Meeting Recap Simulation FACILITATOR DEMO

A worked example of a past Teams meeting, showing the recording consent notice and the AI-generated summary exactly as staff will see it after their own meeting. Two callouts are marked: one on recording consent, one on a summary error that needs a human check before the minutes go out.

YOU
💬Chat
👥Teams
📅Calendar
📞Calls
⋯More
Chat
PN
Priya Nathan28/7
You: sending the meal rotation now
JC
Jonesy Clarke27/7
Fleet numbers confirmed, sending photos
🌕
Katherine Delegation – Moon Festival Sync29/7
Transcript is ready
AK
Alex Kim25/7
Satellite link spec attached
MO
Marnie Osei24/7
Safety checklist v3 uploaded
TR
Tom Reilly22/7
Agenda for next sync attached
‹

Katherine Delegation – Moon Festival Sync

29 Jul 2026 at 10:03 am
PN
Priya Nathan
JC
Jonesy Clarke
AK
Alex Kim
MO
Marnie Osei
TR
Tom Reilly
YOU
You (Host)
Recorded, with consent
32:14 duration
①
Recording consent This badge only appears because everyone was told recording was starting and Teams posted a consent notice in the meeting chat before it began. As host, you say it out loud too; the badge is the record that it happened properly, not a substitute for saying it.
✨ AI generated

Meeting notes

  • Vehicle fleet confirmed: Jonesy confirmed the modified Hilux fleet numbers for surface transport and noted daily maintenance checks are needed at the start of each shift due to dust exposure.
  • Meal rotation locked in: Priya proposed a four week meal rotation; the group agreed shelf-stable meals would be supplemented with two fresh food deliveries during the month.
  • IT equipment priorities: Alex flagged that backup communication equipment takes priority over recreational tech, and the group agreed satellite link redundancy is essential.
  • Safety sign-off pending: Marnie noted the safety checklist is nearly complete but still needs sign-off from the delegation lead before departure.
  • Next sync scheduled: the group agreed to reconvene the following week to confirm final numbers ahead of departure.

Follow-up tasks

  • 🔲Jonesy — confirm final Hilux fleet numbers by Friday
  • 🔲Priya — circulate the four week meal rotation for review
  • 🔲Alex — order backup satellite communication equipment
  • 🔲Marnie — obtain safety checklist sign-off from the delegation lead
  • 🔲 Tom — book flights to the Moon for six delegates by next Monday ②
    This needs a human check Every note in this meeting, and every past conversation about this project, refers to four delegates, the Katherine Four. Copilot has written six. This is the kind of error that slips into minutes if nobody reads the draft before sending it out: plausible, specific, and wrong.

🎯 What to point out live

①Recording consent. The badge on the call thumbnail and the consent notice in the meeting chat only appear because attendees were told recording was starting, out loud, before it began. This is the same expectation covered in the warm-up prompt: hosts explain up front that a meeting is being recorded and why.
②The summary needs checking, not trusting. Four of the five follow-up tasks are accurate. One says six delegates are being booked on flights, when the whole project has been about four staff, the Katherine Four. Ask the room: would you have caught that before forwarding the minutes?
This is the habit to land: read Copilot's output against what you actually know before you send it on. A wrong headcount in a training scenario is harmless; a wrong headcount, date, or dollar figure in a real set of minutes is not.