Timing Town Halls, All-Hands and Product Launches
Event guides9 min readUpdated
In a corporate town hall, the person who overruns is often the most senior one, and the part that gets squeezed is the employee Q&A. That's the reverse of what the audience came for. To keep these events on time, give Q&A a fixed start time that executives rehearse against, agree each speaker's length with them personally at rehearsal, name one person who is allowed to cue them, and give every live demo a decision point and a backup.
The general principles of slot design and changeovers are in the conference timing guide. This page covers what is different when the speakers are your own leadership and the audience is your own staff, or the press.
Protect the Q&A with a clock time, not a length
"20 minutes of Q&A at the end" is the first thing to disappear when the CEO's update runs long. A clock time is harder to erode: "Q&A starts at 10:25, whatever happens". Put it in the agenda that executives see, and have the host say it in the opening: "We'll take your questions from 10:25."
Three habits make the Q&A itself run to time:
- Collect questions in advance as well as live, so the first question is ready the moment Q&A opens and there's no awkward silence.
- Moderate. Someone other than the executives reads, groups and picks questions. In Microsoft Teams, Q&A moderation holds each question for approval before it appears in the feed, organisers can allow anonymous posts, and upvoting is on by default (Microsoft Support: Q&A in Microsoft Teams). Other platforms differ, so check yours before the day.
- Alternate between the room and remote staff so people watching online aren't an afterthought.
For the craft of choosing questions, handling hostile ones and ending on time, see how to run a live audience Q&A.
Executive time discipline without awkwardness
Executives are used to running their own meetings, so being stopped by an AV volunteer feels wrong to everyone. Fix it before the day:
- Agree the length with the executive, not their assistant. At rehearsal, tell them their number: "You have 12 minutes, and Q&A starts at 10:25."
- Rehearse with the clock running and tell them the actual time at the end. Most people are surprised by how long their talk really takes.
- Name the cue-giver. Usually a chief of staff, the host or the producer, someone the executive trusts. Agree the cue: "When you have two minutes left, you'll see it on the lectern screen. If you're over, I'll stand up at the side of the stage."
- Give them a clock they can glance at without looking at their watch on camera. A countdown on the lectern or a floor monitor is the usual answer; confidence monitor vs podium timer explains the options.
If the CEO still overruns, the host protects the Q&A by shortening their own link, or a later section, not the employee questions. The wider set of techniques is in how to stop speakers running over time.
Template: a 45-minute hybrid all-hands
Inputs: 45 minutes in total, three executive updates, in-person audience plus remote staff watching online, one short recorded video, Q&A fixed at 10:25.
| Start | Segment | Who | Length |
|---|---|---|---|
| 09:55 | Holding slide and music for remote viewers | Producer | 5 min |
| 10:00 | Welcome and agenda | Host | 2 min |
| 10:02 | Company update | CEO | 10 min |
| 10:12 | Product or team update | Exec 2 | 6 min |
| 10:18 | Recorded video (customer story or team spotlight) | Producer | 3 min |
| 10:21 | Numbers or people update | Exec 3 | 4 min |
| 10:25 | Q&A, room and remote alternately | Host moderates | 17 min |
| 10:42 | Close and next steps | CEO | 3 min |
There is no separate buffer on purpose: the Q&A absorbs any slip. If the updates run four minutes over and Q&A starts at 10:29 instead of 10:25, it shrinks from 17 to 13 minutes, which is still worth having. If they run fifteen minutes over, only 2 minutes are left and you've lost the room. That is why the cue-giver acts at the first overrun, not the last.
Hybrid audiences: start on time for the people online
Remote staff join at the advertised time and leave if they stare at a blank screen. Start the stream a few minutes early with a holding slide, start the programme on the minute, and make sure remote questions are visibly taken.
Give presenters somewhere to gather before going live. In a Microsoft Teams town hall, organisers and co-organisers prepare with presenters in a green room while attendees wait in the lobby until someone selects Start event, at which point the event recording starts automatically (Microsoft Support: Host a town hall in Microsoft Teams). Use that time to check every presenter's audio and camera, not to chat.
Whether you can schedule a town hall at all depends on the Town halls setting in your organisation's Teams events policy, so ask your IT admin well before the day (Microsoft Learn: manage who can schedule and attend events). The Microsoft Support town hall page lists some features, such as bringing attendees on screen, as Teams Premium add-on features, and Microsoft has changed which features need Premium in 2026, so check before you promise one.
More on keeping online and in-room audiences in step is in timing webinars and hybrid meetings.
Product launches: time the demo, and plan its failure
A product launch is closer to a stage show than a meeting. The script is fixed, the slides are cued, and a live demo is the riskiest minute of the event. Plan it like this:
- Rehearse the demo to a fixed length on the exact device, network and display you'll use on the day.
- Run demos on a separate, wired connection where you can, not the venue Wi-Fi the audience is using.
- Record a backup video of the demo working perfectly, cued and ready on the playback machine.
- Set a decision point and agree it with the presenter: if the demo isn't working by a set moment, the producer cuts to the recording and the presenter talks over it.
- Agree a code phrase the presenter can say to trigger the switch without telling the audience something went wrong, such as "Let me show you this from the top."
A simple decision table for the producer:
| What happens | Decision | Action |
|---|---|---|
| Demo slow but working | Wait | Presenter fills; no switch |
| Demo stalls under 15 seconds | Wait once | Presenter repeats the step |
| Demo stalls past 15 seconds, or crashes | Switch | Cut to the recorded backup |
| Code phrase said | Switch | Cut to the recorded backup immediately |
| Backup also fails | Move on | Presenter describes the feature; go to the next section |
The 15 seconds is a suggestion, not a standard. What matters is that the number is agreed before the show, so nobody is deciding it live.
If timing is tied to something outside the room, such as a press release or a website going live at a set time, treat that moment as fixed and build the running order backwards from it, with the slack before the reveal rather than after.
A rehearsal checklist
- Full run-through with the clock running, in the room, the day before or that morning.
- Every presenter tells you their actual time; adjust the agenda, not your hopes.
- Test the lectern clock and the floor monitor from where the speaker will stand.
- Play every video from the playback machine, start to finish.
- Run the demo fallback once: trigger the code phrase and make the switch.
- Confirm who moderates Q&A and who cues each speaker.
StageClock can hold the agenda as segments, show the countdown on a Stage Display or lectern screen, and let the producer send "5 Minute Warning" or "Wrap Up Now" from the Control Panel. Messages appear on the Speaker Monitor only, not the Stage Display, so put the Speaker Monitor on the screen the executive actually looks at. Only the event creator's Google account controls the event, so decide which one person runs it.
Frequently asked questions
Should remote viewers see the countdown?
Usually only before the start. A countdown on the holding slide tells remote staff when the programme begins. During the programme, a visible clock on the stream tends to make the audience watch the time instead of the speaker.
What if an executive asks to go long on the day?
Agree it on the spot with the producer, and say out loud what gets shorter. "Take three extra minutes, and we'll start Q&A at 10:28" is a decision. "Sure, take what you need" is how the Q&A disappears.
Key takeaways
- Give employee Q&A a fixed clock start and say it in the opening, so executive overruns have a visible cost.
- Agree each executive's length with them at a timed rehearsal, and name the one person who cues them.
- Start hybrid events on the minute for remote staff, and use a green room or backstage call to check every presenter before going live.
- Every live demo needs a recorded backup, an agreed decision point and a code phrase to switch.
- When the timing depends on something outside the room, build the running order backwards from that fixed moment.