Ball-in-court RFIs, submittal logs, daily logs, punch lists, change orders, payment applications — the Procore feature set, retuned for production timelines. Multi-day festivals and city-to-city tours fall over when any one of fifty moving pieces breaks. Unify artist advancing, vendor payouts, crew scheduling, credentials, and KBYG under one platform that doesn't.
RFIs with ball-in-court — Question, recipient, due date, official answer. Open RFIs surface on every project dashboard. On festivals & tours jobs, this shows up as multi-day, multi-stage, multi-city.
Submittal log — Per-spec submittals with revision history, reviewer routing, and approved-as-noted resolution. On festivals & tours jobs, this shows up as multi-day, multi-stage, multi-city.
Daily logs — Weather, manpower, equipment on site, work performed, photos. Auto-populates from time entries. On festivals & tours jobs, this shows up as multi-day, multi-stage, multi-city.
Punch list — Item, location, trade, photo, due date — closeout view with show-ready gate. On festivals & tours jobs, this shows up as multi-day, multi-stage, multi-city.
Festivals and Tours are the hardest shape in live production — dozens of artists, multiple stages, multi-day windows, traveling crew, and a calendar that looks like a subway map. Built for that scale from day one.
The same primitives that ship in our RFIs · Submittals · Punch module — applied to festivals & tours workflows.
Question, recipient, due date, official answer. Open RFIs surface on every project dashboard.
Per-spec submittals with revision history, reviewer routing, and approved-as-noted resolution.
Weather, manpower, equipment on site, work performed, photos. Auto-populates from time entries.
Item, location, trade, photo, due date — closeout view with show-ready gate.
Quantified, priced, approved before the work happens. Writes to the budget on accept.
Schedule-of-values draws against contract value with retainage. PDF exports for AIA-style billing.
Sign up free for small teams. Per-org pricing the rest of the way up.
One database. Every module reads from the same record.
Free, forever, for small teams. Per-org pricing the rest of the way up.