A technical rehearsal should reveal whether people, systems and cues can deliver the program together. It needs to catch more than broken equipment. Missed handoffs, unclear authority, wrong content versions and untested recovery decisions can disrupt a show even when every device works on its own.
Use rehearsal to test the sequence the audience will experience, with the actual assets and representative participants. The most valuable findings are specific enough to correct before the event begins.
Start with the transitions
A microphone check proves that a voice reaches a destination at one moment. It does not prove the handoff from an opening video to a presenter, or from a stage discussion to a remote guest. Those transitions cross departments and need explicit cues.
Walk through the running order and mark each change in picture, sound, lighting, content or participant. Identify who calls the change and who executes it. If two people believe they own the same cue, or nobody does, resolve that ambiguity during rehearsal.
Test the opening and close as carefully as the middle. The audience should receive an intentional first view and a deliberate ending. A program that begins with a private conversation or ends with an unattended stage picture has a sequence problem, not necessarily an equipment fault.
Verify the exact content
Use the approved presentation, videos, graphics and scripts. Substitute files can conceal missing audio, unreadable text, unexpected aspect ratios or a version problem. The playback operator should be able to identify the requested asset without interpreting an informal description.
Confirm how late changes are accepted. Someone needs authority to approve the new version and communicate its effect on cues. If the running order changes after rehearsal, identify which transitions need another check. A previous pass does not automatically cover a revised sequence.
Include the output context. A slide may be readable on the venue screen but poor in the remote composition. A lower-third may cover a detail the presenter needs to demonstrate. Review the actual program view rather than approving each asset separately.
Listen at the destinations
Check what the room hears, what remote participants hear and what the audience stream receives. These can be different paths. A successful local sound check does not establish that playback is included in the stream or that a remote guest has a useful return.
Assign a person to monitor the received program independently. They should report specific observations with the segment and source involved. “Audio is bad” is less actionable than “the remote viewer hears the host but not the video playback.”
For recordings, open saved files during the test. Confirm the intended sources and file destinations. An active record indicator is useful status information, but the deliverable is the playable file the client or editor receives.
Put the real people in the workflow
Presenters need to practice entrances, microphone use, slide control, timing and handoffs. Remote guests need to test from their normal locations where practical. Stand-ins can help technical setup, but they may not reveal the same eyeline, movement or connection issues.
Give the host a clear response when something goes wrong. If a guest disconnects, should the host continue, hold or move to another topic? The producer should decide the acceptable options, and the show caller should know the cue for each.
Avoid using rehearsal only as a performance run-through while technicians silently solve unrelated tasks. There should be room to stop at a failed handoff, identify the cause, correct it and repeat the affected section. Otherwise, the schedule advances without establishing that the problem is resolved.
Test selected failures deliberately
Choose recovery scenarios based on the event’s actual dependencies. A missing playback file, a disconnected presentation source or an unavailable remote guest may deserve a practiced response. Introduce these conditions only in a controlled rehearsal, with the team aware and the normal state restored afterward.
A fallback should name the action, owner and audience consequence. “We have a backup” is incomplete if nobody knows when to use it or how long the transition takes. Ask the operator to demonstrate the response and the producer to confirm that it is acceptable.
Do not try to simulate every imaginable fault at the expense of testing the actual show. Prioritize the failures that are plausible, consequential and recoverable through a planned action. Record limits honestly where the event has no equivalent substitute.
| Rehearsal finding | Why it matters | Useful correction |
|---|---|---|
| Two people call the same cue | Operators may receive conflicting instructions | Name one cue authority and a communication path |
| Playback version is uncertain | The wrong content may reach the audience | Identify the approved asset and replace obsolete copies |
| Guest return is untested | Remote conversation may fail despite a working stream | Run a two-way test with the actual guest setup |
| Recording has not been opened | The expected deliverable remains unverified | Play saved samples from the required destinations |
| Fallback is only verbal | The crew may improvise under pressure | Rehearse the response and document its trigger |
Turn findings into a readiness decision
Keep an issue list with the symptom, affected segment, owner and retest result. Separate an unresolved problem from an accepted limitation. A client may accept a specific compromise, but that decision should be visible to the people running the event.
The designated producer or event authority needs a clear readiness report. Technical teams should state what passed, what remains open and what the available response is. The scheduled start time should not silently convert unresolved issues into approval.
JAZ’s technical direction service focuses on coordinating the show’s technical sequence and departments. The related corporate event work provides scope context for that coordination without implying that every event follows the same crew arrangement.
Bring a usable running order
Before booking rehearsal time, prepare the program sequence, approved assets, speaker list and responsible contacts. Mark the moments involving multiple departments and the decisions that remain open. The paired guide includes a run-of-show structure and readiness checklist you can adapt.
Send JAZ the event plan early enough to reserve the time, crew and access needed for a meaningful rehearsal. The objective is a tested program and a team that knows what happens next, including when the normal sequence needs to change.
Jesse Kaplan
Jesse Kaplan is the third generation of JAZ Entertainment. His work spans permanent studios, professional AV systems and live technical production.
About Jesse and JAZ