A technical rehearsal is a structured run of the show focused on lighting, sound, staging and cues, not a final polish of performance. It's typically scheduled as a dedicated block before the first audience or live element, with UK practice often allowing about one week for technical work after a seven-to-eight-week rehearsal period, including two to three sessions per day, a ring-fenced day off and one to two dress rehearsals, ideally two. National Theatre UK teaching materials
You've probably seen the moment. It's early morning at a London conference venue, the client wants to know whether the keynote deck is ready, presenters are arriving later, and the room still looks more like a worksite than an event. The screens are up, the lighting bars need attention, and every department has a slightly different answer to the question, “Are we ready?”
That question is what a technical rehearsal is designed to answer. It turns separate equipment, people and instructions into one working show, while there's still time to fix the problems that would otherwise appear in front of delegates, cameras or a live audience.
The Morning of the Tech Day
The production team arrives to a half-built conference space. Flight cases are open along the back wall, a video processor is being patched, and the stage manager is already checking which crew members are on comms. A screen is showing a test pattern, but the content operator hasn't yet received the final presentation. At the lighting position, fixtures are being focused and the room lighting is being adjusted around the set.
Nobody expects the event to be ready at that point. The morning is about establishing control.
The stage manager asks the practical questions first. Which presenters are attending? Is the stage configuration final? Are all media files loaded? Can the venue confirm access routes, working lights and emergency arrangements? These questions may sound basic, but they expose gaps before the team starts calling cues.
A technical rehearsal sits between physical setup and live delivery. It's the point where the production manager, stage manager, lighting team, sound team, video operator, presenters and venue staff can work from the same information. The aim isn't to perform the entire programme beautifully. The aim is to test what happens when one moment changes into the next.
What gets tested in the room
A typical corporate tech day may include:
- Presenter microphones: Checking capsule choice, fit, signal, battery status and handover.
- Presentation content: Loading the approved files and confirming playback on the actual screens.
- Lighting states: Testing entrances, speaker looks, stage washes, walk-on moments and blackout conditions.
- Audio cues: Checking playback, speech reinforcement, music starts, fades and transitions.
- Stage movement: Walking furniture changes, entrances, exits and backstage routes.
- Communications: Confirming who calls the cue, who executes it and how issues are escalated.
The room may still look unfinished, but the team is building the operating logic of the event. By the end of the day, the question should have changed from “Where are we up to?” to “What remains open, who owns it and when will it be closed?”
That distinction matters for corporate work. A short venue window leaves little room for improvisation, so the tech rehearsal is a planning decision as much as a production activity.
What a Technical Rehearsal Actually Is
A technical rehearsal is a cue-to-cue or partial run of a production in which the technical departments bring their systems together and test the transitions that make the show work. Lighting, sound, video, props, costume, staging and backstage movement are checked as connected parts of one operation.
The simplest way to understand it is to separate creative continuity from technical integration. A creative rehearsal asks whether the performers, presenters or host can deliver the material from beginning to end. A technical rehearsal asks whether the room, equipment and crew can support every change reliably.

