35 min read

> "If you want to go fast, go alone. If you want to go far, go together."

Prerequisites

  • 8
  • 10
  • 6

Learning Objectives

  • Source vendors through professional networks and explain why searches produce worse results
  • Build and maintain the vendor matrix, from which the certificate table and the contact sheet descend
  • Vet a vendor using portfolio consistency, reference questions, contract behaviour, and insurance
  • Write and issue an RFP that produces comparable proposals
  • Compare proposals on loaded cost and on risk, not on headline price
  • Negotiate in a way that preserves a relationship you will need again

Chapter 12: Vendor Management — Finding, Vetting, Booking, and Coordinating

"If you want to go fast, go alone. If you want to go far, go together." — commonly cited as an African proverb; the specific origin is not established

Chapter Overview

The florist called me at ten past seven on a Thursday evening, three days before a wedding I was not working.

She had a couple whose caterer had gone quiet — no reply for nine days, phone straight to voicemail, and a wedding on Saturday for ninety people. She was not their planner; they had no planner. She had called me because four years earlier I had recommended her to a client, and because in her judgment I was a person who would know who to call at ten past seven on a Thursday.

I made three calls. The second one worked.

I have never met that couple. I was not paid. I spent forty minutes on it and I would do it again, and the reason is not generosity: it is that eleven months later that florist sent me two clients, and one of them was the largest wedding I did that year.

That is how this industry actually works, and the fact that it works that way is not sentiment. It is structural, and this chapter is about why.

In this chapter, you will learn to:

  • Find good vendors, which is almost never done by searching
  • Build the vendor matrix — the document that Chapter 9's certificate table, Chapter 26's contact sheet, and Chapter 25's timeline all descend from
  • Vet a vendor in a way that reveals how they behave when something goes wrong
  • Write an RFP that produces proposals you can actually compare
  • Compare on risk as well as on loaded cost
  • Negotiate in a way that leaves you someone they want to work with again

🏃 Fast Track: If you have procurement or vendor-management experience from another industry, skim §12.5 and §12.6 and read §12.1 (the threshold), §12.2 (sourcing), §12.4 (the failure question), and §12.8 (coordination) in full. The part that will not transfer is that you have no leverage — these vendors are not your suppliers, they do not depend on your volume, and several of them will be at more weddings next year than you will. Then do exercises B.3, C.1, and D.2.

🔬 Deep Dive: Work case-study-02.md, which follows one caterer selection through sourcing, RFP, three proposals, and a decision — with the cheapest headline price finishing third on loaded cost and second on risk.


12.1 The Temporary Company

🚪 Threshold Concept: you are assembling a temporary company

Count the businesses at an ordinary wedding: venue, caterer, bar service, florist, photographer, videographer, band or DJ, ceremony musicians, rentals, tent, lighting, restroom trailer, generator, transport, hair and makeup, stationer, baker, officiant, parking. Eighteen companies, forty to fifty individual people, most of whom have never met.

For roughly eight hours they must behave as a single organization. Their work is sequential and interdependent — the tent before the tables, the tables before the linens, the linens before the centerpieces, the centerpieces before the photographs, the food before the toasts, the toasts before the dancing. A failure anywhere propagates everywhere.

And here is the thing that makes it hard: nobody in this organization reports to you.

You did not hire them; your client did. You cannot discipline them, you cannot fire them without your client's agreement, and you have no authority over their staff. Several of them will work more weddings this year than you will. Two or three are more experienced than you. One of them thinks planners are unnecessary.

Before this clicks: you treat vendors as suppliers — parties who have been paid and should therefore perform. You issue instructions. You are surprised when a vendor does the thing they always do rather than the thing you asked for. When something goes wrong you escalate to the client, which makes you a complainant rather than a manager.

After this clicks: you understand that your authority is entirely borrowed and voluntary, and that it comes from three sources: the client's delegation, your own competence as observed by the vendor, and the relationship. You stop instructing and start coordinating. You learn that the most valuable thing you can be to a vendor is easy to work with, because a vendor who likes you will tell you at 2 p.m. that something is wrong instead of at 5.

The practical test: if a vendor discovered a problem at two o'clock, would they call you? A planner who cannot answer yes has no authority at all — only a list of contracted obligations, which is what you fall back on precisely when it is too late to matter.

What follows from it

