Case Study 1: The Three Signals

Tier 3 — Illustrative. Harvest & Thyme Catering, the Delacroix wedding, and all figures are composites created for teaching. This case returns to the failure that opened Chapter 1 and examines it a third time — from the vetting side.

Why This Case Appears Three Times

Chapter 1 told the story: a caterer who did not arrive at 4 p.m. with 150 guests due at six.

Chapter 8 examined the contract: no remedy clause, liability capped at amounts received, all payments non-refundable, and no insurance provision. The Delacroix family recovered nothing.

This case asks the only question that would actually have prevented it: could anyone have known?

The answer is yes, and the evidence was available in month three, and it was three separate signals that nobody assembled.

The Booking

Month three. Three caterers proposed for a 150-guest wedding at a rented hall with a small warming kitchen.

Harvest & Thyme was $1,500 cheaper than the next, and the couple chose them.

That was a defensible decision. On the numbers as presented, they were the value option, their tasting had been excellent, and the owner was personable and enthusiastic.

Three other things were true and were not assembled.

Signal One: the contract

The planner read it. Chapter 8 lists what she found:

§8 "Caterer shall use commercially reasonable efforts to perform." §9 "In no event shall Caterer's liability exceed the amounts actually received from Client." §5 "A deposit of thirty percent is due upon execution. The balance is due fourteen days prior. All payments are non-refundable." §12 "Neither party shall be liable for failure to perform due to acts of God, war, or civil disorder."

No insurance provision. No substitution clause. No postponement clause. No access or load-out terms.

She read it and filed it, because it looked like a small caterer's standard form, which it was.

What she did not do was compare it to the other two.

Read as a set, the pattern is unmistakable. Two contracts written by businesses with counsel and one written by a business protecting itself from its own fragility.

Read alone — which is how it was read — it looks like a short contract from a small vendor.

🎤 From the Field: Comparison is the cheapest possible contract audit.

Reading one contract requires you to know what a good one contains. Reading three side by side requires only that you notice the differences, and the differences leap off the page.

This is the argument for the RFP going to three vendors (§12.5) that has nothing to do with price. Three proposals produce three contracts, and three contracts produce a comparison that no amount of expertise applied to one document can substitute for.

Signal Two: the reference call

The planner made one. Here is the transcript, near enough.

Planner: "I'm looking at Harvest & Thyme for a wedding in September. Would you use them again?"

Reference: "Oh, absolutely. The food was fantastic. Everybody said so."

Planner: "Anything I should know?"

Reference: "Not really. They were lovely."

Six sentences. Nothing operational. And it was recorded as a positive reference.

Here is the same call with the §12.4 questions:

Planner: "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?"

Reference: "Sure."

Planner: "What did they do better than you expected?"

Reference: "The food, honestly. It was genuinely excellent. Better than the tasting, which never happens."

Planner: "What did you have to manage?"

Reference: (pause) "...They were late setting up. Not disastrously — about an hour and a half. And there were fewer staff than I'd expected, so service was slow. Dinner ran long."

Planner: "Tell me about a time something went wrong. What did they do?"

Reference: "Well — that was it, really. The lateness. Their van had a problem. They didn't call, though. We found out when they weren't there. That was the part I minded, honestly — not the being late, the not knowing."

Planner: "Would you use them again, and anything you'd do differently?"

Reference: "Probably? The food was so good. But I'd want a phone number for someone who actually answers."

Every one of those answers is available in the first version of the call and none of them are volunteered. The reference was not concealing anything. Nobody asked.

What the second version tells you:

• Late, without notice
• Understaffed
• A communication failure under pressure — the failure question, answered
• And a specific, actionable caveat: "a phone number for someone who actually answers"

That last line is the whole case, eight months in advance, delivered by someone who was trying to be helpful.

Signal Three: the certificate

Requested in month three. Not received.

Chased in month five. "I'll get my guy to send it."

Chased in month seven. "Sorry — will chase him this week."

Never received.

The planner did not escalate, because the venue was a rented hall with a modest insurance requirement, because the caterer was pleasant and apologetic each time, and because the request had become a routine item on a list rather than a signal.

⚠️ Common Pitfall: the chase that becomes routine

A document requested three times and not received has stopped being an administrative matter and become information. The transition happens somewhere around the second chase, and it is easy to miss because the third chase feels like the second one.

The fix is a rule, not vigilance: if a certificate has not arrived after two requests spanning three weeks, it goes on the risk register and the client is told.

A rule fires whether or not you are paying attention. Vigilance does not.

Assembling Them

Any one of the three signals is survivable and explicable.

• A short contract from a small caterer is ordinary.
• A vague reference is ordinary.
• A slow certificate is extremely ordinary.

Together they are a picture, and the picture is: a business with no counsel, no insurance it is willing to evidence, thin staffing, a history of failing to communicate under pressure, that wants the full balance a week earlier than its competitors and disclaims all responsibility if it does not perform.

