Two Ways to Plan a Live Broadcast Event: Run Sheet or Signal Map First
Should a live event begin with the schedule or with the signal flow diagram? We compare both starting points for live event workflow planning and say which one we recommend, and why.
The question behind the two options
Every live broadcast event reaches a point where someone has to decide what gets planned first. In our work on live event workflow planning, two starting points come up again and again. One team opens with the production schedule: a run sheet that fixes who arrives when, when each segment goes to air and where the gaps fall. Another team opens with the signal flow diagram: a drawing of every camera, microphone, switcher and router and the paths between them.
Neither approach is careless. Both produce the paperwork a crew needs. The difference is which document shapes the other, and that decides where problems surface. A schedule written first tends to hide technical limits until rehearsal. A signal map drawn first tends to hide human limits, such as a crew that cannot be in two places at once.
I am a lighting designer, so I come to this from the side of the rig, but I see the same pattern in every department. Lighting needs power, positions and time on the stage. Audio needs cable runs and quiet. Cameras need sight lines. The order of planning decides whether those needs collide on paper or on the day.
Option one: starting from the run sheet
A run sheet first has real strengths. It forces the producer to say what the event actually is: how many segments, how long each runs, where the breaks sit and who speaks. Everyone from the director to the runner can read it, and it gives the venue a clear picture of load-in and load-out. For a single-room event with a fixed crew and familiar kit, it is often enough to get going.
The weakness is that a schedule describes intent, not capacity. A line reading 'move to second stage, 4 minutes' looks harmless until nobody has checked whether the camera feed from that stage has a route back to the gallery. Changeovers are the usual casualty. Lighting presets, radio microphone swaps and camera repositioning all take longer than the time a schedule writer imagines.
When we are handed a finished run sheet late in the process, we read it line by line and ask one question of each transition: what has to physically change, and who does it. Often the answer shows that two people are needed in the same place, or that a signal has no path. Those are fixable, but fixing them after the schedule is circulated means reissuing it.
- Strong for: single-room events with known kit and a stable crew
- Weak at: exposing signal routes, power limits and changeover effort
Option two: starting from the signal flow diagram
A signal map first begins with equipment and connections. You list the sources, decide where they land, count the returns, mark the intercom, the clock feed and the talkback, and note where each link could fail. The result is a document engineers trust, because it answers hard questions: how many camera paths does the gallery really receive, where is the single point of failure, and what happens if one fibre or cable run is lost.
This route suits events with several rooms, remote contributions, or a venue where the infrastructure is unfamiliar. It also gives lighting and audio a fixed reference for cable routes and positions before anyone commits to a timetable.
Its weakness is the mirror image of the first option. A beautiful diagram says nothing about people. It will not tell you that your only vision mixer operator also needs to cue the graphics, or that the stage manager cannot be reached on the channel you assigned. Teams who start here sometimes arrive at rehearsal with flawless connections and a schedule that does not fit the hours they have.
- Strong for: multi-room, remote or unfamiliar-venue events
- Weak at: crew load, handover timing and the order of the day
Our recommendation: map first, then schedule against it
For most live broadcast events, we recommend drawing the signal flow first and building the schedule on top of it. The reason is simple: the diagram sets the limits, and the schedule has to live inside them. Once you know how many sources reach the gallery, which cameras share a route and where the power comes from, writing the run sheet becomes a matter of fitting segments into a known system rather than discovering the system through the segments.
In practice this does not mean waiting for a finished diagram. A rough first version, drawn in an afternoon, is enough to expose the large problems. Then the schedule is drafted, and each changeover is checked against the map. Where they disagree, one of them changes. That back and forth is cheap on paper and expensive in a venue.
I would only reverse this for a small, single-room event with a crew that has worked together before and kit everyone knows. There the run sheet carries the risk, and a full diagram adds little. Anything with more than one location, any remote feed or any new venue should start from the map.
- Draw a rough signal map first, even if it is one page
- Draft the run sheet against that map, not beside it
- Check every changeover for who moves what, and how long it takes
- Keep one version of each document and date every change
What each choice means for lighting, sound and cameras
Seen from the departments, the recommendation has practical effects. For lighting, a signal map that includes data lines for dimmers and control desks lets the rig be planned alongside power distribution instead of squeezed in afterwards. I can see early whether the control position has a sensible run to the stage and whether camera positions will fight with lighting stands.
For sound, the map shows microphone counts, split feeds and where the audio chain meets the broadcast mix. Priya on our team often finds that a schedule with several radio microphone changes has more simultaneous frequencies than the venue can comfortably carry, and that is far easier to resolve before the timetable is agreed.
For cameras, the diagram shows which positions return to the gallery and by what path, which tells the director what is realistic. The schedule then describes what the audience sees, rather than promising shots the infrastructure cannot deliver. Each department gets its constraints early, while changes still cost an eraser rather than a rehearsal hour.
Putting it to work in the weeks before an event
At this time of year many producers are planning winter events and end-of-year broadcasts, often in venues they have not used since last season. That is exactly where the map-first habit pays off, because the building will have changed in small ways: a different patch panel, a moved power point, a new network switch. Walk the site with the diagram in hand and mark what differs.
Then share both documents together. A crew that receives the run sheet and the signal map as a pair understands why the schedule looks the way it does, and tends to raise problems earlier. Keep a short list of open questions on the front page of each, with a name beside every item.
If you would like a second pair of eyes on a plan, our live event workflow planning covers production schedules, signal flow diagrams and crew coordination, and we are happy to work from whichever document you already have.
Both starting points produce usable plans, and the better one depends on the event. A single room with a familiar crew can begin from the run sheet. Anything with several locations, remote contributions or an unfamiliar venue is safer when the signal flow comes first and the schedule is written to fit it. Draw the map roughly, test every changeover against it, and keep the two documents in step. The time you spend reconciling them on paper is time you do not lose on the day.