The Event Owner's Operating Map
27 disciplines. Five clusters. One connected way to see your event operation. Read, explore and use everything here freely. No account, no sign-up.
No two events are alike. But the operating disciplines behind them repeat.
Over more than 30 years in live events, I've heard the same sentence at the start of almost every project: "No two events are alike, so we need to start from scratch." The first half is true. The second half is where the opportunity hides.
Think about buying a car. No two cars leave the lot exactly alike, yet every one is built on a structured design. Events work the same way. A private board meeting and a 20,000-person conference look nothing alike, but the disciplines behind them are the same.
The person running an event is a conductor. Every discipline is an instrument, often played by a different company, and the music only works when each one comes in at the right time. This guide is a map of the whole orchestra. It won't tell you how to play each instrument; your team and your partners already know how. It's meant to help you see how the pieces connect.
One idea runs through all of it: learn it once, and the whole organization learns it. For most of my career, that wasn't practical. With today's AI, that becomes practical at a different scale.
Steve Scott, Founder, EventOS
27 disciplines. Five clusters.
These disciplines already exist in your event. The question is whether they run as one connected operating model. Select any discipline to see what good looks like.
One Event.
Multiple Companies.
One Operating System.
Every partner keeps its relationships and its tools. Everyone works from the same understanding of the event.
Most of these 27 disciplines are delivered by different companies. Each brings real expertise. The opportunity isn't to replace any of them. It's to give all of them the same picture: what the event is, who owns what, what's been decided and what changed.
Ten questions about how your event connects.
Answer Yes, Partly or Not yet for the event or portfolio you know best. There's no score, and your answers stay in this browser.
Notice every answer marked "Partly" or "Not yet." Each is a possible starting point, not a failure. Choose the area or areas that matter most right now. If every answer is "Yes," you have a strong foundation to carry into the next event.
If you would like a second set of eyes, email me at scottproductlabs@pm.me with a few times that work for you. I will confirm one and send a Zoom link.
Four questions to put to your event files.
Most teams finish a show and go straight into the next one. This review takes about an hour and makes the next event easier.
Gather four files your team already has
- Budget to actuals, with the contracted amount for each line and any notes
- Every version of the run of show you saved, with the date in each file name
- The registration export, including session choices
- The attendee survey, with ratings by session
- Compare what we contracted with what we actually spent. List every line that changed, by how much, and what the notes and run-of-show versions may help explain.
- Which parts of the program changed most across the run-of-show versions, and how close to the event did each change land?
- Which sessions drew the most registrations, and how did attendees rate them? Where do popularity and ratings disagree?
- Using everything above, draft a one-page brief for next year's planning kickoff: what to keep, what to change and what to decide earlier.
Keep human judgment in charge. Require every finding to point to the supporting file and row. Check the numbers, cut what does not hold up, and decide what matters. Protect your data. Remove personal attendee details first and follow your organization's data policies. These questions can be used in a team debrief, your existing analysis tools, or an organization-approved AI workspace.
One discipline, made visible.
Type directly into this worksheet. One discipline is shown; every discipline in your event has the same shape.
Private by default. What you type stays in this browser. Nothing is sent unless you choose to include it with a Snapshot request.
One discipline on one page is manageable. Twenty-seven, across several companies and changing every day, is where a shared operating system earns its place.
What changes when all 27 connect.
Every discipline in this guide already has capable people and good tools behind it. What EventOS adds is the layer they share: one governed understanding of the event that people, partners, systems and AI can all work from.
Ownership, decisions, dependencies, approvals and changes live in one place. When something changes, everyone it affects sees what changed and what they're responsible for next. And when the event ends, what was learned carries into the next one.
Request Your Event Operating Snapshot
Share your name and email, plus as much or as little context as you like. I'll personally prepare a one-page snapshot covering:
- The areas where a shared operating model would help most
- What good looks like in each
- One practical next step you can take on your own