Choose what “shared” means
A global virtual keynote does not have to mean everyone watches at the same clock time. The shared element may be the message, the live conversation or the follow-up. Decide which matters most before selecting a time that disadvantages part of the audience.
List attendee locations and working hours, not just the headquarters time zone. Use the actual event date when checking offsets: daylight-saving changes can alter the relationship between cities.
Compare three approaches
| Approach | Advantage | Trade-off |
|---|---|---|
| One live session with optional replay | One common live discussion. | Some regions may have inconvenient hours or no live access. |
| Two live deliveries | More participants can engage in suitable working hours. | Additional speaker time, moderation and coordination must be agreed. |
| Recorded keynote with regional live discussions | Consistent core content with local participation. | Questions for the speaker need a separate arrangement. |
Ask about delivery and recording scope before announcing the format. A replay is only a useful alternative if colleagues can access it and participate in whatever follows.
A concrete planning example
For illustration, on 3 October 2026 a session at 14:00 UTC corresponds to 15:00 in London, 10:00 in New York and 22:00 in Singapore. This does not make 14:00 UTC a universally fair choice; it shows why a comfortable headquarters time can be late elsewhere.
Check the actual event date and calendar settings before sending invitations. If the Singapore audience needs live discussion during working hours, consider a second delivery or a separate regional session rather than describing a late replay as equivalent access.
Keep the two sessions connected
- Use the same central brief and share recurring questions with the speaker.
- Assign a moderator to each delivery and agree which local examples can vary.
- Give every region the same follow-up materials and route for questions.
- Avoid sharing private comments from one group with another without permission.
- Evaluate relevance by region as well as overall attendance.
Write invitations that prevent confusion
Include the date, named reference time zone, session duration and an event invitation that converts to the recipient’s local time. State clearly whether the session is live, recorded or a repeat delivery. Explain replay availability and access requirements.
A named location is more understandable than an unexplained abbreviation, and a date-specific UTC reference helps production teams reconcile schedules. Recheck all locations after a date change.
Design the asynchronous experience
Provide an accessible replay and a concise summary if permissions allow. Give a deadline and route for questions, then publish responses or bring them into the next local meeting. An asynchronous attendee should still know what to do with the keynote’s message.
Use the rehearsal checklist to assign responsibility for calendar checks, playback and regional handovers.
A decision record for regional access
List the regions, approximate audience numbers and what live participation each group needs. Then record the chosen delivery plan and its trade-off. “Europe and the Americas attend live; Asia has a separate hosted discussion and a route to submit speaker questions” is more honest and useful than “global live access”.
If sessions repeat, decide whether the second audience receives a fresh delivery or a replay. Give each moderator the same brief and access to recurring themes, without passing on private comments. Check invitations on the event date: the difference between named cities can change around daylight-saving transitions.
A replay is a hosted experience too
A colleague watching later needs context, the agreed materials and a way to ask a question if one was promised. Name who handles that route and how long it will remain open. A recording posted without explanation can lose the opening context and the connection to internal actions.
Keep the event date visible, especially for economics, technology or current-affairs topics. If a later viewer might act on changing information, make clear that the talk reflects its delivery date. Do not quietly imply that a recording is continuously updated.