How to Track Which Vendors Are Actually Reliable, Across Every Event You Book Them For

A studio that has booked the same florist a dozen times has a dozen data points about how that florist actually performs: on time or not, easy to reach during a crisis or not, willing to adjust at the last minute or not. Almost none of that ends up anywhere the rest of the team can see it. It lives in whoever happened to be on-site that day, filed away as a vague impression rather than anything that gets checked before the next booking. The studio has effectively been collecting this information for years without ever building anywhere to put it.

Why the memory does not travel

The coordinator who was on-site when a rental company showed up two hours late remembers it clearly, for a while. Six months and four events later, recommending that same rental company to a new client is a decision made by whoever is doing the recommending that day, and if it is not the coordinator who lived through the late delivery, the studio is relying on a memory that was never actually shared in the first place. The information existed. It just never left the one person who happened to be there.

What actually gets lost

It is rarely the dramatic failures that disappear; a vendor who no-showed entirely tends to get talked about enough that everyone hears. What gets lost is the smaller, more useful pattern: a caterer who is consistently thirty minutes behind their own quoted delivery window, a florist who is unusually good about last-minute changes, a DJ who needs extra reminders to confirm details a week out. None of that is dramatic enough to become studio lore. All of it is exactly the kind of detail that would change how a coordinator plans around that vendor on the next booking, if anyone could actually find it.

Why a gut feeling is not the same as a record

Ask a lead planner which vendors they trust and most can answer instantly, based on years of accumulated experience. The problem is that the answer lives entirely in that one person, and it does not transfer cleanly to a coordinator handling their first event with a given vendor, or to a new planner joining the studio mid-season. A gut feeling is real information. It just is not information anyone else can act on until it gets written down somewhere the whole team can check.

What a shared record actually needs to capture

It does not need to be detailed to be useful. A single line tied to the vendor, the date, and what happened, ninety minutes late without warning, or, adjusted the timeline without being asked twice, is enough to change how the next coordinator plans around that vendor. What matters is that the note lives on the vendor's own record rather than in a single event's wrap-up notes, so it surfaces the next time anyone considers booking that vendor again, not just when someone happens to reread that one event's file.

A worked example

Say a florist shows up ninety minutes late to one wedding in the spring, delays the ceremony setup, and gets no more than a frustrated conversation and a mental note from the coordinator who was there. Booked again in the fall by a different coordinator who never heard about the spring delay, that florist gets the same trust as any other reliable vendor, and the same problem resurfaces with a different couple watching the clock. Logged once, on a shared record tied to that vendor rather than to one coordinator's memory, the fall booking starts with a buffer built in and a clear conversation about delivery time before the contract is even signed. The florist might still be worth booking, plenty of vendors are excellent everywhere except one specific weakness, but that decision should be made with the record in front of the studio, not made blind because the record never existed.

Common mistakes

Only writing something down when it is bad enough to escalate, which misses the smaller patterns, consistently late, consistently excellent, easy to reach or not, that matter just as much for planning the next booking. Keeping notes in a personal notebook or a private message thread rather than somewhere the rest of the studio can see, which recreates the same single point of failure as never writing it down at all. Relying on the same coordinator always booking the same vendors so the knowledge stays with them by default, which works fine until that coordinator is out, or leaves the studio entirely. Waiting until a client asks for a vendor recommendation to try to recall how that vendor actually performed, instead of already having the answer on file from the last time they were booked.

Where to start

The fix is not a formal vendor rating system with scores and spreadsheets; most studios do not need that much structure. It is making sure that when something notable happens with a vendor, on time, late, unusually helpful, hard to reach, it gets attached to that vendor's record on the shared board rather than staying in whoever's memory happened to be on-site. The next coordinator who books that vendor should not have to ask around the studio to find out what everyone else already knows.

Get your studio address, free