The rundown in plain words
A rundown is the running order of a live programme: a list, item by item, of everything that will go to air, in the order it will go there. Each line says what the item is, who is on camera, which sources are needed, how long it should last and what comes next. In a news bulletin that might be a studio introduction, a recorded report, a live link and a weather segment. In a live show it is the same idea with more moving parts.
People outside the gallery sometimes picture it as a script. It is closer to a map. The script is what the presenter says; the rundown is what the whole crew does. The director, vision mixer, sound operator, graphics operator and floor manager all read from it, and each takes different instructions from the same line. That shared reading is what makes a rundown valuable, and it is also why a badly written one causes trouble across the whole room.
What a good line contains
When I look at a rundown during a review, I start with the individual lines. A useful line is short enough to read at a glance while the programme is running, yet complete enough that nobody has to ask a question mid-air. It names the item clearly, gives a duration the whole gallery understands, and says how the item begins and ends. A cue such as a spoken out-line or a fixed visual is far safer than a vague instruction to go when ready.
Sound belongs on the line too, and this is where I most often find gaps. Which microphones are open, whether a pre-recorded package carries its own audio, whether a guest needs a talkback feed: if the rundown is silent on these, the sound desk is guessing. A line that tells the audio engineer what to expect, and when, removes the guesswork. The same applies to camera positions and graphics, each of which should be traceable on the line itself.
- Item name and who is on screen
- Planned duration and a hard or soft end
- Sources: cameras, packages, remote feeds
- Microphones and audio sources expected
- The exact cue that moves to the next item
Timings: front, back and the gap between
Two timing terms cause more confusion than any others. Front timing is how long a programme has run so far; back timing is how long remains until it must end. A gallery that watches only the front timing discovers too late that it is running over. Good rundowns carry both, so the director can see at any moment whether the programme is ahead of or behind where it should be, and can ask for a shorter item before a problem becomes visible to the audience.
The gap between items matters just as much as the items. A forty-second link that really takes fifty seconds, repeated across a dozen items, quietly eats several minutes. During a review I compare planned durations with what the crew actually achieved over a few rehearsals or broadcasts, and the pattern is usually plain: certain kinds of item always overrun. Writing realistic durations into the rundown is a small change that steadies the whole programme.
How crew communication reads the rundown
A rundown only works if the people using it hear the same thing at the same moment. In the gallery that happens over talkback: the director calls the next shot, the producer passes on changes, the floor manager relays them to the studio. A written review looks at who speaks on which channel, how often, and whether instructions are brief and consistent. Long explanations on open talkback are a common source of missed cues, because the person who needs the information is busy listening to something else.
I also look at how late changes travel. Live programmes change right up to the moment they start, and sometimes after. If a revised line reaches the director but not the sound desk, the rundown has become two different documents. A sensible arrangement gives one person responsibility for the master copy and agrees how an amendment is announced. It is not complicated, but it has to be decided before the programme, not during it.
What a written workflow review covers
A Live Show Workflow Review takes the rundown as its starting point and works outwards. We read the document, then look at the gallery layout, the way the crew communicates, and the points where an item hands over to the next. The result is written down, so that producers and studio managers can read it at their own pace and share it with the crew, rather than relying on a conversation that is half remembered a week later.
The review is practical rather than theoretical. Each observation is paired with a change the crew can make with the equipment and people they already have: a reworded cue, a different order of calls on talkback, a clearer way of marking the timing on the rundown. Not every finding is a problem. Where something works well, the review says so, because a team should know which habits to protect.
Questions worth asking of your own rundown
You do not need a consultant to begin. Print the most recent rundown and read it as though you were the sound operator who has never seen the programme. Can you tell what you need to do, and when? Then read it again as the floor manager. If either reading leaves you with questions, the crew has been answering those questions out loud during every show, and that spoken workload is the first thing to remove.
Next, compare the planned durations with the real ones from the last programme. Mark the items that overran and ask why. The answer is often a missing cue, an unclear hand-over or an item that was always longer than anyone admitted. These are small findings, and they are exactly the kind that make a gallery calmer once they are written into the document that everyone follows.
A rundown is more than a list of items: it is the shared agreement between everyone in the gallery and the studio. When its lines are clear, its timings honest and its changes handled by one person, a live programme feels calmer for crew and viewers alike. A written review starts there because so much else depends on it, and the first step costs nothing but a printed copy and a careful read.