Key Takeaways — Chapter 5: The Guest List

1. Guest count is the master variable. In the worked example, cutting thirty names produced the same saving as five substantial compromises to the wedding itself — band to DJ, no videographer, 40% less floral, buffet instead of plated, and a reduced bar. And the smaller wedding with all five of those intact was, by any measure a guest would apply, the better wedding. You cannot have a big wedding and a nice wedding on a fixed budget. Which one you want is a real question with no wrong answer; the planner's job is to make sure it is asked out loud rather than decided by default.

2. Costs split three ways, not two: fully variable (food, bar, place settings, chairs, favors), step-function (tables, servers, bartenders, restroom brackets, tent frames, shuttles, dance floor, generator), and fixed (photography, music, venue fee, attire, planner). In a typical wedding about 62% of the budget responds to guest count.

3. Steps are where the money is. Guest 141 costs $160. Guest 145 costs $567. Guest 151 costs $1,280. Same wedding, same week. Between thresholds a guest is cheap; crossing one is expensive.

4. Never use average cost per guest for a decision. It is wrong in both directions — it overstates the marginal cost by including fixed costs, and it hides every step. Build a step map instead, and be the only person in the room who can answer "what would eight more cost?" in fifteen seconds.

5. Cut to a threshold, never past it. At 154 guests, cutting four names saves $2,737 and cutting nine saves $3,530. The first four are worth $684 each; the next five are worth $159 each. Tell the client exactly that.

6. Every name needs five attributes: household, owner, tier, category, travel. The owner column is what turns "we need to cut twenty-six" from an argument about who loves whom more into arithmetic both people can check. Fairness is what makes a cut survivable.

7. Give contributing parents a fixed allocation of names, and invert the ask: "here are forty-six, they're yours" rather than "cut eight." Identical arithmetic, completely different conversation, and reliably faster. Same mechanism as Chapter 3's contributor role menu.

8. Sort before you cut. Ask the couple to sort names into categories they define, on a low-stakes phone call, before any cut is on the table. Sorting is nearly painless; cutting from a sorted list is largely mechanical.

9. Three policies, decided early and applied without exception: plus-ones, children, coworkers. Any policy applied consistently is defensible; no policy applied inconsistently is. Guests object to discovering that someone comparable to them got something they did not — never to the rule itself.

10. Forecast attendance by category. Roughly 75–85% overall for a local wedding, 55–70% when most guests travel. Long-haul social friends (35–55%) are the most over-estimated category, because couples apply a close-friend intuition to it.

11. Under-forecasting is worse than over-forecasting. Over-forecasting wastes money invisibly; under-forecasting fails in front of every guest. Every industry convention reflects this.

12. Size step items to the plausible high; size variable items to the guarantee. The distinction is reversibility, not uncertainty: a 40′ tent booked in month four cannot become a 50′ tent in week two, but food can be adjusted until ten days out. When you cannot change your mind, buy the version that survives being wrong. When you can, wait.

13. The RSVP deadline is a fiction. Set it five weeks out against a guarantee due at 10–14 days, and use the gap for two chase passes run by the couple, not by you. Non-responders at the guarantee count as not attending — and the couple must be told that in advance.

14. Guarantee the confirmed yes count plus 2–3%. Never the forecast; never the invitation count.

The A/B list

Ethical if the second wave lands more than three weeks out and the tiers never leak. Three absolute rules: never label tiers in a shared document, never discuss them in a group chat, never send after the cutoff. And do not let the wedding party know the tiers exist.

The objection — that it requires ranking friends — misses that the budget forces the ranking either way. Refusing to tier does not produce a wedding where everyone is invited. It produces one where the ranking happened silently, earlier, and with fewer people invited overall.

Common Mistakes

• Treating guest count as a constraint rather than a variable — the most expensive error in the chapter
• Using average cost per guest for a decision
• Cutting more names than necessary because nobody built a step map — this one is cruel as well as sloppy
• A "maybe" column instead of tiers
• Case-by-case plus-ones
• No children policy, or one defined by an adjective — "nieces and nephews" is a rule; "close family" is a fight in month eight
• Letting the couple believe the RSVP deadline will work
• Guaranteeing the invited count
• Labeling the B-list in a shared document
• Saying a number before you have built the step map — a wrong estimate here is not a neutral error. Too high and the client freezes; too low and you have to come back

Decision Framework — how many names must be cut?

1. Compute the deficit in dollars.
2. Build the step map for this specific event.
3. Working downward from the current count, identify the nearest step crossings.
4. Find the smallest cut that closes the deficit.
5. Allocate proportionally by owner.
6. Deliver it as arithmetic, with the number, in one conversation — and lead with your own error if you made one.

Numbers Worth Remembering

All illustrative and regionally variable. Build your own numbers from five weddings' worth of predicted-versus-actual.

Your Project

You should now have, in Reyes–Whitfield: the 186-name list restructured into the five-column architecture with all four owners allocated; a full step map for Wildrye Farm between 110 and 190 with assumptions stated; an attendance forecast by category; the smallest cut that closes the gap, with its precise value and its proportional allocation; a written position on whether Sam's parents' $6,000 buys names and the fixed-allocation version of that conversation; a written position on where you will refuse to look for cuts, given Rosa Reyes; the cut conversation itself; and the three policies with the plus-one cost computed against the step map.

And the finding from Case Study 2 that Chapter 6 has to deal with: at $158.52 fully variable per guest and $16,170 of fixed cost, this budget supports roughly 100 guests, not 140. Chapter 6 is where that becomes a conversation.