What a Handover Actually Means in Live Production
A plain-words look at the term handover in production work: what the document holds, who reads it, and why a programme should run from the page alone.
Marcus Reynolds · · 5 minutes to read
The word means more than a goodbye
In live production, a handover is the moment one person or crew passes responsibility for a programme to another, and the document that makes it possible. Newcomers often hear the word and picture a quick chat in a corridor. In practice the chat is the smallest part. The real handover is a set of pages that lets someone who was never in the planning meetings run the show with the same confidence as the person who wrote it. That is why we teach it as a writing task first and a conversation second. A conversation fades by the time the doors open. A page stays on the desk, can be marked with a pen, and can be read again at the worst possible moment.
The term travels across settings. A conference producer hands over to the floor manager at load-in. A streamed panel coordinator hands over to the technical director when rehearsals end. An evening team takes over from a day team. The situation changes, but the question stays the same: what does the next person need to know to act without asking me?
Production notes and the handover are not the same thing
Production notes are the working record: decisions, contacts, venue quirks, timings that changed and why. They grow over weeks. A handover document is what you distil from them for one specific reader on one specific day. Mixing the two is a common early mistake, and it produces a thick binder nobody opens under pressure.
Think of the notes as the whole kitchen and the handover as the plate. The plate holds what the reader needs now, in the order they will need it. Everything else stays available in the notes, labelled clearly enough that it can be found in under a minute if a question comes up.
- Notes: complete, chronological, kept by the planner
- Handover: selective, ordered by use, written for one reader
- Both should carry the same version number
What the page should hold
A useful handover opens with the shape of the programme in a few lines: its length, the number of segments, the start time and the hard finish. Then comes the running order itself, with each segment's owner and a fallback if it fails. After that, the cue sheet references, the contact list with roles rather than just names, and the access details for the venue or the stream.
Learners at scenepulse practise this by taking a rough agenda and producing the handover for a colleague who has to run it cold. We read the result as that colleague would, and mark every place where we had to guess. Each guess is a missing line on the page.
- Programme summary: length, segments, start and finish
- Running order with owners and fallback options
- Cue sheet references and contact roles
- Venue, access and stream details
Writing for the person who was not in the room
The hardest discipline is forgetting what you know. By handover day the planner carries a hundred small agreements in memory: the guest who prefers the left chair, the speaker who needs two extra minutes, the door that sticks. None of this is obvious to the incoming team, and none of it is written unless you decide it matters.
A good test is to hand the draft to someone outside the project and ask them to describe the first twenty minutes of the programme back to you. Where their description differs from your intent, the page is unclear. Fix the page, not the reader. It is slower than it sounds, but it is the cheapest rehearsal you will ever run.
Common ways a handover goes wrong
The first failure is length. A handover that runs to thirty pages will not be read, so the one critical instruction hides in the middle. The second is vagueness: phrases like check audio before start tell the reader nothing about who checks, with whom, and by when. The third is stale information, where the running order on page two disagrees with the cue sheet on page six because one changed late.
Avoid these by keeping the document short enough to read in one sitting, naming an owner and a time for every action, and stamping every page with the same version. When something changes, reissue the whole set instead of patching single pages, so no one works from a mixture.
- Too long: the key instruction gets buried
- Too vague: no owner, no time, no place
- Out of step: pages carry different versions
A mid-autumn habit worth starting
These weeks bring a busy run of business events, and with them a lot of tired crews passing work between shifts. It is a good moment to adopt one small habit: write the handover as soon as the running order is stable, not on the evening before. Early drafts reveal gaps while there is still time to ask the speaker or the venue.
Then keep one rule for the day itself. Whoever receives the handover reads it aloud with the person handing over, line by line, and asks one question per section. Ten minutes spent this way often saves an hour of confusion once the programme is live.
A handover is a document first and a conversation second. Its purpose is simple: any capable team should be able to run the programme from the page, without calling the planner. Keep it short, ordered by use, and clear about who does what and when. Test it on someone who was not there, fix the gaps, and keep your fuller production notes close behind it for the questions that will inevitably come.
