Your rundown should hold durations, not clock times
The most common thing wrong with a run of show is that it is written in clock times. It looks precise. It is the reason your afternoon falls apart.
Open almost any rundown and the first column is a time: 09:00, 09:15, 09:40. It reads like precision. What it actually encodes is a prediction that every single item before this one went exactly to plan, and that prediction is wrong by 09:20.
The moment your keynote runs four minutes long, every number below it is a lie. Not approximately right, actually wrong, and now three different people are doing mental arithmetic against a sheet that disagrees with the wall.
Durations compose, clock times do not
A duration says "this takes 35 minutes". That statement stays true whether you started on time, ten minutes late, or in a different timezone. Clock times are derived data: give a system the start and the lengths and it can compute every time in the sheet, continuously, as reality moves.
Write the source data, not the derived data. This is the same instinct that stops you from storing someone age in a database when you could store their date of birth.
It is also what makes a rundown reusable
If you run a 9:00 and an 11:00 service, a clock-time sheet forces you to maintain two documents that are identical except for one column. They drift. Someone fixes the video length in the first and not the second, and the second service overruns for a reason nobody can explain.
In durations it is one running order that you start twice. Fix something once and both services get it. The same property is what makes a template worth downloading at all: a rundown full of 09:00 belongs to whoever wrote it, while a rundown full of lengths belongs to anyone.
The two places you genuinely need a real time
Durations are the default, not a religion. Two kinds of item are pinned to the wall clock and should stay pinned:
- Anything with an external commitment. A livestream that goes out at 19:00, a satellite window, a broadcast junction, a venue curfew. The world does not care that you started late.
- Anything downstream of a hard stop. Bar closing, union overtime, the coach leaving. Build backwards from these rather than forwards from the start.
A good console lets you anchor individual cues to a fixed time and let everything else float around them. That is the right shape: durations by default, anchors where the outside world is involved.
What this looks like in practice
- Author every item as a length. Let the start time be an input you supply on the day.
- Anchor only the cues with an external commitment, and mark them clearly so nobody quietly moves one.
- Put the slack in named buffer cues, not spread invisibly across every item. Padding hidden inside each talk teaches speakers that your times are negotiable.
- Keep the planned length next to the actual length after the show. That is the only way you find out which items are honestly timed.
A rundown in clock times tells you what you hoped would happen. A rundown in durations tells you what you are actually asking people to do.
None of this requires software. You can do it in a spreadsheet with a running total, and plenty of very good shows are run exactly that way. What software buys you is that the recalculation happens continuously, on every screen, without anyone touching it while the show is moving.