One event record, from the deal to the P&L.

Build the rundown, then call it. Standby, GO, hold and step-back.

• Standby arms the next cue and warns the room; the separate GO is what fires it.
• A press that changes nothing returns the reason — end of rundown, nothing to arm — instead of looking like it worked.
• Hold banks the elapsed time server-side, so a reload comes back frozen on the same number.

Owned-gear catalog, kits, pull sheets, scan out and back, sub-rentals.

• Every asset gets a permanent, platform-unique, human-readable number.
• The same string is the printed QR and the RFID tag, so a scanner and a phone camera agree.
• Inventory rolls up across in-warehouse, prepping, on-job, repair and missing, weighted by unit.

Trucks, drivers, trips tied to the event, dock and yard.

• A trip carries a company vehicle, a driver from the roster, addresses and the event it serves.
• Addresses geocode on save; mileage comes from a road route, with the fallback labelled as an estimate.
• Incoming trucks feed the venue's dock board, so trucking and load-in stay one plan.

Event details, venue, production spec, people and travel, build board.

• Seven sheets on one event record, autosaving — there is no save button to forget.
• A colleague's edit appears while you are looking at the sheet.
• Anything below full access on the event renders read-only rather than a stale copy.

Proposals and invoices, payments, per-event P&L.

• One document model for proposals, quotes and invoices, with a payments ledger behind it.
• Per-event P&L cross-tracks client invoices against labor, expenses and vendor invoices.
• Labor computes from hands × hours × rate, splitting overtime around a threshold you set.

Two phone portals on the same event: check-in, day sheet, live cue, trips.

• Crew check in on arrival, read their day sheet, and watch the cue that is live.
• Drivers broadcast en route, at dock or delayed in one tap, and run a duty clock.
• The duty clock is a helper, not a certified ELD — and the panel says so.