A technical rehearsal connects people, content, and equipment in a single run-through. We show the order of checks, the issue log, and the criterion for opening doors.
A microphone may work, a video may open, and a lighting scene may look right. A failure often occurs at the moment when these elements should work together. The technical rehearsal of an event checks the entire chain: team, content, equipment, stage entrances, and decisions when deviating from the plan. At Aventura, we use the run-through as a final check: after it, it is clear whether the doors can be opened.
What should a technical rehearsal prove?
In short: The rehearsal should show that complex episodes are performed in the right order and the team understands its actions during normal flow and in case of failure. We check transitions between segments, launching of materials, audibility, visibility, people’s routes, communication, and backup solutions. The outcome is a decision on readiness or a short list of mandatory repeat tests.
A run-through can easily turn into a long viewing of the program. Then participants get tired, and the equipment works without transitions between systems. A useful rehearsal is structured differently. The team selects action handoff points in advance: speaker's entrance, lighting change, microphone opening, presentation launch, and sending the signal to the stream.
The table summarizes the key points of this section: Format, When useful, What can be skipped. Use it as a quick reference when preparing your event.
| Format | When useful | What can be skipped |
|---|---|---|
| full program run-through | short event or first joint rehearsal | separate repeats of already approved scenes |
| run-through by cues, cue-to-cue | long program with many transitions | full speech texts between the entrance and the finale |
We start with the current version of the program. If the script is still changing, we first finalize the main decisions through the event approval calendar. Otherwise, the rehearsal team will check a version that will no longer be used.
Before we go to the venue, we set readiness criteria. The phrase “everything works” is too vague. A clear criterion sounds like this: the video starts on command; the voice is heard at control points in the hall; the presentation opens from a backup media; the speaker knows the route; the directing team sees confirmation of each launch command, or cue.
Rehearsal Team and Right to Stop
The rehearsal should have a single leader who announces each episode, gives the cue, and decides whether to repeat the check. Other participants are responsible for their systems and briefly confirm the result. Any responsible person may stop the episode if continuing would hide a defect, create a risk for people, or damage equipment.
The minimum team depends on the program, but the roles repeat:
- director or rehearsal leader;
- technical director;
- sound engineer;
- lighting specialist;
- video and presentations operator;
- stage coordinator;
- host and speakers for complex episodes;
- venue manager;
- broadcast or translation specialist, if these systems are used;
- project manager who keeps the log of issues.
One person can combine several roles. Responsibility is still recorded separately. The team must know the operator for each video and cue, the file replacement procedure, and the person who accepts the backup option.
The communication channel is checked before the start. For the directing team, this may be an intercom or a separate headset. In a small venue, a pre-agreed voice protocol works. A shared chat is useful for files and recording decisions, but it does not replace live commands during an episode.
How to Organize a Cue-to-Cue Rehearsal
Cue-to-cue, or a rehearsal by cues, moves from one complex point to the next without fully reproducing all performances. The route includes the event start, people's entrances, video and presentation playback, lighting changes, questions from the audience, transitions between scenes, the finale, and backup scenarios. For each cue, the initiator, action, and success indicator are known.
First, we break the program into episodes. Then we mark transitions where people, content, signal, or stage configuration changes. A long speaker's speech can be shortened to the first and last phrases. It is more important to see the entrance, the position at the microphone, the first slide, the ending signal, and the handover of the scene to the next participant.
The table summarizes the key points of this section: Cue field, What to record, What the team checks. Use it as a quick reference when preparing your event.
| Cue field | What to record | What the team checks |
|---|---|---|
| trigger | phrase, timecode, or action | the team understands the launch moment |
| command | short wording in the communication channel | no double interpretation |
| action | light, sound, video, person's entrance | the system performs the required step |
| confirmation | by voice or over intercom | the leader knows the status |
| backup | file, microphone, route, or pause | a failure does not leave the scene without a solution |
We usually start with the most complex block while the team is fresh and there is time for corrections. Then we go through the beginning, transitions, and finale. If the venue is available for a short time, priority is given to scenes that cannot be fully checked in the office: rigging, large screens, radio frequencies, stage routes, and inter-room communication.
If you need a unified production plan with a script, equipment, and responsible parties, request a quote from us. In the request, specify the format, city, date, number of guests, and current preparation stage.
Practical case studies of event preparation are published in Aventura's Telegram channel. There we discuss working documents, the program, and venue solutions.
Content, screens and file versions
At the rehearsal, we run the materials in the same way they will work during the event. The final files are stored in a single folder with clear names and version numbers. The operator has local copies, and videos and presentations for complex segments are duplicated on a separate storage medium. Cloud links remain a way of transfer, but not the only source on site.
Before the run-through, the team checks:
- aspect ratio and resolution of materials;
- readability of text from the far points of the room;
- embedded fonts and videos;
- sound level in the videos;
- correct first and last frame;
- order of presentations in the playlist;
- absence of service comments and extra windows;
- operation of the clicker, timer, and speaker monitor.
Separately, we review the content on the venue screen. Color, contrast, and small text may look fine on a laptop and get lost on an LED panel. W3C recommends making text and graphics readable, using sufficient contrast, and explaining significant visual elements in words. It is useful to check these requirements together with the speaker, not after the first comment from the audience.
The project manager records the exact name, size, and modification time of the final file. After verification, new material does not enter the playlist without a re-run. This way the team protects itself from a presentation with the same name but different content.
How to check sound and stage entrances/exits?
Sound is checked on the microphones selected for the event and at control points in the room, and entrances/exits are walked through along the actual routes. The host speaks working phrases, the speaker takes their place, lighting and video receive the cue, after which the team listens to the beginning, transition, and ending of the segment. Noise, feedback, and dead zones are recorded in the notes log.
A simple 'one, two' check shows the presence of a signal. It says little about voice timbre, speech volume, distance to the microphone, and behavior of a person in motion. We ask the host and speakers of complex segments to say a few phrases from the program. The sound engineer adjusts the system for their voices and notes the rules for handling the microphone.
The stage coordinator walks the path from the waiting area to the performance point and back. The route must be free of cables, packaging, sharp corners, and oncoming traffic. Doors, steps, and changes in lighting are checked under the illumination that will be present during the segment. If a person comes out of a dark corridor, the team gives them a clear landmark.
The equipment scheme is chosen before the run-through. Introductory material about types and tasks is available in the article about sound equipment for events. On site, the specific configuration, radio frequencies, and backup are already checked.
The backup microphone must be turned on, labeled, and accessible to the coordinator. The mere presence of a spare device solves nothing if the team does not know who hands it over and on what command the channel switches.
Accessibility and safety before the doors open
The technical run-through includes the guest route, emergency exits, service corridors, subtitles, translation, and accessible materials. The team checks that equipment and cables do not block paths, announcements are audible, on-screen text is legible, and assistive devices receive the needed signal. Safety remarks prevent the doors from opening until they are resolved.
HSE advises to determine responsibilities in advance, coordinate with the venue and contractors, monitor control measures, and review them when changes occur. Russian law requires that evacuation routes and exits ensure the safe evacuation of people. Final decisions are made by the venue and relevant specialists considering the facility.
W3C recommends to learn participants' needs before the event, check microphones, subtitles, accessibility of materials and routes. During the run-through, we check whether speech is transmitted to the subtitle system. The coordinator takes a step-free route, the presenter verbally explains significant images, and questions from the audience are repeated into the microphone.
Safety goes beyond fire exits. Temporary obstacles must be removed, and fastenings, cable ramps, stage edges, and working lighting must be checked. If the program includes special effects, moving structures, or dense crowds, they are checked separately according to the requirements of the venue and performers.
Basic principles are also collected in our article about corporate safety. The technical rehearsal translates these principles into actual verification of the chosen facility.
What to Do with Speakers and the Host?
Speakers for complex segments and the host should at least rehearse their entrance, stage position, microphone, first and last slide, time cue, and exit. We show the speaker the monitor, clicker, timer, waiting route, and coordinator's contact. If a person cannot participate, the coordinator walks through the segment in their place, and before the performance conducts a short individual check.
The speaker doesn't need all the technical terminology. They need simple cues: where to wait, after which phrase to enter, where to look, how to hold the microphone, and what to do if the presentation stops. The instructions fit into a short cheat sheet and are repeated on site.
The host is more actively involved in transitions. They fill the pause if a video doesn't start, bring back attention after a technical stop, and pass on only approved information to guests. These backup lines are prepared in advance. Improvisation should not add promises or reasons that the team hasn't verified yet.
In a panel discussion, they test seating, the number of microphones, the order of questions, and screen visibility. A rehearsal of the awards covers names, order of appearance, passing the item, photo opportunities, and clearing the stage. In a hybrid segment, the speaker must see remote participants, and the operator must understand which signal goes to the room and which to the broadcast.
If a speaker brings a new file on the day of the event, the material goes to a separate check zone. It is not put straight into the working playlist. The operator opens the file, checks fonts, video, sound, and first launch, then updates the version in the log.
Remarks Log and Re-inspection
We record each remark in such a way that it can be re-inspected: where it occurred, how it is reproduced, who fixes it, and by what time. The wording 'fix the sound' does not help. The entry 'noise appears on the presenter's lapel microphone near the left edge of the stage' sets the location and condition for re-testing.
It is convenient to divide remarks into three levels:
The table summarizes the key points of the section: Level, Example, Solution. Use it as a quick reference when preparing the event.
| Level | Example | Solution |
|---|---|---|
| prevents opening the doors | no safe passage, main and backup signal not working | fix and re-inspect before guests |
| affects the program | wrong video, unstable microphone, speaker cannot see the timer | assign an owner and repeat the episode |
| improvement | brightness, animation speed, stand position | fix if time permits, without hiding priorities |
After fixing, the remark is not closed with a 'done' message. The responsible person repeats the same test under the same conditions. The result is confirmed by the person in charge of verification. If a full test is impossible, the team chooses a backup and records the limitation in the final memo.
The log ends with a list of open items. For each there is a solution: close, replace the system with a backup one, remove the dependent element from the program, or postpone the opening. There is no silent status of 'it should work' in the final list.
When is the rehearsal considered complete?
In short: The rehearsal is passed when there are no comments that prohibit opening the doors, start commands are reproduced, backup solutions are available, and roles are confirmed. The remaining items should not affect the safety and quality of the event. The decision is made by the manager together with those responsible for sound, lighting, safety, and the venue.
The decision to open the doors or not cannot be based on a general impression. Before opening, the team answers specific questions:
- Is there an up-to-date program and a single playlist?
- Have the beginning, difficult transitions, and finale been run through?
- Can the host, speakers, videos, and announcements be heard?
- Are the screens and service monitors visible?
- Are guest, service, and evacuation routes clear?
- Do communication, subtitles, translation, and broadcasting work if they are declared?
- Are backup microphones, files, and channels available?
- Have blocking comments been closed with a repeated test?
- Do those responsible know where to be and to whom to report?
If the answer is negative, the team does not argue with the list. It assesses the time and chooses a safe option. A video can be replaced with a static slide, and a complex entrance can be removed from the program. In the event of a serious defect, the doors remain closed until re-inspection.
Backup actions and the communication channel should be linked to the anti-crisis plan of the event. The run-through shows which scenarios are needed specifically for this project.
Step-by-step technical rehearsal plan
A useful run-through proceeds from data preparation to checking complex transitions and a repeat test. The order can be shortened for a smaller format, but it retains the responsible persons, cue-to-cue route, issue log, and final decision. At Aventura, we include the rehearsal in the production schedule in advance so that the team has time for corrections.
- Record the current program, playlist, and layout.
- Appoint a run-through leader and persons responsible for systems.
- Check the communication channel and the format of brief confirmations.
- Conduct a cue-to-cue for complex transitions.
- Upload the final files and backup copies.
- Run through the opening, entrances, videos, presentations, and finale.
- Check sound in the hall, stage routes, and service areas.
- Check accessibility, announcements, and advertised services.
- Record defects with owners and deadlines.
- Repeat the test for blocking and program-related issues.
- Make a decision on readiness and issue a memo to the team.
A technical rehearsal saves not minutes of the program, but the team's attention on the day of the event. People greet guests and manage the stage instead of searching for the wrong file or a spare cable. For the client, the result of the run-through is simple: a clear readiness status, a list of closed risks, and persons responsible for remaining actions.
Frequently Asked Questions
A run-through can easily turn into a lengthy viewing of the program. Then the participants get tired, and the equipment operates without transitions between systems. A useful rehearsal is structured differently. The team selects transfer points in advance: speaker entrance, lighting change, microphone opening, presentation launch, and signal feed to the broadcast.
The run-through should have one leader who announces the episode, gives the cue, and decides whether to repeat the check. The other participants are responsible for their own systems and briefly confirm the result. Any responsible person may stop the episode if continuing would hide a defect, create a risk to people, or damage equipment.
Cue-to-cue, or a run-through by cues, moves from one complex point to the next without fully reproducing all performances. The route includes the start of the event, people's entrances, launching videos and presentations, lighting changes, questions from the audience, transitions between scenes, the finale, and backup scenarios. For each cue, the initiator, action, and success criterion are known.
During the rehearsal, we launch materials in the same way they will work during the event. The final files are stored in one folder with clear names and version numbers. The operator has local copies, and videos and presentations for complex episodes are duplicated on a separate medium. Cloud links remain a transfer method, but not the sole source on site.
Sound is checked on the microphones selected for the event and at control points in the hall, and entrances are walked along the actual routes. The host speaks working phrases, the speaker takes their place, lighting and video receive the command, and then the team listens to the beginning, transition, and end of the episode. Noise, feedback, and dead zones are recorded in the remarks log.
The technical run-through includes the guest route, emergency exits, service passages, subtitles, translation, and accessible materials. The team checks that equipment and cables do not block paths, announcements are audible, on-screen text is readable, and assistive devices receive the necessary signal. Safety remarks prevent opening the doors until they are resolved.
To plan a technical rehearsal together with the script, venue, and production, request a quote from us. We will clarify the event format, system composition, and complex episodes.
Sources
- HSE: managing an event and coordinating work.
- HSE: getting started with planning a safe event.
- W3C WAI: accessible presentations and events.
- Federal Law No. 123-FZ, Article 89 on evacuation routes and exits.
- Crocus Expo: key requirements for holding events in 2026.
Contents
Was this article helpful?
