Your show fails at the speed of your worst communication link. Not the lighting rig, not the audio stack, not the video wall. The intercom.
I've watched six-figure productions crumble in real time because a stage manager couldn't reach a follow spot operator during a cue transition. I've seen an Emmy Awards segment go sideways because two departments were on the same channel arguing over talkback protocol while the talent was already walking. The gear was flawless. The communication architecture was a disaster.
If you're building shows at any serious scale and you haven't mapped your intercom hierarchy with the same intention you give your signal flow, you are leaving execution speed on the table every single night.
Communication Hierarchy Is a Design Problem, Not a Logistics Problem
Most crews treat intercom like it's plug-and-play. Rent the party line system, hand out beltpacks, assign channels loosely, figure it out during load-in. That works fine for small shows. The moment you scale, that approach becomes a liability.
A real intercom architecture is a deliberate design. You're mapping information flow the same way you map signal flow: who needs to hear whom, who needs to speak to whom, who should never share a channel because the noise slows decisions. Those are design questions, and they need answers before the first cable gets pulled.
I started thinking about this differently after a run of large-scale NBA productions where fifteen or more departments were operating simultaneously. Disney live events pushed it further. When you're running a show for Dick Clark Productions on a broadcast timeline, you don't have time to repeat yourself. You don't have time for channel congestion. Every extra second spent clarifying a miscommunication is a second you're not executing.
The Three Tiers That Actually Work
This is the framework I give every production team I work with, and it has genuinely changed how fast shows run. Think in three tiers.
Tier One: Command
This is your show caller, your technical director, your director of photography if it's broadcast. One channel. Tight. Only the people executing cues or calling holds belong here: stage managers, follow spot leads, playback ops. If someone on this channel doesn't have a direct role in moment-to-moment show flow, they don't belong there. The command channel is sacred. The second it becomes a conversation channel, you've already lost control of your show.
Tier Two: Department
Every major department gets its own channel. Lighting talks to lighting. Audio talks to audio. Video talks to video. Rigging talks to rigging. Department leads monitor the command channel, but their crew lives on the department channel. This is where troubleshooting happens, where a board op can ask a quick question without polluting the show call. This is the layer most shows either execute correctly or skip entirely, and skipping it is expensive.
Tier Three: Cross-Talk
This is the channel where two departments coordinate directly without looping in the command tier. A lighting lead and a video lead working through a specific transition. A rigger talking directly to a carpenter about a deck piece that isn't sitting right. These conversations are real and necessary. Without a dedicated space for them, they bleed into either the command channel or the department channels, and suddenly everyone's bandwidth is consumed by a problem that only two people needed to solve.
The Real Cost of Getting This Wrong
I'm not talking about minor inefficiencies. Missed cues, botched transitions, talent standing in the wrong light, broadcast moments dropped. In a live environment, communication failure is visible failure. The audience sees it, the client sees it, and your crew feels it.
Shows that run on bad intercom architecture run scared. Everyone compensates for a system that isn't working instead of focusing on executing at the highest level. I've seen crews internalize that chaos and normalize it, convinced that's just how live events feel. It isn't. The shows where every department knew exactly where they lived in the comm structure had a completely different energy. People were calm. Execution was sharp. When something unexpected hit, the response was fast and clean because the infrastructure supported it.
What to Do Before Your Next Load-In
Map this out on paper before the next production. Literally draw it. Who's on command, who's on department, where are your cross-talk channels, and who controls gate access between tiers. Then brief your department heads on the architecture during your advance call, not during load-in. By the time you're on the floor, everyone should already know where they live in the system.
- Assign channel numbers early and put them in writing
- Confirm beltpack and IFB assignments match the architecture, not just whatever is available in the case
- Run a comm check that tests the hierarchy, not just that beltpacks are powering on
- Debrief after the show specifically on comm breakdowns; they tell you exactly where your architecture needs work
This is the kind of systems thinking we build out inside Ascend & Achieve. If you're scaling your production operation and want a real conversation about how to build the infrastructure that supports fast, clean execution, take a look at what we offer. The work happens before the show. That's where the speed lives.