The night-before document, retired.
Every program day gets a live day sheet assembled from data the system already holds: who arrives when, which pickup moved, who's on shift, which vendor confirmed. Generic run-of-show tools are editors you fill by hand; this one is fed by the program.
How each day sheet is assembled
Auto-assemble
The day's rows generate from events, flights, transfers and staff: timed, owned and sourced. The airport team sees transfers; the venue team sees the dinner.
Curate
Add manual rows, hide noise, override times. Every override is marked, and manual always wins over auto. Revert any row with one tap.
Lock & run
Lock the sheet for the day. The team runs from one truth on their phones; upstream changes propose rather than rewrite.
It's correct because it isn't a copy.
A hand-built run sheet is a snapshot that starts aging the moment it's saved. This one is a view over the live program: when the flight moves, the pickup row moves, because they are the same fact. That is the anti-double-entry thesis applied to the on-site day: the document holding the event together is finally fed by the event itself.
- Per-row Edit, Hide, Delete and Revert to auto
- Role-scoped views for airport, venue and hotel teams
- A clean version can appear in the Client Cockpit
- Printable, because paper still rides in the van
- Included on Growth and Enterprise
Run of Show questions
Where do the rows come from?
From the program itself: events from the itinerary, pickups from flights and transfers, shifts from staff assignments, contacts from vendor records. Each row shows its source. Manual rows for anything else, and manual always beats auto.
What happens when something upstream changes?
The sheet follows. A flight delay shifts the pickup row; a vendor re-confirmation turns its row green. Significant changes post to program chat, so the team that isn't staring at the sheet still knows.
Can I stop it changing mid-day?
Yes: lock the sheet for the day. The on-site team works from one agreed truth; upstream changes queue as proposals rather than silently rewriting the day. Overrides and reverts are one tap each.
Does it work on a phone in a hotel lobby?
That is the design case: mobile-first, readable at arm's length, tolerant of bad hotel wifi. And it exports to print, because some crew will always want paper: the paper is just no longer the master.
See it on your own programs.
A 30-minute walkthrough with the team, on data that looks like yours. Sales-led onboarding: we load your catalog, your vendors and your first programs with you.