Three things, and they run through the rest of the chapter.

Vetting matters more than contracting. Chapter 8's Case Study 1 concluded the priority order is vet → insure → draft. This chapter is the first of those, and it is first because a contractual right against a vendor who has failed is a claim rather than a performance.

Relationships are infrastructure, not sentiment. The florist called at ten past seven because of a recommendation four years earlier. That is not friendship; it is a network with reciprocity, and it is the most valuable asset a planner accumulates.

Being easy to work with is a professional skill. §12.8. It is also, measurably, cheaper — vendors quote difficult planners higher, and everybody in this industry knows it.


12.2 Sourcing

Almost nobody good is found by searching.

Search results are a ranking of marketing spend and SEO competence, and in this industry those correlate weakly with quality and strongly with volume. The vendors who are excellent and busy have no incentive to rank, and several of the best have websites that have not been updated since 2019.

⚡ Quick Reference: sourcing channels, ranked

Channel Quality Effort Notes
Other vendors' recommendations Highest Low The single best source. §below
Planners you trust High Low Especially for categories you use rarely
Having worked with them Highest Your vendor file (Chapter 1)
Venue preferred lists Mixed Low May be quality control or a revenue stream. Ask which
Professional associations Good Low Membership signals seriousness, not skill
Seeing them work High High The best signal available and hard to arrange
Instagram and portfolios Low–mixed Low Shows the best four minutes of the best events
Directories and marketplaces Low Low A ranking of who paid
Search Lowest Low A ranking of marketing spend

The question that does the work

📋 The Planner's Script: sourcing from another vendor

To any vendor you respect, in any category:

"Can I ask you something — if you were getting married, who would you use for [category]?"

Not "who would you recommend?" — which produces a diplomatic list of everyone they have worked with and cannot afford to omit.

"If you were getting married" produces one name, quickly, and usually with a reason.

Then the follow-up that matters:

"And who would you avoid?"

Most will not answer this directly, and their non-answer is informative. "I'd rather not say" about a specific name is an answer. "Honestly they're all fine" means either they do not know the category or they are managing you.

A third, for a category you do not know at all:

"Who's the person everyone in this business calls when they're stuck?"

Every market has two or three. They are rarely the best-marketed and they are almost always worth knowing.

🎤 From the Field: the reciprocity of the network

Vendor recommendations are the best source and they are not free. They run on reciprocity, and the reciprocity is real, tracked informally by everyone, and slow.

What you owe, and what you get:

You give You receive
A recommendation that leads to a booking Their recommendations, for years
A payment made on time, every time Priority when they are choosing between two dates
A clear brief and a floor plan sent when promised Better work, and less of your own time spent
Telling them early when something changes The same courtesy back — which is worth more
Feeding their crew properly (§12.8) Genuine goodwill, disproportionate to the cost
Not beating them down on price An honest quote next time instead of a padded one
Standing up for them when a client is unreasonable The phone call at 4:07 p.m.

That last row is Chapter 1's opening. The caterer who did not arrive was solved by a network built over four years, and no contract, insurance policy, or planning software would have produced dinner.

Start building it before you need it, because you cannot build it when you do.

The preferred vendor list, interrogated

Venues supply lists, and a planner's instinct is either to treat them as curation or to resent them as restriction. Both readings are sometimes right, and one question separates them.

📋 The Planner's Script: reading a preferred list

To the venue manager:

"How does a vendor get onto this list?"

The answers, and what each means:

Answer Reading
"They've worked here well, repeatedly, and we trust them" Curation. Genuinely valuable — these vendors know the load-in, the power, the quirks
"They pay an annual fee" A revenue stream. The list tells you who paid, not who is good
"They pay us a percentage of the booking" A commission structure, which the client is funding through the vendor's price
"It's whoever we've used, we've never really reviewed it" Inertia. Some good, some there since 2016
"We require it for insurance and licensing reasons" Often legitimate, and check whether an outside vendor meeting the same standard is permitted

And the follow-up that gets the real answer:

"Is there anyone on the list you'd steer a couple away from?"

A venue that curates will answer. A venue selling placement will not.

What to do with a required list: ask the vendors on it the sourcing question about each other. Three caterers on the same preferred list know exactly which of the three is best at this venue, and one of them will tell you.


12.3 The Vendor Matrix

