A Run Sheet Rewrite for a Regional Evening Programme

The call from Marcus

Marcus produces a weekly evening programme from a small regional studio. When he first wrote to us, his request was modest: could someone tidy up the run sheet his gallery used on transmission nights. He explained that the document had grown over several seasons, with each new director and vision mixer adding a line here and a correction there.

In our first conversation he described the symptoms rather than the cause. New freelancers asked the same questions every week. The floor manager kept a second, private copy with her own abbreviations. Two people on the crew read the same cue and understood different things.

I asked him to send what the crew actually held in their hands on a transmission night, not the master file. Three printed versions arrived, each marked up in a different pen. That told me more than any description could have done.

Reading the documents the way the crew does

Before writing anything, I read the three printed copies side by side, and I read them in the order a crew member would on the night: the pre-show checks first, then the cue list, then the notes at the back. The pen marks showed where people had stopped trusting the page and begun to improvise.

Most of the corrections clustered around the opening ninety seconds of the programme and around the handover to the weather segment. Those were the places where the sheet used shorthand that only its original author understood. One line simply read 'go to B', and nobody could say with certainty whether B meant a camera, a source on the mixer or a caption layer.

Marcus agreed that the reading had to be done on his crew's terms. So we arranged a short video call with the director and the floor manager, and I asked each of them to talk me through a cue aloud while I followed on my copy.

• Which lines had been crossed out or rewritten by hand
• Where abbreviations were explained nowhere on the page
• Where two documents gave different instructions for one cue

What we changed in the run sheet

The rewrite began with the vocabulary. We agreed a short list of terms, with one meaning each, and used it everywhere: a camera was always a camera with its number, a source was always named as it appears on the mixer, and graphics were referred to by the label the graphics operator sees. The list went on the first page so a freelancer could read it in two minutes.

Next we restructured the cue list into columns the crew could scan under studio lighting. Timing sat on the left, the action in plain words in the middle, and the person responsible on the right. Anything that depended on a condition, such as a late guest or an overrunning item, was written as an if-then line rather than buried in a note.

We also removed material that belonged elsewhere. Equipment settings that changed once a year moved into the operating notes, so the run sheet only held what changed from one transmission to the next.

• One agreed term for each camera, source and graphic
• Timing, action and responsibility in separate columns
• Conditional cues written as explicit if-then lines

Operating notes for the people who are not there

The second document was harder, because it had to serve a reader who could not ask a question. Marcus wanted a set of operating notes that a freelancer could pick up on arrival and use without a briefing. I wrote it as a sequence: arriving at the gallery, powering up, checking communications, then the routine before going to air.

I kept each step to a single action and put the reason in a short sentence beside it only where the reason would prevent a mistake. If an intercom channel must be checked before tallies are tested, the notes say so and say why, because otherwise a hurried crew will reverse the order.

Priya from our own team read the audio sections and corrected two details about talkback routing, and I verified the remaining steps against Marcus's own notes. Nothing went into the final text that the crew could not confirm in the room itself.

Trying it on a live night

Marcus did not simply switch to the new documents. He printed them for one transmission and asked his director to run the old and new sheets in parallel, marking anywhere the two disagreed. That small trial turned up four places where our wording was still ambiguous, and we corrected them the next morning.

The following week the new run sheet went into use on its own. Marcus told me afterwards that the floor manager stopped carrying her private copy and that a freelancer who joined that week asked only one question during the whole evening, about parking.

I do not read too much into one programme. A document can be clear and still be ignored if nobody maintains it, which is why we agreed who edits it and when, and left the master file with a single named owner.

What stays with me from this one

The case reminded me that documentation fails quietly. Nobody complains about a vague run sheet; the crew simply compensate, and the compensation becomes habit. The first sign of trouble is usually a private copy, a pen mark or a question asked every single week.

If you are weighing up whether your own paperwork needs attention, look at what people write on it and what they ask aloud. Those two things tell you where the page has stopped doing its job.

Writing for a crew means writing for a tired person under bright lights with a few seconds to spare. Marcus's programme still uses the structure we settled on, and he now revises it himself after each series.

• Look for private copies of shared documents
• Count the questions repeated every week
• Name one owner for each master file