Five Live Event Workflow Mistakes and How to Avoid Them
Most problems on a live show start in the planning stage: unclear signal paths, comms gaps and vague crew roles. Here are five common workflow mistakes and the habits that prevent them.
1. Drawing the signal flow once and never revisiting it
The most frequent mistake I see in workflow reviews is a signal flow diagram that was drawn early in planning and then left alone while the show grew around it. A second camera position is added, an extra graphics feed appears, a remote contribution is requested, and nobody redraws the sheet. On the day, the crew works from a document that no longer matches the racks.
The fix is unglamorous. Treat the diagram as a living document with a named owner, and reissue it whenever a source, destination or conversion step changes. Every version should carry a date and a revision letter so that the vision mixer, the engineer and the audio operator can confirm they are looking at the same page.
When we review a production, the first thing we ask for is the current diagram, and the second is who last changed it. If those two answers do not match what is physically patched, we have found the first thing to correct.
- Give the diagram a single owner
- Reissue it after every change to sources or destinations
- Mark revisions with a letter and a date
2. Leaving communications as an afterthought
Intercom is often planned last, squeezed in once video and audio are settled. The result is familiar: too few belt packs, no agreed channel layout, and a producer shouting across the gallery because the director's talkback is busy. On a live show, a missing comms path costs more time than a missing monitor.
Plan communications alongside the video chain. Decide which channels exist, who is on each, and who can break into whom. A director, a technical director and a floor manager rarely need the same lines as camera operators and audio assistants, and mixing them leads to chatter that hides the instruction that matters.
Write the channel plan on one page and keep it near every position. Test every belt pack and every party line before the crew arrives, not while they are standing waiting for a call.
- Define channels before ordering equipment
- Separate director lines from general crew chatter
- Test every position before call time
3. Assigning roles by habit rather than by the show in front of you
Crews carry assumptions from previous productions. One engineer always looks after replay, another always handles the radio mics, and nobody asks whether this show suits that split. On a live event with an unusual format, those habits leave gaps: a graphics cue nobody owns, or a remote link that two people each assume the other is watching.
Write out each task the show needs, then attach a name to it, including the dull ones such as monitoring return feeds or logging timings. A role matrix on a single sheet, with a named backup for anything critical, takes an hour to produce and exposes most of the overlaps before they matter.
This is also the moment to ask what happens if someone is unavailable at short notice. If the answer is a pause while people look around, the plan is not finished.
- List every task before naming anyone
- Name a backup for each critical role
- Confirm who owns return feeds and logging
4. Skipping a proper line-up and rehearsal of failure
Rehearsals tend to run the show as it should go. They rarely run it as it might go wrong. When a feed drops or a console reboots for the first time during transmission, the crew is improvising with an audience, and the decisions made under that pressure are seldom the best ones.
Set aside part of the rehearsal to break things deliberately and agree the response. Lose a camera, drop a return feed, take out the primary talkback, and watch how the crew reacts. Note which actions were obvious and which needed discussion, then write the second group down as a short procedure.
These exercises need not be elaborate. Even ten minutes with a few agreed scenarios shows whether the workflow has a fallback path or only a hopeful assumption that nothing will fail.
- Rehearse at least three failure scenarios
- Record the agreed response in writing
- Check that backups are patched, not merely planned
5. Treating the handover as paperwork
The final common mistake sits at the end. When a show wraps, the notes that would help the next production, such as what was patched where, which settings were changed and what nearly went wrong, stay in people's heads and are gone by the following week. The next team then repeats the same discoveries.
Capture a short debrief while the details are fresh, ideally the same day or the next morning. Keep it factual: the final signal flow, the channel plan as used, a list of faults and workarounds, and any decisions that should change next time. One page is enough if it is accurate.
Over the years this habit has proved more valuable to crews than any piece of equipment. A workflow that is written down can be reviewed, improved and handed to someone new without losing the lessons of the last show.
- Hold a debrief within a day of the show
- File the as-used diagram and channel plan
- Record faults and the fixes that worked
None of these mistakes needs new equipment to fix. They come down to keeping documents current, planning communications early, naming responsibilities, rehearsing failure and writing things down afterwards. A workflow review looks for exactly these gaps, and in the quieter weeks of autumn, before the winter schedule fills up, it is a sensible moment to examine how your own live productions are organised.
Further reading
A Live Show Rehearsed on Paper: Marcus and the Talkback Problem
Marcus produces a regional live broadcast. Before his next show he asked us to review how signals, communications and crew roles fit together. This is what we found and changed.
A Monitoring Fix for a Regional Talk Show Gallery
Priya recounts how Marcus, a technical director at a regional talk show, tracked a recurring audio problem to the monitoring chain and what changed once the gallery listened differently.