One Awards Evening, One Run Sheet: How Aled's Team Stayed on Cue

The call that started it

Aled manages a mid-sized venue and had agreed to stream a community awards evening for people who could not attend. He rang us in the early autumn weeks with a clear worry: the hall had hosted hundreds of events, but never one where a camera feed went out live and a missed cue would be seen by everyone watching at home.

He already had a hired crew, a few cameras and a willing presenter. What he lacked was a shared picture of how the night would run. People in the building each held a different idea of when speeches began, when the music came in and who decided that the stream could move on to the next item.

I joined the first conversation as the audio engineer, because the sound side was where he felt least sure. Very quickly it became clear that the real gap was planning, not equipment. That is the part of our Live Show Workflow Planning work I like best, since a small amount of paper changes how calm a whole evening feels.

Building the run sheet

We began by walking the evening from the moment doors opened to the last credit. Every item went onto a single run sheet: what happens, who is on stage, which camera is on them, what the audio needs and how long the item should last. Aled supplied the content, and we supplied the structure around it.

The sheet had to be readable at a glance in a dim gallery, so we kept the wording short and the timings honest. Where an item depended on a person walking from the audience, we added a buffer rather than pretending they would arrive on the second.

Once the draft existed, Aled circulated it to the presenter and the stage manager and asked for corrections. Three small errors came back, including a trophy presented twice. Finding those on paper, a week ahead, cost nothing, and it gave everyone a first sense that the evening was already under control.

• One line per item, with a planned length
• Camera and audio needs written beside each item
• Buffers added wherever people had to move

Cues that anyone could follow

A run sheet tells people what is planned; cues tell them when to act. We agreed a simple structure with Aled's crew: a standby call about thirty seconds before each change, then a clear go. The director used the same short phrases every time, so nobody had to interpret tone under pressure.

For audio I wrote my own cue notes beside the sheet, marking when a radio microphone should be opened, when the playback track faded and when the hall's own speakers needed to drop so the stream was not fighting an echo. These were small marks, but they meant I was never guessing.

We also agreed what happens when something slips. If a speaker ran long, the director would decide in the moment whether to trim the next item or let the evening stretch. Settling that rule beforehand removed the argument from the live moment, and the crew knew exactly who held the decision.

The briefing and the rehearsal

On the afternoon of the event we gathered everyone in the hall for a short briefing, perhaps twenty minutes. Aled walked through the sheet, each person said what they were responsible for, and we named who to look at if a problem appeared. It sounds obvious, yet at many events it simply does not happen.

We then ran the first fifteen minutes and one awkward middle section as a rehearsal. The presenter practised handing over to a pre-recorded clip, which turned out to need an extra second of silence to feel natural. The camera operators found that one position blocked a sightline to the stage steps.

None of these were dramatic faults. They were the ordinary friction that a rehearsal exists to find, and fixing them while the hall was empty meant the crew arrived at doors open feeling prepared rather than hopeful.

• Short briefing with named responsibilities
• Rehearsal of the opening and one tricky handover
• Sightlines and playback timing adjusted before doors

How the evening actually went

The stream ran for just under two hours. A microphone failed on one presenter's lapel during the third award, and because the run sheet showed a backup handheld waiting at the side of the stage, the swap took seconds and most viewers will not have noticed. That small moment was the plan doing its job.

One speech overran by several minutes. The director made the call he had agreed in advance and trimmed a musical interlude, which kept the later items close to their times. Nobody in the gallery raised their voice, and the calm in the room was noticeable from where I sat at the mixing desk.

Aled told us afterwards that the evening felt different from his usual events, not because everything went perfectly, but because every problem had somewhere to go. He said the crew stopped looking over their shoulders and started looking at the show.

What we took from it

The case reminded me that workflow planning is mostly about agreement. The run sheet, the cue words and the briefing all exist so that a dozen people share one version of the evening. The technology in Aled's hall was ordinary, and it was enough once everyone knew what to expect from it.

It also showed that you do not need a large crew to benefit from structure. A short, honest document and a few shared phrases helped a venue team stream for the first time without panic.

Aled has since asked us to look at his next event in the same way. We will start where we started this time, with the sheet, because that is where a calm broadcast begins.

A live broadcast rarely goes wrong because of one dramatic failure. It drifts when people hold different pictures of the evening. Aled's awards night stayed on cue because the run sheet, the cue words and a short briefing gave everyone the same picture before doors opened. If you are planning a first live stream, start with the paper, and let the equipment follow it.