A client came to us already mid-project — booked, briefed, and weeks from the event date, with another vendor already engaged. Except the plan wasn't holding. Decisions had stalled, timelines had slipped, and neither the client nor the vendor they'd hired could tell us, clearly, what the event was actually supposed to look like on the day.
That's the situation we walked into: not a blank page, but someone else's half-finished one.
Our first move wasn't to start decorating. It was to stop and build the model — the actual plan on paper of what "done" looks like: the walkthrough, the run sheet, who's accountable for what, and a fallback for every point that could fail. Most of the confusion up to that point hadn't been a decorating problem. It was a planning problem, and no amount of last-minute execution fixes a plan that was never really built.
Once the model existed, execution was the easy part. We rebuilt the vendor coordination from scratch, closed the gaps the previous plan had left open, and delivered the event on brief and on time — without the client ever having to manage the chaos themselves.
That's the difference between planning an event and building one. Anyone can react to a checklist. What actually rescues a project already in trouble is going back to the model first — deciding what "right" looks like before touching a single detail — and only then acting on it.
It's why, when a client comes to us mid-crisis, our first question is never "what needs decorating." It's "what does the finished night actually need to look like." Everything else follows from getting that answer right.