The chapter's first technique, and the document more things descend from than any other in this book.

⚡ Quick Reference: the vendor matrix

One row per vendor. Every column is used by something downstream.

Column Used by
Category Everything
Legal entity name Contracts (Ch.8), certificates (Ch.9)
Trading name Communication
Primary contact, role, mobile Contact sheet (Ch.26)
Owner or principal's mobile Emergencies (Ch.28)
On-site lead, if different Day-of (Ch.27)
Status: shortlisted / proposed / contracted / paid Tracking
Contract signed date Budget tracker (Ch.7)
Contract value, and loaded value Budget (Ch.6)
Non-refundable position Shortfall and postponement (Ch.7, Ch.8)
Insurance: required / requested / received / verified Certificate table (Ch.9)
Vehicle on site? Foot on site? The seven skipped categories (Ch.9 CS1)
Load-in time required Timeline (Ch.25)
Strike time required Timeline (Ch.25)
Power required Power budget (Ch.18)
Crew size, and meals required Catering count (Ch.14), budget (Ch.6)
Documents sent: vision doc / floor plan / timeline Briefing
Notes Everything

This is not a spreadsheet for its own sake. Every downstream document — the certificate table, the contact sheet, the power budget, the timeline, the vendor meal count — is a filtered view of this one. Build it once, in month three, and maintain it.

⚠️ Common Pitfall: the matrix built from memory

Chapter 9's Case Study 1: a planner verified certificates for six vendors and skipped five, because she built the list from the vendors she thought of as vendors. The one she skipped had the truck.

The seven categories unconsciously omitted, again: rentals · transport and shuttles · tent and structure · lighting and production · restroom trailer · generator · valet and parking.

The fix is that the matrix is the source of truth, and it is built from a walk through the day rather than from a list of contracts. Walk the event from 7 a.m. to 2 a.m. in your head and write down every business that appears. You will find three you had not counted, and one of them will be arriving in a vehicle.


12.4 Vetting

The chapter's second technique. Four instruments, in increasing order of usefulness.

1. The portfolio — read for consistency, not highlights

Anyone can produce four excellent images. What you are looking for is the floor, not the ceiling.

Ask for Because
A full gallery from one recent wedding, not a highlight reel Shows what an ordinary event looks like, including the parts that were difficult
Work at your venue, or one like it A photographer who has never shot a dark barn; a florist who has never worked without a cooler
Work at your guest count A caterer excellent at 60 may not be excellent at 160
Work in your season September floral is not June floral (Ch.17)
Two or three full galleries One good wedding is not a pattern

The tell: a vendor who cannot produce a full gallery from a recent event, or who offers only curated selections, is telling you something. Good vendors are usually pleased to be asked.

2. Reference calls — and the question that matters

Most reference calls are worthless, because most people ask "were you happy with them?" and receive "yes, they were great."

📋 The Planner's Script: the reference call

Context: a previous client or, better, a previous planner or vendor. Ten minutes.

Open by lowering the stakes:

"I'm not looking for a reference exactly — I'm trying to work out whether they're right for a specific event. Do you mind if I ask a few practical things?"

The four questions, in order:

1. "What did they do better than you expected?" Warms them up and produces a genuine answer.

2. "What did you have to manage?" Not "what went wrong." "What did you have to manage" presumes that something needed managing — which is true of every vendor at every event — and gives permission to answer honestly without making an accusation.

3. "Tell me about a time something went wrong. What did they do?"the failure question This is the one. Every vendor has had something go wrong; what you are learning is how they behave when it does. Did they tell someone immediately? Did they fix it and mention it afterward? Did they conceal it? Did they blame someone?

4. "Would you use them again, and is there anything you'd do differently?" The second half is where the real answer lives. "Yes, but I'd get the timings in writing" is a specific, actionable, and honest answer that "yes" alone conceals.

What you are listening for across all four:

Signal Reading
They mention a problem unprompted and describe how it was handled Excellent. This is a vendor who communicates
Everything was perfect, no detail Either a small event or a person managing you
A specific caveat with a workaround Honest and useful. Most good references sound like this
Hesitation before answering question 2 Ask again, differently
"They're lovely" with nothing operational They may be lovely. You have learned nothing

3. Contract behaviour

Chapter 8 established this and it belongs here as a vetting instrument.

