Production Ops 101: the operating system every show needs
Production ops is the invisible infrastructure of every event. Done well, nobody notices. Done poorly, everybody does. This is a complete primer on what it covers and how teams are consolidating the tool stack in 2026.
What production ops actually covers
Production ops is the set of disciplines that make a show happen on time, on budget, and safely. It is operationally distinct from creative direction (what the show is) and from artist/talent relations (who is on it) — though it touches both.
It spans 7–8 functional areas. Any production team of meaningful size has someone owning each. The question is whether they're all coordinated on one platform or scattered across eight.
The functional map
In no particular order, these are the areas every production org needs to cover. Your titles will vary; the functions are stable.
- Projects — the shows themselves, with dates, venues, milestones
- Advancing — the 16 typed deliverables per show (see /guides/event-advancing)
- Finance — budgets, invoices, expenses, advances, settlements
- Procurement — vendor management, POs, COI / W-9, payouts
- Production — equipment, rentals, fabrication, dispatch
- People — crew, credentials, scheduling, payroll
- Stakeholder comms — portals, KBYG, updates (see /guides/what-is-kbyg)
- Show-day execution — ticketing, clock-in, inventory, incident response
The tool sprawl problem
Most production orgs run 8–12 separate tools. A typical stack:
Asana or Monday for projects. Notion for the wiki. Google Sheets for budgets. QuickBooks for accounting. DocuSign for contracts. Eventbrite or Ticketmaster for tickets. Some custom portal for clients. A separate check-in app for the gate. Slack for internal. Email for external. Each tool solves one problem and introduces three seams.
The seams leak money. Data gets re-entered. Status drifts. People drop through the cracks between tools. A 10-person team can spend 2 FTE just on integration glue.
The consolidation thesis
The shift in 2026 is away from best-of-breed point tools and toward integrated production platforms.
The argument: production data is deeply interconnected. A vendor PO depends on a project budget depends on a client-accepted proposal depends on advancing deliverables depends on a show schedule. If these live in one database, reporting is trivial. If they live in eight, reporting is a full-time job.
ATLVS Technologies is the explicit consolidation play. One Postgres schema, one auth, one set of RLS rules, three shells (ATLVS internal, GVTEWAY external, COMPVSS mobile). See /about for the thesis in detail.
The ops cadence
Regardless of tools, every mature production org runs on a cadence. Here's the default weekly rhythm for an active season:
- Monday standup — what shipped last week, what's this week, what's slipping
- Wednesday finance review — AR/AP, budgets vs actuals, outstanding invoices
- Friday advancing review — all shows 2–6 weeks out, status of every deliverable
- Daily during show week — morning brief 9am, end-of-day debrief 11pm
- Post-show — debrief within 72 hours, lessons back into templates
What a mature production ops setup looks like
You can tell a mature ops org from the outside because nothing is chaotic in the week of a show. Load-in runs on schedule. Advancing is closed 72 hours out. Crew know where to be. Vendors have been paid. Client signatures are filed.
Inside, the mature org has typed primitives for every recurring activity. Deliverables aren't documents in an email thread; they're rows with owners and statuses. Budgets aren't spreadsheets; they're live queries against expenses. KBYG isn't a PDF; it's a role-scoped rendered page.
How to get there
If you're starting from spreadsheets, read /compare/spreadsheets.
If you're starting from Asana or Monday, read /compare/asana or /compare/monday.
If you're already on a production platform and it isn't working, there may be a fit here. Start free at /signup or book a demo at /contact.