Most virtual events fail in planning, not on the day. The stream that freezes, the speaker who can't be heard, the Q&A nobody moderated. Each traces back to a decision that wasn't made six weeks earlier. This guide is the sequence we follow on every production, from the first call to the post-event report.
Start with the audience, not the technology
Before anyone mentions a platform, answer three questions. Who is watching? Where are they watching, at a desk, on a phone on a train, on a screen in a warehouse canteen? And what must they be able to do: just watch, or ask questions, vote, network, download? Every subsequent decision (format, platform, crew, budget), flows from those answers. A town hall for 4,000 shift workers on mobile is a different production from a 40-person investor briefing, even if both are "a virtual event".
Choose the format deliberately
Single-session events suit a broadcast approach: one polished stream, a strong presenter, a tight run order and minimal audience friction. Multi-track conferences need a platform with an agenda, session rooms and registration. Awards shows are a third thing entirely. They live or die on pace, so the risky elements are pre-recorded and the live moments are kept live. Decide the format first and let it dictate the tools, never the reverse. Our platform guide covers when you genuinely don't need one.
Build a real run order
A run order is a minute-by-minute account of the show: who is on, what is on screen, which source, which microphone, what plays next, and who calls it. It is the single document that lets a gallery anticipate rather than react. If your production company doesn't ask you for one (or offer to write it) be nervous. We've published the full run order method and a downloadable template.
Rehearse the failure, not just the show
A technical rehearsal tests every remote speaker on the actual kit they'll use on the day: same laptop, same room, same connection, same headphones. It also tests what happens when something breaks. The backup presenter link, the holding slide, the second internet path. We run every show with redundant encoders and a second connection because sooner or later one of them is needed. What to test, and when.
Pre-record strategically
Anything that cannot be allowed to fail (the CEO's keynote, the awards montage, the product reveal) is a candidate for pre-recording with a live Q&A afterwards. Audiences readily accept a polished pre-record; they don't accept a frozen keynote. The trick is to pre-record in the same set, with the same lighting and framing as the live segments, so the join is invisible.
Crew it properly
The minimum viable crew for a professional virtual event is three people: a vision mixer or vMix operator running the pictures, a producer calling the show and watching the clock, and a speaker wrangler managing the humans. One person cannot do all three well, and on show day "well" is the only acceptable standard. Bigger shows add a graphics operator, a sound engineer and a platform moderator. Our gallery roles guide explains each job.
Plan the interaction, not just the broadcast
Q&A, polls and chat each need an owner. Who moderates questions? Who decides which reach the stage? Who launches the poll on cue, and who reads out the result? Interaction that isn't staffed becomes noise, and noise reads as chaos. How to run it live.
Decide what success looks like before you go live
Peak concurrent viewers, average watch time, Q&A volume, drop-off points, on-demand views in the week after. Set up the analytics before the event and agree the metrics with stakeholders in advance. Otherwise the post-event conversation becomes an argument about which numbers count. Metrics that matter and the report to write.
The one-line version: know your audience, pick the format, write the run order, rehearse the failure, pre-record the un-droppable, crew properly, staff the interaction, agree the numbers.