Why This Matters
The parts of event planning that don't show up in the portfolio
Beautiful florals and a well-lit dance floor are what clients remember. But the reason those things existed on schedule almost always traces back to a vendor agreement, a timeline buffer, or a hard conversation that happened somewhere out of sight.
Vendor relationships are built, not found
A lot of planners treat their vendor list as something they inherited or stumbled into. A caterer they used once, a florist a colleague recommended. That works fine until a big event exposes the gap between "seemed fine" and "actually reliable under pressure."
A trial event, a smaller booking used deliberately to test a new vendor before committing them to a high-stakes date, closes that gap. It's a small investment of time that tells you far more than a phone call or a portfolio ever could. This is one of the first things we work through together.
Contracts written under pressure tend to favor no one
Most vendor contracts get written once, early in a working relationship, and then reused for years without revision. Clauses about weather delays, overtime, or subcontracting often get copied from a template nobody fully understood at the time.
When something does go wrong, a vague contract doesn't protect the planner and it doesn't protect the vendor either. It just leaves both sides arguing about intent instead of referring to agreed terms. We spend a full session rebuilding contract language from the ground up so it holds up under actual pressure.
A tight timeline without buffer is a trap
It's tempting to build a schedule that reads well on paper: fifteen minutes here, ten minutes there, everything precise. But a timeline with no slack anywhere means the first fifteen-minute delay, and there's almost always one, cascades through the rest of the day.
We teach a method for placing buffer deliberately at the points in an event where delay is statistically most likely to start, rather than spreading it evenly or leaving it out entirely.
What you say in the moment shapes what the client remembers
Clients rarely judge an event purely on whether something went wrong. They judge it on how it was handled when it did. A calm, honest update delivered early tends to be forgiven. A vague reassurance followed by a visible scramble rarely is.
This session isn't about scripts you recite. It's about practicing the underlying habits: acknowledging the issue plainly, stating what's being done, and avoiding promises you're not certain you can keep.
The common thread
Every one of these topics, vendor trials, contracts, timelines, client conversations, and debriefs, shares a common thread. They're all about building a repeatable system instead of relying on instinct or memory. That system is what this workshop hands you, in a form you can actually use on your next event.
See how the two days are structured