How the cue-to-cue process works
The team doesn't usually run the complete show at normal speed. Instead, the stage manager calls a moment, pauses, checks the response and repeats the transition until the departments agree that it works.
A cue might involve a presenter walking on while a music track fades, the room lighting changes, a screen switches from a holding slide to a presentation, and a confidence monitor displays the correct source. If one element is late, missing or unsafe, the team stops and corrects it before moving on.
This is why a technical rehearsal is an integrated system test, not a final run-through. UK production practice generally places it after fit-up and before dress rehearsal or performance. National Theatre materials describe it as the point when music, sound, lighting and other departments come together for the first time, while UK stage-management guidance treats it as a controlled checkpoint for cueing, communication and safety. National Theatre production guidance
The distinction is particularly important for live events. A keynote may be creatively ready, but the show still isn't operationally ready if the microphone handover hasn't been checked, the presentation source hasn't been tested or the stage manager and operator aren't using the same cue list.
Technical, Dress and Run-Through Rehearsals Compared
These rehearsal types overlap, but they prove different things. Confusing them is a common reason planners book too little venue time or expect a technical rehearsal to deliver a polished performance.
Rehearsal Types at a Glance
| Rehearsal Type | Main Focus | Typical Timing | Who Attends |
|---|---|---|---|
| Technical rehearsal | Systems, cues, transitions and backstage operation | After fit-up and before dress or performance | Technical departments, stage management and relevant performers or presenters |
| Run-through rehearsal | Continuity, pacing and the complete sequence of the programme | Once the material is sufficiently prepared | Performers, presenters, director or producer and key production staff |
| Dress rehearsal | Full performance conditions, including technical systems and presentation detail | After technical work and before the first audience | Full cast or presenter team, technical crew, stage management and relevant client or production leads |
A run-through is about flow. The host works through the agenda, speakers practise their entrances, and the production team observes timing and continuity. It's useful for finding editorial or pacing problems, but it won't necessarily reveal whether every cue can be executed from the control position.
A technical rehearsal is more interruptive. The stage manager may stop after a few seconds to adjust a followspot, change a playback level or correct a screen source. That stop-start rhythm is productive because the team is fixing the operating system rather than judging the performance.
A dress rehearsal combines the two. It should resemble the live event as closely as practical, with presenters or performers in the relevant costume, content loaded, cues active and transitions completed at performance pace. In a corporate setting, that might mean running the opening, keynote, video playback, panel changeover and closing sequence with the actual microphones and screens.
The mistake is treating the dress rehearsal as the first time the technical team discovers how the show works. By then, the dress should confirm readiness, not provide the first opportunity to build it.
Roles and Responsibilities on a Tech Day
A tech day works when everyone knows who can make a decision and how that decision reaches the crew. The Royal Shakespeare Company's stage-management guidance describes the stage manager as overseeing what happens in the rehearsal room and onstage, then communicating it to technical departments and the wider organisation. That communication thread is central to a controlled rehearsal.
The stage manager or show caller owns the sequence. They call “standby” and “go”, control pauses, confirm that departments are ready and maintain the record of changes. They shouldn't be competing with the client, director or presenter for the cue-calling role.
The lighting designer or lighting operator focuses fixtures, checks coverage and adjusts programmed states. In a conference, the practical priorities may include a flattering speaker look, readable lectern lighting, safe backstage movement and a camera-friendly balance between stage and screen.
The sound engineer checks microphones, playback and reinforcement. They'll confirm which microphone belongs to which presenter, listen for handling noise, verify levels from the speaker position and check that music fades land where the stage manager expects them to.
The video operator loads media, tests playback paths and confirms that the correct image reaches the correct display. That includes presentation screens, confidence monitors, recording feeds and any stream output where relevant.
The people who keep the decisions moving
The production manager deals with venue liaison, access, staffing, schedule pressure and unresolved dependencies. They're often the person who decides whether a change is safe and achievable within the available window.
The client representative or producer checks content and approves visible decisions. They can sign off a holding slide, speaker walk-on music or a change to the stage layout, but they shouldn't bypass the show caller during a live cue sequence.
Practical rule: one person calls the show, one person manages production risk, and one authorised client representative signs off content.
Everyone should know which channel to use, where notes are recorded and who owns the next action. A shared cue sheet, annotated run sheet or production schedule is more reliable than a series of separate messages. For a wider explanation of the technician's role in this chain, see what an AV technician does.
This short video provides useful visual context for how technical teams coordinate their work on a production day:
A Practical AV Checklist and Sample Schedule
A useful checklist starts before anyone calls the first cue. The team needs a stable version of the show information, a clear signal path and enough time to test changes rather than just observe them.
Before the first cue
- Confirm the room: Check stage dimensions, audience sightlines, access routes, power arrangements, rigging restrictions and working lights with the venue.
- Load approved content: Store presentation files, films, stills, logos and holding slides in an agreed folder structure. Record the version used for rehearsal.
- Trace signal paths: Test source devices, switchers, processors, distribution, screens, confidence monitors, recording feeds and stream outputs.
- Prepare the cue list: Match every lighting, audio, video and stage-management cue to the latest run sheet.
- Check communications: Issue comms, confirm channels and make sure every department understands the call and escalation process.
- Run presenter checks: Fit microphones, check playback, confirm lectern and stage positions, and let speakers practise with the equipment.
- Brief for safety: Cover movement routes, blackout conditions, working areas, venue rules and stop procedures.
A technical rehearsal should be booked as its own production activity, not treated as the same thing as performance time. The BBC's guidance describes a cue-to-cue rehearsal and notes a UK venue model that allows around 1.5 times the booked slot plus an extra 10 minutes for safety and briefing. BBC Bitesize guidance on technical rehearsals TheSpaceUK gives the same one-and-a-half-times-plus-10-minutes planning rule in its technical rehearsal planning guidance.
A one-day working pattern
| Stage | Activity |
|---|---|
| Venue access | Crew briefing, safety information and confirmation of the room |
| Build confirmation | Check screens, lighting, sound, staging and content paths |
| Cue preparation | Work through opening, transitions and complex sequences |
| Presenter checks | Fit microphones and test presentations with each relevant speaker |
| Main cue-to-cue | Call technical transitions, pause for fixes and record notes |
| Dress or partial run | Test the agreed sequence at performance pace |
| Close-out | Confirm outstanding actions, owners and next review point |
The schedule needs room for decisions. A production schedule such as the one explained in what a production schedule is gives the wider project a single timeline, while specialist material on audio visual production with Flexwork Podcast Studios can help teams think through recording and content workflows before they reach the venue.
Common Problems and How to Solve Them
Most failed tech days aren't caused by one dramatic equipment fault. They're caused by small planning gaps that arrive at the same time, then consume the slot that was meant for testing.
Late content delivery is the clearest example. If the final film, presentation or holding slide arrives after cue building has started, the video operator may need to recheck playback, aspect ratio, audio and downstream outputs. Freeze the content deadline, label versions clearly and keep an approved fallback asset available.
Mismatched cues create a different problem. The run sheet may say “video two”, while the cue list says “media three”, and the stage manager may be calling from a third version. Use one master cue list, with changes dated and visible to every department.

