Where Marcus started
Marcus produces an early evening news programme for a regional channel. When he first contacted us, his complaint was not about equipment. The kit worked. What troubled him was that every live show felt slightly out of control, and the same small things went wrong in different ways each night: a late graphic, a missed cue to the presenter, a camera cut that nobody had called.
He asked for a Live Show Workflow Review because he wanted something written down that the whole crew could read. Earlier attempts at improvement had been conversations in the gallery after transmission, and those faded by the next morning. A document, he said, would at least give the team something to argue with.
I joined the work from the lighting side, since part of the problem sat on the set, but the review itself followed our usual shape: watch, listen, write, then agree changes with the people who will live with them.
Watching two live shows from the gallery
The first step was simply to sit in the gallery for two consecutive transmissions and say very little. We logged how the rundown was read out, who spoke on talkback and when, and how long it took the director to get from one item to the next. Nothing in the log was dramatic. It was the accumulation of small hesitations that stood out.
On the second evening a package ran two seconds longer than its listed duration, and nobody on the floor knew until the presenter was already mid-sentence. Marcus had not mentioned this because, to him, it was just how the show ran. Seen from outside, it was a gap in how timing information travelled between the gallery and the studio.
- Rundown read-outs logged against actual running times
- Talkback traffic noted by speaker and purpose
- Hand-offs between gallery and floor timed
What the written review actually said
The review ran to a handful of pages and avoided general advice. It named the three points where information was getting lost and proposed one change for each. Talkback was crowded because the producer, the director and the floor manager all spoke at once during busy moments, so we suggested a clear order of who speaks and when.
The rundown carried only planned durations, so we proposed a column for running totals that the floor manager could see on a monitor. The third finding was about the set: the news desk light levels shifted during the second half of the show as the daylight through a side window faded, and the camera operators were correcting by eye. Each finding came with a reason and a plain description of the change, nothing more elaborate than that.
Making the changes without disrupting the week
Marcus did not want a rehearsal day, and the channel could not spare one. So we staged the changes across a week of normal transmissions, one at a time. The first night, only the talkback order changed. The second night, the rundown gained its timing column. Priya's lighting adjustment, a fixed level for the desk that no longer depended on the window, went in on the third.
Introducing them singly meant the crew could tell which change helped and which felt awkward. The floor manager disliked the first version of the timing monitor, which was too small to read at a glance, and we replaced it within the week. Working this way kept the review a conversation rather than a verdict handed down from outside.
What Marcus noticed afterwards
A fortnight later Marcus described the difference in modest terms. The shows were not faster or flashier. They were quieter. Talkback no longer had the overlapping chatter during item changes, and the director could hear the floor manager's single, clear count-in. Late packages still happened occasionally, but the presenter now knew about them in time to adjust.
He also said the document had become something the crew referred to. A new camera operator joined and was given the talkback order page on her first day, which saved a conversation nobody had time for. That, more than any technical measure, was what he had been after: a shared description of how the show works, written in ordinary language.
What we took from the case
Reviews like this one tend to confirm that most live problems are communication problems wearing technical clothes. The fix is rarely a purchase. It is usually a clearer order of speaking, a number put where people can see it, or a light level that stops being a daily judgement call.
For us the case was also a reminder to keep the written review short and specific. Marcus's team read every page because every page referred to something they had seen themselves in the gallery. A review that describes your own Tuesday evening is far harder to put in a drawer than one that describes live production in general.
Marcus's review did not change his equipment or his headcount. It gave his crew a written account of how their own show runs and three small changes to make it calmer. If your live output feels slightly out of control in ways nobody can quite name, a Live Show Workflow Review starts by watching, listening and writing down what is actually happening.