A weekly live show with too many versions of the plan
Marcus produces a weekly live entertainment programme from a mid-sized studio, and when he first got in touch he described the problem in one sentence: everyone had a running order, and no two of them matched. The director worked from a printed copy marked up in pen. The vision mixer kept a spreadsheet. The floor manager had a version pasted into a message thread on Tuesday that nobody had updated since.
None of this was careless. Live shows change constantly, and every change was made in good faith by someone who assumed the others had heard. Yet on air night, a segment moved up by four minutes would reach the gallery before it reached the floor, and the floor crew would find out when the talent was already walking. Marcus did not want a grand overhaul. He wanted one plan that everybody read from.
What we looked at first
Before suggesting anything, we asked Marcus to walk us through a full week, from the first production meeting to the final wrap. We sat in on a rehearsal and noted who asked whom for what, and how often. The pattern was clear: most of the questions in the gallery during rehearsal were not technical, they were questions about sequence. What follows the band? Is the interview before or after the break? Who is cueing the graphics for the second half?
Those questions cost minutes each time, and rehearsal time in a live studio is rarely generous. We also listed which roles needed which details. The director needs timings and shot intentions, the vision mixer needs source and transition notes, the sound crew needs microphone changes, and the floor needs positions and talent calls. A single running order has to hold all of it without becoming unreadable to anyone.
- Who changes the plan, and who must be told
- Which details each role actually reads
- Where questions slow rehearsal down
Building one running order the whole crew can read
We set up the show's running order inside the Live Show Gallery Coordination tools as a single document with one line per item. Each line carries a planned duration, the source or set it uses, any audio changes and the floor notes. Marcus's team agreed on a short list of terms so that a line meant the same thing to everyone, and we kept the wording plain enough that a new freelancer could follow it on their first night.
The important decision was about ownership. One person, in this case Marcus's production manager, became the only editor of the plan during the week. Everyone else could read it, and could raise a change with her, but nobody amended it on the side. That sounds restrictive, yet it removed the arguments about which copy was current. A change made once appeared for everybody at the same moment.
- One line per item, with timings and sources
- A shared vocabulary written down once
- A single named editor during the week
The first live night with the new plan
The first broadcast on the new system was not flawless, and Marcus said so himself. One line had been entered with the wrong duration and the gallery noticed it during the pre-show check, which was exactly what the check is for. Because the fix was made in one place, the floor manager saw the corrected time within moments rather than learning about it through a runner.
What Marcus remarked on afterwards was the quiet. The gallery chatter that had once been a stream of sequence questions dropped to the routine calls of a live show. The director spent the minutes before air looking at shots rather than checking paperwork. A late guest swap, which in earlier weeks would have caused visible confusion on the floor, was absorbed by a single edit and one clear call over talkback.
Keeping the plan honest as the weeks go on
A shared plan only helps while it stays accurate, and Marcus has been firm about that. His team now closes the week's running order at a fixed point before the dress rehearsal, and any change after that is treated as a live decision, said aloud and confirmed by the director. It keeps the document trustworthy, because the crew know that what is written is what is intended.
They also review the previous show's plan against what actually happened, marking where timings drifted. Over a few weeks this gave the production manager a realistic sense of how long certain segments really run, and the planned durations became more truthful. The running order stopped being a hopeful sketch and became a record the team could learn from, week after week.
- A fixed point to close the written plan
- Late changes spoken aloud and confirmed
- A short review of planned against actual timings
What other productions can take from it
Marcus's show is one case, and every studio has its own habits, but the lesson travels. The value was not in new equipment or a clever feature. It was in agreeing that a live production needs a single account of what is about to happen, kept by one person and readable by every role in the building.
If your gallery and floor sometimes seem to be working from different stories, start by counting the versions of the plan in circulation. Then decide who owns the one that counts. The tools help once that decision is made, but the decision comes first, and it costs nothing except an honest conversation among the people who run the show.
Marcus did not need a bigger system, only a single running order that the director, vision mixer, sound crew and floor all trusted. Once one person owned it and everyone read from it, rehearsals shortened and air nights grew calmer. If your own gallery still juggles several versions of the plan, that is the place to begin, and our team is glad to talk it through.
