Production Intercom Tech Rider: Crew, Channels, and Cueing

TL;DR — A production intercom tech rider should identify who must communicate, which conversations must be shared or private, where each user works, and who supplies every station, headset, interface, cable, power source, and wireless device. Document show-calling authority, channel assignments, cue language, coverage, testing, and a fallback. Design from roles and workflows rather than copying an equipment list from another show.

Table of contents

1. Map the communication workflow
2. Choose channels and user stations
3. Document system handoffs
4. Advance cueing, staffing, and tests
5. Build a usable fallback
6. FAQ

Map the communication workflow

A production intercom tech rider describes the crew communication needed to prepare and run a show. It connects people and locations to channels, stations, interfaces, responsibilities, and cue procedures. It is not the artist monitor plan, audience PA, or a general contact list.

Begin with the jobs that require immediate production communication:

• stage manager or show caller;
• production manager;
• audio, monitor, lighting, and video operators;
• stage, backline, automation, or changeover leads;
• followspot operators;
• front-of-house or venue duty manager;
• artist liaison or dressing-room position when operationally necessary;
• safety or security lead where the venue plan requires it.

For each role, record the working location, whether the person moves, the conversations they must hear, the people they must call directly, and the times they need service. Do not assign a wireless beltpack simply because a role sometimes leaves a desk; mobility, coverage, channel access, and venue restrictions must be advanced together.

Create a user schedule

Replace Confirm during the advance. A complete schedule names the user, service, location, provider, and test owner instead of requesting an unexplained quantity of beltpacks.

Choose channels and user stations

Shared and direct conversations

A partyline is a shared conversation in which participants on the same channel can hear and speak with the group. A point-to-point path connects selected users or stations directly. Either workflow may be carried by wired or wireless equipment, depending on the confirmed system.

Use the smallest channel plan that keeps critical calls intelligible:

More channels do not automatically improve communication. Each added conversation requires compatible user access, labeling, configuration, and rehearsal. Confirm whether a user can listen to several channels, reply selectively, or needs a separate station function.

Wired and wireless positions

Wired stations suit fixed positions and can reduce dependence on radio coverage and battery management. Wireless stations suit people who must move, but the advance should confirm usable coverage, antenna or base-station locations, available devices, battery workflow, local spectrum coordination, and who configures the system.

Specify the operational need before a brand or model. If exact compatibility with a carried station, headset, interface, or show configuration makes a model essential, state the interface reason and name the person who can approve an alternative.

Document system handoffs

Equipment and responsibility schedule

Record every required component and boundary:

• main, remote, desktop, wall, or rack stations;
• wired and wireless beltpacks;
• headsets, handset or loudspeaker stations, and connector types;
• power supplies and system power responsibility;
• base stations, antennas, chargers, and batteries;
• two-wire, four-wire, network, radio, paging, or program-audio interfaces actually used;
• cable types, lengths, routes, protection, and stage crossings;
• rack space, mains power, network access, and environmental requirements;
• configuration, labeling, operation, and troubleshooting owner.

Do not assume that two intercom systems connect because both carry speech. Confirm the electrical or network interface, audio direction, level, connector, isolation, call signaling where required, configuration owner, and test method. Keep private network credentials and sensitive access details out of public rider links.

Program audio, cue lights, and paging

If users need program audio in their headsets, identify its source, feed owner, level-control workflow, and behavior during calls. If the show uses cue lights, paging, dressing-room calls, tally, or radio interfaces, document each as a separate destination and state whether it is advisory or part of the approved cue process.

Do not treat a public-address microphone, phone group, or consumer messaging app as an automatic replacement for production intercom. Latency, coverage, hands-free use, channel structure, access, and failure behavior differ. A fallback should be deliberately accepted by the production and venue leads.

Advance cueing, staffing, and tests

Establish show-calling authority

Name who calls the show, who may issue a stop or safety call under the venue plan, and which operators acknowledge cues. Agree concise cue language before rehearsal. A practical sequence separates warning, standby, execution, and confirmation:

