Live Event Workflow Planning: Mistakes We See and How to Avoid Them
Most trouble on a live broadcast starts weeks earlier, in the schedule and the signal diagram. Tom Fletcher goes through the planning mistakes he meets most often and how crews can sidestep them.
Why live workflows fail before the doors open
When a live broadcast goes wrong, the cause is rarely the equipment on the day. It is usually a decision that was left open during planning: who calls the cues, which feed goes to which monitor, what happens if a link drops. I have written production schedules and signal flow plans for live events for many years, and the pattern repeats. Crews are capable, kit is reliable, yet small gaps in the plan turn into long minutes in the gallery.
This article is the third in our look at live event workflow planning, and it is deliberately about errors rather than method. Some will sound obvious written down. They are still the ones we find on paper when we are asked to review a plan a few days before an event.
In mid autumn the calendar fills with conferences, awards evenings and regional broadcasts, and plans get written quickly. Speed is where most of these mistakes creep in, so it is a fair moment to go through them one at a time.
None of what follows needs new equipment. Each fix is a conversation, a page of notes or an hour spent checking something against the real venue.
Mistake one: a schedule that only the producer understands
A production schedule is often written by one person and read by the same person. It lists times, but not who is responsible at each point, so on the day the crew keeps asking the producer what comes next. That makes the producer the bottleneck at exactly the moment they should be watching the show.
A better schedule is written for the person with the least context. Each line says what happens, who does it, what must already be in place, and what the next line depends on. Camera operators, audio, graphics and the floor manager should each be able to find their own thread without asking.
I also ask for a version that is readable at a glance in poor light: large type, one page per segment, no abbreviations that only the author knows. A plan nobody can read in the gallery is not a plan, however carefully it was assembled in the office.
- Name an owner for every line, not just a time
- Say what each step depends on
- Print a version legible in a dim gallery
Mistake two: signal flow drawn from memory
Signal flow diagrams are frequently sketched from how the last event was set up. The result looks tidy but hides assumptions: that the same router is available, that the same number of returns exists, that the venue's cable run reaches where the last venue's did.
Draw the diagram from the actual brief and the actual site visit. Trace each source from its origin to every place it must appear: vision mixer, monitors, recording, any outgoing feed. Mark connector types and cable lengths where they matter. When a line on the diagram has no stated format or destination, treat that as a question to answer, not a detail to settle on site.
Keep the diagram and the schedule consistent with each other. If the schedule introduces a remote guest at a certain point, the diagram must show how that guest arrives, and what the crew does if the link is poor. Mismatches between the two documents are one of the most common things we correct.
Mistake three: no plan for the failure you can predict
Every live event has a short list of things that are likely to fail: a wireless microphone, a network link, a laptop playing back graphics. Plans often assume these will work, then improvise when they do not.
Agree the fallback before the event, and write it beside the item it protects. If a presenter's radio microphone fails, who hands over a spare, and does the audio operator know which channel to open? If a playback source freezes, is there a second source ready, and who decides to switch?
The aim is not to plan for every possibility. It is to remove hesitation from the handful of problems that are genuinely probable. A crew that has heard the fallback said aloud once will act faster than one reading it for the first time under pressure.
- List the three likeliest failures for this event
- Write the fallback next to the item it covers
- Say aloud who makes the call to switch
Mistake four: rehearsal treated as a formality
A rehearsal that skims through the running order proves very little. Cues are not called in full, transitions are talked about instead of performed, and the crew leaves believing the show is ready.
Use rehearsal time to test the parts most likely to go wrong, not the parts that are easy. Run the tightest changeover twice. Check the segment with the most sources. Make the person who calls the show practise the exact words they will use, so the camera operators and vision mixer hear the same language they will hear live.
Where time is short, shorten the rehearsal by skipping the straightforward segments, not by running everything lightly. Leave a few minutes at the end to note what changed, and update the schedule and diagram straight away so the next person to read them sees the real version.
Mistake five: communication left to chance
Crew coordination is the least visible part of a workflow and the most often under-planned. Talkback channels get assigned on the day, nobody confirms who is on which, and half the team cannot hear the person calling shots.
Decide the talkback arrangement in advance and put it on paper: which groups share a channel, who can speak to whom, and who has the authority to interrupt. Agree short, fixed phrases for standby, go and hold, and avoid casual wording that can be misheard over noise.
Finally, confirm arrival and call times with every department, and make sure someone owns the question of who is still missing. A late sound assistant or an absent floor manager is a scheduling problem long before it becomes a technical one, and it is far cheaper to find out the day before.
- Assign talkback groups before arrival
- Use fixed phrases for standby, go and hold
- Confirm call times with every department
Good live workflow planning is mostly careful reading: of the schedule, the diagram, the venue and the people involved. The mistakes above are ordinary and easy to fix once they are noticed. If you would like a second pair of eyes on a plan before an event, the contact page is the place to start, and we will tell you plainly what we see.