A virtual conference agenda needs an explicit time zone, manageable session blocks and visible screen breaks. Remote attendees should know the event date, when they can join and how to reach each session. A schedule is incomplete if the times are clear but the access instructions are missing.
The original example below is a three-hour, single-stream online event from 13:00 to 16:00 UTC. It is a suggested format to adapt to your audience, not a universal optimum for online participation.
A three-hour virtual conference agenda
| Time | Minutes | Agenda item | Purpose |
|---|---|---|---|
| 13:00–13:10 | 10 | Welcome and technical orientation | Explain access, questions and support |
| 13:10–13:40 | 30 | Opening talk | Introduce one central issue |
| 13:40–13:50 | 10 | Questions | Clarify the first contribution |
| 13:50–14:00 | 10 | Screen break | Step away from the session |
| 14:00–14:35 | 35 | Practical demonstration | Show a complete example |
| 14:35–14:45 | 10 | Screen break | Rest before discussion |
| 14:45–15:20 | 35 | Moderated discussion | Compare approaches |
| 15:20–15:40 | 20 | Audience questions | Resolve practical concerns |
| 15:40–15:50 | 10 | Closing | Summarize and explain follow-up |
| 15:50–16:00 | 10 | Optional informal exchange | Continue selected conversations |
State the date and reference time zone
Write the event date and reference zone next to the schedule heading, not only in a footer. UTC is an unambiguous reference for this example. If you publish a venue-based local time, identify the relevant location or named zone and verify the offset for the event date.
Do not assume that a city’s offset stays the same all year. The IANA Time Zone Database records local time rules, including offset and daylight-saving changes. Use date-aware conversion rather than copying a conversion from another event.
Check the audience overlap
List the regions where your main participants are based and review the proposed window in their local time on the actual date. Decide which live sessions are essential and whether another option is available for people outside a reasonable window.
For a simple offset calculation, 13:00 UTC corresponds to 15:00 in a zone using UTC+02:00 and 08:00 in a zone using UTC−05:00. These are offset examples, not year-round claims about specific cities. Conversions can also change the calendar date for other start times.
Keep breaks separate from optional activities
A screen break should allow people to step away. Do not quietly fill it with a sponsor pitch or require networking throughout. If you offer an optional activity, label it and make clear that leaving the screen is allowed.
Test the total duration with speakers. The discussion and Q&A in this example are separate blocks; a presenter should not assume questions are extra time after an already full talk.
Plan access and support
Tell registered attendees where their joining instructions will arrive and what to do if access fails. Confirm the technical host, moderator and support route. Test speaker audio, presentation sharing and any participation features before the public start.
Keep private joining links in the appropriate attendee channel if access is restricted. An agenda can explain the route without publishing a link intended only for invited participants. Provide relevant accessibility information in advance and confirm any promised captions or recordings.
Make recording promises carefully
If recordings will be available, confirm speaker permission, the actual recording plan and expected access before advertising them. State which sessions are included. If there is no recording plan, do not present “watch later” as a guaranteed alternative.
Finish with a clear follow-up: materials, unresolved questions and the next contact point. Distinguish the formal closing from an optional conversation so attendees in inconvenient time zones can leave with the essential information.
Put the plan into practice
Set one reference time zone for the draft and record it clearly in the event information. Verify local conversions separately before sharing the schedule. Open Agenda Creator to draft the sequence and test the timing.