Theatre Sound Tech Rider: Cast, Cues, and Audio Handoffs

TL;DR — A theatre sound tech rider connects the script-driven show to the venue: cast and orchestra inputs, wireless microphone assignments, playback and effects, foldback, communications, console and system handoffs, backstage work areas, rehearsal time, and recovery plans. Use stable source IDs even when transmitters move between performers. Separate the equipment inventory from the cue workflow, name responsibility at every boundary, and test representative scenes through the complete system before the first audience.

Table of contents

1. Define the production and venue boundary
2. Map cast, orchestra, and playback sources
3. Plan wireless microphones and backstage workflow
4. Document outputs, communications, and cues
5. Advance rehearsals and recovery
6. FAQ

Define the production and venue boundary

Start with the version of the production being presented. Record the company, show, venue, performance dates, running time, interval, current revision, technical contacts, and the person authorized to approve changes.

Then define what tours and what the venue supplies:

Replace broad promises such as venue supplies suitable sound. Name the device or function, quantity, connection, location, provider, setup time, and test that proves the handoff.

Attach a dimensioned layout when scenery, orchestra, control positions, loudspeakers, backstage racks, or cable routes affect the fit. A theatre ground plan and a band stage plot serve different purposes, but stable labels and measured boundaries matter in both. Use the stage dimensions guide for clear measurements.

Map cast, orchestra, and playback sources

Build one source register before assigning console channels. Give every source a stable ID that remains meaningful across the plot, input list, RF plan, console file, cue notes, and labels.

Cast and stage sources

For each performer microphone, record:

• cast or role name and understudy relationship;
• microphone element and mounting method;
• transmitter or wired connection;
• receiver output and stage input;
• costume, wig, mask, movement, moisture, and quick-change constraints;
• fitting, check, handoff, and return responsibility;
• spare or substitution plan.

Microphone placement is part of the production design. Wardrobe, hair, makeup, movement, and visual requirements can change what is practical, so resolve those interfaces during rehearsal rather than treating them as a show-day patch detail.

Add practical microphones, boundary or overhead microphones, effects microphones, onstage instruments, and audience or room microphones only when the production actually uses them. Their positions must respect scenery moves, performer paths, feedback risk, and stage noise.

Orchestra and playback sources

Keep the orchestra or band input list connected to its physical layout. Include source, microphone or DI, stand, phantom-power note, stage-box destination, musician monitor destination, and provider. For a changing or reduced orchestration, publish the exact version used at this venue.

Playback entries should identify the output, channel meaning, connector and format, operator, backup, and cue relationship. Keep click, guide, rehearsal slate, and private talkback out of public program outputs.

The table is an example structure, not a universal channel plan. Follow the input-list and patch-sheet guide for the full channel document.

Plan wireless microphones and backstage workflow

Do not make the console channel, transmitter, performer, and costume the same identifier. They may change at different times.

Create linked schedules for:

1. audio source or cast role;
2. transmitter and receiver path;
3. microphone element and mount;
4. costume or scene assignment;
5. person responsible for fitting and checking;
6. handoff time and location;
7. spare available for recovery.

Example assignment schedule

Only share a transmitter when the schedule, physical handoff, hygiene process, battery plan, costume access, and sound check make it workable. Never infer a change window from scene names alone; time it in rehearsal.

List every production and venue wireless system, including microphones, IEMs, communications, and other coordinated RF devices. Record tuning capability from current device documentation, antenna locations, coordination owner, local regulatory constraints, scan time, battery policy, and the point at which assignments are frozen. Use the wireless microphone tech rider for the detailed RF checklist.

Define the backstage workspace: receiver and monitoring position, microphone preparation bench, charging and battery area, storage, costume handoff points, safe cable routes, and access during the performance. The workflow is incomplete if the equipment list has no place or time to operate.

Document outputs, communications, and cues

Map each output by listener and purpose:

• main audience system, fills, delays, and under-balcony zones;
• front fills or stage effects loudspeakers;
• orchestra, conductor, cast, and backstage foldback;
• lobby, dressing-room, paging, and show-relay feeds;
• recording, archive, stream, or press feeds when agreed;
• assisted-listening or accessibility system handoff;
• measurement and monitoring points.

