Key Takeaways — Chapter 12: Vendor Management

1. You are assembling a temporary company. Eighteen businesses and forty to fifty people who have never met, working sequentially and interdependently for eight hours, where a failure anywhere propagates everywhere — and nobody in it reports to you. Your authority is borrowed and voluntary, from three sources: the client's delegation, your observed competence, and the relationship.

2. The test: if a vendor found a problem at 2 p.m., would they call you? A planner who cannot answer yes has only contracted obligations — which is what you fall back on precisely when it is too late to matter.

3. Vetting outranks contracting. The priority order is vet → insure → draft, because a contractual right against a vendor who has failed is a claim, not a performance. (The exception: where you have no choice of vendor — an exclusive caterer, a required list of one — vetting produces information but no decision, and the contract becomes your only instrument. Spend the asks.)

4. Sourcing runs on networks, not searches. Search ranks marketing spend; several of the best vendors in any market have websites from 2019. Ask: "If you were getting married, who would you use?" — not "who would you recommend?", which produces a diplomatic list. Follow with "and who would you avoid?" — the non-answer is informative.

At a raw site, ask the vendors who set up beside them — tent suppliers, rental companies, florists — not other caterers, who compete directly and see each other rarely.

5. The network runs on reciprocity, tracked informally and slowly by everyone. Build it before you need it, because you cannot build it when you do.

6. Interrogate a preferred vendor list with one question: "How does a vendor get onto this list?" Curation, a paid placement, a commission, and inertia all look identical from outside. Then: "Is there anyone on it you'd steer a couple away from?" — a venue that curates will answer.

7. The vendor matrix is the source of truth. The certificate table (Ch.9), contact sheet (Ch.26), power budget (Ch.18), timeline (Ch.25), and vendor-meal count (Ch.14) are all filtered views of it. Build it from a walk through the day, 7 a.m. to 2 a.m. — not from contracts or memory, which skip rentals, transport, tent, lighting, restrooms, generator, and parking. Several of those arrive in vehicles.

8. Vetting, in increasing usefulness: portfolio read for consistency, not highlights (a full gallery from a recent event at your venue type, count, and season) · reference calls · contract behaviour · seeing them work.

9. The four reference questions:

10. What did they do better than you expected? — warms them up
11. What did you have to manage? — presumes something needed managing, so it permits honesty without accusation
12. Tell me about a time something went wrong. What did they do? — the failure question. The only thing a portfolio cannot show

13. Would you use them again, and anything you'd do differently? — the second half is where the real answer lives

14. Send the same RFP to three vendors on the same day. Include the site's constraints, the relevant vision extract, and — most usefully — "please list what is not included." State the budget and invite them to say if it is unrealistic. Tell them how many you asked.

15. Compare on three sections: cost, scope, risk. In the worked comparison, menu prices spanning $16 produced loaded rates within 2.7% — and **the lowest menu price was not the lowest loaded rate.** Inclusions were worth $2,714, more than the entire spread.

16. Count the RFP questions a proposal leaves unanswered. Six or more means they did not read it, which tells you how they will read your timeline.

17. Never ask for a discount. Give a target and a constraint. "I've got twelve-five. I don't want you to just cut the price — tell me what you'd change. And the couple ranked food first, so protect the food." They solve it with knowledge you do not have, and what comes back is usually better than what you would have asked for.

18. What vendors value, in order: paid on time · documents when promised · early warning of changes · crew fed properly · constraints respected · you answer the phone · you defend them to the client · specific thanks. Friendliness is not on the list.

19. Say you are the point of contact, in writing, at booking. Most vendors have never been asked and will gladly comply. And make the pre-event call two weeks out: what time are you arriving, what do you need from me, and is there anything about this site that worries you? The third question surfaces more real problems than any document in this book.

The Signals, Assembled

Any one is ordinary. The set is a picture.

• A short contract with no remedy clause and no insurance provision
• A reference that produces no operational detail
• A certificate requested three times and not received
• A balance due a week earlier than competitors
• A price 8%+ below two comparable bids
• Six or more unanswered RFP questions

The signals that matter rarely feel like signals. They feel like admin — which is why they need a process rather than attention. Build the risk register (CS1 mini-project) and review it at the same weekly sitting as the budget tracker.

Common Mistakes

• Sourcing by search — a ranking of marketing spend
• Building the matrix from memory — seven categories get skipped and one has the truck
• Reference calls that ask "were you happy?"
• Comparing headline prices rather than loaded rates
• Comparing on cost and ignoring risk
• Reading one contract instead of comparing three — comparison is the cheapest possible audit
• Different briefs to different vendors, then comparing the proposals
• Asking for a discount instead of giving a target and a constraint
• Not stating that you are the point of contact
• Skipping the pre-event call
• Letting a certificate chase become routine rather than a trigger
• Treating vendors as staff — they are colleagues, several are more experienced than you, and none report to you

Decision Framework — should we book this vendor?

1. Does the portfolio show consistency at this venue type, guest count, and season?
2. Did a reference answer the failure question in a way that reassures you?
3. Is the loaded cost within budget?
4. What is excluded, and what does that cost to supply?
5. Contract: remedy clause, cap basis, postponement, balance date?
6. Certificate of insurance produced, correct, and in reasonable time?
7. How many RFP questions did they leave unanswered?
8. Would you be comfortable if this vendor were the one thing that went wrong?

A "no" on 6 stops the engagement. A "no" on 2 warrants another reference call before proceeding.

Numbers Worth Remembering

Your Project

You should now have, in Reyes–Whitfield: the vendor matrix built from a walk through the day, with at least fourteen businesses and at least four from the commonly-skipped categories, each marked for vehicle, foot, load-in, power, crew, and meals; the sourcing question written and directed at a tent supplier and a rental company rather than at caterers; a seven-section catering RFP whose constraints section carries the no-kitchen, two-circuit, noon-access, 10 a.m.-removal, no-open-flame, 10:30-curfew, and 32-inch-doorway facts; the three proposals compared on cost, scope, and risk with the loaded arithmetic shown; a recommendation and the sentence you say to Alicia; the target-and-constraint negotiation written; and the point-of-contact sentence you send at booking.

And the observation worth sitting with: Harvest & Thyme is the caterer who does not appear in Chapter 1's cold open. You now have, in front of you, the three signals that would have predicted it — and none of them felt like a warning.

Chapter 13 orders the tent, the tables, and the generator.