Product Launch Run-of-Show: AV Milestones Planners Own

Product launches live or die on timing: the reveal lands on the wrong beat, the demo video fires before the hardware is uncovered, or the house lights come up while the CEO is still mid-sentence. The run-of-show is where those failures get prevented — and most of the AV decisions that protect it belong on the planner's checklist, not buried in a vendor's internal spreadsheet.

This guide covers the AV milestones you should own from first draft through doors open: what to lock by when, what to bring to your production partner, and the rehearsal gates that catch sync problems before an audience sees them.

Build the run-of-show around AV-critical beats first

Marketing teams write run-of-show documents around messaging arcs and speaker transitions. Production teams read them looking for cue points — where audio, video, lighting, and scenic have to move together. For a product launch, those beats are non-negotiable and they should appear in the document before anyone debates lunch timing.

AV-critical beats to define early:

• Pre-show state — house lighting level, walk-in loop or ambient content, mic status, and whether the LED wall shows holding slides or is dark.
• Walk-on sequence — music bed, VOG or live intro, presenter mic live point, and lighting preset change.
• Reveal moment — exact trigger (presenter line, button press, timed automation), what drops (scrim, curtain, case lid), and what fires simultaneously (video, lighting, SFX, IMAG switch).
• Demo segments — live product on stage vs. pre-recorded fallback, camera coverage plan, and who calls the switch if the live path fails.
• Supporting content blocks — sizzle reels, partner logos, spec slides; each needs an in/out cue and a defined audio path (program mix vs. VOG duck).
• Transition resets — how long between segments to reset scenic, reload content, or swap presenters without dead air.

If your run-of-show lists "Product Reveal — 10:22 AM" without sub-cues, your show caller is improvising the most important thirty seconds of the event. Break every major beat into technical sub-cues before you send the document to production.

AV milestone timeline — what to lock and when

Product launch AV has hard dependencies: content renders at native wall resolution, scenic builds around rigging points, and rehearsal time is finite. Use this timeline to keep marketing, creative, and production aligned.

Eight weeks out:

• Format locked — seated keynote, theater-in-the-round, or demo lab walk-through; drives camera count, PA design, and whether IMAG is mandatory.
• Reveal mechanism chosen — scrim drop, lift platform, case open, wall content wipe; scenic and automation need this before shop drawings start.
• Content aspect ratio locked — native LED resolution and safe zones documented; motion and slide teams build to the same canvas.
• Run-of-show v1 — all AV-critical beats with placeholder times; production can bid crew count and equipment against it.

Four weeks out:

• Final speaker list and mic inventory — every presenter, demo operator, and panelist assigned a wireless or wired path with backup.
• Content pipeline defined — who delivers final files, what format (ProRes, HAP, PNG sequences), and where they land on the media server.
• Cue-to-cue scope agreed — full run, abbreviated tech run, or segment-only; block calendar time accordingly.
• RF and venue coordination started — frequency scan date, union jurisdiction, and any broadcast restrictions if you're near a stadium or airport.

One week out:

• Content locked — no new renders after this date unless you accept untested files on show day.
• Run-of-show vFinal — times, sub-cues, contingency notes, and emergency holds documented; distributed to show caller, department heads, and client approver.
• Rehearsal call sheet issued — who must be on stage for each segment, not just "full rehearsal at 2 PM."
• Failover paths written — pre-recorded demo if live product fails, backup walk-on music, manual scenic reset if automation hangs.

Show day:

• Pre-show checklist signed — every department confirms ready state before doors; not a verbal "we're good."
• Timed run at least once — full cue-to-cue at show pace, including presenter pauses and audience reaction time.
• Post-rehearsal change control — any run-of-show edit after final rehearsal requires show caller and department head sign-off.

Planners who miss the four-week content lock are the ones requesting a new sizzle reel at 6 AM. Production can often accommodate it. They cannot accommodate discovering it doesn't match the wall resolution at 7:45.

Questions to bring your production vendor

A product launch brief that only lists "LED wall, 4 cameras, wireless mics" invites guesswork on the reveal — the moment that actually matters. Bring these to your first production meeting:

• Who owns the run-of-show document — client marketing, production company, or shared; and who has final authority on cue changes during rehearsal.
• Show caller assignment — dedicated show caller or shared with stage manager; confirm they have the final run-of-show and comms to every department.
• Automation vs. manual cues — which transitions run on timecode or QLab, and which depend on a stagehand or presenter trigger.
• Reveal sync tolerance — how tight must scenic, video, lighting, and audio land; sub-second, or is a half-beat drift acceptable on a live button press.
• IMAG and stream paths — separate switcher presets for in-room IMAG vs. broadcast feed; confirm the reveal reads on camera, not just to the live audience.
• Content testing protocol — when and where full-resolution content plays on the actual wall, not a preview monitor.
• Rehearsal attendance requirements — which segments need the CEO on stage vs. a stand-in; product demo segments almost always need the actual operator.
• Change window cutoff — last time a run-of-show edit can be made without overtime or missed cues.

Answers belong in writing. Verbal agreements at the production meeting evaporate when three departments interpret "after the reveal" differently.

Rehearsal gates — test the show, not the gear

Gear checks confirm inputs work. Rehearsal gates confirm the show works — the reveal timing, the presenter pacing, the failover nobody wants to use. Block rehearsal time against these gates, not against a vague "tech run."

Rehearsal sequence for a product launch:

1. 1.Segment isolation — run the reveal three times cold: no warm-up, no "we'll get it in the full run." If the reveal fails in isolation, it fails in the show.
2. 2.Full cue-to-cue at pace — presenters at actual speed, including pauses for applause and demo setup; timecode-only rehearsals lie about show length.
3. 3.Fail one path — kill the primary media server output, drop the automation trigger, or mute the presenter lav; confirm backup procedure and who calls it.
4. 4.Camera and IMAG review — watch the switcher output on a confidence monitor sized like your IMAG wall; a reveal that looks dramatic live can read as a dark blob on the back row screens.
5. 5.Audio handoffs — walk-on music into VOG into presenter lav into demo audio; confirm ducking, echo, and that demo audio routes to both house and stream.
6. 6.Reset drill — time how long scenic and stage take to return to pre-show state; if it exceeds your transition window, the run-of-show needs a hold or a crew add.

Document who calls what: show caller owns cue execution, technical director owns switcher and playback, audio lead owns mic state and playback levels, lighting lead owns preset transitions. Product launches add roles; they don't add time unless the run-of-show accounts for it.

From the floor: the reveal that waited for a file name

One launch rehearsal hit the reveal cue perfectly — scrim up, lighting snap, audio sting — and then thirty seconds of holding slide while the media server searched for a file that had been renamed that morning. The run-of-show listed "Demo_Reveal_Final_v3"; the server held "Demo_Reveal_Final_v3_APPROVED."

Same content. Different string. The show caller held the room while someone typed.

The fix was a content naming convention in the run-of-show itself — exact file names, verified in the pre-show checklist, no aliases. The reveal cue didn't change. The thirty seconds of stillness did.

Product launch AV is not about owning every fader move. It's about owning the milestones — content lock, cue documentation, rehearsal gates, and the sign-offs that keep departments reading the same document on show day.

For LED walls, reveal staging, and show-day coordination on your next product launch, see our LED wall production services. Ready to walk through your run-of-show, reveal mechanics, and rehearsal plan? Request a consultation.