Do not assume every output carries the same mix or delay. Name the bus, format, physical or network path, processing owner, destination, and acceptance position.

Separate cue data from system data

The rider should define the systems that reproduce cues and the process used to deliver them. The current cue list or playback session remains controlled show data.

For each cue family, record:

• playback system and backup;
• output mapping and level reference;
• timecode, MIDI, GPIO, network, or manual trigger interface when used;
• who calls, triggers, confirms, and may stop a cue;
• rehearsal and update procedure;
• recovery position after interruption.

Avoid copying an obsolete cue list into a static rider. Keep one controlled version and identify its revision in the production package.

Connect stage management and sound

List required intercom stations and channels for stage management, sound, lighting, automation, flys, wardrobe, orchestra, and front of house. Add cue-light, paging, program-audio, and show-relay interfaces where used. The production intercom guide explains the full station and channel schedule.

Advance rehearsals and recovery

Build a schedule from dependencies, not a single soundcheck block:

1. venue system and infrastructure access;
2. control, network, playback, and RF setup;
3. line identification and output-zone verification;
4. microphone fitting and individual checks;
5. orchestra and playback checks;
6. cue-to-cue rehearsal for technical transitions;
7. representative scenes with costumes, movement, scenery, and full routing;
8. notes, fixes, save, backup, and performance preset.

Test the scenes that stress the system: large cast moments, quiet dialogue, rapid microphone changes, movement near loudspeakers, orchestra peaks, playback transitions, backstage paging, and any recorded or streamed output.

Recovery table

Do not promise seamless recovery unless it has been designed and rehearsed. A useful fallback is understandable, selectable, and safe for performers, crew, and audience.

Pre-send checklist

• Production version, venue, dates, contacts, and revision are current.
• Touring and venue responsibilities are explicit.
• Cast, orchestra, playback, effects, and practical sources have stable IDs.
• Wireless assignments connect roles, transmitters, elements, costumes, and handoffs.
• RF coordination, antennas, batteries, spares, and backstage workspace are planned.
• Every output has a destination, path, mix owner, and acceptance point.
• Cue, playback, timecode, and communications interfaces are documented.
• Rehearsal time covers representative scenes and technical transitions.
• Recovery plans name the fallback and decision owner.
• The current rider, plot, schedules, and show data use matching revisions.

FAQ

What should a theatre sound tech rider include?

Include production control, venue and touring responsibilities, cast and orchestra inputs, playback, wireless inventory and assignments, outputs, PA and foldback zones, backstage workspace, communications, cue interfaces, rehearsal schedule, contacts, tests, and recovery plans.

How do you make an input list for a theatre production?

Give each cast, orchestra, playback, effects, and practical source a stable ID. Record connection, microphone or DI, provider, stage input, console channel, destination, phantom-power note where relevant, and scene or assignment information in linked schedules.

How are wireless microphones planned for theatre?

Link each role to a microphone element, transmitter, receiver path, costume or mounting method, handoff window, battery plan, check owner, and spare. Coordinate all venue and production RF systems, then verify assignments with costumes and movement during rehearsal.

What audio cues belong in a theatre tech rider?

Document the playback systems, output mapping, trigger and timecode interfaces, operator responsibilities, backup, rehearsal process, and controlled cue-list revision. Keep the detailed current cue list as managed show data rather than duplicating stale entries.

How do touring theatre productions advance sound with a venue?

Exchange the current rider and venue pack, reconcile equipment and responsibility boundaries, confirm dimensions and access, agree RF and network ownership, build a dependency-based schedule, and test inputs, outputs, cues, communications, representative scenes, and recovery before opening.

Keep the production map current

Build the stage layout and connected input list in Techrider.live, invite the production sound team to edit the same Rider, save the confirmed version, and share one current handoff with the venue.

---

Last updated: 2026-08-12 · Reviewed for theatre cast and orchestra inputs, wireless assignments, playback and cue interfaces, backstage workflow, communications, rehearsals, and recovery.