Inside a live day: how we support crews on site

On a live day I am usually in the building well before the presenters. The first hour is not glamorous. I walk the studio floor, listen to the room with nothing running, and note what has changed since the last visit: a door left propped open, a new cable run, a fridge humming behind a flat. Most trouble on air starts as something small that nobody wrote down.

Then I move to the gallery and meet whoever is running it. We go through the rundown line by line, because support only works when I know which moments carry risk. A two-way with a remote guest needs more attention than a studio link, and a cold open needs more than a sit-down interview.

By the time the crew arrives, I know the room, the running order and the weak points, and they know who to call when something sounds wrong.

• Listen to the empty room before any equipment is switched on
• Walk the rundown with the gallery team, marking the riskiest moments
• Note anything that has changed since the previous visit

People often picture support as someone standing by with a toolbox. In practice it is closer to a second pair of ears. I watch levels, check that talkback is reaching everyone who needs it, and keep an eye on the small details a busy director cannot follow while calling shots.

Because my background is acoustics and audio, I tend to hear problems first: a lavalier brushing a collar, a guest drifting off their microphone, a faint buzz that only appears when a particular light is raised. I flag these quietly to the right person rather than taking over their desk.

The aim is never to run the show for the crew. It is to remove the surprises, so the people who own the programme can concentrate on it and make their own decisions in the moment.

Some of our work is with teams who have inherited a studio they did not build. The equipment is there, the previous crew has gone, and nobody is quite sure why a certain switch is taped over. Training starts with that detective work: tracing signal paths, labelling what is undocumented, and agreeing what each person is responsible for.

We keep sessions practical and short. Instead of a long lecture on theory, a trainee sets up a microphone, hears the result, moves it, and hears the difference. Repetition on real equipment in their own room teaches more than any slide deck, and it means the habits stay with the crew afterwards.

We also write down what we find, in plain language, so the next person who joins the team does not need to repeat the detective work from scratch.

• Trace and label every signal path before changing anything
• Short hands-on exercises in the crew's own studio
• Written notes left behind for future team members

A full rehearsal, run at the pace of the real programme, tells us more than any checklist. We stop only when something would genuinely harm the broadcast, and otherwise let the run continue so the crew feels the rhythm of the hour and the length of the gaps.

During rehearsal I deliberately listen for the things that vanish once the studio fills with people. Bodies absorb sound, so a room that rings when empty may behave differently with a full set, and we adjust our expectations accordingly rather than over-correcting.

After each run we take ten minutes for notes while everything is fresh. Each note gets an owner and a decision before the next run begins, so nothing is left as a vague worry going into transmission.

Once the programme is on air, my job is mostly to stay calm and say little. If everything is working, the best support is invisible. I keep headphones on, a notepad beside me, and a short list of agreed actions for the problems we have already thought about.

If something does fail, the crew should not have to explain it twice. We agree beforehand who speaks to the director, who touches which piece of equipment, and what the fallback is. That agreement, made in rehearsal, is what lets a fault be handled in seconds rather than minutes.

I resist the urge to fix things during a broadcast that can be fixed afterwards. A note made for the debrief often serves the programme better than a risky change made live.

• Agree beforehand who speaks to the director during a fault
• Keep a short list of rehearsed fallback actions
• Log non-urgent issues for the debrief rather than fixing live

When the programme ends, we do not pack up immediately. We gather the crew for a short debrief while memory is sharp: what worked, what nearly went wrong, and what we would change before the next live day. These conversations are often where the most useful improvements come from.

Afterwards I write a short summary with the settings used, the issues noted and the actions agreed, and send it to the team. It is deliberately brief, because a document nobody reads protects nobody.

For crews we are training, the handover is the real goal. Success means they no longer need us on the next live day, or need us only for the unusual ones.