Healthy Event Systems Start with ACCORD

Two days before a Tier 1 event — hundreds of thousands registered, tens of thousands expected concurrently — the sponsorship lead sent a message asking what it would cost to build a custom sponsor page for one of the show's major partners.

Not whether it was possible. Not whether it was in scope. Just the price.

I considered quoting something absurd, but caught myself: there was a real chance she'd find the money, and then we'd actually have to do it. So I said no. She escalated to the client manager, who said the same thing, and that was the end of it.

What stayed with me wasn't the ask itself. It was that the ask even happened — that two days before a major event, at that scale, a significant scope request could still be in play, framed as a budget question, because nothing upstream had made it structurally impossible to raise. No closed decision. No clear ownership. Just someone doing their job and not realizing it was the wrong time by about six weeks.

That's the pattern I've spent nearly 15 years watching. Not the fire drill. What made it possible.

What the ask revealed

Most event problems don't start onsite. Onsite is just where they become visible — where the vague goal from the kickoff meeting becomes a hotly-debated deliverable, where the ownership that was assumed but never assigned becomes a gap, where the system nobody stopped to examine stops quietly picking up the pieces.

But by the time a problem is visible, you're usually too deep in delivery to do anything but manage it. The decisions that would have prevented it were upstream — sometimes weeks or months upstream — and they weren't made clearly, weren't made by the right people, or simply weren't made at all.

The ACCORD framework diagnoses those conditions before they become consequences. It maps six dimensions of a healthy event operating model: not what your event looks like, but how your organization is actually set up to deliver it.

Six dimensions of a healthy event operating model

Strategic Alignment — “Do what we did last year” is not a plan. The difference between strategy and repetition is whether anyone has revisited the goals, defined what success actually looks like, and made explicit tradeoffs about scope.

Clear Communication — Most event teams communicate constantly. The problem is rarely volume — it's structure. When the right information doesn't reach the right people in time to change a decision, communication has failed regardless of how many messages were sent.

Culture of Collaboration — If it’s the same three people “getting things across the finish line” every event, that's not a high-performing team dynamic. That is heroics cosplaying a functional team. Sustainable delivery requires shared ownership, not shared exhaustion.

Technology Operations — Switching platforms is the most common response to event tech frustration, and usually the least effective one. Technology is a mirror of the systems around it. Configure a new platform on top of unclear requirements and misaligned teams, and you'll get the same outcomes, plus a steep learning curve.

Operational Readiness — Requirements, documentation, and testing aren't paperwork — they're the scaffolding that determines whether your team is actually prepared or just optimistic. You can't test what isn't documented, and you can't document what was never agreed on. Most readiness failures trace back to an assumption that was never made explicit.

Event Delivery — What happens onsite is a direct output of every decision made before it. The teams that execute well under pressure aren't just experienced — they operate inside systems that are designed for both the predictableness and mayhem of onsite.

Each dimension has its own deep-dive: what it looks like when it's working, what the recurring breakdown patterns are, and where to start.