Keeping a Regional News Bulletin on Air: Rowan's Run Sheet

Rowan runs the evening bulletin at a small regional station, and when he first rang us the programme was working, which is exactly why nobody had touched the way it was organised. The running order lived in a shared document that three people edited, the gallery knew the cues because the same two operators had always been there, and a fault was handled by whoever happened to notice it first.

He did not ask for new equipment. He asked why a perfectly ordinary Tuesday could still produce a minute of dead air, and why the answer was usually that someone had been away from their desk. I visited the gallery on a bulletin night and sat at the back with a notepad, saying very little. Most of what I wrote down was about habits rather than hardware: who spoke to whom, and when.

The gallery had a good vision mixer, sound desk and intercom, and the crew were competent and calm. The trouble sat in the gaps between them. The run sheet showed story order and timings, but not which source each item came from, who owned the cue, or what the fallback was if a package failed to roll.

Two items in the middle of the bulletin routinely overran, and the producer absorbed the difference by trimming the sports slot live. Nobody had agreed that this was the plan; it had simply become the habit. When a graphics machine froze one evening, three people reached for different remedies at once. The incident passed, but it showed me that the team was relying on goodwill where it needed a written step.

• Cues recorded by story, not by source or owner
• Overruns absorbed informally rather than planned for
• No single place listing what to do when a feed drops

We rebuilt the run sheet with Rowan's producers across two sessions. Each line now carries the source, the person responsible for the cue, the planned duration and a marked point where an item can be cut without breaking the flow. The page reads top to bottom the way the gallery works, so the director no longer has to translate it in their head.

We kept the layout plain on purpose. It prints on a single sheet, it can be marked up with a pen, and a stand-in director can pick it up cold. The aim was never an elaborate document. It was a sheet that answers the three questions that come up mid-bulletin: what is next, who has it, and what do we do if it is not there.

Rowan was wary of rehearsals, because a station that goes live every evening has little spare time. So we kept it short. Twenty minutes before the first bulletin of the week, the crew run the opening, one package roll, one live link and the close, with a deliberate fault introduced by whoever is not directing that night.

The point is not to catch anyone out. It is to let each person practise the moment when something goes wrong while the stakes are low. Within a few weeks the gallery talk had changed. Calls became shorter and the same phrases were used each time. The director stopped repeating instructions, because the crew had heard them before and knew what they meant.

• Twenty minutes, once a week, before the first bulletin
• One planted fault, chosen by someone outside the chair
• A two-line note afterwards on what was learned

The last piece was the checklist, and it is the shortest document we wrote. It covers the faults the gallery had actually met: a frozen graphics machine, a lost remote link, a dead microphone on the desk and a late package. Each has a first action, a second action and a named person who makes the call.

It sits on a card above the vision mixer, not in a folder. Daniel, our senior broadcast engineer, checked each step against the real signal flow so that nothing on the card depends on a button that does not exist. Rowan told me the card gets used less than he expected, and he considers that the sign it is working: the team now knows the steps well enough that the card is mostly reassurance.

We went back after a few autumn weeks and watched another bulletin. The overruns were now planned, with the cut point agreed before the programme began. A remote link dropped during the second half, and the director moved to the fallback within seconds without a word of confusion. The viewer would not have noticed anything.

Rowan did not describe it as a transformation. He said the evenings felt quieter, and that the newest operator, who joined during that period, was running a position confidently well before he expected. That seems to me the honest measure of workflow planning: fewer surprises, and a crew that does not need to be rescued by its most experienced members.