Two shows need two operating plans

A double-show date can look deceptively simple on a tour calendar: one city, one venue, one hotel. On the ground, the early audience has to leave before the late audience enters. Guest lists belong to different performances. A delayed first show can compress the second show’s preparation. Tomorrow’s departure still needs an owner.

Keep the date-level plan together, but label each performance separately. This is a document structure, not a claim about how a software product models multiple performances. Give every entry a local date, time zone, owner and status. The example below is a planning exercise, not a recommended performance length or a substitute for the venue’s agreed schedule. Confirm access, staffing, breaks and turnaround with the people responsible before distributing the final version.

Build the day sheet around handoffs

The day sheet should answer three questions quickly: where do I go, when do I need to be there, and whom do I contact when something changes? Link to the approved advance rather than copying a long technical document into the schedule. If you need a broader structure, start with the tour itinerary guide.

Fictional date: Saturday, Example City. Time zone: America/Los_Angeles. All times local; set the actual event date before use. Version 3, issued Friday at 18:00 by the tour coordinator. The show labels EARLY and LATE must also appear on the guest lists and closeout records.

Do not infer a venue curfew, labor arrangement or required break from this example. Add those restrictions from the approved advance. If the agreed reset takes longer, revise the plan before tickets and audience communications create conflicting expectations.

Treat turnover as a decision, not an empty gap

Write down who gives the go-ahead for late doors. That person needs the room-reset status, audience-exit status and any unresolved production issue. The touring coordinator should know how to reach them without leaving a performance to search through an email chain.

Suppose the first performance finishes fifteen minutes late. The coordinator records the actual finish, checks the reset implications with the venue and asks the responsible parties to approve a revised plan. Any audience-facing communication belongs with the authorized venue or producer. Update the shared schedule, identify the changed entries and obtain acknowledgment from the people affected. A message saying “running late” does not tell the door team what to do.

Keep guest lists and financial records performance-specific

Use separate EARLY and LATE guest-list versions. Record the delivery deadline, box-office contact, allocation owner and last approved change. Avoid sending personal guest information to the entire crew when only the entry team needs it. A person attending both performances should be handled according to the venue’s process; do not assume one list admits them twice.

The same distinction helps at closeout. Record which performance each sales report, approved expense or adjustment belongs to. Shared costs such as transport or hotel can remain attached to the date, with an agreed allocation method if separate performance reporting is required. Do not split everything fifty-fifty by default.

For example, an illustrative $300 shared vehicle cost could be recorded once against the date. If the agreement calls for separate show reporting, document the chosen allocation and approver rather than entering $300 twice. The settlement worksheet can organize the discussion; signed terms and agreed supporting records determine the actual settlement.

Finish tomorrow’s plan before everyone leaves

Tomorrow’s transfer should be visible while the team is still together. Confirm the meeting point, departure time, transport provider, luggage constraints, destination contact and who checks for changes. Keep booking references and sensitive travel details in an appropriately restricted place.

A late finish does not automatically make the original departure workable. Ask the responsible transport provider and tour lead to review the plan against their obligations and the team’s needs. Do not let a template overrule those decisions.

Use a short open-items register:

Choose tools by testing the whole date

Ticketing, touring and settlement tools can overlap. ComedyPass publicly describes multiple showtimes, ticketing, door operations and comic settlements. Do not assume a product stops at selling tickets. Compare the actual handoffs your team needs rather than broad category labels.

In a Ternwheel evaluation, bring this two-show example and ask to see how schedules, travel, team access, expenses and settlement information are handled. Verify which details belong to the date versus the performance and what can be exported. Use the budget template and calculator to prepare your assumptions, then review the tour-manager demo. Confirm required functionality in the product before committing your live run.

Before distributing your plan

Check that both performances have distinct labels; all times include the local date and time zone; room turnover has an approving owner; guest lists have separate deadlines; shared costs will not be duplicated; tomorrow’s transfer is confirmed; and every open item has someone responsible. Save the final version where the team expects to find it. The useful plan is the one that remains clear when the first change arrives.

Copyable performance handoff

For an editable starting point, download the Excel operations workbook. It includes a general day sheet, budget and settlement sheets—not a comedy-specific ticketing system. Duplicate and clearly label day-sheet copies for the two performances; confirm the venue's own guest-list and payment process separately.

Sources and scope

Platinum Road’s comedy advancing guide provides practitioner context on confirming production details and tracking unresolved questions. ComedyPass’s producer page describes that vendor’s product scope. The tables and examples here are original, fictional planning aids, not either source’s prescribed procedure. Ternwheel product scope is described on its tour itinerary builder page. Sources checked November 2, 2026.