The first mistake I see is a running order written for one audience only. A festival producer builds a timeline of acts, the broadcast side builds a separate one for cameras and feeds, and nobody lays the two over each other until the site build is already under way. The result is a changeover that looks generous on one sheet and impossible on the other.
A workable schedule has layers: the stage timeline, the load-in and line-check windows, the broadcast cues and the crew breaks. Each layer is owned by a named person, and all of them sit on one page that everybody has seen before the first truck arrives.
When I review a plan, I read the changeovers first. That is where a schedule is honest about how much work the crew is really being asked to do in the time given.
If two documents disagree, the shorter timing usually wins on the day, so settle the difference on paper, not at the stage barrier.
- Keep one master timeline with layers for stage, broadcast and crew
- Name an owner for every layer
- Read the changeover windows before anything else
Signal routing is often described in a sentence: audio goes to the truck, video goes to the gallery. That sentence hides dozens of decisions about splits, returns, clocking, talkback and who supplies which cable run. When those decisions are left until the build, they get made by whoever is nearest the patch bay, and they are rarely written down.
A routing plan does not need to be elaborate. It needs every source and destination listed, every split point identified, and the owner of each connection stated. For sound, that includes the front of house feed, the monitor world and the broadcast mix, because they have different needs and should never quietly share one send.
Write the plan so that a crew member who was not in the planning meeting could patch from it alone. If they cannot, it is not finished yet.
I also ask for a simple marked-up copy kept at the patch point. Changes made during the day go on that copy, so the next shift inherits the real state of the system.
- List every source, destination and split point
- Give broadcast audio its own dedicated feed
- Keep a marked-up copy at the patch point
Cable runs and power are the least glamorous part of a workflow and the cause of more delays than any piece of equipment. A common error is measuring distances on a site plan and forgetting the route a cable must actually take around barriers, crowd paths and vehicle access.
Power is similar. Teams add up the equipment they know about and forget the small loads: monitors in the gallery, talkback, charging for radios, the catering of the crew area. A realistic power plan is built from a full equipment list with a margin, and it says what happens if a distribution point fails.
Walk the route with the plan in your hand before the build day if you can. Cables are cheap to reroute on paper and expensive to reroute with a crowd on site.
Where cables cross a walkway, decide the protection method in advance, so that safety and audio quality are both considered by the same person.
- Measure cable routes, not straight-line distances
- Count small loads as well as the main equipment
- Decide how crossings are protected before the build
A crew plan that lists names against positions is only half a plan. Live work runs long, and people who have been awake since early morning make slower and less careful decisions by the evening. I have seen a technically sound system undermined by a tired operator at the end of a sixteen-hour day.
Build breaks into the plan, and name who covers each position while its operator is away. Handovers need a few minutes of overlap with a short written note: what is patched, what is muted, what is waiting to be fixed. That note costs very little and saves a great deal of confusion.
For broadcasts, make sure the people on talkback know who to call for each fault. A fault reported to the wrong person loses minutes that a live show does not have.
Rotas are easier to keep honest when the operations lead checks them against the schedule layers, not against a list of names alone.
- Plan breaks and named cover for every position
- Use short written handover notes
- Publish a fault contact list on talkback
Most rehearsals concentrate on the show: the acts, the cues, the cameras. The parts that fail are usually elsewhere: the switch from one stage feed to another, the recovery after a lost link, the restart of a recorder. These are rarely tried before they are needed.
Choose a small number of failure cases and run them deliberately during the line-check window. Pull a cable, drop a feed, and see how long it takes the crew to find and fix it. The time it takes is useful information, and the discussion afterwards usually changes the plan for the better.
Rehearsal should also include the quiet moments, such as the start of the broadcast, when many sources must come up in the right order and everyone is watching.
Keep the findings brief and put them into the master document. A lesson learned at rehearsal that nobody records will be learned again in front of an audience.
- Rehearse a few chosen failure cases
- Time how long each recovery takes
- Record findings in the master document
The last mistake is treating the workflow plan as a pre-event paper that has done its job once the first act is on. During a long day, small changes pile up: a late act, a swapped slot, an extra feed requested by a guest. If the plan is not updated, the crew works from memory, and memory differs from person to person.
Assign one person to hold the current version and to approve changes. Everyone else sends requests to them, and they confirm back with the affected positions. It sounds formal, but on a busy day it is the thing that keeps four departments from acting on four different versions.
After the event, a short review with the same document in hand shows where the plan held and where it did not. That review is where next year's plan really starts, and it is worth the hour it takes.
None of this needs special tools. A shared sheet and a clear owner are enough, provided people actually use them.
- Name one keeper of the current plan
- Route all change requests through them
- Hold a short review afterwards
Most of these mistakes share a cause: decisions that were postponed until someone was under pressure. Putting the schedule on one page, writing the routing down, walking the cable runs, protecting crew rest and rehearsing failures all move those decisions to a calmer moment. None of it needs expensive equipment, only time set aside early and one person willing to keep the plan honest through the day.