Behaviour Reading
Sends a full contract promptly, before booking Well-run
Engages with two reasonable asks Has counsel or good instincts
Offers a better clause than you asked for Rare and excellent. Note the name
No remedy clause, refuses to add one Template inertia or fragility — ask which
Full balance due unusually early (>21 days) Cash-flow pressure. Notice it
Cannot produce a certificate of insurance Stop

4. Seeing them work

The best instrument and the hardest to arrange. Ask a planner you know if you can shadow an event where the vendor is working, or attend an open house, or — for caterers — a tasting.

What you learn in two hours on site cannot be obtained any other way: whether their crew is calm, whether the lead communicates, whether they clean as they go, and whether the people doing the work seem to like working there.

🔄 Check Your Understanding

  1. Why is "what did you have to manage?" a better question than "what went wrong?"
  2. What are you actually learning from the failure question?

Verify

  1. Because it presumes that something needed managing — which is true of every vendor at every event — and so it gives permission to answer honestly without making an accusation. "What went wrong" invites a defensive "nothing, really."
  2. How the vendor behaves when something goes wrong, which is the only thing that matters and the only thing a portfolio cannot show. Did they tell someone immediately, fix it and mention it, conceal it, or blame someone? Every vendor has failures; the question is what they do with them.

12.5 The RFP

The third technique. It exists so that three proposals can be compared, which they cannot be if each vendor is answering a different question.

⚡ Quick Reference: what an RFP contains

One page, or two. Sent to three vendors in a category, identically.

1. The facts. Date, venue and address, guest count (and whether it is expected or invited), start and end times, and the couple's names or an anonymized reference.

2. The site's constraints, extracted from Chapter 10's survey. This is the section vendors most value and most rarely receive: no commercial kitchen · two 20-amp circuits · vehicle access from noon · all property removed by 10 a.m. · no open flame · amplified music ends 10:30.

3. The scope of supply. Precisely what you want them to quote for, so that three proposals cover the same ground.

4. The relevant extract of the vision document (Chapter 4 §4.8) — the sentence, the vetoes, the ranking position, and the specifications that touch their discipline. Not the whole document.

5. What you need in the proposal, listed: - Itemized pricing, with the loaded total stated - Staffing: how many, for how long - What is not included - Load-in and strike time required - Power required - Crew size and whether meals are required - Insurance limits carried - Payment terms

6. The deadline, and when you will decide.

7. Whether you are stating a budget. §below.

Should you state a budget?

Genuinely contested, and here is the honest position.

Stating a range produces proposals that fit it — which is efficient, and which means you never learn what the vendor would have proposed unconstrained. You also lose the information that comes from a vendor saying "you cannot do this for that."

Not stating it produces incomparable proposals and wastes everyone's time, including the vendor's.

The workable compromise: state the range, and add one sentence — "if you think that's unrealistic for what we've described, please tell me rather than cutting to fit. I'd rather know." Roughly a third of vendors will take you up on it, and that third is telling you something valuable.

✅ Best Practice: send the same RFP to all three, on the same day, with the same deadline. Then, when the proposals arrive, you know that any difference between them is a difference in the vendor rather than in the brief.

And say, in the RFP, how many others you have asked. "I'm asking three caterers." It is honest, it is what they will assume anyway, and it prevents the situation where a vendor invests four hours in a proposal believing they are the only candidate.


12.6 Comparing Proposals

Two axes: loaded cost and risk. Most planners compare on the first and ignore the second.

⚡ Quick Reference: the proposal comparison sheet

Vendor A Vendor B Vendor C
Headline price
Service charge / admin fee
Tax base
Gratuity expected?
Loaded total (Ch.6 §6.4)
Loaded per guest
Staffing ratio
What is included
What is excluded
Load-in / strike required
Crew size and meals
Remedy clause? (Ch.8)
Liability cap basis
Postponement clause?
Balance due at
Insurance limits, certificate produced? (Ch.9)
Substitution named?
Reference: the failure question
Portfolio at this venue type / count / season
Contract behaviour

Three sections: cost, scope, risk. A proposal that wins on the first and loses on the third is the most common trap in this chapter, and it is Chapter 8 Case Study 1 — the cheapest of three caterers, whose contract disclaimed everything and who failed six weeks later.

💰 Run the Numbers: three caterers, compared properly

