A studio handover can happen while the news is on, a producer is asking a question and someone is trying to find the right audio for the next segment. There isn’t always time for a long conversation.
That’s exactly why a useful handover matters. The person taking over needs to understand the state of the shift quickly, especially when something has changed or a system isn’t behaving as expected.
In broadcast operations, information often moves between presenters, producers, panel operators, traffic, engineering and other stations. A detail can be obvious to the person who has been dealing with it for three hours and completely invisible to whoever walks in next.
Explain the current situation
A useful handover starts with what the incoming person needs to know now. Is the programme running to plan? Has a feed changed? Is there a guest waiting on a different line? Has an item moved in the rundown?
Keep the immediate information easy to find. If the next break needs attention, that belongs ahead of a general note about something happening next week.
Separate confirmed changes from possibilities. “Interview moved to after the news, confirmed with producer” gives the operator something they can act on. “Interview might move” needs an owner and a follow-up. Otherwise, the next person inherits the uncertainty as well as the task.
Write down the workaround
If a system has a fault, explain what isn’t working, what has been checked and what is currently being used instead. Include any reference number or escalation contact that’s relevant.
For example, a hypothetical note saying “remote feed issue” leaves a lot unanswered. A more useful note would identify the affected feed, describe the symptom, state that engineering has been notified and explain which approved backup is in use.
Be precise about the status of that backup. A source being available is different from someone having tested it. The incoming operator needs to know which situation they’re taking over.
Avoid placing passwords or other sensitive access details in a general handover. Refer people to the organisation’s approved process for retrieving them.
Give unfinished work an owner
A handover can easily become a list of problems that everyone assumes someone else will fix. Each outstanding item needs a clear next step and someone responsible for it.
That might be a producer confirming a guest, traffic checking replacement material or engineering investigating a fault. Add the deadline when timing matters. “Before the next bulletin” is more useful than “when possible” if the programme depends on it.
The record should be somewhere the relevant team can access. A verbal update is helpful, but it becomes difficult to refer back to once the outgoing person has left and the programme is moving again.
Keep the process usable under pressure
A handover template should fit the operation. Too many fields can encourage people to leave it unfinished or bury important details in general commentary.
Start with a few clear prompts covering the current programme, technical issues and outstanding actions. Agree which changes also need a direct verbal handover. Review old entries and close out resolved items so yesterday’s issue doesn’t keep appearing as an active problem.
It’s also worth asking the incoming team whether the information helped. If they regularly need to chase the same missing detail, change the prompt. The document should earn its place in the workflow.
At Audex Media, we support broadcast operations and the systems around them. Clear handovers are one practical part of helping teams deliver live programmes with fewer avoidable surprises.