glitaraContact
← Guides
Case story

A Saturday Studio Show That Kept Drifting: Marcus and the Workflow Review

Marcus runs a small live studio show and could not find why it fell apart each week. A written workflow review gave him a short, ordered list of fixes. This is how it went.

Daniel Okafor

5 min read

A show that never ran the same way twice

Marcus produces a weekly live programme from a modest studio, with a crew of six and one gallery. When he first wrote to us, he did not ask for new equipment or a redesign. He asked a plainer question: why does the show feel fine in rehearsal and shaky on air, and why does it go wrong in a different place every week?

I was the one who read his notes first. He described late graphics, a presenter who sometimes could not hear the producer, and a recorded insert that played with a faint lip-sync slip. Each problem sounded separate. None of them sounded expensive. That combination usually points to a process problem rather than a hardware one, and it is exactly what a written review is built to find.

We agreed a scope by email: the live chain from the cameras to the output, the recorded inserts, and the way the crew handed work to one another.

What we asked to see before writing anything

A review starts with material, not opinions. Marcus sent a signal diagram that he had drawn himself, the running order from the last three shows, and a list of who sits where in the gallery. He also sent a short voice note describing what the crew say goes wrong, in their own words, which turned out to be the most useful item.

I asked for nothing that would take him a day to produce. A rough diagram is enough, because the gaps in it tell us as much as the lines. Where he had drawn an arrow with a question mark beside it, I noted that the crew did not fully know where that signal went.

Then we arranged one visit during a rehearsal, so that I could watch the real handovers rather than imagine them.

What the rehearsal showed

Sitting at the back of the gallery, I wrote down every spoken instruction and every time someone waited. The show itself was well made. The trouble sat in small gaps. The graphics operator received the running order as a document that changed after he had printed it, so he sometimes cued an out-of-date item.

The producer's talkback shared a channel with a general crew line, which is why the presenter missed instructions when others were talking. And the recorded inserts came from a playback machine whose audio path differed from the live microphones, producing the slight drift Marcus had noticed.

None of this needed a purchase. It needed decisions about who owns which document, which channel is kept clear, and where the audio is aligned.

The written review and how it was ordered

The report ran to a few pages, and I kept it deliberately plain. Each finding stated what we saw, why it matters on air, and what to do about it. Then I ranked them. The running order issue and the shared talkback came first, because they cost the crew the most confidence and could be fixed within a week at no cost.

The audio alignment for inserts came second, with a clear method for measuring the offset and a note of the delay to apply. A few lower items, such as labelling patch points and tidying a cable run, sat at the end for quieter weeks.

A review that lists thirty items of equal weight gets filed and forgotten. A short list in a sensible order gets used.

  • Fix the running order handover first
  • Give the producer a dedicated talkback line
  • Align insert audio with a measured delay
  • Leave labelling and cable tidying for later

What changed over the following weeks

Marcus told us afterwards that the first two changes took one afternoon. The running order now lives in a single shared file that the graphics operator checks against the producer's copy before the show. The talkback channel was reassigned, and the presenter stopped missing cues almost at once.

The insert drift took a little longer, because the delay had to be set and checked against a clap test, but it was settled within the fortnight. He did not report a dramatic transformation, and I would be wary of anyone who did. He reported a quieter gallery and fewer moments when someone said what just happened.

That is a modest result, and a believable one. The show still has its surprises, as live television always will.

What I took from it as a lighting designer

I usually write about light, so it is fair to ask why I am telling this story. I sat in on the review because the lighting cues on his show were also tied to that shifting running order, and I wanted to see how the handover affected them. It did. Two cues had been called late for the same reason as the graphics.

Seeing the whole chain made me better at my own part of it. A lighting plot can be perfect and still look wrong on air if the cue arrives at the wrong moment.

The lesson I keep is that a show is a sequence of handovers, and most weekly problems live in those handovers rather than in the equipment.

Marcus did not need a new studio, only a clear picture of how his own show actually ran. A written review gave him that picture in an order he could act on, starting with what cost him most and ending with what could wait. If your live or recorded programme drifts in a different place each week, the cause may be a handover rather than a machine, and it is worth looking there first.

More from the guides

glitara
Get in touch14 Trafalgar Lane, Brighton BN1 4ED01273 244 063hello@glitara.net