# Meeting Minutes

## Metadata

| | |
|---|---|
| Organisation | Not stated |
| Reference | Not stated |
| Meeting | Client M204 Larkfield MK - Thursday session |
| Date | Not stated |
| Duration | Not stated |
| Attendees |  |

## Objectives

Rehearse the webinar flow and agree final presenter, Q&A, timing and technical-contingency arrangements.

## Executive Summary

The team rehearsed the webinar opening, handovers, Q&A flow and contingency plan. They agreed that Priya would handle the opening, housekeeping, handovers and close; Tom would keep his intro and answers tight; Nadia would manage questions and timing prompts; and Callum would handle technical safety-net duties, recording and the closing slide. A short warm-up was agreed for 08:30 before the live 11:00 session.

## Key Discussion Points

| Topic | Discussion | Outcome |
|---|---|---|
| Topic 1 | Priya will open the webinar with housekeeping, muted microphones, cameras off and questions in chat. | See discussion |
| Topic 2 | Tom should wait for Priya's handover cue before starting. | See discussion |
| Topic 3 | Slide-two animation has been removed and needs to be restored. | See discussion |
| Topic 4 | Priya will take over briefly for the case study and then hand back to Tom. | See discussion |
| Topic 5 | The screen-sharing handover creates a short dead-air risk, so Priya will cover the gap verbally. | See discussion |
| Topic 6 | Nadia will monitor and group chat questions, then feed Priya the best questions privately. | See discussion |
| Topic 7 | Callum will act as technical safety net on a separate connection. | See discussion |
| Topic 8 | Content should finish by 35 minutes, leaving 20 minutes for questions. | See discussion |
| Topic 9 | Nadia will message Tom a five-minute warning while he is presenting. | See discussion |
| Topic 10 | The opening script should mention the speech-bubble icon for mobile attendees. | See discussion |
| Topic 11 | The team will spot-check the joins and question section rather than rerun all content. | See discussion |
| Topic 12 | Q&A should open with an easy question, such as whether the recording and slides will be sent afterwards. | See discussion |
| Topic 13 | Nadia will prepare planted questions in case the live audience does not ask any. | See discussion |
| Topic 14 | Priya will close with a clear thank-you, recording/slides follow-up, contact route and next step. | See discussion |
| Topic 15 | A closing slide should include the booking link and QR code. | See discussion |
| Topic 16 | Callum will start recording as Priya begins, confirm the red recording indicator and take a screenshot. | See discussion |
| Topic 17 | If Tom drops off, Priya will fill verbally while Callum contacts Tom and can take over sharing from a backup deck. | See discussion |
| Topic 18 | A short warm-up run of the opening and first handover is planned for 08:30 before the 11:00 live session. | See discussion |

## Actions

| Owner | Action | Due |
|---|---|---|
| Callum | Restore the animation on the three-things slide. | Not stated |
| Callum | Build the closing slide with the booking link and QR code, then re-share the deck. | Not stated |
| Nadia | Write three backup questions tonight and circulate them to the team. | Not stated |
| Nadia | Monitor and group the chat questions during the webinar. | Not stated |
| Nadia | Send Tom a private five-minute timing warning during the webinar. | Not stated |
| Tom | Keep the personal introduction to about 30 seconds. | Not stated |
| Tom | Keep Q&A answers concise and avoid overrunning. | Not stated |
| Tom | Drop the not-see-you joke from the opening. | Not stated |
| Priya | Use the opening housekeeping script, including the tap-the-speech-bubble instruction for mobile attendees. | Not stated |
| Priya | Cover dead air during screen-sharing handovers and handle the closing. | Not stated |
| Callum | Start recording when Priya begins, check the red recording indicator, take a screenshot and monitor the recording. | Not stated |
| Team | Run a short warm-up at 08:30 covering the opening and first handover. | Not stated |