Field Note: What Every Vendor Needs to Know by 30 Days Out

By thirty days out, every vendor should be working from the same event, not six nearby versions of it.

The date isn’t universally final at that point. It’s a coordination gate, the moment I make sure the high-impact facts are aligned and the remaining uncertainty is visible enough to actually manage.

Publish one shared baseline

Event date, venue, current guest-count range, approved floor plan and timeline versions, access and loading windows, the weather version and who decides it, by when, primary contacts. Every vendor confirms they received it. A distribution list is not a read receipt, no matter how much I would like it to be.

Lock the interfaces where teams actually touch

Power: who provides it, connects it, tests it, stays responsible. Loading: what arrives when and where it stages. Food and bar: what equipment, water, and refrigeration they actually need. Sound: who owns the microphones and the cutoff. Guest route: is the whole path from access to departure actually complete.

Label the open decisions honestly

Final, provisional, awaiting client, blocked, conflicting, whatever it actually is. Almost done hides the one thing I need, who is actually finishing it and what evidence closes it out.

Judge every late change by its real consequence

Which vendors it touches, what it costs, what it does to timing and safety. Then the team can decide honestly whether the benefit is worth reopening the baseline.

Put the final proof points on the calendar

Mockups, tastings, technical tests, cue rehearsals, quantity locks, all scheduled with a name attached to what evidence closes each one.

Send one real 30-day release

Current files, open decisions and their owners, changed assumptions, the next irreversible deadlines. Each vendor also needs their own piece of it written as instructions, not as a file dump. I ask every vendor to flag conflicts within a defined window, not whenever it occurs to them.

The point of the thirty-day gate was never ceremonial finality. It is making sure instability shows up while it can still be fixed, instead of in the final week when everyone discovers they were quietly building different events the whole time.