Corporate Event AV: What a Technical Run of Show Needs
A technical run of show for corporate event AV should identify every production cue, its trigger, the responsible operator, the required equipment or media, and the fallback action if something fails. Unlike a general agenda, it tells the crew exactly how to execute each transition across audio, video, lighting, staging, and presenter movement.
What is a technical run of show?
A technical run of show is the shared execution document used to coordinate the live production of an event. It translates program moments—such as a keynote introduction, panel discussion, or awards presentation—into specific actions for the technical crew.
An agenda might say, “10:00 a.m.: Opening keynote.” The technical version explains when walk-in music fades, which microphone opens, what appears on screen, how lighting changes, and who confirms that the presenter is ready.
For AV production for a corporate event, this distinction matters: a schedule describes what the audience will experience; a technical run of show defines how the crew will deliver it.
Ramar Event Productions coordinates corporate AV services around these operational details so creative intent and technical execution work together.
What every technical run of show should include
Timing, duration, and cue triggers
Include both the planned start time and the expected duration of each segment. However, do not assume every cue should happen at a fixed clock time.
A speaker may pause, skip a slide, or finish early. Identify whether each cue is triggered by a clock time, spoken phrase, visible action, or show caller instruction.
“Play video at 10:05” is less reliable than “On the host’s words, ‘Let’s take a look,’ show caller calls video GO.” Record the planned time for scheduling and the observable trigger for execution.
Cue IDs and department actions
Give cues unique identifiers that remain stable through revisions. Separate the actions for audio, video, lighting, and stage management so operators can quickly find their responsibilities.
Each instruction should describe an action and its intended result. “Lights change” is vague. “Fade lectern special to keynote look over three seconds” is actionable.
Reference the exact playback filename, presentation version, microphone assignment, and lighting look wherever relevant. Avoid labels such as “latest deck” or “final video” without a specific version identifier.
Crew ownership and communication
Assign a responsible role to every action. Establish who calls cues, who executes them, and who can approve a program change.
For a typical corporate program:
- Show caller: Coordinates standbys and GO calls across departments.
- Audio operator: Manages microphones, music, playback sound, and audio routing.
- Video operator: Controls presentations, playback, screen destinations, and confidence feeds.
- Lighting operator: Executes stage looks, audience looks, and transitions.
- Stage manager: Confirms presenter readiness, entrances, exits, and stage changes.
- Client decision-maker: Approves editorial changes, segment cuts, and program priorities.
On smaller events, one person may cover multiple roles. Confirm that simultaneous responsibilities are realistically manageable rather than simply assigning every task to the same technician.
Dependencies and contingency actions
A cue should not proceed until its prerequisites are satisfied. A panel introduction, for example, may require chairs placed, microphones checked, panelists ready, and the correct title slide loaded.
Document a fallback for consequential failures, including playback problems, an unavailable presenter, or a microphone issue. Name who authorizes the fallback and what the audience should see or hear while the crew resolves the problem.
A practical technical run-of-show template
Use this structure as a starting point for corporate event production. Split complex moments into separate cues rather than crowding multiple transitions into one row.
| Cue / planned time | Trigger | Department actions | Owner / readiness | Contingency |
|---|---|---|---|---|
| Q01 / 8:55 | Caller GO after doors confirmation | Audio: walk-in music. Video: holding slide. Lighting: audience entry look. | Caller; stage manager confirms room ready. | Hold entry if venue or production readiness is unresolved. |
| Q02 / 9:00 | Host at entrance; caller GO | Audio: fade music, open host mic. Video: welcome slide. Lighting: host look. | Audio, video, lighting; stage manager confirms host ready. | Keep holding slide and music until host is ready. |
| Q03 / 9:03 | Host: “Let’s take a look”; caller GO | Video: play opening film. Audio: playback up, host mic muted. Lighting: playback look. | Playback operator confirms exact file loaded. | On caller instruction, return to host look and use approved bridge script. |
| Q04 / 9:05 | Film complete; caller GO | Video: keynote title. Audio: keynote mic open. Lighting: keynote look. | Stage manager confirms speaker ready. | Host returns if speaker is unavailable. |
| Q05 / 9:30 | Keynote exit; caller GO | Audio: transition music. Video: panel title. Lighting: transition look. Stage: place chairs. | Stage manager confirms stage clear before reset. | Extend transition music; caller holds introductions. |
The working document should also include segment duration, asset references, revision information, and any event-specific routing or communication notes.
How to plan transitions without dead air
Transitions are production sequences, not empty space between agenda items. Give each one an owner, a duration, and a defined audience experience.
For a keynote-to-panel transition, specify who moves furniture, whether microphones travel with presenters, what appears on screen, and whether music or a host introduction covers the reset. Confirm that stage lighting supports safe movement without distracting from the intended presentation.
For remote contributors, identify who checks the connection, confirms return audio, and signals readiness. If a remote guest is not ready, the caller needs an approved alternative—not an improvised conversation across multiple crew members.
How to make contingency instructions useful
“Use backup” is not a complete contingency plan. State what the backup is, where it is located, who activates it, and whether the program pauses or continues.
For a microphone failure, identify an accessible replacement and the person responsible for delivering it. For presentation failure, specify the alternate playback source and whether the speaker can continue with a holding slide. Any planned redundancy must be included in the equipment scope and tested before doors open.
Safety-related holds require a different approach. Reference the venue’s emergency procedures and identify the authorized decision-maker; a show caller should not improvise instructions that conflict with venue safety direction.
Keep one current, usable document
Give the document a revision number, timestamp, and owner. Distribute changes through one agreed channel, withdraw outdated copies, and verbally confirm critical updates with affected operators.
At Ramar Event Productions, planning connects design with practical production requirements. Our veteran-owned team supports events with meticulous, expert precision, backed by our 25,000 sq. ft. Production & Fabrication Facility — Torrington, Connecticut. See our work for examples of the environments that coordinated production helps bring together.
Frequently asked questions
Who creates the technical run of show?
The producer or show caller typically develops it with the technical lead, department operators, stage manager, and client. The client supplies program priorities; the crew translates them into executable cues.
How is it different from a rehearsal schedule?
A rehearsal schedule allocates time to practice. A technical run of show specifies the live sequence, triggers, responsibilities, and fallback actions. Rehearsal helps validate and refine that document.
Should every slide change be listed?
Not necessarily. List slide changes that trigger other departments or require operator control. For presenter-controlled decks, document the deck version, starting slide, control method, and key coordinated moments.
When should the document be finalized?
Set an agreed approval deadline before rehearsal, then issue controlled revisions as needed. Confirm the show version before doors open and communicate any subsequent changes directly to affected crew.
Build a clearer plan for your next corporate event
Ramar Event Productions serves the tri-state area first, with support across the East Coast, the Caribbean, and fly-out programs nationwide. To coordinate AV, crew responsibilities, and seamless transitions, request a quote. We reply within 24–48 hours during peak event season; for urgent requests, call/text 860-318-5557.