Where time disappears
Under-booked rehearsal time is usually a planning error, not a crew-performance problem. UK guidance shows that technical slots are often tightly scheduled, with only modest additional time allowed for safety briefings and operational checks. A performance might run smoothly in an hour, but the technical team needs time to stop, adjust, repeat and document each transition.
The fix is to negotiate the tech period separately from the show duration. Prioritise high-risk moments first, including complex changeovers, live microphones, blackouts, video playback and any staging movement.
Missing presenters and last-minute layout changes create similar pressure. Ask relevant presenters to attend their cues, and lock the stage plan before the rehearsal begins. National Theatre guidance notes that performers may not be permitted into a scene if they miss the technical rehearsal, because their cues, microphone checks and integration haven't been verified. National Theatre technical rehearsal resource
Venue, Safety and Risk Assessment Considerations
A technical rehearsal is a safety checkpoint as well as a production test. The Association of British Theatre Technicians guidance says risk assessments should cover the full production process, including preparation, get-in, technical and dress rehearsals, performances and get-out. That places technical rehearsal inside the safety system, rather than treating it as an informal period between build and show.
The team should check how the venue expects people to work around lighting bars, rigging, scenery, cables, screens and backstage routes. Working lights matter because performers and crew need to understand what they can see during movement. UK guidance also says artistes should walk the set in costume in working light conditions, and that scene changes should be rehearsed in working lights. Blackouts and amplified sound need particular attention, because the team must be able to stop an effect quickly if it creates a risk.
Stop procedures and accountability
Everyone needs to know who is in charge and how an instruction is communicated. The stage manager should be able to halt the rehearsal, while the production manager or venue representative resolves access, staffing or compliance issues.
ABTT-aligned guidance states that anyone asked to do work they don't feel qualified or comfortable doing should stop immediately. It also supports stopping another person if their method appears unsafe until the concern is resolved. That principle applies to rigging, lifting, electrical work, work at height and backstage movement, not just to the formal safety briefing.
For corporate planners, the practical lesson is simple. A signed risk assessment isn't a substitute for checking the actual operation in the room. Use an event risk assessment template to organise the information, then walk through the relevant controls during the technical rehearsal.
A calm production team doesn't hide safety concerns to protect the schedule. It raises them early, changes the method where necessary and records the decision.
Best Practice Tips and Frequently Asked Questions
Freeze content early, prepare the master cue list before arrival, book realistic venue time, and keep communications disciplined. A short pre-tech with the client, producer and technical leads can expose missing assets or unclear approvals before the crew enters the room. For wider venue controls, see these GM GROUP Services event security tips.
How long should a technical rehearsal be? There is no universal duration. Allow more time than the performance itself. The UK benchmark of around 1.5 times the booked slot plus 10 minutes gives a defensible starting point for briefing and safety checks. theSpaceUK planning guidance
Do presenters need to attend? Anyone involved in a technical cue should attend that part, particularly for microphone fitting, entrances, presentations and handovers.
What if the slot runs short? Prioritise safety-critical and complex cues, record deferred checks, and do not approve an untested sequence.
How does hybrid production differ? Add the stream, remote contributors, return feeds and viewing experience to the cue structure. The remote audience needs separate checks, not only a camera aimed at the stage.
London Audio Visual Hire can help plan and deliver the technical rehearsal, covering cue sheets, signal paths, presenter microphones, lighting, video and on-site coordination. Visit London Audio Visual Hire with your venue details and running order to discuss suitable technical time and crew structure.


