The 24-Hour Webinar Tech Check (Dry Run Checklist)

The 24-Hour Webinar Tech Check (Dry Run Checklist)

Three minutes into a product launch webinar a few years back, I watched a keynote speaker’s audio turn to gravel in front of several hundred live attendees. Hotel Wi-Fi, laptop mic, no backup plan — and we discovered all three problems in production instead of rehearsal. That show recovered, barely, but it changed how my team preps every event since. Across a thousand-plus enterprise webinars, the pattern is boringly consistent: the disasters were almost never platform failures. They were things a proper dry run would have caught 24 hours earlier.

This is the exact webinar dry run checklist we run the day before every live event. It takes about 45 minutes with all speakers present, and it has quietly prevented more failures than any piece of software we have ever bought.

Why 24 hours out — not 30 minutes before

Most teams do their “tech check” in the green room half an hour before going live. That is not a tech check. That is a discovery session for problems you no longer have time to fix.

The 24-hour window is the whole trick. If a speaker’s mic sounds thin, there is time to courier a USB mic or switch them to a different room. If their upload speed can’t hold a screen share, there is time to move them onto ethernet or pre-record their segment. If the polls were built in the wrong session template — a mistake I have made personally more than once — there is time to rebuild them. Every one of those fixes takes hours, not minutes. Thirty minutes before showtime, your only fix for anything is “hope.”

One rule we hold hard: the dry run is non-negotiable for every speaker, including the executive who “has done a hundred of these.” Especially that one. In my experience the most senior speaker on the roster is the single most likely person to show up on a laptop mic over conference-room Wi-Fi.

The full-platform rehearsal

The rehearsal happens on the same platform, in the same session type, with the same roles you will use live. Not a Zoom call to talk about the Goldcast event. Not a Teams meeting to discuss the Zoom webinar. The actual event environment — because permissions, layouts, and backstage behavior differ between a test meeting and a production webinar session on every platform I have used. If you are still deciding which platform that should be, settle it before rehearsal week — here is our honest comparison of Zoom vs Teams vs the dedicated webinar platforms.

What we walk through, in order:

  • Entry and roles. Every speaker joins through the real speaker link, not a forwarded calendar invite. Confirm each person lands with the right permissions — panelist, not attendee.
  • Camera and framing. Eyes in the top third of the frame, light source in front of the face, no window behind them. Two minutes of adjustment here is the cheapest production-value upgrade that exists.
  • Slide handoffs. Practice the actual transitions — who advances, who shares, what the handoff cue is. This is where a written run of show earns its keep; every cue in the rehearsal should map to a line on that document.
  • First 90 seconds, out loud. Have the host actually deliver the open. The awkwardness you hear in rehearsal is the awkwardness attendees would have heard live.

Guest speakers get this checklist in writing at least a week before, alongside their prep call — the full process is in our guest speaker briefing playbook. Speakers who know what to expect show up ready. Speakers who don’t show up on hotel Wi-Fi.

Audio setup: the one thing attendees never forgive

Here is the trade I will make every single time: average video, great audio. Attendees will happily watch a slightly soft webcam image for an hour. They will leave within minutes if the audio is echoey, clipped, or buried in keyboard noise. In our post-event surveys, audio complaints outnumber video complaints by a wide margin — it is not close.

The audio portion of the dry run: each speaker talks for 30 uninterrupted seconds while everyone else listens on headphones and one producer listens on laptop speakers — because that is how your attendees will hear it. Listen for echo (hard-walled room), hiss (gain too high), and plosives (mic too close). Then have them type while talking. Laptop mics pick up keystrokes like a hailstorm.

You do not need a broadcast studio. This budget kit has covered hundreds of our speakers:

ItemBudget pickApprox. costWhy it matters
USB dynamic micSamson Q2U or similar~$70 at the time of writingDynamic mics reject room echo that condensers amplify
Wired headphonesAny wired earbuds~$15Kills echo and Bluetooth dropouts; wired beats wireless for reliability
Ethernet adapterUSB-C to gigabit ethernet~$20The single biggest stability upgrade available
Front lightSmall LED panel or a window in front~$30 or freeFace light does more than any webcam upgrade

Roughly $135 per speaker, and it outperforms setups costing ten times more that skip the fundamentals.

Internet and hardware: hardwire or gamble

