Binder or Shared Document: Choosing How to Hand Over a Live Programme

Early autumn is when many programmes change hands. A conference series moves to a new coordinator, a streamed discussion gets a different technical crew, or a colleague goes on leave just before a busy run of events. In each case the question is the same: how do you give the next team everything they need to run the programme from the page?

In our Production Handovers and Notes module, learners meet two practical options. The first is a printed binder, built once and carried to the venue. The second is a shared online document that the whole team opens on a laptop or tablet and that stays editable until the doors open.

Both can work well, and I have seen each fail. This note compares them on the things that matter during a show, then ends with a recommendation you can adapt to your own programme.

A binder is calm. Nobody needs a battery, a network connection or a login, and nothing updates itself halfway through a segment. When a presenter walks off stage and asks which cue comes next, the stage manager turns a page and points. That predictability is why many backstage teams still trust paper for the live hour.

A binder also forces decisions. Because printing a revision costs time and a little effort, people think before they change a start time. The running order, cue sheets, contact list and venue notes sit in a fixed order, with tabs that anyone can learn in two minutes.

In teaching, I ask learners to build a binder first because it exposes gaps. If you cannot fit the fallback plan for a late guest on one page, the plan is not clear yet. The discipline of paper tends to produce tidier notes, even if you later move them online.

• Works without power or signal
• Fixed page order that new crew learn quickly
• Revisions are deliberate and visible
• Easy to mark up with a pen during rehearsal

The weakness of paper is staleness. A segment gets shortened at the last tech check, a remote guest changes their slot, and half the team is still holding the older page. I have watched a camera operator prepare for a cue that had been cut an hour earlier, simply because the revised sheet had not reached their copy.

Binders also scale badly. A single venue and a small crew is manageable, but a programme with several days, multiple rooms or a streamed element joins together more notes than a binder can hold without becoming heavy and slow to search.

There is a handover cost as well. If the next coordinator works in another city, the binder has to be scanned or shipped, and a scan is only a photograph of what was true on one afternoon. For programmes that change often, paper alone leaves too much room for quiet disagreement.

A shared document solves the staleness problem. One current version exists, and everyone sees the same running order, the same revision note and the same contact list. When a remote contributor moves, the producer edits one line and the change is there for the sound technician, the moderator and the person handling the stream.

It also suits distance. Daniel, who teaches our streamed events sessions, often works with teams who never share a room until show day. For them a shared document is the only practical home for production notes, because questions and answers can be left beside the line they refer to.

Search is the other gain. When someone needs the fallback for a guest dropping out, they type a word instead of paging through tabs. For a long programme with many segments, that saves real minutes during rehearsal, where minutes are tight.

• One current version for every role
• Changes reach the whole team at once
• Comments can sit beside the line they concern
• Searchable when the programme is long

A document is only as dependable as the device and connection holding it. Venues with weak signal, a tablet that dims at the wrong moment, or an update that moves a table while someone is reading it can all cost you at the worst time. Screens also invite constant small edits, and a running order that changes every few minutes is hard to trust.

The usual failure is unclear ownership. Without a named person who approves changes, three people edit the same segment and the team never knows which time is final. A shared document needs a rule about who may change what, and a visible note of the latest revision.

Finally, not every role wants a screen. Presenters often prefer one printed page they can hold. If the document is the only format, you may find people printing their own copies from different moments, which recreates the staleness problem you were trying to escape.

For most programmes I recommend a hybrid with a clear order of authority. Keep the shared document as the single master, with one named owner and a revision line at the top. Then, shortly before the first rehearsal and again before doors, print only the pages people need for the live hour: the running order, the cue sheets and the contact list.

Mark each printout with the revision and the time it was produced. If a change comes after printing, the owner announces it and hands out the replacement page, and the old one is collected. This keeps the calm of paper at the moment it matters while keeping the flexibility of a document during the planning weeks.

Small, single-room programmes with a stable team can manage with a binder alone, and fully remote streamed discussions can stay entirely online. For everything in between, one master and a short printed set is the combination I would hand to any team I was leaving behind.

• Master document with one named owner
• Printed live-hour pages with revision and time
• Replacements handed out, old copies collected