Engine 01 · Tour
Flagship engineShow Calendar. Announce → on-sale → doors.
The single calendar every other engine reads from. Holds, confirms, announce dates, fan-club presales, artist presales, general on-sale, doors, set times, curfew countdowns. One source of truth from the first venue hold to the last encore.
100%
On-sales hit time
0
Curfew breaches
12
Concurrent holds tracked
1
Source of truth
The job nobody else is doing properly.
Tours die in the calendar — clashing presales, leaked announce dates, curfews missed by 90 seconds because nobody owned the cue clock. The Calendar engine refuses that future.
Every hold, confirm, announce, on-sale and door time lives in one ledger. The rigging plot, the broadcast cut, the freight schedule and the Local Marketing engine all read from the same row.
When a venue moves, when a presale slips, when a curfew tightens — every dependent engine sees the change in the same minute the desk does.
What it does.
01
Holds & confirms
Multi-venue holds with auto-release, conflict detection and routing implications.
02
Presale ladder
Fan-club, artist, partner and general on-sale staggered with cool-down rules.
03
Doors & cues
Doors, support set, headline walk-on, encore and curfew countdown — all timed.
04
Routing-aware
Calendar enforces drive-times and day-off rules — no announce that breaks the route.
05
Embargo timeline
Press, partner and broadcast embargo dates locked alongside the public calendar.
06
Versioned history
Every move auditable — who, when, why — across the lifetime of the tour.
How it runs, end to end.
- 01
Tour route holds opened across candidate venues with auto-release windows.
- 02
Holds confirmed; presale ladder and on-sale times locked into the calendar.
- 03
Doors, walk-on, encore and curfew countdowns published to ROC walls.
- 04
Post-show, calendar reconciles against actuals and feeds Settlement.
AI on the calendar
Routing-aware conflict detection — the calendar refuses to publish an on-sale that would force the tour to break a curfew, miss a freight window or violate a day-off rule.
What changes for the artist and the venue.
No clashing presales, no leaked announce dates.
Every dependent engine reads the same date, every time.
Curfew countdowns visible to artist, FOH and venue ops simultaneously.
Auditable history for every routing or on-sale decision.
Common questions about Show Calendar.
Only authorised promoter, agency and venue users. Every change is versioned with who, when and why.
Each show's curfew is published to ROC walls and the artist runner — when the encore is at risk of overrunning, the orchestrator flags it before the cue fires.
Take the next step