Runbook or Checklist: Which Suits Your Live Show Better
A plain comparison of full written runbooks and short cue checklists for live production crews, with a recommendation on which to start with and when to add the other.
Two ways to write down a live show
When a crew asks me to help them repeat a live show reliably, the first question is usually what form the paperwork should take. In practice there are two real options. The first is a full runbook: a narrative document that describes the show from power-up to wrap, with roles, signal paths, fallbacks and the reasoning behind each decision. The second is a set of checklists: short, numbered lists that a person ticks off while the show is running or being prepared.
Both are legitimate, and I have seen each work well and fail badly. The difference lies in who reads them, when they read them and how much attention they have to spare. A runbook is read calmly, usually before the day. A checklist is read under pressure, often with one eye on a monitor and a hand on a fader.
This article compares the two honestly, says where each earns its place, and ends with a recommendation for small and mid-sized teams who have to choose where to begin.
What a runbook does well
A runbook carries context. It can explain why the talkback group is split between the floor and the gallery, why the backup feed is patched to a particular input, or why the graphics operator waits for a verbal confirmation before taking a lower third. That reasoning is what lets a new crew member make a sensible decision when something unexpected happens, instead of following a step that no longer fits.
It also holds the whole picture in one place: the schedule, the cast of roles, the equipment list, the contact numbers for the venue and the agreed fallbacks. When a show returns after a gap of several months, the runbook is what brings the team back to the same starting point without relying on one person's memory.
The cost is length and upkeep. A good runbook for a single studio show can run to a dozen pages, and every change to the rig means an edit somewhere inside it.
- Best for onboarding new crew and handing a show to another team
- Records the reasons behind decisions, not only the steps
- Gives producers and engineers one shared reference
- Needs a named owner or it drifts out of date
What a checklist does well
A checklist is built for the moment of use. It strips a task down to the actions that must happen, in the order they must happen, and nothing else. Line check before doors, camera shading before rehearsal, the closing sequence after transmission: each of these is a short list that a tired operator can follow without thinking about anything beyond the next line.
Checklists catch the errors that experience tends to hide. Experienced crews skip steps precisely because they have done them a hundred times, and the one time the step matters is the one time it was skipped. A list that is physically present at the desk makes that omission visible.
The weakness is that a list says nothing about why. When a checklist item no longer applies, a junior operator may either follow it blindly or drop it without understanding the consequence.
- Best for repeated, time-critical actions at the desk
- Short enough to use during rehearsal and transmission
- Easy to revise one line at a time
- Gives no reasoning, so it needs a runbook behind it
Where each one breaks down
The typical runbook failure is that nobody opens it on the day. It is too long to scan, so the crew falls back on habit, and the document becomes something that was written for a handover and then forgotten. The typical checklist failure is the opposite: it grows. Every incident adds a line, nobody removes one, and eventually a twenty-line list becomes sixty lines that people tick without reading.
Both failures share a cause, which is the absence of an owner and a review habit. A document that is never revised after a real show slowly describes a show that no longer exists. I would rather see a short, accurate pair of documents than a thorough set that is six months behind the rig.
One practical rule helps. If a step is needed at the desk in the middle of a show, it belongs on a checklist. If it is needed to understand or plan the show, it belongs in the runbook.
Our recommendation for small teams
If a crew can only produce one document this season, I would start with the checklists, and keep them to a single page per phase: setup, line check, transmission and wrap. They are quick to write, they pay back at the very next show, and they expose the gaps in what the team actually does. Writing them is itself a useful exercise, because people discover that two operators have been doing the same step differently.
Once the checklists have survived two or three real shows, build the runbook around them. It can be shorter than you expect: roles, signal flow, fallbacks, contacts and the reasons for the choices the checklists assume. At that point the two documents support each other, with the checklist as the working tool and the runbook as the explanation behind it.
Teams with frequent crew changes or several venues may reverse this order, since a runbook carries the most value when people arrive without any background.
- Start with one-page checklists per phase of the show
- Add a runbook after two or three live shows of testing
- Review both after every show, while the faults are fresh
- Name one person who owns each document
Putting it into practice this autumn
The darker months bring more studio and event work, and crews that were improvising through the summer often find themselves repeating the same show weekly. That is a good moment to write things down, because the pattern is stable enough to describe and the pressure to change it has eased.
A sensible first step is to sit with the crew after the next transmission and list what each person actually did, in order. Do not copy an old document or a template from another team. Record what happened, then trim it into a checklist. Keep the original notes, because they become the first draft of the runbook.
If you want help with either document, this is the kind of work our documentation service covers, and we write for the people who will use the pages rather than for the file they sit in.
Neither format is better in every case. Checklists protect the show while it is running, and runbooks protect it between shows and across changes of crew. For most small teams the order matters more than the choice: begin with short checklists, test them against real transmissions, then write the runbook that explains them. Keep both short, give each an owner, and revise them after every show so they describe the work your crew really does.
Get in touch
- Phone
- 01522 390417
- [email protected]