118 guests. Sales tax 7.75%.

Harvest & Thyme Sundown Provisions The Copper Kettle
Menu price **$78** | $94 $85
Service charge 24% 20% 18%
Distributed to staff? No Yes No
Admin fee 3%
Tax base Food + SC Food only Food + SC
Gratuity added (18%) Yes No Yes
Loaded rate $120.60** | **$120.09 $123.37
Total, 118 guests $14,231** | **$14,171 $14,558
Staffing ratio 1:30 1:18 1:22
China and glass Rented separately Included Rented separately
Remedy clause None Yes, 100% cap Yes, 150% cap
Balance due −21 days −14 days −14 days
Certificate produced Not yet, after 3 weeks 2 days 4 days

Worked: Harvest & Thyme = $78 + 24% SC ($18.72) + 3% admin ($2.34), tax 7.75% on food + SC ($7.50), gratuity 18% of food ($14.04) = **$120.60. Sundown = $94 + 20% SC ($18.80), tax on food only ($7.29), no gratuity = **$120.09. Copper Kettle = $85 + 18% SC ($15.30), tax on food + SC ($7.77), gratuity 18% of food ($15.30) = $123.37.

On loaded cost the three are within $387 of each other — 2.7%.** The $16 spread in menu price has almost entirely disappeared, and the lowest menu price is no longer the lowest cost.**

On everything else they are not close. Sundown includes china and glass (worth ~$1,850), staffs at 1:18 against Harvest & Thyme's 1:30, distributes its service charge, and produced a certificate in two days. Harvest & Thyme has no remedy clause, wants the balance a week earlier, and has not produced a certificate in three weeks.

Adjusted for the china, Sundown is cheaper than Harvest & Thyme by about $1,910 and cheaper than Copper Kettle by about $2,240 — and it is also the lowest-risk of the three. That happens more often than the industry's folklore suggests, and it is only visible if you build the sheet.

The exclusions column is where proposals actually differ

Three proposals that appear to be for the same thing are almost never for the same thing, and the difference lives in what each one silently omits.

⚡ Quick Reference: what proposals commonly exclude

Category Frequently excluded, and what it costs to supply
Catering China, glass, flatware ($12–$18/guest) · linens · staff for non-food service (coat check, bathroom attendants) · cake cutting · vendor meals · the plating equipment a raw site needs
Bar Glassware · ice · mixers and garnish · the alcohol itself · a licence · bar structure · liability insurance for liquor
Floral Vessels (rented or purchased — a large difference) · installation labour · strike and removal · candles · delivery beyond a radius
Photography Second shooter · engagement session · album · travel and accommodation · rights beyond personal use · hours beyond the package
Music Ceremony sound · cocktail-hour coverage · MC duties · uplighting · a power drop · overtime rate
Rentals Delivery and collection · setup and breakdown (often a separate line) · damage waiver · late-night strike premium · levelling on uneven ground
Lighting Power distribution · rigging · a technician on site during the event · dimming control
Tent Flooring · sidewalls · lighting · heating · permit and engineering drawings · levelling

The single most useful question to put in an RFP: "Please list what is not included."

Most vendors will answer it honestly, most have never been asked, and the answers make three proposals comparable in a way that no amount of price analysis can.

🔄 Check Your Understanding

  1. Three caterers quote $78, $94, and $85 per head. After loading, they land within 2.7% of each other. What does that tell you about how to spend your comparison effort?
  2. Why is "please list what is not included" more valuable than "please itemize your pricing"?

Verify

  1. That price is not where the decision lives. The headline spread of $16 nearly vanishes once service charges, distribution, admin fees, and tax bases are applied. Comparison effort should go to scope — what is included and excluded — and to risk: staffing ratios, contract terms, insurance, and how they behaved when asked for a certificate.
  2. Because an itemization tells you what a vendor is charging for; an exclusions list tells you what you will have to buy from somebody else. In the worked case, Sundown's included china and glass were worth ~$1,850 — more than the entire spread between the three loaded totals — and no itemization would have surfaced it as a comparison.

12.7 Negotiating

Everything in Chapter 6 §6.4.1 and Chapter 8 §8.7 applies. Three additions specific to vendors.

Attack the base, not the rate. Reducing a food subtotal by menu construction saves the service charge and the tax with it. Asking for a discount saves a percentage of a percentage and costs goodwill.

