Field Note: The Vendor Handoff Is Where Good Plans Go to Die

Good plans rarely die in the planning. They die in the handoff, where decisions turn into screenshots, stale files, and someone’s vague verbal approval nobody wrote down.

A handoff isn’t sending information. It’s confirming the next team actually received it, understood the same thing you meant, and knows what happens next. Those are three different things, and I’ve watched all three fail independently.

The words that quietly hide risk

“Ready” should mean installed, tested, and signed off by a named person, not vibes. “Final” should mean a version number and no open decisions left dangling. “Included” should mean an exact quantity and who’s responsible for delivery, setup, and strike. “Approved” should mean by whom, for what scope, in writing. I’ve learned to distrust every one of these words until someone attaches a specific, checkable fact to it.

Control the current version like it’s the only thing that matters, because it is

Floor plans, timelines, guest counts, menus, lighting plots, they all need one current home, an owner, and a visible status. Old versions can stay traceable. They should never look current.

Say the dependencies out loud before they become delays

I list exactly what each vendor needs from another team, rigging approval, floor protection, power, a confirmed cue, and I give every dependency a provider, a receiver, and a deadline. Nobody should be discovering a dependency at load-in. Most of them are visible months earlier, standing at the dock with a cart and no elevator.

Attach the ripple to the decision

A guest-count change touches chairs, linen, florals, service, power, capacity. I write the affected systems right next to the decision instead of trusting every vendor to independently notice the ripple on their own. That list is what a vendor brief is actually for.

Close the loop, every time

The sender issues the version and says what’s needed. The receiver confirms receipt and flags any conflict. The owner resolves it. The receiver confirms the updated commitment. Silence is not confirmation, no matter how badly I’d like it to be.

Run one meeting that only covers where teams actually touch

Power, loading, timing, staging, guest routes, cleanup, that’s it. It should end with changed documents and named owners, not another recap email nobody reads.

The fastest way I know to test a handoff is to ask the receiving team to explain what they’re delivering and what would stop them. Any mismatch there isn’t a personality clash. It’s a handoff defect, and it’s fixable before it becomes an event-day problem.