For whoever runs a fully-online tech event
Remote StageWhen the feed dies, everyone thinks it is their own connection.
Enter the sessions in UTC, the speakers and where they are, and who is free to run production. Free in your browser: how many things happen at once, each speaker's local start (and who would present at 2 a.m.), the platform you actually need, how ready each speaker has to be, moderators and watchers by name, and the fallback line for the minute a feed drops. A run writes the production plan, or a tech brief for every speaker.
1 The event and its sessions free
connection: good, unknown, bad, or cannot (cannot hold a live slot) - check: real platform, another tool (named), or blank if not yet.
2 The production, worked out free
What the page flags
The day, in UTC
Every session - speaker, readiness, staffing
Platform, speakers, moderation, drill
3 Production plan or speaker briefs metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Posture and platform
Speakers
Staffing
Failure drill, rehearsal, budget
Gates
Record
Caveats
The page's check of this reply
4 Saved productions
How it works
Decide first whether people are inside your event or watching a feed - everything follows from that. A feed on a public video platform plus the chat space your community already uses covers most events; a single feed with comments closed is an honest choice when nobody can watch chat. Pay for a full virtual venue only when sessions run at once, a sponsor bought a booth, or someone already chose it for you.
Send every speaker a short home-setup note with the link, check anyone new on the real platform - never on a different tool - and have speakers with a demo or a shaky connection record locally as a backup. Put a named moderator on every session that runs at the same time, never the speaker. And publish one sentence before the day saying where to go if the feed dies: a virtual event fails as silence.