Why workflow mistakes are quiet ones
Most failures at a festival, party or live-streamed event do not look like failures when they are made. They look like a reasonable shortcut taken on a Tuesday: a cable run left unlabelled, a schedule shared as a screenshot, a question about power postponed until load-in. The cost appears on the day, when the crew is tired, the audience is arriving and nobody has time to trace a fault back to its origin.
I have worked on events of every size, and the pattern holds from a small private party to a multi-day site. The mistakes below are not exotic. They are ordinary lapses in signal flow, scheduling and crew coordination, and each can be prevented with a short conversation at the right moment.
Treat this as a list to read before the planning meeting, not after the first rehearsal. A few minutes spent on each point is far cheaper than an hour spent fixing it live.
Mistake one: no written signal flow
The most common problem is that the signal path exists only in one person's head. Audio, video and communications are routed from memory, and when that person is at the other end of the site, nobody else can say where a feed comes from or where it goes. A fault then becomes a search rather than a repair.
A single page showing every source, every destination and every conversion between them solves most of this. It does not need to be elegant. It needs to be current, printed, and kept where the crew can reach it. When something changes during the day, the page changes too, with the time noted beside the edit.
For live-streamed events the page should also show where the programme feed leaves the building and what the fallback is if that link drops.
- Label both ends of every cable run
- Keep one printed copy at each control position
- Mark the fallback route for the stream feed
Mistake two: a schedule that ignores changeovers
Running orders are often written as if the performers simply appear. In reality each act needs a line check, a monitor adjustment, a lighting cue change and sometimes a different camera plan. When the schedule gives every changeover the same ten minutes regardless of what is moving, the day starts to slip by the second act and never recovers.
The better approach is to list what actually changes between each slot: backline, microphones, playback sources, lighting state, camera positions. Acts with heavy changes get more time, and acts with little can follow quickly. This also shows where an overrun can be absorbed and where it cannot.
Share the schedule with every department in the same format, and name one person who owns the master copy so that nobody works from an outdated version.
Mistake three: crew briefed in pieces
Crew coordination fails when information reaches people unevenly. The sound team knows the stage plot changed, but the lighting operator does not. The camera crew has the old start time. Each person is competent, yet the production behaves as though nobody has spoken to anybody.
A short briefing before doors, with every department present, is worth more than a dozen messages. It should cover the running order, who calls cues, how problems are reported and who decides when something must change. Keep it brief and write the main points on a board in the control area.
Agree the communication channels in advance too. If intercom is for cues only, say so, and give faults and logistics their own route.
- Name one person who calls the show
- Decide who can approve a change on the day
- Keep a written contact sheet for the whole crew
Mistake four: power and distribution left late
Power is rarely glamorous, so it is often settled last. Then the load-in reveals that the lighting, sound and streaming equipment all sit on one circuit, or that the nearest supply is a long way from the control position. Fixing this on the day means long cable runs, tape across walkways and a nervous crew.
Ask early what supply the venue provides, where it terminates and how much of it is shared with catering or other contractors. Plan the distribution on paper, keep audio and video equipment apart from noisy loads where possible, and leave room for the equipment nobody mentioned until the last week.
Check cable routes against audience and staff movement. A route that is tidy on the plan can be a hazard once people are using the space.
Mistake five: no rehearsal of the failure case
Most teams rehearse the show and nobody rehearses the problem. When a link drops or a console freezes, the crew improvises, and improvised fixes are slow. A short run-through of the two or three most likely faults changes this: who notices, who acts, what the audience sees in the meantime.
This does not need a full dress rehearsal. Walk through the stream failover, the loss of a radio channel and a late artist, and agree the response to each. Write the answers down in one place.
Afterwards, note what actually went wrong during the event and keep the note for next time. Over a season, that record becomes the most useful document the production owns.
- Test the backup stream path before doors open
- Keep spare cables and batteries at each position
None of these mistakes needs special equipment to fix. They need written plans, shared information and an honest look at what could go wrong. With autumn events moving indoors, where power and space are tighter, the same habits matter even more. Start with the signal page and the changeover list, and the rest of the workflow tends to follow.
