A Checklist for Judging a Production Handover Before You Sign Off

Before looking at a single page of a handover, decide who will hold it on the day. A stage manager calling cues needs different detail from a producer watching the clock, and a remote technician joining late needs something different again. In my sessions I ask learners to name that person in writing, with their role and what they will already know. If you cannot do that, the document is not ready to judge, because every other question on this checklist depends on who is reading.

Once the reader is named, try a simple test. Hand the draft to someone who has not worked on the programme and ask them to explain the first ten minutes aloud. Where they hesitate, guess or ask you a question, the page has a gap. Write down each question they ask, because those questions are the real edit list, and they are usually faster to fix than a full rewrite.

• Name the person who will run the show from the page
• Say what that person already knows and what they do not
• Ask a newcomer to talk through the opening aloud

The running order is the spine of any handover, so read it as a stranger would. Each segment should show a start time, a planned length, an owner and what leads into the next item. If a segment depends on a decision made in a meeting, that decision must appear on the page, not in anyone's memory. I often find that a rundown looks complete until you ask who introduces the third item and what happens if the guest is not ready.

Look closely at fallback options too. A handover that only describes the happy path leaves the receiving team improvising at the worst moment. For each segment with a known risk, such as a remote guest or a video playback, there should be one line saying what to do if it fails and who decides. Short and plain is better than thorough and buried.

• Every segment shows start, length, owner and lead-in
• Decisions from meetings are written down, not remembered
• Risky segments carry a one-line fallback and a named decider

Cue sheets are used in dim rooms, under pressure, often by someone glancing down for a second. Test yours the same way. Print it, hold it at arm's length and see whether the next action is obvious. Cue numbers should run in order, wording should be short, and the person responsible for each cue should be clear without reading a legend. If a cue needs a paragraph of explanation, the explanation belongs in the production notes, with only a pointer left on the sheet.

Check that the cue sheet and the running order agree. Mismatched timings between the two are among the most common faults I see, usually because one was updated after a rehearsal and the other was not. Pick three cues at random and trace each back to its segment. If the times differ, the handover is not ready, however neat each document looks alone.

• Readable at arm's length in poor light
• Cue numbers in order, wording short
• Three random cues traced back to the running order

Production notes tend to fail through assumption. The author knows that the side door sticks, that the moderator prefers a ninety-second warning, that the second microphone is the quieter one. None of this is written down because it feels obvious. Go through the notes line by line and mark every sentence that relies on knowing something unstated. Each mark is a place where a new team could stumble, and each is worth a short sentence of its own.

Contact details deserve the same scrutiny. Every person with a task on the day should have a role, a way to be reached and a named backup. Venue access times, load-in windows and who holds keys belong in the notes too. A handover can describe the programme perfectly and still fail because nobody could find the person who unlocks the room.

• Mark every sentence that depends on unstated knowledge
• Each task owner has a contact method and a backup
• Venue access, keys and load-in times are written out

A plan that was rehearsed carries lessons a blank plan lacks. Check whether the handover records what changed during walkthroughs: segments that ran long, a cue that moved, a speaker who needs a different cue word. Without that record, the receiving team repeats mistakes already solved. I ask learners to add a short section called what we learned, kept to a handful of lines, so the next team inherits the corrections as well as the schedule.

Also confirm which version is current. Handovers often circulate in several drafts, and the wrong one can reach the room. Put a version label and a date range of validity at the top, and say plainly which earlier copies should be discarded. This small habit prevents more confusion on the day than almost any amount of extra detail inside the pages.

• Record changes made during walkthroughs
• Label the version clearly at the top of every page
• State which older copies should be discarded

After working through the list, make a clear decision: ready, ready with named fixes, or not ready. Do not leave it as a vague feeling that it is probably fine. If fixes are needed, give each one an owner and a deadline before the programme, so the review ends with actions rather than worry. A handover with three honest open items is far safer than one that claims to be finished.

Finally, record the open items inside the document itself. A short list headed still to confirm tells the receiving team where to be careful and what to check on arrival. It shows the plan was reviewed, and it gives them permission to ask. That tone, calm and plain about what is settled and what is not, is what makes a handover usable by people who were never in the planning meetings.

• Choose one of three outcomes: ready, ready with fixes, not ready
• Give each fix an owner and a deadline
• List unresolved points inside the document