The virtual summit tech checklist: 28 things that have to be true.

The front door, and the thing you are actually selling.

Everything downstream inherits from this group. A wrong time on the schedule page becomes a wrong time in eleven speakers’ promotional emails; a pass whose inclusions are described differently in three places becomes refund requests on the busiest day of your quarter.

The item people skip is the last one, and it is the expensive one. If registration lives in one system, attendance in a second and the pass purchase in a third, then every post-summit segment worth having — attended but did not buy, bought and watched nothing, watched three sessions on replay — has to be assembled by hand while the interest is cooling. Decide now whether those three things share a record or whether you are booking a day of reconciliation.

Every item here has a dependency on somebody who does not work for you.

Which is exactly why this group runs earliest and slips most. You cannot fix a speaker’s microphone at 09:04, and you cannot chase a headshot during the session it belongs to.

Two of these save whole mornings. The tech check catches the problems that otherwise become the first ten minutes of a live session — the wrong camera, a screen share that will not start, a room that needs an install. And playing pre-recorded sessions end to end catches the failures a spot-check never does: audio that drops at minute thirty-one, a file that transcoded badly, a recording that stops before the close.

The reserve item is not pessimism. Across a dozen speakers and three days, something will move — illness, a client emergency, a timezone misread. A summit with a planned recovery loses fifteen minutes; a summit without one loses the day’s momentum and spends the evening apologising.

Capacity, the join path, and proof that the recording exists.

A summit is the event most likely to overflow its room, because you are promoting through other people’s audiences and the ceiling was set for yours.

Check the ceiling against the busiest session rather than the average, and check it against registrations rather than against what you hope attends. Turning people away from a session they were invited to by a speaker is the one failure with no recovery path: no apology reaches them, and the speaker who sent them hears about it before you do.

The join path is the other quiet one. Test it as an attendee, from a second device, using the real link out of the real confirmation email — not the preview, not the host link. Every install step, login wall or app prompt between the reminder and the room is attendance you paid to acquire and then lost at the door.

The days are held together by the emails between them.

A multi-day summit is not one event with reminders. It is three or four separate attendance decisions, and each one is made the evening before by somebody reading an email.

That is why the morning-and-evening pair is built per day rather than once for the whole summit. The evening email is the one that earns its place: what happened, what is still watchable and until when, and the one session tomorrow worth rearranging something for. Attendance on day two and day three is won there, not in the schedule.

The failure mode is banal and extremely common: the sends exist as drafts rather than as scheduled sends, and nobody notices until the room is thin on day two. Open the schedule and count them — two per day, plus the replay window sends, plus the pass deadline. Counting takes a minute and is the highest-yield minute in this group.

Roles, written down, before anyone is tired.

On the day, judgement gets expensive. Everything this group asks for exists so that nobody has to make a decision at 09:04 that could have been made in week one.

The chat item is the one people argue with and then regret. A presenter cannot present and read chat at the same time; what actually happens is that chat goes unread for forty minutes and the questions that would have shaped the follow-up scroll away. If you genuinely have nobody, say so out loud at the top of the session and collect questions in a queue instead — an honest constraint handled well beats a promise you break every session.

Agree one sentence for when something breaks, before it does. Something close to: “We have lost the speaker’s connection — we are giving it two minutes, then moving to the next session and rescheduling this one into the replay window.” Said calmly, in the first fifteen seconds, it costs you nothing. Improvised at minute four, in silence, it costs you the room.

The week after is where the pass and the offer are decided.

More people will watch a summit after it ends than during it. Treating the replay window as cleanup rather than as the second event is the most common way a well-attended summit still fails to pay for itself.

Two mechanical things make it work. Name recordings on the day — a library of untitled files is a replay window that opens late, which is the same as a deadline you have already broken. And automate the window’s opening and closing, because the deadline you announced has to hold even on the evening when everyone involved is exhausted.

Define the segments before day one. After the summit you will be defining them at speed, in a spreadsheet, at the exact moment the audience is warmest — and the difference between “pass buyer”, “attended and did not buy” and “registered and never came” is the difference between a follow-up that reads as attentive and one that reads as a blast.

One day, with an owner and a fallback on every row.

A run-of-show without owners is a schedule, and a schedule does not tell anybody what to do when something fails. The fallback column is the point of the document.

Below is one day of an illustrative three-day summit — the times, sessions and names are examples, not a recommendation. Copy it, put your own sessions in, and give every row a name rather than a role where you can. Then share it with your speakers too: the ones who know what happens at 12:00 are the ones who stay for it.

The three shaded rows are the ones that get improvised: the pre-show, the day close and the evening send. They are also the three that decide whether anybody comes back tomorrow, which is why they belong on the document with a name against them.

A stitched stack runs the summit. It does not remember it.

This is the one place on this page where the products you choose genuinely change the work rather than the preference. It is worth being precise about where the cost actually lands.

The cost of stitching is not paid during the summit. It is paid in the week afterwards, when the follow-up that should have gone out on the Tuesday goes out on the Friday because somebody was matching three exports on email address — and again when a speaker asks how their link performed and the honest answer is an estimate.

For a first summit, stitching is a reasonable choice and this page works exactly as well. The threshold is the second one, or the moment the all-access pass becomes the model rather than a nice extra.