What a production showflow should do that a spreadsheet cannot

Every production person I know has run a show off a spreadsheet, and most of them have run a good one. It is worth saying why before saying what it costs.

A spreadsheet is instantly available, infinitely flexible, and understood by everyone on the job without training. You can restructure it mid-meeting. You can print it. It has never once been down. Those are real advantages and no tool should pretend otherwise.

It fails at exactly one point: the moment the show goes live and the document needs to be a shared, moving state rather than a description of a plan.

A session is a row. A cue is not. Cue 47.1 is "VT roll — opener", it belongs to A/V, it is standby, it is hard-locked to a timecode, and it has a specific relationship to 47.0 and 48.0 either side of it.

You can represent that in columns, and people do. What you cannot do in columns is act on it: mark it standby for one department while another is already in go, or know that a change to 47.0 has consequences for 48.0 that someone must be told about.

FOH, LX, A/V, GFX and comms need the same running order and almost none of the same detail. A graphics operator does not need the lighting states. A lighting operator does not need the lower-third names.

In a spreadsheet, this becomes either one sheet everybody squints at or five tabs somebody maintains. Both are the same-source-of-truth problem at a smaller scale, and they fail the same way, faster, under more pressure.

This is the one that costs real minutes. A session overruns by six. In a spreadsheet, every subsequent time is now wrong, and someone has to decide whether to retype forty cells mid-show or hold the wrong numbers in their head for the rest of the day.

Durations plus dependencies mean the running order recalculates itself and shows you the consequence: what now lands late, what has slack to absorb it, and which hard-locked item — a broadcast window, a satellite hit, a scheduled break — is the wall you are heading for.

The deepest difference is that a spreadsheet describes the show and a showflow is in it.

When the caller marks 47.1 as go, that is not a note about what happened — it is the state, and every connected surface has it. The GFX operator sees it. The prompter advances. Nobody has to be told, which means nobody has to be told twice, which means comms is free for the things that genuinely need a human voice.

Speed of entry, mostly. The reason people reach for a spreadsheet under pressure is that typing into a grid is the fastest input method ever invented, and any tool that makes building a rundown slower than a spreadsheet will lose, correctly.

So: paste a block of rows in and have it resolve into cues. Keyboard-first. No modal between you and the next line. Earn the structure without charging for it at the point of entry.