Team Roles in a Multicamera Production.

A multicamera production rarely falls apart because of the switcher. It falls apart because nobody knows who decides what at each moment: the director requests a shot while the operator changes a battery, broadcast audio goes unwatched exactly at the cut, and the connection deteriorates while the entire team looks at the multiview. The failure is almost never equipment; it is the allocation of responsibilities.

This guide translates a live unit’s traditional roles into real teams, without imaginary organisation charts. The aim is to understand each function, how functions combine when people are missing, and what deteriorates first when staffing is reduced, rather than memorising job titles. With that map, you can build anything from a twelve-person festival broadcast to a DJ session streamed by three.

An organisation chart that grows with you

In a large unit, every function is separate because it requires continuous attention and cannot be delegated to the same brain that is cutting shots. In a small unit, those functions do not disappear: they combine. The usual mistake is confusing “I don’t have that person” with “that task does not exist”. If nobody covers broadcast audio, someone will do it badly or not at all.

Before assigning names, write the critical functions on a sheet and mark which happen simultaneously. Cutting shots while watching broadcast levels is possible for minutes, not two hours.

Who does what in a small production

These are the twelve roles found in any production, even when combined in a reduced team:

• Director: decides the story, which camera goes live and when. Gives instructions and protects the pace.
• Vision mixer: executes cuts on the switcher and keeps transitions clean.
• Camera operators: maintain their shot’s framing, focus and exposure.
• Shader/CCU: matches and corrects each camera’s iris, pedestal and balance from control.
• Graphics: prepares and triggers titles, scoreboards and lower thirds.
• Replay operator: records and replays the moment, with slow motion and filler material.
• Broadcast audio: builds the broadcast mix and watches peaks and loudness.
• Streaming engineer: configures the encoder, bitrate, destinations and monitoring.
• Technical director: coordinates signals, switcher, synchronisation and faults.
• Intercom: the system and function keeping the team on the right channel.
• Stage liaison: connects production with the stage and artists.
• Data wrangler: copies, verifies and names material before anything is touched.

Nobody with a four-person team covers all twelve roles at once, but they must know which is uncovered and consciously accept the risk.

Direction, switching and image control

The director and vision mixer form the central pair. The first thinks about the viewer; the second thinks about the machine. When both roles fall to the same person, the live production gains speed and loses anticipation: planning the next block is difficult while executing the current one.

The technical director enters when production becomes more than an isolated switcher. Their job is to keep the chain working: correct inputs, stable genlock, truthful tally and a backup plan for a failed source. With a multicamera production architecture already built, this role keeps the configuration alive between rehearsal and broadcast.

The shader/CCU works between camera and control. If camera control units are available, they make corrections there; otherwise, they give each camera operator clear exposure and balance instructions so images arrive reasonably matched. Matching before the broadcast saves minutes of blind correction.

Graphics, replay and data

Graphics determines which information the audience sees and when. A mistimed title distracts more than its absence. Prepare templates before the broadcast and test the actual output on the programme monitor, rather than only in the software preview.

The replay operator is essential in sport and very useful at concerts with replayable moments. They need recorded ISO signals, quick markers and a dedicated output channel to avoid accidentally taking over programme. Their material also feeds the aftermovie, so agree filenames from the start.

The data wrangler closes the loop: collecting cards and recordings, verifying checksums, making copies and labelling material. This role prevents an entire show being lost to a poorly formatted drive. Multicamera recording and multitrack postproduction details what is recorded and how it is organised.

Audio and intercom

Broadcast audio does not mix for the venue. Its reference is the broadcast: intelligible voices, present music, enough ambience for context, and nothing overloading. It needs a mixer split or an independent feed, and a position where nobody intrudes on the operator’s listening during the broadcast. Broadcast audio with split, Dante and mix-minus explains how to obtain that signal.

Intercom is the invisible backbone. A poorly assigned channel turns the broadcast into confused murmuring. Before starting, check that every position hears what it needs, that the director has a private channel with the technical director, and that the stage liaison can speak to the stage without shouting. Intercom noise itself enters recorded ambience if open microphones are nearby.

Streaming, connection and data

The streaming engineer watches what the control team does not: actual bitrate, drops, latency and destination status. They must receive a clean programme signal, know what to do if the main connection fails, and maintain a local recording even if the live stream fails. Their work is detailed in streaming, encoding and multistream.

The stage liaison is the human translator between control and reality. When the stage requests a running-order change or an artist is late, the director should not leave the panel to negotiate: this role conveys the decision and returns information to the team.

Practical allocation with one, two and three people

Here is the practical core of operating a small production with 1–3 people:

• One person: handles direction, switching, broadcast audio and streaming. It works with one or two fixed cameras, wide shots and little granularity. Give up replay and live graphics.
• Two people: one in control—direction, switching and basic graphics—and another on sound and the connection. Cameras remain fixed or motorised. This is the reasonable minimum for a quality DJ-session broadcast.
• Three people: add a camera operator or shader/CCU. With that person, control can maintain shots and reverse angles, and audio gets breathing room. Technical direction, stage liaison and data wrangling are handled in turns.

Below two people, any unexpected event forces a function to be abandoned. Above four, separating technical work from direction starts making sense, so nobody cuts and repairs simultaneously.

Allocation mistakes and how to avoid them

The most expensive mistake is assuming someone covers something. Write down who is responsible for what and review that allocation at rehearsal, rather than during the broadcast. Define a substitute for each critical function and make sure intercom has a channel for reporting issues without interrupting programme.

The second mistake is failing to rehearse the entire workflow: signal, cutting, broadcast audio and the connection. A fifteen-minute rehearsal with the actual people reveals more problems than an hour of equipment-only testing. The third is failing to write down who makes the copies at the end.

Next step

This is the cluster’s final guide, so the natural next step is returning to the start and applying the allocation to multicamera production architecture: draw your signal chain, assign every function to a specific person, and explicitly record any uncovered role. If you will broadcast with a small floor-control team, review switching and direction: cut, mix, keyers and macros first, so one person is not assigned more than the switcher allows them to execute.