Wi-Fi is fine until someone in the house starts a video call, a backup kicks off, or the microwave runs. Hardwired ethernet removes an entire category of failure, which is why it is a requirement — not a suggestion — for every speaker in our programs.

  • Ethernet connected and confirmed. During the dry run, have each speaker disable Wi-Fi entirely for 60 seconds. If the session holds, they are genuinely hardwired. You will be surprised how often they are not.
  • Speed test from the actual machine. 10 Mbps upload is a comfortable floor for camera plus screen share. Test at the same time of day as the live event if possible.
  • Power, not battery. Laptops throttle performance on battery, and a 90-minute event will outlast more batteries than you would think.
  • Close everything else. Slack, Outlook, browser tabs with autoplay. Notifications during a screen share are both a bandwidth problem and an embarrassment problem.
  • Restart the machine the morning of. A fresh boot clears the mystery processes that accumulate over a two-week uptime.

Polls, screen shares, and the clicks that fail live

Interactive elements fail more often than audio or video, because they depend on configuration done days earlier by someone who is not in the room. So we launch every single one during the dry run — not “confirm they exist.” Launch them.

  • Fire each poll live. Confirm it appears to a test attendee, not just in the host view. Half of poll failures are visibility failures.
  • Run every screen share. Each speaker shares the exact deck or demo they will use live. Check for font substitutions, missing videos, and the dreaded presenter-notes-on-screen layout.
  • Play any video with sound. Sharing computer audio is a separate checkbox on most platforms and the single most commonly missed setting I see.
  • Test the handout and CTA links. Click them from the attendee view. A typo in a CTA link costs real pipeline and is invisible from backstage.

The failure drill: who takes over when a speaker drops

This is the part almost nobody rehearses, and it is the part that separates a professional operation from a lucky one. At some point a speaker will drop mid-sentence — power cut, ISP blip, blue screen. The question is never whether it happens; it is whether the next ten seconds are handled or chaotic.

In the dry run, we simulate it. One speaker kills their connection without warning, and everyone else executes the plan:

  • The host bridges immediately. A prepared line — “Looks like we lost Maria for a moment; while she reconnects, let me pull up the question several of you asked” — buys two to three minutes without dead air.
  • Slides have a second driver. The producer or host holds a copy of every deck and can advance from their machine within seconds.
  • The dropped speaker knows the re-entry route. Rejoin link pinned in a group text, phone dial-in as the audio fallback, and instructions to rejoin quietly — no on-mic apology tour.
  • The backchannel is off-platform. A text or Slack thread that survives even if the webinar platform itself is the thing that failed.

The drill takes five minutes. The first time it saves an event — and it will — those five minutes become the best production investment you make all year.

The final 60 minutes on show day

If the 24-hour dry run happened, show day is calm by design. The last hour is verification, not discovery:

  • T-60: Producer opens the live session, confirms recording settings, loads polls, and re-clicks every CTA link.
  • T-30: Speakers join backstage. Quick audio spot-check — 15 seconds each, headphones on. Confirm the final reminder email fired on schedule (our four-email sequence, including the at-start “we’re live” send, is laid out here).
  • T-15: Run of show open on every screen. Phones on silent, group text pinned, water within reach.
  • T-5: Quiet backstage. No new information, no last-minute slide edits. Late changes create more failures than they fix.

Then you go live knowing every switch has already been flipped once in the last 24 hours. That knowledge changes how relaxed your speakers sound — attendees can hear confidence.

Frequently asked questions

What is a webinar dry run?

A webinar dry run is a full rehearsal held on the actual webinar platform with every speaker present, covering audio, video, internet, screen shares, polls, and handoffs — plus a failure drill. It is a working session, not a social call: every element that will be used live gets exercised once before it counts.

How long should a webinar dry run take?

Plan 45 minutes for a standard two-to-three speaker event: about 10 minutes on connections and audio, 20 on content walkthrough and handoffs, 10 on polls and screen shares, and 5 on the failure drill. First-time speakers or complex demos justify a full hour. Under 30 minutes usually means something got skipped.

Should the dry run be on the same platform as the live webinar?

Yes — always. Rehearsing a Zoom webinar in a Zoom meeting, or a Goldcast event in a Teams call, tests almost nothing that matters. Backstage behavior, speaker permissions, poll mechanics, and layouts differ between session types even within the same vendor. Use the real event environment, ideally a duplicate of the production session.

What should a webinar tech check include?

At minimum: speaker entry links and roles, microphone and headphone check, camera framing and lighting, hardwired internet confirmed with Wi-Fi disabled, a live launch of every poll, every screen share run end-to-end, CTA links clicked from the attendee view, recording settings confirmed, and a rehearsed plan for a speaker dropping mid-session.

Do experienced speakers really need a dry run?

Experienced speakers need the dry run more than anyone, because they are the most likely to skip prep and improvise their setup. The rehearsal is not about their speaking ability — it is about their mic, their network, this platform’s quirks, and this event’s handoffs, none of which their experience covers.

This is lesson-one material from our courses — see what’s coming, or get the free lessons by email as they ship.