Six Live Event Workflow Mistakes We See Planned Too Late
Hannah Doyle
6 min read
Most live event problems begin on paper, long before doors open. Hannah Doyle walks through six workflow mistakes common at festivals and televised events, and how a calmer plan avoids each one.
1. A run sheet written for the producer only
The most common fault I meet is a run sheet that makes perfect sense to the person who wrote it and to nobody else. It lists acts and times, but not what each department must do between them. The sound crew needs to know when a changeover begins, which microphones are live and who confirms the stage is clear. Vision needs to know which camera takes the first shot. If the sheet says only 'band two, 21:15', every department fills the gap with its own assumption.
A better sheet is written in layers. The top layer is the programme as the audience sees it. Beneath it sit cues for each department, with a named person against every cue. At the festivals and live shows we plan, we circulate a draft early and ask each head of department to mark what is missing. The corrections that come back are nearly always about handovers, not about the acts themselves.
- Give every cue a named owner, not a department
- Show changeover steps as separate lines
- Circulate a draft early and collect marked-up copies
2. Signal routing decided on the day
Signal routing is often treated as something the crew will sort out once the equipment arrives. By then the cable runs are fixed, the patch points are crowded and nobody has time to draw anything. Mid autumn events add damp ground and short daylight, which makes rework on site slower and less safe. A routing diagram drawn before load-in lets you spot a missing feed, a run that is too long or a single point where one failure silences two stages.
We draw routing as a simple map: sources on the left, destinations on the right, every tie line labelled with the same name used on the physical cable. That labelling matters more than the artwork. When a feed fails at night, a technician reading a torch-lit label should be able to find its twin on the diagram in seconds, without calling anyone.
- Draw routing before load-in, not after it
- Use identical names on the diagram and on the cable
- Look for single points of failure across stages
3. No plan for the audio and video handoff
Televised and streamed events fail in an odd place: the join between the sound desk and the broadcast feed. Front-of-house mixes are made for the room, and a stream needs something different, with the crowd mic balanced against the stage so the home viewer hears an event rather than a rehearsal. When nobody owns that join, the stream carries either a muddy copy of the room mix or a thin feed with no atmosphere at all.
Decide early who builds the broadcast mix, where it is taken from and how it is monitored. A dedicated feed from the desk, with its own headphone check at the vision end, avoids most arguments. I would rather give a small stream one extra person for the whole evening than ask a single engineer to serve two audiences from one fader bank.
4. Crew planning that ignores breaks and handovers
A crew rota is usually built around when equipment must be working, not around when people need to eat, rest or hand over. On a long festival day this produces a quiet failure: the most experienced engineer is covering both the busiest set and the one after it, and the mistakes arrive in the final hours when concentration drops. Nothing dramatic happens. Small errors simply stack up and a clean show begins to feel ragged.
Plan relief as carefully as you plan kit. Name who covers each position during a break, and make sure that person has actually seen the show file or the patch, not just heard about it. Where a role cannot be covered, say so in advance and adjust the programme instead. A fifteen-minute gap in the schedule is far cheaper than a tired mistake at peak audience.
- Name a cover for every position, not only the key ones
- Brief covers on the actual show file
- Build real gaps into the programme
5. Treating rehearsal as a formality
Rehearsal is often squeezed to a quick line check because the doors open soon and the artists arrive late. A line check proves that sound exists. It does not prove that a cue works, that a camera cut lands on time or that the person calling the show has the rhythm of the running order. Those things are learned by running a section the way it will actually happen, including the awkward transitions.
Even a short run of the first ten minutes and the hardest changeover is worth more than a long, quiet soundcheck. Ask the person calling the show to speak through the cues aloud, with every department listening on talkback. Gaps in the plan show up at once, and they cost minutes to fix at that point rather than embarrassment in front of an audience.
6. No agreed way to change the plan during the show
Live events change: an act overruns, a sound issue delays a set or weather moves an outdoor stage. The mistake is not that the plan changes, but that nobody has agreed who may change it. In that vacuum, three people give three instructions over three channels and the crew does the safest thing, which is to wait.
Agree a single voice for changes and a single channel for them. Everyone else raises concerns to that person rather than issuing orders. Write down the two or three likely disruptions, such as an overrun or a feed loss, and the first action for each. These short pages are rarely needed in full, but having them lets a crew stay calm and act together when something does go wrong.
- One person authorises changes, one channel carries them
- Write a first action for each likely disruption
Few of these mistakes need new equipment to fix. They need a plan that is written down, shared early and tested once before the audience arrives. If you are preparing a festival, party or televised event and want a second pair of eyes on the run sheet or the routing, send us the draft through the contact page and we will tell you where we would look first.