Article

A useful theatre handover tells the receiving venue what is arriving, tells the touring company what is ready, and makes unresolved questions easy to find. Start with a short shared record: the engagement, responsible contacts, current schedule, outstanding decisions and the person who can approve changes.
This guide offers a planning format for that record. Adapt it with your production team and venue. It does not prescribe technical procedures, staffing levels or working-hour requirements.
Give the handover a clear owner
Choose one person to maintain the handover record and name a venue counterpart. Their job is to collect confirmed information and route questions, not automatically approve every department's decisions. Record who can approve schedule changes, additional costs and technical changes separately.
That distinction matters when several plans overlap. Theatre planning tools such as Propared bring schedules, people, spaces, resources and budgets together. A handover still needs to say whose confirmation makes each entry usable.
Put these fields at the top:
Production and engagement name, venue and performance dates.
Document owner and venue counterpart, with agreed contact methods.
Version number, issue timestamp and time zone.
Link to the current record and a short summary of changes.
Overall status: working draft, issued with open items, or confirmed for the stated scope.
Avoid a blanket “all confirmed” label when only travel has been agreed. A record can be ready to share while clearly identifying decisions still outstanding.
Separate the day sheet from supporting detail
Keep the day sheet readable on a phone. Include calls, locations, relevant contacts and exceptions. Link to the approved supporting documents instead of copying their contents into several places.
The handover checklist should cover:
Arrival: vehicle arrival point, access contact and who confirms the approach instructions.
People: touring and local contacts, department leads and who receives changed calls.
Production information: current document references, outstanding venue questions and the department responsible for answering them.
Schedule: agreed calls, planned intervals and dependencies still awaiting confirmation.
Company movement: accommodation or transport references and who distributes practical instructions.
Closeout: departure arrangements, outstanding costs and information needed by the next venue.
Keep restricted commercial information and personal details out of broadly shared copies. A day sheet can identify the accommodation coordinator without reproducing everyone's room allocation.
Worked example for a fictional transfer
The following example is entirely fictional. Northbank Players is transferring The Last Window to Harbour Studio. The entries illustrate document control, not a recommended production timetable. The actual team must establish suitable calls, staffing and breaks.
Record: NP-HS-01, version 0.3, issued 2 November 2026 at 16:00 UTC. Event date: 5 November 2026. All schedule times: UTC. Owner: Alex, company coordinator. Venue counterpart: Morgan, venue coordinator. Status: issued for review with open items; not a final call sheet.
Time | Proposed event | Accountable contact | Status in version 0.3 |
|---|---|---|---|
09:00 | Touring vehicle arrives at agreed entrance | Alex | Confirmed with transport supplier and Morgan |
09:15 | Venue welcome and department handover | Morgan | Confirmed |
10:00 | Production work begins under separate department plans | Rowan, production lead | Awaiting final venue response |
13:00 | Company arrival at stage door | Alex | Proposed; transport not confirmed |
14:00 | Rehearsal session | Casey, stage manager | Proposed; depends on production readiness |
19:30 | Performance | Casey | Confirmed engagement time |
After show | Departure arrangements reviewed | Alex | Pending next-day transport confirmation |
“Confirmed” describes the listed arrangement only. It does not imply every preceding task has been completed or authorize anyone to bypass a department's approval.
Below the schedule, keep a separate decision list:
Question | Owner | Next action and deadline | Status |
|---|---|---|---|
Is the proposed company pickup available? | Alex | Obtain supplier confirmation by 3 November, 12:00 UTC | Waiting |
Can the production plan support the proposed rehearsal? | Rowan | Review with venue department leads by 3 November, 15:00 UTC | Under review |
Who receives departure changes? | Morgan | Confirm venue distribution contact by 3 November, 12:00 UTC | Open |
Make changes visible before calling them settled
Suppose the supplier cannot provide the proposed pickup. Alex records the alternative and asks the affected decision owners to review it. Changing the transport row alone would leave the rehearsal proposal looking more certain than it is.
Once the relevant owners agree, issue the next version with a plain change note: “Company arrival changed; rehearsal proposal awaiting review.” Notify the affected people and record their acknowledgements. Mark an old PDF as superseded when replacing it. A timestamp helps someone holding a printed copy recognise that they need the newer instructions.
Check the handover before arrival
Three common pitfalls deserve a final check. First, a familiar venue name can hide an unfamiliar entrance: confirm the arrival point rather than copying last season's instructions. Second, a named contact may not be on duty: confirm coverage and the escalation contact. Third, a completed conversation can leave an unfinished record: put the actual decision, owner and confirmation reference into the handover.
After the engagement, carry forward only reusable information. Close resolved questions, record remaining actions and check venue-specific details again before the next visit. Ternwheel's broader tour manager checklist can help organise surrounding travel and closeout work. Use the tour budget template separately for planned and actual costs, rather than crowding them onto the day sheet.
The handover is ready when the next person can find what they need, distinguish a proposal from a commitment, and identify who owns the next unanswered question.
Copyable handover register
Item or decision | Current source / version | Status | Decision owner | Next update due |
|---|---|---|---|---|
Vehicle arrival and entrance | [reference] | [pending / confirmed] | [role] | [date, time, zone] |
Company arrival | [reference] | [pending / confirmed] | [role] | [date, time, zone] |
Production readiness for proposed rehearsal | [department reference] | [pending / confirmed] | [role] | [date, time, zone] |
Venue contact coverage | [reference] | [pending / confirmed] | [role] | [date, time, zone] |
Departure and next venue handoff | [reference] | [pending / confirmed] | [role] | [date, time, zone] |
Download the editable operations workbook for a general day sheet, checklist and budget sheets. It is a touring administration starting point, not a production cue sheet, technical method statement or theatre compliance system. Adjust its rows to your confirmed engagement.
Evaluating the shared workflow
Ternwheel’s tour itinerary builder describes connected schedules, travel, venue contacts and role-based access for live touring. Bring a fictional handover to the tour-manager demo and check which information your team can share and update. Keep specialist production planning in the approved departmental process; do not assume a touring itinerary replaces it.
Sources and scope
Propared describes arts-production planning across schedules, people, spaces, resources and budgets. Ternwheel’s tour manager checklist provides related touring context. The worked handover is an original fictional planning exercise, not a professional standard or a claim of theatre customer adoption. Sources checked November 2, 2026.