That is a business in trouble, and it was in trouble in month three, and it failed six weeks after the wedding.

💰 Run the Numbers: what the three signals were worth

	Cost of catching it in month three	Actual cost
Comparing three contracts side by side	25 minutes	—
Four reference questions instead of two	6 minutes	—
Escalating the certificate at the second chase	10 minutes	—
Total	41 minutes	—
Switching to Marchmont in month three	+$1,500	—
Emergency substitute caterer on the day		$15,400
Paid to Harvest & Thyme, unrecovered		$14,400
Actual cost		$29,800

Forty-one minutes and $1,500, against $29,800.

And the $1,500 is the honest part of that comparison: **choosing the safer caterer was not free.** A planner who recommends the more expensive option on the strength of a contract comparison and a reference call is spending real money on a risk that will probably not materialize. Most of the time, Harvest & Thyme delivers dinner and the $1,500 was wasted.

That is what risk management is, and it is why it is hard to sell.

What the Planner Said Afterward

She was good. She solved it on the day in twenty-eight minutes with a network built over four years, and no guest knew.

Her own note, written the following week:

"I read the contract and didn't compare it. I made the reference call and asked the wrong questions. I chased the COI three times and let it become a chore instead of an answer. All three were in front of me in March.

The thing I keep coming back to is that none of them felt like a warning at the time. They felt like admin."

That is the accurate diagnosis, and it generalizes: the signals that matter rarely feel like signals. They feel like paperwork, and they are noticed only by a process rather than by attention.

Post-Mortem

Root cause: three independent warning signals were each assessed in isolation and none was assessed as a set.

Contributing causes:

1. The contract was read but not compared. Comparison is the cheapest possible audit and it was available — two other contracts were on file.
2. The reference call asked "were you happy?" Every fact that mattered was available and unvolunteered.
3. The certificate chase became routine rather than escalating. There was no rule, only intention.
4. The price difference was framed as a saving. $1,500 cheaper reads as value; it should also have read as a question — why is one of three caterers 8% below the others on loaded cost while staffing at 1:28?

What went right: the recovery, the network, the discipline of not telling the couple mid-event, and — genuinely — the honest note afterward, which is how a planner turns a failure into a practice.

Transferable rules:

1. Compare contracts across bidders. Twenty-five minutes, and the differences leap off the page.
2. Ask the four reference questions. Six minutes, and everything the reference knows becomes available.
3. Make the certificate chase a rule with a trigger, not a task on a list.
4. A price meaningfully below two comparable bids is a question, not a saving.
5. Assemble the signals. Any one is ordinary; the set is a picture. Build the risk section of the comparison sheet (§12.6) so the assembly happens on paper rather than in your memory.
6. The signals that matter feel like admin. Which is why they need a process rather than attention.

Discussion Questions

1. Choosing Marchmont would have cost $1,500 more and — most of the time — bought nothing. How do you present that trade to a client in month three, when the risk is abstract and the money is real?

2. The reference gave a positive verdict and described lateness, understaffing, and a communication failure. Is that a positive reference? What does it tell you about how much weight to give a reference's overall verdict versus their specific answers?

3. The planner's note says the signals "felt like admin." Design the process — not the intention — that would have assembled them. Where does it live, and what triggers it?

4. Harvest & Thyme's food was genuinely excellent and their tasting was the best of the three. How much should that weigh against the three signals? Is there a level of quality at which you accept the risk?

5. The case concludes that the price difference should have been "a question, not a saving." At what margin below comparable bids does a price become a signal? Is there a rule, or is it judgment?

Mini-Project

Build the risk register.

A one-page document per engagement, listing every open risk with: what it is, what would trigger escalation, who owns it, and the date it was last reviewed.

Populate it with the things that feel like admin:

• Certificates requested and not received (trigger: two requests over three weeks)
• Contracts with absences you asked about and did not get (Chapter 8's documented refusals)
• Permits filed but not granted (trigger: within 14 days of the stated lead time)
• Vendors who have not confirmed a load-in time
• Any vendor whose price is more than 8% below comparable bids
• Any reference that produced no operational detail

Then add the rule that makes it work: review it at the same weekly sitting as the budget tracker (Chapter 7 §7.1). Fifteen minutes for the budget, three for the risk register, all engagements in one pass.

Test it against this case: at what point does your register fire on Harvest & Thyme? If the answer is later than month five, tighten the triggers.

References

Tier 3 — Illustrative. Harvest & Thyme Catering, Bellwether, Marchmont, the Delacroix wedding, and all figures and quoted contract language are composites created for teaching.

Related chapters: The failure as narrative — Chapter 1. The contract analysis — Chapter 8 CS1. Reference questions — Chapter 12 §12.4. The comparison sheet — Chapter 12 §12.6. Certificate chasing and the two-deadline structure — Chapter 9 §9.3. The weekly review that the risk register attaches to — Chapter 7 §7.1. Emergency substitution on the day — Chapters 27 and 28.