One run of show, shared the way each person needs it
Build the run sheet once, then share it as a live link, an email or a PDF — full technical detail for the crew, a clean version for the venue, without maintaining two documents that drift apart. Calendar export means the crew's call times land in their own diaries.
- Run sheets shared by link, email or PDF
- Different levels of detail for crew and venue
- Calendar (.ics) export
Track the things that actually cost money
Catering, equipment, staffing and vendors are tracked against the run of show with quantities, suppliers, costs, arrival times and delivery status — so the question "did the AV arrive?" has an answer in the same place as the schedule it belongs to, and budget lines are visible while there is still time to change them.
- Catering, equipment, staffing and vendor tracking
- Quantities, suppliers, costs and delivery status
- Budget lines against the schedule
Catch clashes days early, not on site
Clash detection checks rooms and speakers across events, so a double-booked breakout or a speaker who is meant to be in two places at once surfaces while it is still a scheduling problem rather than a live one.
Tasks with a trail
Work is assigned to named people with a full activity trail, so what was asked, who picked it up and when it was done is recorded rather than reconstructed. R2, the AI operations assistant, can act on the plan too — check the agenda for clashes, push the afternoon back thirty minutes, email the run sheet to the crew — and it previews exactly what it will change before it changes anything.
- Tasks assigned to crew, with an activity trail
- AI operations assistant that previews every change
Onsite, on the same platform
On the day, QR check-in at the door runs on the same system that holds the registrations and the run sheet — so the door, the schedule and the reporting are not three different tools reconciled afterwards.