Before the Dark Evenings: Steadying Your Live Workflow This Autumn

Why these weeks suit a workflow review

Mid autumn is a quiet moment that most studios do not recognise as quiet. The summer schedule has ended, the winter run of evening news, election-style specials and seasonal live shows has not yet filled the calendar, and the gallery team is usually back at full strength. That gap is the cheapest time to look hard at how a show is actually run, because nobody is asking you to change a procedure the night before transmission.

A Production Workflow Review is a written look at rundowns, cueing, talkback and fallback procedures. It is not an equipment survey and it does not require new kit. It asks a plainer question: when something goes slightly wrong at ten minutes to air, does the team know who says what, and in what order? Doing that work now means the answers are written down before the clocks go back and the evenings get long.

Start with the rundown you really use

Most studios have two rundowns: the tidy one that is circulated, and the marked-up one that the director and the producer are actually reading from. During a review I ask to see the second one. The scribbled timings, the arrows moving an item up, the circled cue words are where the real habits of the programme live, and they tell me more than a template ever will.

Compare the two honestly. If the same correction is made by hand every week, the template is wrong and should change. If items are regularly reordered during transmission, the running order needs a clearer rule about what can move and what cannot. A rundown that reflects how the team works is easier to follow under pressure, and it makes handovers between presenters and directors far less fragile.

• Collect last month's marked-up rundowns, not the clean versions
• Note every item that moved or was dropped on the night
• Agree which items are fixed and which may float

Cueing: say less, and say it the same way

Cueing language drifts. One director says stand by camera two, another says two ready, a guest producer says nothing and points. On a calm evening this causes no harm. On a night with a late guest, a failed link or a presenter who is ill at ease, every inconsistency costs a second of hesitation, and those seconds show on air.

In the review I listen to a recording of a recent show and mark each cue in the order it was spoken. We then agree a short, fixed vocabulary for the common moments: standing by, going to, rolling, and cutting. Shorter phrases leave room on the talkback channel for the one thing that is new. The aim is not formality for its own sake but a gallery where nobody has to translate.

• Fix one phrase for each common cue and drop the alternatives
• Keep talkback free for exceptions by saying less routine

Talkback: who can speak, and when

Talkback is often set up once and never revisited. Over time extra people are added to the channel, a floor manager keeps a button held down, and a producer chats through a live link. The result is a channel that is technically working but practically crowded, and the director loses the clean line they rely on.

I look at who is on which channel and what each person genuinely needs to hear. A floor manager needs the director's instructions to the floor; they rarely need the audio engineer's comments about a microphone. Separating these where the intercom allows it, and agreeing a short rule for interrupting, is a procedural change before it is a technical one. Often the fix is a one-page note pinned at the desk, not a rewiring job.

• Map each role to the channels it must hear
• Agree a clear rule for who may interrupt during a live link

Fallback procedures written for a tired team

Every studio has a fallback plan: what happens if a camera fails, a remote guest drops, or the graphics machine freezes. In many places that plan exists only in the head of one experienced person. When that person is on leave, or simply tired at the end of a long week, the plan is not available.

The written part of the review sets out each likely failure in plain steps, with the first action given in a single line and the decision-maker named by role rather than by person. Winter evenings also bring more weather-related problems with remote contributors and travel, so I ask teams to rehearse two or three of these in a quiet slot. A rehearsed fallback usually takes seconds; an improvised one takes much longer.

• Name the decision-maker by role for each failure
• Rehearse two or three fallbacks while the schedule is light

What you receive and how to prepare

The result is a written report, not a presentation. It records what I observed, what the team already does well, and a short list of changes ordered by how much difference they make for the effort involved. You can hand it to a new director or studio manager and they will understand how the gallery is meant to run.

To prepare, gather a few recent rundowns with their handwritten notes, a recording of one typical transmission if you can share it, and your current fallback notes, however informal. Tell me which evenings are most demanding in the coming months. The review then concentrates on those shows instead of spreading attention evenly over the whole schedule.