1. identify the department or operator;
2. issue a standby with the cue name or number;
3. wait for the agreed acknowledgement when required;
4. call the execution word clearly;
5. confirm completion only when the workflow requires it.

The exact vocabulary belongs to the production’s agreed procedure. Do not publish an assumed emergency protocol that conflicts with the venue’s safety plan.

Put communication in the schedule

Add intercom installation, configuration, user distribution, line checks, cue rehearsal, and collection to the Concert Production Schedule. The system should be operational before departments need to coordinate final checks—not first powered during doors.

Use a named communication lead for larger systems. That person should receive the accepted user and channel schedule, coordinate the venue and touring boundaries, label stations consistently, and maintain the show-ready configuration.

Test the complete workflow

• Every required user has the correct station and headset.
• User labels, channel labels, and locations match the accepted schedule.
• Wired paths work at their final cable lengths and routes.
• Wireless users can communicate throughout required working areas.
• Program audio, paging, cue lights, radios, or external interfaces work as agreed.
• Callers and operators can hear intelligibly at realistic show noise levels.
• Batteries, chargers, spares, and collection responsibilities are ready.
• Cue words, acknowledgements, and communication discipline are rehearsed.
• The fallback is available and understood.

Check actual working locations, including backstage routes and control positions. A successful test beside the base station does not prove coverage where a mobile crew member works.

Build a usable fallback

Prioritize the conversations needed to start, run, and stop the show safely. A fallback may reduce the channel count, move critical users to wired stations, issue approved radios to selected roles, add a cue-light path, or define runners and hold points. It should name the trigger for switching, the decision owner, and how every affected department is told.

Record material changes in the current rider and Show Advance Checklist. If another department changes position or operator, recheck the communication schedule rather than assuming its old station assignment still works.

Common intercom-rider mistakes

Requesting only a beltpack quantity. This omits users, channels, locations, interfaces, headsets, and providers.

Putting every conversation on one channel. Setup traffic can mask show calls; design groups around the actual workflow.

Assuming wireless coverage. Test the areas and routes where mobile users work, then document battery and spare responsibility.

Ignoring carried-to-house compatibility. Name the complete interface and its configuration and test owners.

Leaving cue language implicit. Operators need an agreed caller, standby, execution, acknowledgement, and stop workflow.

Testing too late. Intercom supports other checks, so it must be ready early enough to coordinate them.

FAQ

What should a production intercom tech rider include?

Include users and locations, shared and direct conversations, channel assignments, station and headset types, wired and wireless requirements, interfaces, program feeds, power and network boundaries, providers, show-calling authority, cue procedure, schedule, tests, spares, and fallback.

What is a partyline intercom system?

A partyline is a shared communication channel. Participants assigned to it can hear and speak with the group, subject to their station controls and system configuration. It differs from a point-to-point path intended for selected endpoints.

Who needs intercom at a concert?

The answer depends on the show. Common users include the show caller or stage manager, production manager, department operators, stage or changeover leads, followspots, and selected venue roles. Assign service from communication need and location, not job title alone.

What is the difference between wired and wireless intercom?

Wired intercom connects a station through installed or temporary cable and works well at fixed positions. Wireless intercom gives mobile users freedom to move but adds coverage, antenna, configuration, spectrum, battery, and spare considerations. Both can support shared conversations, depending on the system.

How do you test a production intercom?

Test every user at the final location, verify channel access and labels, walk all required wireless areas, check external interfaces and program feeds, listen at realistic noise levels, rehearse cue language, and demonstrate the agreed fallback before the show-ready deadline.

Keep the communication plan with the Rider

Build the stage plot and technical package in Techrider.live, invite the production manager or department lead to edit and save the same Rider, inspect history after revisions, and share the accepted communication handoff with the venue.

---

Last updated: 2026-08-05 · Reviewed for production intercom users, channels, stations, interfaces, cueing, testing, responsibilities, and fallbacks.