Two asks on the contract, and pick the two that matter for this category (Chapter 8 Case Study 2's ask matrix).

And the third, which is specific to this chapter:

📋 The Planner's Script: asking a vendor to come down

Never: "Can you do better on the price?" It is an invitation to discount, which good vendors resent and which bad vendors accommodate by removing something you will not notice until the day.

Instead — give them a target and a constraint, and let them solve it:

"Your proposal's at fourteen-eight and I've got twelve-five for catering. I don't want you to just cut the price — I'd rather you tell me what you'd change to get there, because you know your costs and I don't.

For what it's worth, the couple ranked food first, so I'd protect the food. Everything else is negotiable."

Why this works: - It is a calibrated question (Chapter 3's further reading): they solve your problem using knowledge you do not have. - It explicitly declines a straight discount, which protects their margin and their dignity. - It tells them what to protect, which means the cut lands somewhere the client will not mind. - It gives a real number rather than "as low as you can go."

What comes back is frequently better than what you would have asked for: three canapés instead of five, a less expensive protein done well, family style instead of plated, one fewer server offset by a simpler service. A caterer solving a $2,300 gap with their own knowledge produces a better wedding than a caterer discounting $2,300.

And if they cannot:

"Understood — thanks for being straight with me. Let me go back to the couple, because it may be that the number moves rather than the menu."

Then actually go back. A vendor who says "I can't do that well for that money" has done you a service, and they should hear that you treated it as one.


12.8 Coordinating, and Being Worth Working With

The ongoing relationship, and the part that determines whether you get the 2 p.m. phone call.

⚡ Quick Reference: what makes a planner good to work with

Ranked by what vendors actually say, which is not what planners assume.

1 Pays on time, every time. Nothing else is close
2 Sends the floor plan and the timeline when promised, not the week of
3 Tells them early when something changes. A change at −6 weeks is a scheduling matter; the same change at −6 days is a crisis
4 Feeds the crew properly, and asks how many rather than guessing
5 Knows their constraints — load-in time, power, strike, crew size — and does not schedule against them
6 Answers the phone
7 Defends them to the client when the client is being unreasonable
8 Says thank you afterward, specifically
9 Does not beat them down on price
10 Does not treat them as staff

Note what is not on the list: being nice, being friendly, being fun to work with. Vendors are professionals and they value professional behaviour. The friendliest planner in the market who pays late is the one nobody wants.

🔍 Why Does This Work?

Why is paid on time first on that list, ahead of everything about communication, respect, or how pleasant a planner is to be around?

Because of who these businesses are. A florist, a photographer, a band, and a small caterer are cash-flow-constrained businesses with lumpy income (Chapter 7 §7.2.1). A late payment is not an administrative annoyance; it is a supplier they cannot pay, a payroll they have to cover from savings, or a decision about whether to take a job next month.

And it is the one thing on the list that a planner can get right with no skill at all — it requires only a calendar. Which is precisely why failing at it is read as a statement about how seriously you take the relationship.

The corollary is useful: a planner who pays on time, reliably, for two years is operating in the top tier of their market on the criterion vendors weight most heavily, and it costs nothing but attention. There is no other professional advantage available this cheaply.

Two practices worth naming:

Vendor meals. They are in most contracts, they are the most commonly omitted budget line (Chapter 6 §6.5), and the way they are handled is a signal read by everyone. Ask each vendor how many crew, and feed them the same food the guests eat, at a table, at a reasonable time. The cost is $30–$40 each; the goodwill is disproportionate. A crew fed a sandwich in a hallway at 9 p.m. will work the wedding and will remember.

The pre-event call. Two weeks out, ten minutes, with each significant vendor. Not an email. What time are you arriving, what do you need from me, and is there anything about this site that worries you? That third question has surfaced more real problems than any document in this book.

🚨 When It Goes Wrong: the vendor who told the client instead of the planner

(Tier 3 — illustrative.)

The situation. Nine days out, a florist realizes she cannot source the specified garden roses — a crop failure at her supplier, no alternative at the price. The substitution changes the palette noticeably.

What she did: emailed the bride directly, apologetically, offering three alternatives.

What happened: the bride, nine days out and already at peak anxiety, read an email from a vendor saying something had gone wrong. She called the planner in tears. The planner had not known.

The planner's failure, not the florist's:

  1. The florist had never been told the planner was the point of contact. It had been assumed rather than stated.
  2. There had been no pre-event call. Question three — "is there anything about this site or this order that worries you?" — would very likely have surfaced the supply risk a week earlier.
  3. The RFP had specified a variety without a substitution clause (Chapter 8's ask matrix: for florists, ask 1 is approval for variety substitution).

What to do about it, structurally:

In the RFP and again at booking: "One practical thing: please route anything that changes through me rather than the couple. Not because they're fragile — because I can usually solve it before it needs to be a conversation, and if it does need to be one, I'd rather it came from me with a solution attached."

Almost every vendor will do this gladly. Most of them have never been asked.


12.9 Practical Considerations

Build the matrix in month three from a walk through the day, not from the contracts.

Ask the sourcing question — "if you were getting married, who would you use?" — of every vendor you respect. It costs nothing and it is the best channel there is.

Use the failure question in every reference call.

Send the same RFP to three vendors on the same day, and tell them how many you asked.

Build the comparison sheet with all three sections: cost, scope, risk.

Give a target and a constraint rather than asking for a discount.

Make the pre-event call.

Feed the crew.

Common mistakes:

  1. Sourcing by search. A ranking of marketing spend.
  2. Building the matrix from memory — the seven categories get skipped and one has the truck.
  3. Reference calls that ask "were you happy?"
  4. Comparing headline prices. Chapter 6's loaded rate exists for this.
  5. Comparing on cost and ignoring risk.
  6. Different briefs to different vendors, then comparing the proposals.
  7. Asking for a discount instead of giving a target and a constraint.
  8. Not stating that you are the point of contact, and assuming it is understood.
  9. Skipping the pre-event call.
  10. Treating vendors as staff. They are colleagues, several are more experienced than you, and none of them report to you.

Things to do this week:

  • Build the vendor matrix template with every column
  • Ask three vendors the sourcing question
  • Write the four reference questions on a card
  • Build the RFP template
  • Build the three-section comparison sheet

12.10 Chapter Summary

Key concepts

  • You are assembling a temporary company — eighteen businesses and forty to fifty people who have never met, working sequentially and interdependently for eight hours, none of whom report to you. Your authority is borrowed and voluntary, from the client's delegation, your observed competence, and the relationship.
  • The test: if a vendor found a problem at 2 p.m., would they call you?
  • Sourcing runs on networks, not searches. The best question is "if you were getting married, who would you use?" — not "who would you recommend?" Then: "and who would you avoid?"
  • The network runs on reciprocity, tracked informally, slowly, by everyone. Build it before you need it.
  • The vendor matrix is the source of truth, and the certificate table, contact sheet, power budget, timeline, and vendor-meal count are all filtered views of it. Build it from a walk through the day, not from the contracts — or you will skip rentals, transport, tent, lighting, restrooms, generator, and parking.
  • Vetting, in increasing usefulness: portfolio read for consistency not highlights · reference calls · contract behaviour · seeing them work.
  • The reference questions: what did they do better than expected · what did you have to manage · tell me about a time something went wrong — what did they do · would you use them again, and what would you do differently.
  • The failure question is the one that matters. Every vendor has failures; you are learning what they do with them.
  • Send the same RFP to three vendors on the same day, include the site's constraints and the relevant vision extract, and tell them how many you asked. State a budget range and invite them to say if it is unrealistic.
  • Compare on three sections: cost, scope, risk. In the worked comparison, three caterers whose menu prices spanned $16 landed within 2.7% on loaded cost — and were not remotely comparable on staffing, inclusions, contract terms, or insurance.
  • Give a target and a constraint; never ask for a discount. "I've got twelve-five, tell me what you'd change, and protect the food." What comes back is usually better than what you would have asked for.
  • 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 · specific thanks. Not friendliness.
  • Say you are the point of contact, in writing, at booking. Most vendors have never been asked and will gladly comply.

Action items

  • [ ] Build the vendor matrix template
  • [ ] Ask three vendors the sourcing question
  • [ ] Put the four reference questions on a card
  • [ ] Build the RFP and comparison-sheet templates

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 — not the headline — 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. Would you be comfortable if this vendor were the one thing that went wrong?

A "no" on 6 stops the engagement (Chapter 8 CS1). A "no" on 2 is worth another reference call before proceeding.


Spaced Review

Answer before opening.

  1. (From Chapter 9) What is the difference between a certificate holder and an additional insured, and why does it matter?
  2. (From Chapter 6) Compute the loaded rate for a $90 menu price with a 22% service charge (not distributed), 8% tax on the SC-inclusive base, and an 18% gratuity.
  3. (Bridging) Chapter 8 said the priority order is vet → insure → draft. This chapter is the first of the three. Explain why vetting outranks drafting, and identify the one situation in which that order should be reversed.
Answers 1. Certificate holder is simply the party the certificate was issued to — an address, conferring nothing. Additional insured means the party has been added to the policy by **endorsement**, and is what venues require. A certificate listing the venue only as certificate holder **looks correct and does nothing.** 2. $90 × [(1.22)(1.08) + 0.18] = $90 × [1.3176 + 0.18] = $90 × 1.4976 = **$134.78.** 3. Because **a contractual right against a vendor who has failed is a claim, not a performance.** Drafting allocates responsibility between parties; it cannot make a vendor competent, solvent, or present. Vetting reduces the probability that the clause is ever needed. **The reversal:** where you have no choice of vendor. A venue's exclusive caterer, a required approved list of one, or a destination market with a single supplier of something — there, vetting produces information but no decision, and the contract becomes the only instrument you have. **In that situation, spend the asks you would otherwise have saved** (Chapter 8's two-ask rule relaxes), because the alternative to a good clause is nothing.

What's Next

In Chapter 13: Rentals and Production, we order the physical objects. Building a rental order from a floor plan and a guest count, sizing a tent and understanding its subsystems, calculating power load and generator size, sequencing a load-in that actually fits the access window, and reading a rental contract's damage and delivery terms. It is the chapter where Chapter 10's constraint list finally becomes a purchase order.

Before you go on, build the matrix and issue the RFP. Chapter 13 orders from vendors you have selected.


📐 Project Checkpoint: the Reyes–Whitfield vendors

Tier 3 — Illustrative. The Reyes–Whitfield wedding is a composite created for this book.

1. Build the matrix. Walk the day from 7 a.m. to 2 a.m. and list every business that appears at Wildrye Farm. You should find at least fourteen, and at least four of them are in Chapter 9's commonly-skipped categories. Build every column.

Then mark, for each: vehicle on site? foot on site? load-in time required? power required? crew size and meals?

2. Source three caterers. Write the sourcing question as you would ask it, and name who you would ask it of — remembering that at a raw site with no kitchen, the vendor most likely to know which caterers can work in a field is a rental company or a tent supplier, not another caterer.

3. Write the RFP. All seven sections, one page, for catering. The constraints section is the important one: no commercial kitchen, two 20-amp circuits, vehicle access from noon, all property removed by 10 a.m., no open flame, amplified music ends 10:30, 90 minutes from the city, and a 32-inch interior doorway (Chapter 10) that some hot boxes will not fit through.

Include the relevant vision extract: the sentence, the ranking position (food is first), and the vetoes.

State the budget — $11,800 from the Chapter 6 allocation — and include the invitation to tell you if it is unrealistic.

4. Compare the three proposals using the §12.6 figures (Harvest & Thyme $78, Sundown $94, Copper Kettle $85, with their respective terms). Build all three sections. Then answer:

  • Which is cheapest on loaded cost?
  • Which is cheapest adjusted for what is included?
  • Which is lowest risk?
  • Which do you recommend, and what is the sentence you say to Alicia?

Note that Harvest & Thyme is the caterer who fails to appear in Chapter 1's cold open. You now have, in front of you, the three signals that would have predicted it.

5. Write the negotiation. Sundown comes in at $14,521 all-in against an $11,800 allocation. Give them a target and a constraint. Write it.

6. Write the point-of-contact sentence you send every vendor at booking.

File it in Reyes–Whitfield. Chapter 13 orders the tent, the tables, and the generator.


Chapter 12 Exercises → exercises.md

Chapter 12 Quiz → quiz.md

Case Study: The Three Signals → case-study-01.md

Case Study: One Caterer, Three Proposals → case-study-02.md

Key Takeaways → key-takeaways.md

Further Reading → further-reading.md