Answers to Selected Exercises

What is here.

Every starred (★) exercise in Chapters 28–41 — 430 of them — has a worked answer below. That is the promise those chapters make at the head of their exercise sets, and this appendix keeps it.

For Chapters 1–27, which promise selected solutions, three exercises per chapter — eighty-one in all — are answered here — chosen because they have a definite answer or a method that can be checked. The remaining exercises in those chapters, and every Part D and Part E item in the book, are open-ended by design; rubrics for them are in the instructor guide.

How to read the answers.

Where an exercise has a computable answer, the arithmetic is shown. Where it does not — most of Parts C, D, and E — what appears is a rubric: what a strong answer contains, what a weak one does, and where the interesting disagreements are. A rubric is not a way of avoiding the question. Several of these exercises ask you to attack a claim this book makes, and in those cases the rubric names the attacks that land, including the ones the book does not survive.

Two standing cautions.

📜 Every dollar figure below is Tier 2 or Tier 3. Prices, ratios, and industry norms vary by country, city, season, and year. The arithmetic transfers completely; the numbers transfer not at all. See Appendix B.

And the answers to the case-study and field exercises are not the point of doing them. Reading that a guest walk typically finds six to twelve hesitations is not the same as walking one, and this appendix cannot substitute for the exercises that send you outside.

Part One — Chapters 1–27, Selected Solutions

Three exercises per chapter, chosen because they have a definite answer or a method that can be checked. The open-ended items in Parts C, D, and E are covered by rubrics in the instructor guide.

Chapter 1 — The Events Industry

B.1 — Reconstruct the quote. Besides the eight hours: travel to and from · a pre-wedding meeting and a timeline call · culling and editing, which is 15–30 hours for a full wedding · gallery hosting and delivery · equipment depreciation and insurance · second-camera bodies carried as backup · the print release · and the unbillable enquiry and proposal hours (Ch.36).

Total realistic hours: 40–55. $4,200 ÷ 48 ≈ $87/hour of gross revenue — before equipment, tax, insurance, and the 40–65% billable ratio, which puts the take-home nearer $30–40 an hour. The lesson is Chapter 37's, arriving in Chapter 1: an event-day fee is a fraction of the hours it pays for, and this is the arithmetic every vendor at the wedding is doing about themselves.

B.3 — The Saturday arithmetic. The method, and only the method transfers:

(a) target take-home                        e.g. $45,000
(b) events physically servable = your hours ÷ hours per event
    at 150 hrs full-service and ~1,100 billable hours → ~7
(c) required fee = (a) ÷ (b)                      $6,428
(d) with 30% to expenses and self-employment tax:
    required gross = (a) ÷ 0.70 = $64,285
    → fee = $64,285 ÷ 7 = $9,184
(e) is that sellable in your market?

(d) is the step everybody omits and it moves the answer by about 43%. If (e) is no, Chapter 37's answer applies: you have a positioning problem, not a pricing problem — change the service level, the client, or the number of engagements, not the courage.

B.6 — Read the incentive.

The general point: every model has an incentive that runs against the client, and the professional move is to name yours out loud — which also happens to be the most persuasive thing you can do in a first meeting.

Chapter 2 — What a Planner Actually Does

B.1 — Find the inclusions error. Every unmeasurable term is one where you and the client could disagree about whether it happened. Rewrite with counts:

"Unlimited email" → "replies within one business day, and up to four scheduled calls." "Vendor management" → "management of the six vendors named in Schedule A." "Design support" → "one mood board, one revision, and a floor plan." "Full-day coverage" → "present from 10:00 until 30 minutes after the last scheduled event, up to 12 hours." "As much help as you need" → delete; it cannot be written into any list.

B.5 — Price the tiers coherently. With full-service at $5,200 and the §2.1 hour counts, the naive answer divides by hours and produces something like partial $2,700 and month-of $1,600.

That is wrong for month-of, and the reason is Chapter 36's: every tier carries the same 12–18 hours of per-client overhead — enquiry, contracting, onboarding, invoicing, debrief — and that overhead does not shrink with the tier. A month-of priced at the full-service hourly rate loses money on every engagement.

Adjust by loading the overhead equally rather than proportionally: take the fixed per-client cost out first, divide the remaining hours at a common rate, then add the fixed cost back to every tier. The effective hourly rate then rises as the tier falls, which is the correct shape (Ch.37).

B.7 — Diagnose the tent. The four documents: the venue contract (what the site provides), the rental order (what was hired), the floor plan (what has to fit), and the guest count (how many it must hold). The conflict was visible the moment any two of them were laid beside each other.

The routine that surfaces it at month two: a scheduled cross-check of exactly those four, at the point the guest count is first estimated — which is Chapter 39's trigger set, arriving thirty-seven chapters early. Nothing here required expertise. It required a moment at which four documents are opened together.

Chapter 3 — Client Management

B.1 — Translate the proxies. The three-part response, every time: the literal answer · the fear named · a next concrete step with a date.

"Are you sure the barn is big enough?" → (a) "Yes — 211 for a ceremony in rows, and we're 100." (b) "I think what you're really asking is whether people will be crammed in." (c) "I'll bring the floor plan on Thursday and we'll walk it."

The pattern to check in your own answers: the literal answer alone never works, because the question was not literal — and naming the fear is what stops it being asked again in three weeks in a different form.

B.4 — The excluded budget. The questions: "does that include the rings? the dress and suit? hair and makeup? the honeymoon? the rehearsal dinner? transport? accommodation? gratuities? stationery and postage? my fee?"

Using Chapter 1 §1.2's proportions, the categories couples most often omit total roughly 15–25% of a wedding's real cost — and gratuities alone are 1–2% and appear in cash in the final week (Ch.30 B.6). A client who says $50,000 usually means $50,000 of the visible categories and is describing a $58,000–62,000 event. Establish it in meeting one, in writing, or Chapter 6 begins from a false total.

B.6 — Diagnose the silence. Five observable behaviours: one partner answers and the other watches them answer · a pause before a number, and a glance · "we'd love to but..." with no completion · a decision made in the room and reversed by email that evening · and somebody not in the room being cited by name in three separate answers.

All five are Chapter 3's central point: decision rights are visible in a consultation and are almost never where the seating suggests.

Chapter 4 — Discovery and Vision

B.1 — Translate ten words. Every abstract word must become three specifications from three different categories, or it has not been translated.

"Intimate" → lighting: everything under 8 ft, no overheads after dark · layout: long tables, 24-inch spacing, one room · service: family style, so people pass things. And the question that finds which they mean: "when you say intimate, is that about how it looks or about how it feels to be there?"

A translation that produces three specifications in one category has not translated the word — it has decorated it.

B.3 — Price a board. Rubric. For each of five images: name the cost driver (volume · installation · scarcity · labour · venue), give a range for your market, and design the 70–80% version at under a third.

The arithmetic that must be shown on at least two, and the recurring finding: the cost is almost never the flowers. A ceremony installation is labour and structure; a 200-stem table is volume; February peonies are scarcity; a hanging anything is installation plus a rigging conversation (Ch.34). Cut the driver, not the look — foliage and candles at $450 against a $6,000 full design is Chapter 28's floor column, and it photographs.

B.7 — Diagnose the ranking failure. They ranked flowers first because flowers are what a wedding is supposed to be about, not because they care. The behaviour is the data: four months of no questions is the real ranking, and the stated one was aspirational or borrowed — often from a parent, sometimes from a board.

What you ask: "Can I check something — you put flowers first in February and you haven't asked about them since. Was that ranking yours, or does it just feel like what you're supposed to say? Because if the money's better spent somewhere else, now's the time." Asked once, warmly, and it usually relocates several thousand dollars.**

Chapter 5 — The Guest List

B.4 — Find the smallest cut. 168 guests, $4,600 over. Catering $88 + 24% service + 8% tax. Bar $26. Steps at 160 ($340), 152 ($850), 150 ($480). A table every 8 guests at $135.

Loaded catering per head: 88 × 1.24 × 1.08 = $117.85.** **Plus bar $26 = $143.85 variable per guest.

The smallest cut is nineteen names, to 149, saving $4,673.15.** **Note that 150 gets to $4,529.30 and falls $70.70 short — which is the kind of near-miss that makes a couple want to argue with the arithmetic.

And the sentence for the client: the first eight names you cut are worth $203 each and the ninth through sixteenth are worth $267 each, because there are things behind them. After 150 a guest is worth $143.85 and nothing else happens. Which is why the cut is nineteen and not thirty.

B.6 — Allocate a cut. 24 names from 172. A 71, B 44, A's parents 38, B's parents 19. Contributions: A's parents $18,000, B's parents $4,000, the couple $22,000.

(Contribution-weighted: each party's weight is their share of the list divided by their share of the money, normalised — so a party paying more is asked to cut less.)

Recommend proportional, and present it as arithmetic rather than as judgment: "everybody loses the same percentage of their list." It is the only one of the three that cannot be argued with, because it contains no opinion about anybody's family.

Equal is defensible and it is brutal to B's parents, who would lose nearly a third of their nineteen. And contribution-weighted should almost never be shown to the families at all — it makes the money explicit, it tells B's parents in a table that they matter less, and it is the most reliable method in this chapter for starting a conflict that outlives the wedding. Show it to the couple, once, privately, as one option — and let them choose.

B.7 — Price three plus-one policies. 140 guests, 28 single guests, using the B.2 step map.

Method, and the answer is a table with three totals and one sentence each. Universal plus-ones: 28 additional guests — variable cost × 28, plus every step crossed between 140 and 168, which is where the real number is. Wedding-party-only: typically 6–10. Cohabiting-partners-only: usually 12–18 and requires you to know, which means asking, which is a Chapter 19 communication problem.

Present it as: "here are three policies, here is what each costs, and here is the one sentence you'd put on the invitation for each." The cost difference between universal and cohabiting-only is usually one full step bracket — a bartender, a shuttle, a restroom trailer — and that is the number that decides it, not the per-head.

Chapter 6 — Budget Architecture

B.1 — Loaded rates, six quotes. Every quote must be converted to what will leave the account: base × (1 + service) × (1 + tax), plus delivery, plus gratuity where it is not in the service charge.

At 24% service and 8% tax the multiplier is 1.3392 — so a $58 per-head menu is **$77.67, and a six-quote comparison done on base prices is comparing the wrong six numbers. The commonest error is comparing one quote that includes service against one that does not**, which is a 24% error hiding inside a decision.

B.5 — Drift. Drift is the accumulation of small increases against named lines — none of them a decision, all of them real.

Track it in a single column: budgeted, actual, variance — and then the fourth column Chapter 30 adds, what it should have been. The Reyes–Whitfield drift was $964.78 against a $962.69 contingency, and it went undetected for a year because the contingency tracker recorded deliberate contingency spending and was read as how much is left. A contingency tracked only against contingency decisions is not a contingency tracker.

B.6 — Contingency sizing. 5–10% of the total, and the arithmetic that decides where in that range: how many unknowns are left.

Higher end (10%) when: the venue is a raw site · the guest count is not settled · any element is weather-dependent · a supplier has not been chosen · or the couple are early in the process. Lower end (5%) when: an all-inclusive venue, a settled list, and everything contracted.

And the two rules that matter more than the percentage: it must be netted against line drift (Ch.30) and it must have no unallocated remainder sitting outside every category — the $437.31 that was invisible from month one.

Chapter 7 — Budget Management

B.3 — Burn rate. Total committed ÷ total budget, plotted against months elapsed ÷ months to go — and the useful output is not the percentage but the shape.

A healthy wedding burns slowly for six months and then steeply, because the large deposits (venue, catering, photography) land early and the balances land late. What you are looking for is the crossing point: the month in which committed spend exceeds the proportion of the timeline elapsed and keeps going. That is the month the budget stopped working, and it is visible three months before anybody feels it.

B.4 — Write four change orders. Every one has the same five fields: what changed · why · the cost difference, computed with the loaded multiplier · who approved it and when · and which budget line it comes from.

The fifth field is the one that gets omitted and it is the one that matters: a change order with no line named is how a budget acquires $964.78 of drift nobody decided on. And "from contingency" is a valid answer only if the contingency tracker nets it.

B.6 — Solve a shortfall. In this order, because it is the order of least damage: (1) find the unallocated money — there usually is some, and it is usually in gratuities, postage, or the remainder that never got assigned. (2) Re-derive the loaded quotes, since a 24%-and-8% error somewhere is worth more than most cuts. (3) Cut the step, not the line — one bracket crossing is worth twenty guests' worth of trimming (Ch.5). (4) Degrade rather than delete (Ch.28's ladder). (5) And only then, the guest list, which is the largest lever and the one with people attached.

Present three options with numbers, not one recommendation — Chapter 3's rule, applied to money.

Chapter 8 — Contracts and Legal

B.1 — Run the absence audit. The audit is: what is not in this contract that should be? — which is harder than reading what is there and is where the failures live.

The standard absence list: what happens if they cannot come (substitution, notification, remedy) · postponement as distinct from cancellation · force majeure, and whose definition · liability caps and what they cap · payment schedule with dates rather than milestones · what is excluded · overtime rates · and who owns the images.

Any contract with fewer than six of those is a contract that has only been read forwards.

B.4 — Cap arithmetic. A liability cap at the value of the contract means the vendor's maximum exposure is the fee you paid them — so a $1,300 DJ whose failure costs you a $4,000 replacement at 48 hours' notice is capped at $1,300.

Compute the exposure rather than arguing the principle: for each vendor, what would replacing them at short notice actually cost, and how does that compare to their fee. Where the gap is large — caterers, venues, photographers — the cap is the negotiation, and where it is small the clause is not worth an email. Chapter 28's substitutability categories tell you which is which.

B.6 — Triage the asks. Rank every proposed contract change by (expected cost of the risk) × (likelihood), and ask for the top three.

A vendor who receives eleven redlines negotiates all of them; a vendor who receives three gives you two. The three that are almost always worth asking for: substitution and notification · a postponement clause that is not a cancellation clause · and payment terms that match your own outgoings (Ch.36). And the ask that is almost never worth making is the indemnity rewrite, which costs a relationship and is decided by an insurer anyway.

Chapter 9 — Insurance, Permits, and Liability

B.1 — Audit five certificates. Five checks, in order: is the policy in force on the event date (not the date of the certificate) · are the limits at or above the venue's stated requirement · is the venue named as additional insured where required · does the coverage include the actual activity (alcohol service, rigging, cooking, structures) · and is the named insured the same legal entity as the one on the contract.

The fifth catches more real problems than the other four combined — a certificate for Bankole Sound LLC against a contract with T. Bankole is not cover.

B.4 — The chain, traced. Trace a single injury through: the guest → the venue → the vendor whose equipment or act caused it → their insurer → your policy → the couple's policy → and the venue's own.

What the trace reveals is that liability follows control, not contract — and the practical output is a two-line note per vendor: who controls this activity, and whose policy responds. Where the answer is "nobody is sure," that is the finding, and it is answered before the event, in writing, not afterwards.

B.5 — Alcohol, four arrangements. Ranked by exposure, highest first: (1) the couple buys and unlicensed friends serve — the worst arrangement available and the commonest at a raw site. (2) The couple buys and a licensed bartender serves — better, and the licence may not cover supplied alcohol. (3) A licensed bar company supplies and serves — their licence, their liability, their insurance. (4) The venue holds the licence and serves.

The decision is not about cost, it is about who is legally serving — and (1) should be declined by the planner in writing, once, with the reason, because it is the arrangement where a bad outcome reaches a member of the family personally.

Chapter 10 — Venue Selection

B.1 — Price three venues all-in. Site fee is not the price. Add: catering minimum or per-head, with the loaded multiplier · rentals the venue does not have (chairs, linen, glass, tables) · power (generator at a raw site) · sanitation · lighting · staffing · access hours and any overtime · parking or shuttles · and the cost of the rain plan.

The finding is Chapter 1's, computed: a raw site with a $2,000 fee routinely costs more all-in than an all-inclusive venue at $9,000, and the difference is invisible on a comparison of site fees. Present three all-in totals, and show the working — because the couple has already compared the site fees themselves.

B.5 — Sun analysis. Get the actual sunset time for the actual date at the actual latitude, then work backwards: golden hour is the 60 minutes before sunset and it is when the photographs the couple will keep are taken.

Then check the direction. A west-facing ceremony at 5 p.m. in September puts the sun in the guests' eyes and behind the couple, which is a photographic and a comfort problem and is fixed by rotating the aisle or moving the hour. This is a fifteen-minute exercise at the site visit and it constrains the entire timeline — Chapter 25's real starting point.

B.6 — The doorway problem. Measure it. 32 inches clear is the minimum for a wheelchair, 36 is comfortable, and any step is a barrier (Ch.29).

And the second measurement nobody takes: the largest object that must pass through it. A cake table, a round table top, a piano, a coffin at a memorial, or the 53-ft trailer's largest flight case — and the finding is usually that the door is fine and the corner four feet inside it is not.

Chapter 11 — Floor Plans, Layouts, and Flow

B.1 — Working capacity. Gross square footage is not capacity. Deduct: the bar footprint, the dance floor, the DJ or band, the cake and gift tables, service circulation, and anything structural — then divide the remainder by the per-person figure for the activity that will happen (Appendix B.2).

Wildrye's barn: 36 × 54 = 1,944 gross, 1,068 usable → 89 for a seated dinner at 12 sq ft, 211 for a ceremony in rows at 6. Both numbers are correct and they answer different questions, which is the error this book spent eighteen chapters carrying.

B.3 — Bar arithmetic. One bartender per 75 guests, one service position per 60–75 at peak, and the queue is a Chapter 29 friction point rather than a beverage problem.

And the placement rule that matters more than the ratio: never put the bar where it queues into the dance floor or across a service route. Two smaller bars beat one large one at almost every guest count above 120, because a queue is a function of service points, not of bartenders.

B.5 — Dance floor sizing. 2–3 sq ft per dancing guest, and about 40% of guests dance at once. For 140 guests: 140 × 0.40 × 2.5 ≈ 140 sq ft — a 12 × 12 floor.

And the failure mode is oversizing, not undersizing. An empty-looking floor stops people dancing, so a slightly small floor that fills is better than a correct one that looks abandoned at 9:15. Chapter 22's four causes of an empty floor are mostly not about the floor — but the one that is, is this one.

Chapter 12 — Vendor Management

B.3 — Compare three proposals. They cannot be compared until they are the same specification — which is why the brief goes out identically to all three (Appendix A.6).

Normalise: hours, headcount, what is included, service charge, tax, delivery, overtime rate, and what happens if they cannot come. Then compare. The commonest finding is that the cheapest quote excludes something the others include — staffing hours, delivery, or the second shooter — and that the spread between three genuinely comparable quotes is usually 10–20%, not the 60% the raw numbers show.

B.5 — Rewrite the discount ask. Do not ask for a discount. Ask what the price includes and what a smaller version would cost.

"That's a bit above where we are. Rather than ask you to cut your price, can I ask what a version at around $2,400 would look like? I'd rather buy less of something good than the same thing cheaper."

Why it works: it protects the vendor's rate, which is what they are actually defending, and it produces a real answer instead of a grudging 10%. A discount asked for and given is a relationship that starts with somebody feeling worse.

B.7 — The exclusions audit. For each vendor, obtain in writing what is not included. The five that are always missing: overtime and its rate · travel and delivery · what happens if the guest count changes · setup and strike labour · and vendor meals (Ch.6, 14).

Vendor meals are the classic: 8–14 people at $30–45 each, appearing in no budget, discovered at −2 weeks.** **The audit takes an hour across eleven vendors and finds, typically, $1,200–2,500.

Chapter 13 — Rentals and Production Logistics

B.2 — Count the linens. Not one per table. Count: dining tables · the cake table · gift table · escort card table · bar fronts · buffet or station tables · the DJ table · the guest book table · and the two you have forgotten.

Then add 5–10% for the ones that get spilled on before dinner, and specify the drop — a 120-inch round on a 60-inch table is floor-length, a 108 is not, and the difference is visible in every photograph. The commonest rental error in this chapter is not a quantity, it is a size.

B.4 — Power budget. Enumerate every load in watts · sum · multiply by 1.25 · size the supply above it (Appendix B.7).

Then two decisions the arithmetic does not make: what runs on battery — the PA, therefore the ceremony — and whether AV is on its own leg, because catering's thermostatic loads produce dips that appear as flicker and noise (Ch.34 B.7). A generator sized correctly and shared incorrectly still fails.

B.6 — Cost the flip. A flip — the same room used for ceremony and dinner — costs: staff hours at the changeover · a place for guests to be for 45–75 minutes · and a real risk of running late.

Cost it against the alternative: a second space, or a marquee, or a different venue. The flip usually wins on money and loses on stress, and the number that decides it is how many people are needed and whether they are already on site. A flip requiring four extra staff for ninety minutes is not free because nobody invoiced for it — it is Chapter 34's minimum call, at wedding scale.

Chapter 14 — Catering

B.1 — Convert ratios into minutes. A staffing ratio is not a service time until you multiply it out.

Plated, one server per 20 guests: a server plates and delivers roughly 20 covers in 8–12 minutes, so a 140-guest room with 7 servers serves a course in about 10–12 minutes and clears in 8. Three courses, with the eating time between, is 75–105 minutes — which is the figure that belongs in the timeline, not the ratio.

The exercise's real output: the difference between one server per 20 and one per 30 is not a quality difference, it is fourteen minutes per course, and fourteen minutes × 3 is the reason the speeches ran into the dark.

B.4 — Build a dietary matrix. Columns: guest name · table number · requirement · severity · who is told · how the plate is marked · and who hands it over.

The last two columns are the whole document, because the failure is not the kitchen — it is the fourth handoff, kitchen to guest (Ch.29 §29.4). And severity must be a column: "vegetarian" and "anaphylactic to tree nut" are not the same class of information and must not be in the same list without a flag. Marisol Vega's plate is hand-delivered by name at every service point, including the canapés and the dessert.

B.6 — Set a guarantee. The guarantee is the number you pay for, given to the caterer typically 5–7 days out, and it is a floor rather than an estimate.

Set it from the confirmed count, not the invited count — invited 115, expected 100, guarantee 100 and pay for 100 even if 98 attend, which is what happened. Setting it at 108 "to be safe" buys eight dinners nobody eats, at $117.85 loaded, and it is the largest waste measure at the event (Ch.35 M.1). The safety margin is already inside the caterer's 10–20% over-preparation; adding your own doubles it.

Chapter 15 — Beverage and Bar

B.2 — Forecast four events. Method: guest count × (1 − the non-drinking share) × (2 in the first hour + 1 per hour thereafter).

For 100 guests, 5 hours, 20% not drinking: 80 × (2 + 4) = 480 drinks. Then split by type from the room — a lunchtime corporate event is not a September wedding — and convert: 5 glasses per 750 ml bottle of wine, and ice at 1.5 lb per guest.

And state the honest caveat the chapter states: this model has no published evidence base. It is a planning heuristic that has never been validated, it is what everybody uses, and the only thing that would improve it is thirty of your own counts in the same units (Ch.30 M.7).

B.4 — Solve a queue. A bar queue is a function of service points, not of bartenders — two bartenders behind one bar is one queue.

Compute it like registration (Ch.31 B.7): arrivals in the peak, seconds per transaction, and desks required — a wedding's peak is the eleven minutes after the ceremony ends. The fixes, in order of effectiveness: a second service point · trays of a pre-poured drink at the exit of the ceremony, which removes 60–70% of the peak entirely · and a simplified menu for the first twenty minutes. Adding a bartender to one bar is the least effective of the three and is the one always chosen.

B.6 — Cap a consumption bar. A consumption bar with no cap is an open-ended liability on a fixed budget.

The cap: agree a dollar figure in writing, agree what happens when it is reached — the bar switches to beer and wine, or to cash, or the couple authorise an increase — and agree who is told and how. The mechanism that makes it work is a named person at a named number and a stated authority (Ch.27's protocol): "at $2,400, Devin texts me, and I ask Sam." A cap with no notification procedure is a number discovered afterwards.

Chapter 16 — Design and Aesthetics

B.3 — Run the subtraction. List everything on the table, then remove items one at a time and ask whether the room is worse.

The finding, reliably: three to six items can be removed before anybody notices, and the room usually improves. Design is subtraction — and the reason the exercise works is that a mood board accumulates by addition and nothing in the process ever removes anything.

Test the survivors against the through-line. Wildrye's was "everything on a table is food, light, or something that grew here. Nothing is white, and nothing was bought for a wedding." Anything that fails the sentence goes, and the sentence is why the decision is not a matter of taste.

B.6 — Test for the dark hour. Half of a wedding happens after dark and most mood boards are photographed at 2 p.m. in June.

Take every design decision and ask what it looks like at 21:30 under the lighting you have specified. Findings that recur: dark linen disappears · fine detail disappears · anything at table height that is not lit is not there · and colour goes. Which is Chapter 18's argument arriving from the design side: lighting is the highest-leverage dollar on the event, and a $6,000 floral scheme unlit after dark is a $6,000 daytime scheme.

B.8 — Price the top five. For the five most expensive items on the board: cost, driver, and the 70%-for-a-third version.

And then the question Chapter 29 adds and Chapter 16 cannot answer: which row of the notice ranking is each one in? The forty-first arrangement is in row four and six more chairs, printed vows, a quiet room, and a car from the gate are in row one and together cost less. Price the top five, then put the ranking beside it — and sell row four honestly as what it is (Ch.29 B.7).

Chapter 17 — Floral and Décor

B.1 — Decompose a quote. A floral quote is four things: stems · labour · hard goods · and delivery, installation, and strike.

Typical shape: stems 35–45%, labour 30–40%, hard goods 10–15%, logistics 10–15% — which means the flowers are usually under half the number. Ask for the split. A florist who will not give it is either protecting a margin or has not costed it, and both are worth knowing. And the practical consequence: cutting stem count from a design with heavy installation saves very little, which is why Chapter 4's cost-driver question comes first.

B.3 — Price the four routes. Full florist · florist with client-supplied hard goods · a grower plus your own labour · and foliage and candles.

Reyes–Whitfield: $677.69 total, foliage from eleven miles away, no arch. The four routes typically span 8–10× in price for outcomes that photograph within 20% of each other, and the variable that actually decides quality is not the route — it is whether somebody competent arranges it and whether it is lit.

B.6 — Fix the quantities. The commonest quantity errors: one arrangement per table when the head table needs three · nothing for the ceremony-to-reception repurpose · no allowance for the cake, the bar, and the escort table · and personal florals counted for the wedding party and not for the four parents and two grandparents.

Count from the floor plan and the photograph list, not from the proposal — and write the unit next to the number (Ch.39): 12 arrangements — DINING TABLES ONLY, excludes head table, bar, cake, ceremony.

Chapter 18 — Lighting, Sound, and Atmosphere

B.1 — Compute four power budgets. Enumerate, sum, ×1.25, size above (Appendix B.7).

The four cases and the trap in each: a barn with two 20-amp circuits — 4,800 W total, and catering alone exceeds it. A marquee — no supply at all; the generator is the design. A hotel ballroom — supply is adequate and the distribution board is shared with a kitchen. A raw field — everything, including the loos and the coffee.

And the item that must appear in all four: what runs on battery. The PA, therefore the ceremony.

B.2 — Translate five design words. "Warm" → 2700 K, not 5000 K — and the barn floods at Wildrye are 5000 K and unusable. "Soft" → diffused, indirect, nothing at eye level. "Dramatic" → high contrast, which means things that are not lit, which frightens people. "Romantic" → low, warm, and under eight feet. "Bright" → almost always means "I am worried it will be gloomy," which is Chapter 3's proxy and is answered with a dimmer rather than more light.

Every one of the five is a number, and a lighting designer can act on a number.

B.5 — Plan ceremony sound. Three sources to mic: the officiant, the couple's vows, and any reading or music.

The plan: a wired or reliable radio mic on the officiant at his own height · a handheld the officiant carries to anybody who speaks — which is how Rosa speaks seated · a battery-powered PA so the ceremony survives a generator failure · and a test at 14:00 with the rest of the sound check, by a named person.

And the item that is not sound and belongs here: printed vows, about eleven dollars per hundred guests (Ch.29). Sound is the commonest unmet access need at any wedding, and the print is what covers the failure the microphone cannot.

Chapter 19 — Stationery, Signage, and Guest Communication

B.1 — Build four timelines. Save-the-dates at −8 to −12 months (−12 for destination) · invitations at −8 to −10 weeks (−12 for destination) · RSVP deadline at −4 to −5 weeks · final numbers to the caterer at −5 to −7 days.

The chain that matters: the RSVP deadline exists to serve the final-numbers deadline, and everything upstream is set by it. A four-week gap between RSVP and final numbers is what makes the chasing possible — because roughly 20% never reply and somebody has to phone them.

B.6 — Walk a route. Signage is a sightline problem, not a sign problem (Ch.29 B.12).

Walk the route and stop at every point where a guest must choose a direction. At each: what can they see? If the answer is "the right thing," no sign is needed. If it is "two doors and no difference between them," you need a sign or a person — and a person is better, cheaper, and remembered.

B.8 — Build a $150 suite. Reyes–Whitfield's actual number.

Digital or printed-at-home save-the-dates · a single flat printed invitation with the details on the reverse rather than an insert · an RSVP by website or text rather than a card and stamp · one printed ceremony programme carrying the vows (~$11 for 100, and it is the highest-value item in the suite) · printed departure times · escort cards on card stock · and two seating charts at 24-point, alphabetical.

The economies are postage and inserts, not paper quality. And the item never to cut is the programme with the vows in it, because it is an access document wearing a stationery budget.

Chapter 20 — The Ceremony

B.1 — Time four ceremonies. 20–35 minutes, and the failure is always addition.

Build the timing from components: processional 4–6 min · welcome 2 · readings 3–4 each · address 5–10 · vows and rings 6–8 · signing 4–6 · recessional 2. A civil ceremony with two readings and a signing is 28 minutes; the same ceremony with a third reading, a song, and a family blessing is 41 — and nobody added more than four minutes at a time.

Reyes–Whitfield's was 36:25, timed to the second in Chapter 25 because the sunset depended on it.

B.2 — Do the processional arithmetic. A processional is a queue: number of units × walking time per unit + the gaps.

200 feet at a processional pace is 60–75 seconds; eight units at 20–25 seconds' spacing is 3–4 minutes, and it is longer if anybody is walking slowly, which is a question you ask rather than assume. The commonest error: timing it at your own walking speed on an empty aisle — the real thing is slower, and it is slower by more at a bare-field site on grass.

B.3 — Fix an overrun. Do not cut the ceremony. Move what is downstream, or move the start.

In order: check what is actually waiting (Ch.25's cascade — usually the photographs and the sunset) · take it out of the cocktail hour, which has 30 minutes of tolerance · move dinner, which the caterer can absorb with notice and cannot absorb without · and only then look at the ceremony.

And the structural fix is upstream: the ceremony grew because three people added things and nobody was holding a total. A stated length, agreed with the officiant at −8 weeks, is the whole prevention.

Chapter 21 — Multicultural and Interfaith Events

B.1 — Sort a list. Every item goes into one of three columns: required · customary · optional — and the sort is made by the authority, not by you and not by the couple's memory.

The reason it matters: a couple negotiating with each other about "the tradition" are usually negotiating about something in column two while believing it is in column one. Establishing the sort dissolves perhaps half of these conflicts without anybody being asked to concede anything.

B.2 — Build a fixed-hour timeline. Some elements have hours that cannot move — a sunset, a specific time of day, the end of a fast, a day of the week.

Build the timeline from those outward, in both directions, exactly as Chapter 25 builds from the ceremony. And identify the collisions early: a ceremony that cannot begin before a certain hour and photographs that need the hour before sunset are the same hour, and that is a conversation for month two, not for month eleven.

B.8 — Write the month-one question set. Six questions, asked once, early, of the couple and — with permission — of the relevant authority.

"What has to happen for this to be a valid marriage in your tradition?" · "What would your family expect that isn't required?" · "Is there anything that would make somebody feel they couldn't attend or couldn't participate?" · "Who is the authority I should be asking, and may I?" · "What's been difficult about this so far?" · and "what would you like me to explain to the other family, and what would you rather I didn't?"

Note what is not in the set: any suggestion. You are not the authority on anyone's tradition — establish, then propose nothing.

Chapter 22 — Music and Entertainment

B.2 — Place four peaks. A reception has an arc and it has roughly four peaks, and their placement is a design decision that is almost always left to a DJ.

Typical: the entrance · the first dances clustered early rather than spread · a deliberate lift about forty minutes into the dancing · and a defined close. Between them are troughs, and troughs are correct — a room at a constant intensity for four hours is a room that leaves at nine.

And the constraint the arc must respect: the bar and amplified music end at 22:30, so the close is designed backwards from that, not discovered at 22:25.

B.5 — Diagnose four empty floors. Four causes and only one is the music.

Nobody has been told it has started — the commonest, and it is fixed by an announcement and by the couple being on the floor. The lighting is wrong — a fully-lit room does not dance (Ch.18). The floor is too big (Ch.11 B.5). And the music is genuinely wrong for the room — which is a briefing failure at −6 weeks, not a DJ failure at 21:40.

Diagnose before intervening, because three of the four are not solved by changing the song.

B.7 — Build a do-not-play list. Short, specific, and with a reason where there is one.

The list has two parts and they are different: songs the couple dislike, and songs that would hurt somebody in the room — an ex-partner's song, a song from a funeral, a song a family has a history with. The second list is confidential, is not shared with the room, and is the one worth asking about explicitly, because nobody volunteers it. "Is there anything that would be painful for somebody here?" is a question that has to be asked to be answered.

Chapter 23 — Photography and Videography

B.1 — Compute four family matrices. Each combination is 3–4 minutes, and the number of combinations grows faster than anybody expects.

A "simple" family list of 12 combinations is 36–48 minutes, which is the single largest block in the post-ceremony hour and is routinely allocated twenty. Compute it, then cut it with the couple, by name, in advance — and have a named person from each family who knows the list and can find people, because the time is lost in retrieval, not in shooting.

B.2 — Build a photo timeline. Backwards from sunset (Ch.10 B.5): golden hour is the 60 minutes before, couple portraits sit inside it, family combinations before that, and the ceremony before that.

Reyes–Whitfield: sunset 19:48, ceremony 16:25 — and the ceremony time was derived from the sunset, not the other way round. Photography is a timeline constraint, not a service, and a timeline built without it produces the photographs the couple did not want.

B.4 — Solve five collisions. The standard five: family photographs versus the cocktail hour · golden hour versus dinner service · the first dance versus the light · the getting-ready room versus a real deadline · and a ceremony restriction that moves everything.

The method for each is identical: identify which side has a hard constraint — sunset and the caterer's service are hard, the cocktail hour is soft — and move the soft one. The one that is genuinely both hard is golden hour versus dinner, and the answer is a ten-minute break in the middle of dinner, agreed with the caterer in advance, which every caterer will accommodate and none will accommodate at 19:40.

Chapter 24 — The Rehearsal

B.2 — Convert eight running-order lines into cues. A running order says what happens; a cue says who does what, when, and on what signal.

"Rosa speaks" → "16:36 · ROSA speaks · SEATED · Rev. C brings the mic · cue: ELENA touches her arm — she cannot hear one · backup: BEATRIZ."

Every cue needs four things: a time, a person, an action, and a trigger — and a fifth if the person is a family member: a second name (Ch.40, injection 4).

B.4 — Design the assignments. One task, one owner, by name, with a time.

Then lay each person's tasks on a single line and look for collisions — which is where the real findings are. Elena had eight tasks. Danny is on the gate at 15:40 and is therefore not the florist's collector. And every task assigned to a non-professional gets a second name, which is eleven words at the rehearsal and is the difference between a plan and a hope.

B.7 — Compare two documents. The rehearsal script and the run sheet are different documents for different readers.

The script is for the people in the ceremony, is in plain language, and contains no times a guest would not care about. The run sheet is for the planner and the vendors, is in 24-hour time, and contains everything. The failure is handing one person the other — a wedding party given a run sheet reads the vendor rows and worries, and a planner working from a script has no cues.

Chapter 25 — Timeline Construction

B.2 — Find the critical path. The longest chain of dependent tasks, and it is never the sum of the items.

Draw the dependencies before the calendar (Ch.34's method at wedding scale): the ceremony's time is fixed by the sunset; the photographs depend on the ceremony ending; dinner depends on the photographs; the light depends on nothing and waits for no one. What the path tells you is what can move when something runs late — and the answer is only ever the things nothing is waiting on.

B.3 — Run three cascades. Take a delay and trace it forward: what is waiting, what absorbs it, and where it becomes irreversible.

The finding is the chapter's threshold: delay is directional. A florist ninety minutes late against a 2:00 install window is absorbed entirely; a caterer ninety minutes late against a 6:30 dinner is not. Which means the correct first response to "we're running late" is a question, not an action — and it kills most of what reaches a planner on the day (Ch.27).

B.4 — Place the buffers. Not evenly, and not at the end.

Buffers go immediately before the hard points and immediately after the unpredictable ones. The unpredictable ones: the getting-ready room, family photographs, and anything involving a hundred people moving. The hard points: the ceremony, the sunset, and the curfew.

Reyes–Whitfield held six minutes of float before the ceremony, for the track — and used it, for one guest, and the ceremony still started at 16:25.

Chapter 26 — The Run Sheet and Production Book

B.4 — Build a contact sheet. Every supplier: company, the individual who will be on site, their mobile, a second number, and the office.

The second number is the one that gets omitted and it is the one Chapter 28 needs at 4:12. Plus the venue's Saturday contact — a different person from the events office, which is closed — and the couple's own numbers, which live in a phone and belong in the book (Ch.40's absence test).

B.6 — Write an emergency page. One page, paper, distributed to five people.

It contains: an address a satnav accepts and what3words for the gate and the building · the named first-aider · a named gate runner and an alternate · every guest whose medical situation somebody must know · and the one sentence that is site-specific — at Wildrye, "an ambulance reaches the barn door, not the meadow."

Chapter 26 found that this document belonged to no chapter and therefore did not exist, after twenty-five chapters. It was written in twenty minutes.

B.8 — Design a pocket card. What fits in a pocket and is read at speed: the five cues that must not be missed, the five phone numbers, and the two decisions that have deadlines.

Everything else is in the book. The card exists because at 19:15 nobody opens a book — and its design constraint is that it must be legible held in one hand, in low light, by somebody who is being spoken to.

Chapter 27 — Day-Of Execution

B.1 — Triage twenty problems. Two questions, in order: will a guest notice? and what is waiting on this?

Applied honestly to twenty realistic problems, roughly twelve are answered "no" by the first question and die there. Of the remaining eight, three or four are answered by the second. What is left — two or three — is the actual day.

The exercise's finding is not the triage rule; it is the ratio. A planner who reacts to all twenty has spent the day on sixteen non-events, and the cost is Chapter 28's second-order failure: the sweep that did not happen.

B.3 — Write a decision protocol. Four elements: a dollar figure · a scope boundary · a named person to ask · and a review clause.

Reyes–Whitfield's: $200 · change how, not what · ask Sam, not Alicia · and — Alicia's own amendment — unless it's about a person.

Agreed in May, in six minutes, when nobody was under pressure. A protocol amended by the client is one they will trust in September, and the amendment is what makes it theirs.

B.6 — Design a sweep route. The same physical route, walked twice, with two different instructions.

The route: the car park and the gate · the entrance · the toilets · the bar queue · the edges of the room · the exits · and the quiet places outside. The first sweep is walked reading the list; the second is walked looking at the room, and they find different things.

And the two stops that belong to Chapter 29: the edges and outside — because that is where the guest who is cold, alone, unwell, or unable to hear has gone, and every one of them will tell you they are fine.

Part Two — Chapters 28–41, All Starred Exercises

Every ★ item, in order.

Chapter 28 — Crisis Management

A.1 Answered already · needs a decision now · cannot be solved at all. The commonest error is deliberating about the first kind — the answer is in a document written in month six. The most damaging is treating the third as the second, which is a planner attempting to project-manage a grief.

A.4 Indoors. The asymmetry: wrong indoors is a wedding in a barn on a dry day; wrong outdoors is a hundred people and a marquee company in the rain with seventy minutes of work and no time to do it. One is a disappointment, the other is the event failing.

A.7

A.11

Can: separate people physically by giving one of them a task · remove the audience · buy time · protect the couple from knowing during the day · brief a family ally in advance · hold the line on the run sheet so the day continues.

Cannot: resolve the underlying dispute · make anyone apologise · adjudicate who is right · change a thirty-year-old family system in an afternoon.

A.15 The second-order failure is what the crisis cost you elsewhere — the sweep that did not happen, the guest who was not met, the 3:15 vendor check that was dropped. It is invisible because nobody can see an absent action: the first-order failure has a story and a name, and the second-order failure looks like nothing happening. Which is why the first move in a crisis is to say out loud what you are dropping.

A.20 What happened · when · who was involved · what you did · what you decided and why · who was told and when · any cost incurred. Factual, unemotional, no speculation about cause, no blame. Three reasons: an insurance claim may follow (Ch.9) · you will misremember before the conversation with the couple · and it is the only honest input to Chapter 30's debrief.

B.1 Work backward from the arrival, not from the ceremony. Guests arrive 2:30; the move takes 70 minutes; the last possible start is 1:20 p.m., which is the point of no return. Set the decision deadline at 1:00 and spend the twenty minutes on margin — the same structure the Reyes–Whitfield plan used (13:25 against a 13:45 point of no return).

And the 60-vs-80 shortfall obliges you to ask what the 60 was computed for. A conservatory that "seats 60" at tables holds something closer to 120 in chairs in rows at 6 sq ft (Appendix B.2) — but if the 60 is a fire-code occupancy limit, it is a hard number and no arithmetic moves it. These are opposite situations and the phrase "seats 60" does not distinguish them. At the deadline you must already know which it is, which means the question belonged at the site visit. Write the unit next to the number (Ch.39).

B.3 A worked playbook. Categories A–C in one line each; D in full.

A — replaceable within hours: rentals, cake maker, minibus. Money problems. B — replaceable at a cost or a downgrade: DJ, photographer, videographer, florist. Use the degradation ladder. C — hard to replace, event survives: marquee company (once erected, the failure is service not structure). D — event does not work: caterer · officiant · venue · power.

Category D, written out: Caterer — two named local caterers with numbers, the venue's kitchen capability confirmed in writing, a pizza floor costed at ~$14 a head, and a bar and canapés guaranteed regardless. Officiant — second number, the parish or registry office number, one named alternate confirmed as an extension of the permission (a permission runs to a named person), and a four-sentence fallback script. Venue — insurance position, the nearest realistic alternative, and the couple's rebooking preference asked once, in writing, at contract. Power — enumerated load × 1.25, the generator supplier's out-of-hours number, and the list of what runs on battery: the PA, and therefore the ceremony.

B.6 The first ninety seconds.

0–10 s — You call emergency services. Yourself, immediately, before checking whether it is serious. The chapter's rule is that a possibly-serious event is called: unnecessary ambulances are the acceptable cost. 10–25 s — Send a named person to the gate with the address and what3words, and say it as an instruction, not a request. An ambulance will not find a farm track. 25–60 s — Ask, out loud, for a medic in the room, then clear space around the person: two arms' reach, and everybody else back. 60–90 s — Turn the music off, not up. Get the person's own family to them. Find the couple before anyone else does, and tell them in the order §28.7 gives.

Do you say anything to the room? One sentence, from the DJ's microphone or the officiant's, and only when the ambulance has been called: "We're looking after someone; please stay where you are for a few minutes." Silence and a huddle produces a crowd; a sentence produces stillness. Nothing about who, and nothing about how serious.

B.9 A degradation ladder for a $60,000, 120-guest wedding. (Tier 3, illustrative — the structure transfers, the prices do not.)

The floor column is 7.5% of the full column and it is still a wedding. That ratio is the whole argument of §28.6: nothing in the right-hand column stops two people getting married in front of a hundred and twenty people who love them.

B.12 A worked ordering. Invented: the linen is the wrong colour (A) · the caterer has not answered in twenty minutes at T−90 (D) · Sam's father has just been told his brother is not coming and is upset (a person) · and a guest has asked whether the ceremony could start ten minutes late (not a crisis at all).

Order: (1) the caterer — start the absent response now, because starting is reversible and waiting is not. (2) The person: two minutes, someone who loves him, somewhere quieter. (3) The late start: no, and it takes eight seconds — Ch.25's cascade says the photography and the sunset are waiting. (4) The linen: nothing, today. It is a Chapter 30 conversation.

What you are dropping, said out loud: the 3:15 vendor check and the seating-chart walk-through, handed to a named person or explicitly abandoned. Not silently deferred.

C.2 Rubric. A strong write-up records the failure factually, and then answers the question the planner has almost certainly never been asked: what did the rest of the event lose while they dealt with it? Look for a specific dropped action, not a general "it was stressful." If the interviewee cannot name one, that is the finding — and it is worth writing down that the second-order cost is invisible even to the person who paid it.

C.5 Rubric. Three columns for every element you sell, with the floor written in plain words and no euphemism. The resistance is the point of the exercise: name it in a sentence. Most planners report the floor column feels like admitting they might fail, and §28.6's answer is that the alternative is reconstructing the middle column at 4:05 with no DJ, which takes forty minutes and produces a worse result than the ninety seconds the floor takes.

D.2 Rubric — the strongest opposing case, roughly: it is the couple's wedding and their money; the planner's incentive is an event that runs smoothly rather than one that is right for them; a planner who moves a ceremony indoors at 1:00 has taken the single most visible decision of the day from the people it belongs to; and the "relief" §28.3 reports is partly the relief of someone being managed.

Does the chapter's position survive? Partly, and it should be conceded that it is weakened. What survives is the timing argument — the decision must be made at a deadline, on evidence, by someone not being asked twelve other things — and the revocability clause ("if either of you feels strongly, ring me in the next ten minutes") is doing most of the ethical work. A named decider without revocability does not survive this objection.

D.4 Rubric. A reasonable estimate: at ~14 guests over 70 in a hundred-person wedding and perhaps one faint or fall per twenty weddings, a planner running fourteen weddings a year might call an ambulance once every two or three years, and perhaps half of those turn out not to need one. So: roughly one unnecessary ambulance per five years per planner.

The rule is still right, and the argument is asymmetry, not frequency. The cost of an unnecessary call is an apology and an hour of somebody's time; the cost of a delayed call in the cases where it mattered is not recoverable. State what would change the answer: evidence that unnecessary calls materially delay other emergencies in your area — which is a real consideration in a rural service with one vehicle, and worth knowing before you need it.

D.7 Rubric. Count them honestly. The chapter's examples include: the caterer no-show (fault: the caterer) · rain (no fault) · the guest who collapses (no fault) · the officiant stranded (arguably the planner's, for a permission never checked) · the family conflict (fault predates everyone) · the barn capacity (the planner's, and the book's) · §28.8's unsolvable crisis (no fault).

So roughly three of seven involve fault and two of those are the planner's. A defensible verdict: the chapter is not choosing the easy case — it is choosing the honest distribution — but the opening scene specifically does duck the hardest interpersonal case, which is a crisis somebody in the room caused and is standing in front of you denying. A strong answer says which case the chapter avoided.

M.2 Not necessarily a crisis, and two facts settle it. (1) What is waiting on them — Chapter 25's cascade: if the florist is late and the ceremony is at 4:25 with a 2:00 install window, ninety minutes is absorbed by float; if the caterer is late and dinner is at 6:30, it is not. (2) Whether they are late or absent — reached and en route is a schedule problem, unreachable at T−90 is a category question. Delay is directional: ask what is downstream before you react.

M.5 Chapter 9 said the claim requires the policy to be in force on the date, the injured party not to be an excluded class, the activity not to be excluded, the limits to be adequate, and — critically — notice given promptly. §28.9 adds the thing that makes any of it work: the incident note, written that night, factual and contemporaneous, plus photographs of the site condition and the names of who was told and when. An insurer's first question is what the record says, and memory eleven months later is not a record.

M.8 Three later lapse points and their owners:

The pattern is §29.4's fourth handoff: kitchen to guest. The protocol survives three handoffs and fails at the one nobody owns.

M.11 What each visit added: Ch.1 — the scene, and the fact that a planner's value is legible only when something fails. Ch.8 — the clause that should have existed: substitution, notification, and remedy. Ch.12 — the vetting that would have made it less likely, and the second number. Ch.26 — the run sheet's contact block, and the discovery that the second number had never been asked for. Ch.28 — the response itself, and the category-D preparation.

Did the book keep its promise? Yes, with one honest qualification: it never solves the no-show, because it cannot be solved on the day — the ten-minute sequence in §28.4a produces food for a hundred and fifty people that is not the food that was ordered. The book's actual claim is that the work that mattered happened in month six, and four of the five visits are about month six.

E.1 Rubric. The objection, at its strongest: we were told to rank our priorities, then told what our budget could not do, then a stranger decided where we would be married and the first we knew was a text at one o'clock. We hired someone to give us the wedding we wanted and we were managed out of the only decisions that were ours.

Concede these three: the protocol is a transfer of authority and calling it a service is a euphemism · the "relief" is genuine but is partly the relief of a person under pressure being relieved of pressure, which is not the same as consent · and a planner benefits from a smoothly-run day in ways that are not identical to the couple's interest.

Then answer: the authority is bounded (a dollar figure, a scope — change how, not what), revocable within ten minutes, agreed months in advance when nobody is under pressure, and it applies to a specific class of decision made at a specific deadline with specific evidence. A strong answer says plainly that all of that is defensible and none of it makes the objection wrong.

E.3 Rubric for 800 words. The chapter is the evidence and it divides cleanly.

Teachable and demonstrably so: the substitutability categories · the five parts of a rain plan · the deadline arithmetic · the ten-minute vendor sequence · the disclosure order · the incident note. These are documents and procedures and a competent person learns them in a week.

Not teachable in the same way: §28.8. What is being asked for there is not a procedure but a bearing — the ability to stand next to somebody in the worst hour of their life and be useful without needing it to be resolved. A strong essay resists two easy positions: that character cannot be developed (it can, by exposure and by working next to someone who has it), and that it can be reduced to a checklist (§28.8 is not a checklist and the chapter does not pretend it is).

The most interesting claim available: the teachable part exists to protect the unteachable part. A planner whose category-D playbook is written has attention left for the thing no playbook covers.

E.6 Rubric. This is a personal document and the only failure mode is vagueness. A strong answer names circumstances, not principles. For example: I will stop an event, without asking anybody's permission and without regard to what it costs me, if — a structure is moving in wind, if there is a fire, if a person needs an ambulance and the music is preventing us from hearing them, if a guest is being harmed by another guest, or if someone is being put behind the wheel of a car by people who are cheering. Weak answers say "if there is a safety issue." Strong ones say what they will do in the first ten seconds, who they will tell, and what they expect it to cost them — because §28.10's argument is that nobody improvises courage at 9:40 p.m., and a decision written in advance is the only version that is available at 9:40 p.m.

Chapter 29 — Guest Experience and Accessibility

A.1 The disclosure problem: the absence of complaints is evidence of nothing. Four reasons: it is a wedding, and people do not complain at weddings · nothing can be fixed by then, so saying it has no purpose · friction is attributed inward — "I should have left earlier," "my hip is bad at the moment" — rather than to the event · and disclosure has a history, which is the one that bites hardest: the people with the most to report have the most experience of what reporting costs them, so silence correlates with need rather than with satisfaction.

A.4 Finding it · parking · the walk in · arriving · waiting · the ceremony · the gap · finding a seat · eating · the evening · leaving.

Points 1–4 and 11 — finding it, parking, the walk in, arriving, and leaving — are roughly half the friction and roughly none of the budget. They are the beginning and the end, they are the two moments planned least, and they bookend everything that was planned most.

A.7 Because it asks the guest to classify themselves. The mechanism: to answer it, a guest must first decide that they are a person with special requirements — and the people who need something most are exactly the people who do not think of themselves that way. The guest who cannot walk 400 metres of gravel does not have a special requirement; she has a hip that is bad at the moment. She answers "no," truthfully, and then has a difficult afternoon. The question fails before it reaches the provision.

A.10 Printed vows and readings. About eleven dollars for a hundred guests.

Besides the deaf or hard-of-hearing guest it was written for, it serves: everyone in row nine and behind · the grandmother whose hearing has gone and who has told nobody · every guest whose first language is not the ceremony's · the guest whose child is making noise · and anybody the wind is against. That is universal design in a single item: designed for the edge, used by the middle.

A.13

A.16 Who can hear (near the front, away from the band and the kitchen door — this alone serves more people than every other measure in the chapter combined) · who can get out (near a door, a toilet, an edge) · who is alone (seated by design, not by what was left over) · who is walking (nobody with a stick should cross the room for a drink) · and who needs a specific plate (the dietary matrix's table numbers, and the fourth handoff).

A.19 Of a hundred adults: roughly 15–20 have some hearing loss; roughly 0–2 use a wheelchair.

What follows is the chapter's most useful ratio: the largest access group is about ten times the size of the one every venue certifies against, and it is invisible. A venue can be certified accessible, have a ramp, an accessible toilet, and level parking — and still fail fifteen people in the same afternoon because a microphone was held at chest height. The marginal dollar belongs to sound, not to ramps — and neither of those is where most accessibility budgets go.

B.1 Rubric. Eleven rows, one per friction point, each naming a specific failure at that venue — not a general risk. Strong answers read like: "Point 2, parking: the overflow field has no sign and the gate is 90 metres past the entrance, so a first-time arrival drives past it and turns in a lane." Weak answers read like: "Parking could be confusing." The test is whether a stranger could act on the row without asking you a question.

B.4 A worked arrival sequence — 600 m gravel drive, one small car park.

In the invitation (and it states facts, it does not ask questions): "Wildrye is at the end of a 600-metre gravel drive. Parking by the barn is limited to about twenty cars; there is a field for the rest, signed, 200 metres further on. A car will run continuously from the field to the barn door between 3:15 and 4:00 — just wave. If getting from a car to the ceremony is likely to be difficult for anybody in your party, reply to this email or call me and we will arrange something specific."

On the day: a sign at the road turn (the point at which people phone) · a person in the small car park at 3:00 directing the first arrivals and filling it deliberately, closest spaces left free · a named driver and a car, running continuously, not on request · a second person at the barn door who says hello — the highest-value unstaffed-to-staffed change at any wedding · a torch and the same driver for departures, and the departure times printed rather than announced.

Note what is not in this plan: nobody was asked to describe themselves, and everything except the driver's time is free.

B.7 Four options for $1,800, ranked.

And what you say when they choose the arch: "That's a completely reasonable choice and I'll make it beautiful. I want to be honest about what it buys, because you're paying for it: your guests will mostly not register the arrangements, and you will see them in your photographs for the rest of your lives. That's real — it's just not something the guests get. If you want both, the chairs and the programmes are about a hundred and twenty dollars and I'd rather find that somewhere than lose it."

Then you stop talking and you do the thing they asked for, well. It is their wedding and their money. Row four buys something real; it should be sold honestly as what it is.

B.10 A complete guest-experience package, 110 guests. (Tier 3 — illustrative.)

Three of the seven items cost nothing, and two of those three are in the top row of the notice ranking. The whole package costs less than the floral upgrade it competes with, and it is the chapter's argument in one table.

B.12 Rubric. At every decision point the answer must be a sightline, not a sign: what can the guest see from where they are standing. Strong answers find at least two points where the honest answer is "nothing" or "two doors and no difference between them." A sign is what you add when the sightline cannot be fixed — and the commonest finding is that the sightline could have been fixed by moving one table.

C.1 Rubric. Report hesitations, not solutions — the discipline is the exercise. Expect six to twelve on a first walk at any venue, and expect almost none of them to appear on the floor plan, because a floor plan is drawn from above and a hesitation happens at eye level. The most common finding: the walk takes longer than anybody had assumed, and nobody had ever timed it.

C.4 Rubric. The general question — "was anything difficult?" — will produce mostly "no, it was lovely." The specific question — "how was the parking?" or "could you hear the ceremony?" — produces detail from the same people, in the same conversation. Report the difference as a count, and note that you have just reproduced §29.5's finding in miniature: the information exists and the general question cannot reach it.

C.7 Rubric. Look for: "any special requirements" · "let us know if you have any needs" · "please advise of any disabilities" · "anyone requiring assistance should..." Every one asks the guest to classify themselves. Rewrites state the fact and offer the specific solution: "There's about 200 metres of gravel between the car park and the ceremony. A car will run from the gate from 3:15 — just wave, or reply here and I'll make sure someone finds you."

D.2 Rubric — the objection is strong and partly correct. Its best form: being asked is also a burden. I would rather arrive somewhere that already worked than be interviewed about my body by a stranger, however kindly. The chapter has replaced one demand with another and called it hospitality.

What survives of §29.5: the form of the asking, which is precisely designed to avoid this — it states facts and offers provision, and it never asks anybody to describe themselves. "There's 200 metres of gravel and a car will run from the gate" imposes no disclosure at all: the guest who needs it simply waves.

What does not survive: the framing that asking is the answer. The stronger position, which the chapter half-concedes and a good response should state outright, is that the first move is to remove the need to ask — a route that works, a chair that exists, a microphone used properly — and asking is what remains for the cases that universal provision cannot reach.

D.3 Rubric. The ranking has no data, and the exercise is to attack it seriously. Defensible attacks:

"The music" is placed too low. It sits in row two and there is a reasonable case it belongs in row one — for a large fraction of guests the evening is the music, and a bad DJ is remembered for years.

"The room when they first walked in" is placed too low, and its placement is suspiciously convenient for the chapter's thesis: Chapter 16 argued the first impression is a real effect, and row two understates it.

Or the reverse case: "whether the couple seemed happy" is unfalsifiable and probably not a design variable at all — it may belong outside the ranking entirely.

What would settle it: a debrief-based study — guests contacted at 3–6 months, asked open-ended recall first (to avoid cueing), then specific prompts, with the design and hospitality spend of each event known. And a strong answer names the confound: what guests recall is not what affected their experience, and the ranking silently equates them.

D.5 Rubric — engage with the literature, do not wave at it. The objection is real and researched: disability simulation exercises can worsen attitudes, because a few minutes in a wheelchair simulates the impairment and not the adaptation, producing pity and an exaggerated sense of catastrophe rather than an understanding of what actually disables people, which is usually the environment.

What to do instead, in order of value: ask disabled guests and disabled colleagues, and pay them for their time · read and act on first-person accounts · measure, rather than simulate — 36 inches, 32 inches, 60-inch turning circle, gradient, surface, distance, lux, and whether the microphone works · and walk the route yourself with a stopwatch, which is a measurement exercise and not a simulation.

What survives of the chapter's technique: "walk it carrying two bags and a coat" is not a disability simulation and is a useful load test. A strong answer distinguishes the two and does not defend the indefensible half.

D.7 Rubric. Any ranking is defensible if it is argued; what is being tested is whether the reader will let evidence move them. The likeliest honest ranking puts the sound failure first — a ceremony she could not hear is unrecoverable and unrepeatable — the walk second, and the decorative failures last, which is exactly what §29.8 predicts.

But look for the case where the rankings diverge, and it is usually this: a failure that the notice ranking places low can be devastating when it is about the guest — a chair that was not there for her specifically, a plate that arrived wrong with her name on it. The notice ranking is a claim about aggregates and Cecilia is one person. A strong answer says that, and concludes that the ranking is a budgeting instrument, not a description of anybody's day.

M.1 The 36-inch rule protects circulation — the gap between table edges, which is the difference between a room people move through and a room people squeeze through. It protects a wheelchair user, a guest with a stick, a server carrying two plates, and anybody trying to leave a table in the middle of a speech.

Who discovers when it is broken: the guest, at 7:40 p.m., in front of everybody. A 26-inch gap is invisible on a drawing — it looks like a gap — and is a wall in a room. That asymmetry is why Chapter 11 made it a number instead of a judgment.

M.4 Because the sweep observes rather than asks, and §29.2's four reasons all apply to asking and none of them apply to looking. The route (Ch.27): the car park and the gate · the entrance · the toilets · the bar queue · the edges of the room · the exits · and the quiet places outside.

The two stops that belong to this chapter: the edges of the room and outside — because that is where the guest who is alone, cold, unwell, or unable to hear has gone, and every one of them will tell you they are fine.

M.6 Chapter 15 said 15–25% of any room is not drinking, and that the bar model must be built on drinking guests rather than on guest count, or you buy 25% too much.

This chapter adds the guest-experience half of the same fact: those people need something that is not a jug of water in a corner — a specific, good, adult non-alcoholic option, served the same way, in the same glass, by the same person, without anybody having to explain themselves at the bar. The commonest reason a guest is not drinking is one they do not wish to discuss, and a bar that requires a conversation to serve them is an access failure with a drinks list.

M.9 The four new named jobs are: the driver running from the gate (3:15–4:00) · the greeter at the door (from 3:20) · the person at the seating chart (6:20–6:35) · and the person who walks Rosa to her car (9:10).

Applying Chapter 24's rule — one owner, and check the minutes — the collision is the driver and the greeter, both live at 3:20 and both at different ends of a 200-metre track. They cannot be the same person, and on the Reyes–Whitfield wedding they nearly were: Danny is on the gate at 3:40, which is precisely why the floral collection had to go to Tomás (Ch.40, injection 1). The seating chart and Rosa do not collide with anything.

E.1 Rubric. Report the actual position rather than an impression of it. In most jurisdictions the honest finding is: a private event in a private venue is largely outside the scope of public-accommodation law, while the venue itself is usually inside it — so the legal duty sits with the venue, is about the building, and is discharged by a ramp and a toilet. Employment law may reach your staff and suppliers.

The gap between legal and decent is the whole report. Nothing in any statute requires a microphone to be used properly, a chair at the back, a car from the gate, or a seating plan that puts a guest with a stick near the bar — and those are the measures that serve the most people. Legal compliance is a floor that misses the largest access group entirely.

E.3 Rubric. Three things that recur in first-person accounts and appear nowhere in this chapter — expect some of: the exhaustion of being the one who always has to ask; being seated somewhere "practical" and away from the people they came with; being praised for attending, which is not a compliment; having a plus-one or a carer treated as an inconvenience; being told about accessibility by someone who has not measured anything; and the specific dread of the toilet question. The instruction is to report what is there, not to find what the chapter predicted.

E.5 Rubric — and the last part is genuinely the hard part.

A workable design: sample guests across 20–30 weddings with known design and hospitality spend · contact at 3–6 months, late enough that novelty has faded and early enough for recall · open-ended recall first, always — "tell me about the day" — coded blind by two coders · then and only then the specific prompts (parking, hearing, food timing, comfort, the room, the flowers) · and record spend per category to test whether spend predicts recall.

Avoiding the disclosure problem contaminating your own data is where most designs fail. You cannot ask "was anything difficult?" and believe the answer, and you cannot fix that by asking it more kindly. The available moves: ask about specific stages rather than about satisfaction · ask about other people ("did anyone in your party find anything difficult?"), which is measurably easier to answer · use a third party who is not the planner, the venue, or the couple, since the guest is protecting all three · anonymise properly and say so · and include behavioural measures that do not rely on report at all — when people left, where they sat, how long the seating-chart queue was, whether the quiet room was used.

And state the limit honestly in the write-up: a study of what guests report is not a study of what they experienced, and this chapter's central claim is precisely that those two differ.

Chapter 30 — After the Last Dance

A.1 🚪 The load-out is planned with the load-in, or it is not planned. They are the same problem in opposite directions, with one difference: the second one happens when everybody is exhausted and it has a deadline.

What determines everything else: how much of the breakdown happens before the party ends. Gifts moved at 9:30, empty rentals stacked as they empty, the bar counted at 10:15 while it is still serving — that decision, made in the plan, sets what time you get to bed.

A.4 One named owner · moved by 9:30, not at the end · and somebody confirms out loud that it has moved.

The sentence that precedes every loss: "I'm sure someone's got it."

A.7 1. Does the venue permit equipment to remain after handback, and at what cost? Many permit it free if asked; some charge a full second day. 2. Who is liable for it while it sits there? Almost never you — confirm it in writing rather than discover it. 3. Who lets the collection in?

The third fails most often. The venue is closed on Sunday, nobody has a key, and a truck arrives at eight.

A.10 The return is the unspent money, given back deliberately and itemised — on the Reyes–Whitfield wedding, $299.22.

It matters out of proportion because it is the only moment in the engagement where the planner's incentive and the client's are visibly aligned, and the couple can see it. Nobody tells their friends their planner came in on budget — that is the expectation. Everybody tells their friends about the money that came back, because a returned cheque is a story with a number in it, and it is the cheapest reputation any planner will ever buy.

A.13 1. Your own finding log, written that night and during the day — the primary document, and nobody else can produce it. 2. Vendor debriefs, which are about your process. 3. Specific questions to the couple about events rather than experience — "did everybody get the meal they asked for?", not "was the food good?" 4. Specific questions to two or three guests, chosen from the edges — who left early, who came alone. The fourth is the instrument nobody uses.

A.16

Only the third has been learned. The first two feel like learning and recur, in a form that feels like wisdom and is not.

A.19 A referral is produced during the work, not requested at the end of it — by how you treated the guests' aunt, whether the vendors would work with you again, and whether the couple's friends watched you be calm. The wrap-up collects it; it does not create it.

The only active thing you do: make it easy and specific at the moment the goodwill is highest — "if anybody asks you who to talk to, I'd love you to send them to me" — once, in the wrap-up, and then never again. A request repeated is a request that has become a favour.

B.1 Load-out run sheet — 130 guests, hotel, music ends midnight, room needed for a conference at 8 a.m.

21:00  Gift table and card box → the couple's room. NAMED. Confirmed out loud
21:30  Empty rentals from the ceremony space stacked in the service corridor
22:00  Personal-items sweep 1 (planner, with the list)
22:15  Escort cards, signage, and anything with a name on it collected
22:30  Bar count begins — WITH THE BAR STILL SERVING. A number taken while
         the thing exists is a fact; a number taken after is a recollection
23:00  Florals released to guests (a hotel skip is the alternative — Ch.35)
23:15  Non-critical AV struck: uplighters, anything not the dance floor
23:45  Vehicles brought to the loading bay. Lift booked and CONFIRMED
       ★ THE HOTEL'S SERVICE LIFT IS THE CRITICAL PATH AND IT IS SHARED
00:00  Music ends
00:05  Sweep 2 — same route, looking at the room rather than at the list
00:15  Photographic damage walk with the duty manager, on a phone
00:30  Everything the couple own → their room, in one trip, listed
01:00  Off site
       Rentals collected Monday: the hotel's store room, agreed at
       contracting, in writing, with a named person who has a key
07:30  (Sun) Text to the duty manager with the walk photographs, before
         anybody sends anything on Tuesday

The point of the sheet is the left-hand column: everything above midnight is the answer to "what time do you get to bed?" — and in a hotel the second answer is the service lift, which is shared with room service, the kitchen, and the conference set-up crew, and which nobody books.

B.3 Rubric. The list is category four — the couple's things — and it is written from their side: rings, licence, the card box, gifts, the top tier, the guest book, the dress and its bag, personal florals, worn shoes, chargers, both sets of parents' coats, and the things guests hand people during the evening.

The second sweep's route is the same physical route and a different instruction. The first is walked reading the list; the second is walked looking at the room — under tables, on window ledges, behind the bar, in the toilets, in the room nobody used. They find different things because they are different cognitive tasks, and a single sweep done twice as carefully finds less than two sweeps done differently.

B.6 A gratuity schedule, 100 guests. (Tier 3, US-shaped — among the most regionally variable figures in this book.)

What you tell the couple, and when. Twice.

At the budget stage (Ch.6), as its own line, because gratuities are the classic unallocated remainder — $505 is 1.2% of a $42,000 wedding and it is exactly the kind of figure that lives outside every category and then appears in cash in the last week.

And at −2 weeks, in the form of an instruction: the amounts, in labelled envelopes, prepared in advance, handed to one named person who is not the couple and who has the list of who gets which and when. The couple should not be finding cash at 11 p.m.

And say the honest part out loud: gratuity norms are regional, they change, and the service-charge question is the one that matters — a couple who tips 20% on top of a 24% service charge that already reaches staff has spent $2,000 twice.

B.8 The wrap-up opening, with a genuine costly error. (Ch.30's rule: you go first, and before the money.)

"Before we do anything else, I want to tell you the things I got wrong, and I want to start with the big one, because you already know about it and I'd rather it came from me.

Dinner was thirty-five minutes late and that was my error, not the caterer's.* I gave Marguerite a ceremony end time of 5:15 and the ceremony ended at 5:50. She built her whole service around the time I gave her. She did nothing wrong and I want to be clear about that in case you'd been thinking otherwise.***

What it cost: your cocktail hour ran ninety-five minutes instead of sixty, you ran out of canapés, and about a third of the room was standing for longer than anyone should stand. Your speeches then ran into the light, which is why the photographs of the toasts are the ones you don't like.**

What I've done about it: the caterer's brief now takes its time from the run sheet rather than from me, and there's a −7 day confirmation where the caterer reads their timing back to me and I check it against the actual ceremony length. That should have existed.

And the money.* Marguerite charged an additional $340 for the extended staff hours. I've paid that, not you — I've credited it against my final invoice, which you'll see in the reconciliation in a moment. I'm not doing that to buy anything from you; it's just that you shouldn't pay for my arithmetic.***

That's the big one. There are three smaller ones. Then when I'm done, I want the things you noticed, including the ones you think are too small to say."**

Three things to notice about the script. The error is named without hedging and without distributing it ("the timing was tight" would be a lie). The vendor is explicitly cleared, because the couple have been privately blaming Marguerite for eleven weeks. And the money is settled by the planner before the couple ask — which is the difference between an apology and a correction.

B.10

Note that all three changes are edits to templates rather than resolutions to remember. A finding that does not change a document has not been learned.

B.12 Rubric. Which guests: the edges. One who left early, and one who came alone — not the couple's closest friends, who will say it was wonderful and mean it. Two weeks is right: long enough for politeness to relax, short enough for detail to survive.

And the questions must be about events, not experience:

1. "How long did it take you to get from your car to your seat?" — an answer with a number in it. 2. "Was there any point in the day where you weren't sure where to go or what was happening?" — the friction question, without the word "problem." 3. "Could you hear the ceremony from where you were sitting?" — the single commonest unmet need, and it is never volunteered. 4. "Was there any point you'd have liked to sit down and couldn't?"

All four are answerable without criticising anybody, which is the whole design constraint: the disclosure problem means a guest will not report a failure but will happily report a fact.

C.1 Rubric. Report the three terms as written, verbatim. The interesting part of the exercise is the last clause — whether you had to ask — and the usual finding is that handback time is in the contract, damage-deposit terms are in the contract, and the overnight-equipment policy is not written anywhere and has to be asked for, which is exactly why §30.6's third question fails most often.

C.3 Rubric. Verbatim is the instruction, because the paraphrase is where the sting goes missing. Expect some version of: late final numbers · changes on the day that were decided a week ago · being asked for things by three different people · unclear access and no parking for their vehicle · being told "as soon as possible" instead of a time · and no meal. The exercise works because it is an admission rather than a request, and a vendor who has been asked this question by no planner in eleven years usually answers without pausing.

C.6 Rubric. The report must name the file that changed and quote the old and new text. "I'll remember to check that" is not a systems change, and the exercise exists because roughly nine in ten findings die at exactly that sentence.

D.2 Rubric. The objection is fair and should be stated at full strength: we are not your quality-assurance process. You are asking us to go looking for faults in the best day of our lives, two weeks after it, in order to improve your business — and the asking itself changes how we remember it. There is a real risk of manufacturing a disappointment that did not exist.

What survives: §30.8's technique already concedes most of it. The planner goes first and names their own errors, which means the couple are asked to confirm rather than to generate. The questions are about events — "did everybody get the meal they asked for?" — which is a factual question with no critique in it. And the couple are never asked to evaluate their own wedding.

What does not survive: any version that opens with "so what could I have done better?" That is the imposition the objection describes. A strong answer also concedes the harder point — that the planner's learning is a benefit to the planner — and concludes that this makes it something to be done gently and briefly, not something to be dropped.

D.4 Prediction, and it is correct: Chapter 38 says the highest-value marketing activity is relationships with venue coordinators and other vendors — CPA ~$278 — **and that past-client referrals are cheapest of all at ~$91.** Which sounds like a contradiction: §30.9 says referrals are not requested, and Chapter 38 says referrals are the best marketing channel there is.

The reconciliation is that they are claims about different things. §30.9 is about the mechanism of a referral — it is produced by the work and cannot be extracted afterwards by asking harder. Chapter 38 is about where a planner's attention should go, and its finding is that the cheapest channel is the one produced by work already done. The two agree exactly: the marketing activity is the work. What Chapter 38 adds is that you should notice it, count it, and know which channel produced each booking — which is the one active thing §30.9 permits, extended into a column in a spreadsheet.

D.6 Rubric. The ratio is asserted and should be attacked. It has no basis — it comes from one planner's logs, on one kind of event, and the classification of a finding as "about your own process" is made by the person whose process it is, which is the least reliable possible judge.

Is there a principled number? Probably not, and a strong answer says so. The ratio's honest defence is diagnostic, not descriptive: a log that is 0% about your own process is almost certainly not being written honestly, and a log that is 90% about your own process suggests either a first year or a person being unkind to themselves. The number is a smell test wearing a statistic's clothes, and the chapter should have said that. The Reyes–Whitfield log came out at 9 of 24, or 38% — which is consistent with the claim and is also a single observation.

M.1 The fourth column is what it should have been in the first place — the estimate you would give the same wedding tomorrow. Budget, actual, and variance tell you what happened; the fourth column is the only one that changes the next quote.

And the only thing that improves your estimating is comparing your estimate to the outcome, in writing, repeatedly, on the same categories. Not experience — experience without the comparison produces confidence rather than accuracy.

M.3 The disclosure problem transfers almost intact: the couple are grateful, nothing can be fixed now, and they attribute problems to themselves — "we should have started the speeches earlier."

The extra reason that does not apply to guests: the couple do not know what was supposed to happen. A guest cannot compare the day to a plan; the couple cannot either, because the plan was yours. They cannot report that the cocktail hour ran thirty-five minutes long, because as far as they know it was sixty minutes and it felt long. Which is why the instrument is a specific question about an event, and why you go first.

M.5 The incident note is contemporaneous, factual, and defensive — written that night, one incident, for an insurer and for a conversation you will otherwise misremember. No speculation, no blame, no improvement. The finding log is cumulative, evaluative, and improving — many entries, across the whole event, explicitly including your own errors, and it exists to produce systems changes.

If you merge them, two things happen and both are bad. The finding log's honesty poisons the incident note — a document that says "I should have checked the permission" is a document an insurer or an opposing lawyer will read, and it converts a factual record into an admission. And the incident note's discipline sterilises the finding log: a log written in a register that avoids blame will not say the one thing that matters, which is that you were nine of the twenty-four entries.

M.7 The bar count at 22:15 feeds consumption modelling — the thing Chapter 15 admitted it could not support, because there is no published evidence base for "two drinks in the first hour, one an hour after."

For the count to be worth anything it needs to become data rather than an anecdote: the same planner, recording the same fields — guest count, drinking guests, duration, whether spirits were served, weather, and whether dinner was seated — across twenty or thirty events, in the same units (bottles opened, not bottles gone), and counted at the same moment relative to service. One count from one wedding tells you what one wedding drank. Thirty tells you what your clients' weddings drink, which is the only population you need.

M.9 Chapter 9 needed: the policy in force on the date, the loss not excluded, adequate limits, and prompt notice. §30.4 provided the evidence: the ten-minute photographic damage walk with the venue manager, done that night, and the twenty load-in photographs from Chapter 13 — which together establish the condition of the site both before and after, with timestamps. §28.9 added the incident note: written that night, factual, contemporaneous, recording what happened, who was involved, what was done, and who was told when.

Together they are why a Tuesday claim is a five-minute email rather than a fortnight. The venue that receives a 7:15 Sunday message with photographs usually does not send the Tuesday email at all.

E.1 Rubric. A thirty-minute instrument that produces changes rather than reflections has roughly this shape:

(a) Five minutes, that night: the finding log, unfiltered, no categorisation. (b) Ten minutes, the next week: the reconciliation's fourth column — what it should have cost. (c) Ten minutes: convert findings to systems changes, with the two columns that make it real — artefact, owner, due date — and be explicit that most findings will not be converted. (d) Five minutes: pick the three or four you will actually do this season, and defer the rest with dates rather than deleting them (Ch.39).

The instrument fails if it has a "reflections" box. What it misses, and every honest report of this exercise should say so: everything the planner did not see — which is why instruments 2, 3, and 4 in §30.8 exist and why a solo review is structurally incomplete.

E.3 Rubric — structural reasons, and the essay should refuse the moral ones. Available structural arguments: the review has no client and no deadline, so it loses to everything that has both · the next wedding's deposit arrives before the last one's lessons · the work is seasonal, so the review falls in the week you are least able to do anything · the finding is separated from the fix by months, so nobody is present at the moment the change would pay · a solo planner has nobody to be accountable to, and the practice is unenforceable in a business of one · and the review's product is invisible — nobody can see the crisis that did not happen.

One change that would make it happen: put the review inside a document that already has a deadline. The final invoice, the reconciliation, or the deposit return — attach the finding log to a thing the planner must do anyway to get paid. The general principle, which is Chapter 39's: a practice that depends on discipline fails, and a practice attached to an existing obligation survives.

E.5 Rubric. Define "actionable" first and defend it: a finding is actionable if it names a specific artefact that could be changed — a template, a checklist, a clause, a script — and a strong definition adds a second gate: whether the change was still in place a season later, since a change that is reversed was not actionable, it was enthusiasm.

The design: across 20–30 events, run all four instruments every time, time each one, and have findings coded blind by two coders against the definition. Report actionable findings per hour, and report overlap — the more interesting result is almost certainly not which instrument wins but how little the four overlap, which is the argument Appendix F makes from the Reyes–Whitfield wedding: seven instruments, roughly forty findings, and not one instrument found what another found.

Name the confounds: the planner runs three of the four instruments and knows the hypothesis; the fourth (guests) has the lowest response rate and the highest value, which will bias per-hour cost against it if non-response time is counted and in its favour if it is not.

Chapter 31 — Corporate Events and Conferences

A.1 🚪 A corporate event has a business objective, and somebody will be asked about it by name.

The planner's first job is interrogative, not logistical: to find out what has to be true afterwards that is not true now, and who will be asked whether it worked. It is not logistical because every logistical decision — the agenda, the room set, the food, the AV budget, the evening — is either justified against that objective or inherited from last year, and you cannot tell which until the objective exists in writing. Most do not exist in writing. Priya Raghunathan's reaction to seeing hers written down was "nobody's ever written it down," and she had run the event for six years.

A.3

Most events have two objectives and pretend to have one.

A.6 A room block is a number of room-nights the hotel holds for your attendees at an agreed rate. Pickup is how many are actually booked. Attrition is the clause that charges you when pickup falls below an agreed threshold — typically 80% of the block — at an agreed basis. The cut-off date is when unbooked rooms return to the hotel's general inventory, after which your attendees pay whatever the hotel is charging that week.

A.8 Attrition · the F&B minimum · the cancellation schedule · and the walk clause (what happens when the hotel oversells and moves your attendee to another property — who pays, for what, and how far away).

The number you must ask for: the hotel's actual pickup history for comparable groups, three years. They have it. They will not offer it, and it is the only evidence that will move an attrition threshold — the Cascadia's own history was 74%, 77%, 71%, which made 80% indefensible and 75% obvious.

A.11 Attention: 50–60 minutes per mode. Transitions: 12–15 minutes for 400 people, 20 with one corridor. Breaks: 20 minutes minimum, 30 if there is a queue. Breakout size: 25–40 for discussion, 12–20 for practice. Room sets: theatre 6–8 sq ft per person, classroom 15–18, rounds 12–15, U-shape 30+. The first morning always starts late — build in 15 minutes on day one.

And the rule that governs all six: every one of them is a floor, they compound, and a fully-programmed conference day is over-programmed.

A.14 The sponsor is the person who will be asked in April whether it worked — the budget holder and the only person who can move an executive's stage time. The programme owner is who you talk to daily, who owns the agenda operationally and usually has no authority over the people on it.

The commonest error a wedding planner makes: treating the programme owner as the client. In a wedding the person you talk to is the person who decides. In a corporate event they are two people, and taking an agenda problem to the programme owner produces sympathy and no change. The second error, which follows: naming a VP. A planner who says "the EMEA update should be cut" has made it a fight between that VP and the planner, which the planner loses. You price the hour and hand the decision to the sponsor.

A.17 Capability is the strongest available measure — whether people can do something afterwards they could not do before.

It requires being designed in advance: a defined competency, an assessment instrument that exists before the agenda does, agenda time for practice rather than exposure, and — the part that gets cut — the assessment actually built into the programme rather than promised for afterwards. Northwind certified 371 of 400 against a target of 340 because certification was on the agenda as a session, not because 400 people were told about a product.

A.20 Tech rehearsal (AV alone, no talent) · speaker rehearsal (everyone who will stand on that stage, in that room, with their own slides, fifteen minutes each) · the walk-on and walk-off · the transitions · and a full run of the first twenty minutes at speed with everything live.

The transitions are where general sessions actually fail. Individual speakers are usually fine. The failure is the six seconds between them — a laptop that will not switch, a video that starts silent, a person walking on while the previous one is still talking — and it is invisible in a plan and unmissable in a room.

B.1 Four questions, and what you are listening for.

1. "What has to be true in October that isn't true now?" — Listening for: whether an objective exists at all. Silence, a laugh, or "good question" is the answer, and it is the commonest one. If they answer immediately with "the directors need to be aligned on the restructure," you have a real objective in the first ten minutes.

2. "Who's going to be asked whether it worked, and what will they be asked?" — Listening for a name. A named person with an accountability can tell you what counts as success; "the exec team, I suppose" means nobody will be asked, which means the event is recognition or inheritance and should be budgeted as such — honestly, and out loud.

3. "What was on the agenda last year, and who built it?" — Listening for the inheritance. "We just do the same shape" and "we ask people how long they want" both mean the agenda encodes the org chart. This is the question that finds the six wasted hours.

4. *"Is $95,000 a budget or last year's number?"*** — **Listening for whether anybody has ever tested it.** And follow it immediately with the one they have never been asked: ***"forty directors for two days is 640 hours of director time — do you know what that costs?"*** **At a $140 loaded rate that is $89,600, which is the entire budget again, and it is in nobody's spreadsheet.

B.3 250 attendees, 2 nights, rate $189, block 460 room-nights, threshold 80%, pickup 331.

Now the three moves, separately.

Three observations the exercise is for.

The threshold move is the largest single saving ($4,347) and it costs nothing but evidence — ask the hotel for three years of pickup history.

The rate-less-tax move is the smallest ($325) and it is the one planners spend the most negotiating breath on, because it feels like a principle. It is worth about 5% of the exposure.

And the resell credit eliminates the remaining balance entirely — because 40 resold room-nights against a 14-night shortfall is not a partial credit, it is a wipe-out. That is why it is worth more than the other two combined at any hotel with real transient demand, and it is the clause most often missing from the contract. Note that this is a demand-dependent claim: in a hotel that will not resell, the credit is worth zero, and the chapter should be read as saying so.

B.5 11 hours × 320 people = 3,520 person-hours. At $92 loaded: $323,840.

Per hour of general session: 320 × $92 = $29,440.

The one sentence you say in the meeting:

"Every hour we're all in that room together costs about twenty-nine and a half thousand dollars of people's time, and there are eleven of them — three hundred and twenty-four thousand dollars, which is more than the event budget. Given the objective is capability, how many of the eleven do we think produce it?"

Three things about that sentence. It contains a number nobody in the room has ever seen. It names no person and cuts no session — it asks a question. And it converts an argument about seniority into an argument about arithmetic, which is the only argument a planner can win.

B.7 280 arrivals over 90 minutes, 40% in the peak 30 minutes = 112 arrivals in 30 minutes.

Staffed desks at 45 seconds each: 112 × 45 = 5,040 seconds of work ÷ 1,800 seconds available = 2.8 desks.

And this is where the formula must not be trusted. Three desks is 93% utilisation, and a queue at 93% utilisation does not behave like a queue at 70%: the average wait is about 3.3 minutes and the person who arrives at minute 22 waits far longer than five. Four desks takes the average wait to roughly 16 seconds.

Answer: four desks. The formula sizes capacity; it does not size a wait, and the difference between them is the whole of queueing.

Pre-printed self-serve badges at ~12 seconds: 112 × 12 = 1,344 seconds ÷ 1,800 = 0.75 stations. Two kiosks holds the average wait under five seconds — and you still staff one desk for the misspellings, the walk-ups, and the person whose name is not on the list, who are roughly one arrival in eight and who take three minutes each.

So the honest comparison: four staffed desks, or two kiosks and one desk. The technology decision is worth more than the staffing decision, and it was made three months earlier by whoever chose whether badges would be pre-printed.

B.9 Four procurement questions in week one, and what each changes about your cash flow.

1. "Do I need a purchase order before I invoice, and who raises it?" — If yes, your invoice cannot be paid until it exists, and the PO usually takes longer than the approval. No PO means an invoice that sits in a queue nobody owns. 2. "What are your standard payment terms, and are they net 30, 45, or 60 from invoice or from month-end?" — Net 60 from month-end is up to 90 days. This single answer decides whether you can afford to carry the event's supplier deposits. 3. "Am I paying vendors directly, or are they being contracted by you?" — The difference between $8,000 of exposure and $340,000 of exposure. If you are paying them, you are financing the client's event out of your own account. 4. "Do you have a supplier onboarding process, and how long does it take?" — Vendor registration, insurance certificates, tax forms, and portal access routinely take four to six weeks, and the answer "oh, a few days" is given by people who have never done it. Ask before you sign, not before you invoice.

B.11 The paragraph a sponsor reads to a CFO — good pipeline number, weak attribution.

"The event produced $14.2 million of identified pipeline against a $4.1 million baseline, and 371 of 400 attendees certified on the new product against a target of 340. I want to be straight about what those two numbers are worth. The certification number is directly attributable — we assessed people in the room, and they could not have passed it before. The pipeline number is not. Q1 pipeline is affected by the event, by the product launch, by the comp plan change, and by two competitors' pricing moves, and no method available to us separates them. What I can say is that pipeline is up 3.5× on the same quarter last year, that the largest increases are in the regions with the highest certification rates, and that this is consistent with the event working — but consistency is not attribution. If we want attribution next year we would need to hold a comparable group out, and I do not recommend that we do."

Why that paragraph works: it gives the CFO the number they asked for, tells them what it can carry, and offers the one design that would fix it while advising against it — which is more credible than either overclaiming or refusing to answer. A planner who says "we can't measure that" gets replaced by one who says they can.

B.14 The four category-D items at a corporate event, and what must exist in advance.

Note the fourth: the demo is category D not because it cannot be replaced but because it fails publicly, on stage, in front of the objective. The recorded version takes ninety minutes to make and it is the cheapest insurance at the entire event.

C.1 Rubric. Report the four clauses verbatim, then the changes. Expect to find: attrition at 80% with damages at full rate and no resell credit · an F&B minimum stated as a cumulative figure exclusive of service and tax (so the real number is 35% higher) · a cancellation schedule that escalates to 100% inside 90 days · and a walk clause that promises "comparable accommodation" with no distance limit and no compensation.

What to change: threshold to 75% with evidence · damages at rate-less-tax · a resell credit, explicitly · the F&B minimum stated as consumption exclusive of service and tax, and a written statement of whether it is cumulative · and the walk clause given teeth: a distance limit, a paid transfer, one night at the hotel's cost, and return the following night.

C.3 Rubric. Record the registration wait in minutes, honestly, including your position in the arrival curve. The eleven friction points transfer almost intact — the notable difference is that a conference has badges, which is a friction point weddings do not have and which the chapter's arithmetic sizes. Most delegates report a wait of 5–20 minutes at a badly-staffed event, and the exercise's value is comparing that to the two-line calculation in B.7.

C.6 Rubric. Time it end to end and report the gap between approved and PO issued — which is where the money actually is. Expect two to six weeks, expect the people inside the process to be surprised by the number, and note that a planner who does not know this number is financing it.

D.1 Rubric. Both cases are available and the honest answer is that it is mostly a difference in convention.

For a real distinction: a corporate objective has a named person accountable for it, a budget justified against it, and a counterfactual (what would have happened anyway) that somebody cares about. A wedding's objective — two people are married and the people they love had a good day — is genuinely achieved almost regardless, so measurement has little to act on.

For a difference in convention: a wedding could be measured, easily, and this book measures it. Chapter 29's guest-experience instruments, Chapter 30's finding log, and the debrief are measurement. Did everybody get the meal they asked for? Could people hear? How long was the seating-chart queue? — all countable, none conventionally counted.

What to actually do: measure the wedding on process rather than on outcome. Do not ask whether the day was good; count whether the things you designed happened. That is the version that improves practice and does not turn a wedding into a KPI.

D.3 Rubric. The opposing case at full strength: a planner who prices an hour and then refuses to say which hour is hiding behind arithmetic. You have the whole agenda in front of you, you know which sessions serve the objective, and the sponsor is paying for judgment. "Here are three versions, you choose" is a way of never being wrong.

That case has real force and should be conceded. The reconciliation is about mechanism rather than courage: a planner's recommendation is only usable if it survives the politics, and a recommendation that names a VP is dead on arrival — it converts an argument about the objective into an argument about the planner.

So: yes, say which — but say it to the sponsor, in private, as an answer to a direct question, and only once the arithmetic is on the table. "You asked what I'd cut. I'd cut the three regional updates, and here's the number." In the meeting with the VPs in it, you present three versions and no names. The distinction is not between having a view and not having one; it is between where the view is said.

D.5 Rubric. The claim is strong and mostly holds. What attribution would require: a control group of comparable employees who did not attend, assigned in a way not correlated with performance or seniority · a pre-registered outcome and window · retention measured at 12 and 24 months · and enough people to detect an effect on a base rate of perhaps 12–15% turnover, which for a plausible effect size means thousands of employees, not four hundred.

Is any of it feasible? Almost none, for three reasons: you cannot randomise attendance at an event whose purpose is inclusion; the sample is an order of magnitude too small; and the confounds — pay, manager, promotion, the market — are larger than the effect. What is feasible: measuring the mechanism rather than the outcome. Whether attendees report a clear plan, whether they met the people they need, whether they can do the thing. Those are attributable and they are honest, and the professional move is to offer them instead of a retention claim.

D.7 Rubric. §31.10's claim — corporate attendees disclose less because it is their workplace — is testable in principle and untested here. What would make it true: a measurable disclosure gap for the same need in the same person across the two settings; a plausible mechanism (career consequence, visibility to a manager, the fact that the dietary form goes to somebody in HR who is also on the promotion panel); and higher observed unmet need despite better provision.

What would make it false: corporate events have anonymous registration forms, a professional intermediary, and no social relationship with the requester — all of which reduce the cost of disclosure. A guest at a wedding is asking their friend's planner for special treatment at their friend's wedding, which is arguably worse. A defensible verdict: the direction is not obvious and the chapter overstates it.

What it changes: if corporate disclosure is lower, the provision must be universal rather than requested — accessible seating that is simply there, captioning as default, food that is labelled rather than special-ordered. Which is the right answer either way, and that is worth saying: the design that survives being wrong about the disclosure question is universal provision.

M.1 At 400 people the cascade gains mass. A wedding's delay propagates through a chain of about six things; a conference's propagates through parallel tracks that must re-converge — three breakouts that all feed one general session, and the whole day waits for the slowest room.

The genuinely new source of delay is the transition itself. 400 people between rooms is 12–15 minutes and 20 with one corridor — a duration that does not exist at a wedding, is invisible on an agenda, and is not the same as a break. An agenda that schedules a session to end at 10:30 and the next to begin at 10:30 has scheduled a 20-minute delay and will accumulate one every time.

M.3 Scales directly: the per-head arithmetic (consumption, dietary proportions, the banquet multiplier — 1.3516 at 24% and 9%, identically) and the service-timing arithmetic (a plated course takes what it takes, per server, per table).

Does not scale at all: the dietary handoff. At 100 guests you can carry the exception in your head and hand the plate to Marisol yourself. At 400, across nine meal periods and three rooms with rotating staff, the fourth handoff — kitchen to guest — has no owner unless one is manufactured, and the mechanism must be structural: printed table-level manifests, coloured plate markers, a captain per room whose job it is, and a badge that carries the requirement so the guest does not have to.

M.5 Worse at a conference: finding it (a large venue with four entrances and no signage), arriving (the badge queue, which is a wedding friction point that does not exist), finding a seat (every session, several times a day, in the dark, alone), and the gap — a conference has more unstructured time than a wedding and less permission to leave.

Better: parking (usually structured), the ceremony → sessions (you can leave a session), eating (buffets have no seating anxiety attached), and leaving (a delegate leaves when they like and nobody notices).

And the one nobody plans: the conference equivalent of "who is alone." A delegate attending alone is the majority case at a conference and the minority case at a wedding, which inverts the design — at a wedding you seat the solo guest carefully; at a conference you have to manufacture the reason two strangers speak, and unstructured time does not do it by itself.

M.7 Theatre 6–8 · classroom 15–18 · rounds 12–15 · U-shape 30+ sq ft per person.

The set most often wrong in a hotel proposal is classroom — and it is wrong in a specific direction. Hotels quote classroom capacity at theatre-like densities, because the capacity chart in the sales kit was built for the room's maximum and not for a table, a chair, a laptop, and a person's arms. A room sold as "classroom for 120" is a comfortable classroom for 70, and the failure appears at 8:55 on day one with twenty people standing.

M.9 Still applies from Chapter 3: one voice at a time (a committee needs a single named channel or you will receive contradictory instructions from three people, all sincere) · decisions in writing with a date and a reason · the two-options-and-a-deadline technique · and the distinction between a request and an anxiety.

What is genuinely new: the committee is not the client. A wedding's decision-makers are the people in the room; a committee's authority sits outside it, with a sponsor who is usually not in the meeting. Which means the planner must know which decisions the committee can actually make — and route the ones it cannot to the person who can, without embarrassing the committee, since you will work with them daily for nine months.

E.1 Rubric. The chain must be unbroken and each link must be written before the next is designed: objective → agenda design → instrument → the April paragraph. The common failure is designing the agenda first and reverse-engineering an instrument that measures whatever the agenda happened to produce.

Then the attack. A competent attacker will say: your measure moved and so did four other things · the people who attended are not comparable to the people who did not · your instrument measures confidence rather than capability · and the strongest one: the objective was written after the agenda existed. A strong submission survives the first three and concedes the fourth honestly if it is true.

E.3 Rubric. Expect mechanisms the chapter does not name, some of them uncomfortable: the agenda is set by whoever controls the calendar invite · a segment survives because a sponsor's boss is in the room · stage time is a proxy for headcount in the next planning round · the fight is settled by whoever is willing to be unpleasant in a meeting · and the commonest of all — nobody fights, the agenda is copied, and the sender of last year's file wins. Report verbatim, and note which mechanisms are about the objective and which are about the org chart. It is usually all of them.

E.5 Rubric. A working one-pager is short and answers four things: what has to be true afterwards · who will be asked · what they will be asked for · and what number would count as success. Everything else is decoration.

Where it breaks, and every honest report finds this: at question four. People will answer the first three and then say "I don't know, what's normal?" — and the instrument must have an answer ready or it stalls. The fix that works is offering a range with a mechanism attached ("a capability objective is usually a pass rate against an assessment — would 85% of attendees be a success?"), which converts an impossible question into a yes/no. Report where your version stalled, not where it succeeded.

Chapter 32 — Galas, Fundraisers, and Social Celebrations

A.1 Cost per dollar raised = total cost ÷ gross raised.

Galas: typically $0.25–0.50.** **Major gifts: $0.05–0.15 — Fairhaven's major-gifts programme ran at $0.06** and its gala at **$0.373. Donor acquisition runs at $1.00–1.50 and is correct, which is why the ratio is not a verdict on its own: fundraising is a portfolio, and a portfolio containing only cheap channels is a portfolio that is shrinking.

A.3 Five things a letter cannot do: put prospects and the organisation in a room together · let somebody who has been helped speak in person · make giving public and therefore social · recognise donors in front of their peers · and give a board a reason to ask their friends for something.

Least efficiently: raise money. On pure cost per dollar raised a gala is beaten by a letter, an email, and a phone call. Its case rests entirely on the other four, and a gala whose only justification is the money should usually not be held.

A.6

Sponsorship and the paddle raise produce most of the money for almost none of the effort. The silent auction produces the least for the most, and it is the one that gets the volunteers.

A.8 The ask goes early — before the main course, at around 7:50 in a 7:00 room, not at 9:40.

Three reasons the traditional placement is worse. The wealthiest guests leave first, and sixty of Fairhaven's had gone by 9:40. Four hours of an open bar is not a fundraising aid — it produces noise, not generosity, and it produces regret the next morning, which is a donor-relations problem. And attention is a depleting resource: a room at 7:50 is present, a room at 9:40 is managing its own evening. The move costs one conversation with a caterer and at Fairhaven it was worth $102,000.

A.11 A lead gift is a large gift secured privately before the event and given publicly first, at the top of the ladder.

It is necessary because nobody wants to be first to raise a paddle at $25,000 in front of four hundred people. Without one: the top rung gets silence, the auctioneer drops a level to rescue the moment, and every rung below runs one rung low — the loss compounds all the way down and it looks like a soft room rather than a preventable error. It was preventable by one phone call three weeks earlier.

A.14 Fairhaven's silent auction: 95 items, $61,000 gross, 1,100 volunteer hours from 40 people, 11 of them trustees — $55.45 per volunteer hour.

The cost nobody computes is the opportunity cost. Those hours were not free and they were not fungible: eleven trustees spent a season sorting items, and the same eleven trustees, asked individually for one sponsor each, produced $155,000 from perhaps forty hours.** **The auction did not cost nothing. It cost $155,000 of sponsorship — and it happened because sorting items is pleasant, bounded, and visibly productive, and asking a friend for $25,000 is none of those things.

A.16 A committee is for access and asking — the people its members know, and the willingness to ask them. It is not for design, catering, décor, or the run of show, and a committee given those things will spend nine months on them and never make an ask.

The kind of ask that works: individual, specific, bounded, and made by a person rather than to a room. "Would you ask Kwame at Halstead for a $25,000 sponsorship? Here's the one-page, I'll draft the email, and I'll follow up in a fortnight." A general appeal to a committee — "we all need to sell tables" — produces nothing, reliably, because it is addressed to nobody. Eleven trustees asked individually; seven delivered.

A.18 No. Underwriting does not reduce cost per dollar raised — the costs are the same costs, and if the underwriting is counted as revenue, the ratio is unchanged or slightly worse.

What it changes is a sentence. "Not one dollar of what you give in the next twelve minutes pays for any of this — the evening is paid for." That sentence is worth more than the money it describes: at Fairhaven the $1,000 rung took 38 paddles instead of 25. What underwriting buys is the removal of the donor's suspicion that their gift is paying for the flowers, and that suspicion is expensive.

B.1 Net $267,000. Cost per dollar raised $0.44.

"We grossed four hundred and seventy-eight thousand dollars and netted two hundred and sixty-seven, at forty-four cents of cost per dollar raised."

"That number isn't a verdict, it's a demand for an argument: it's a good number if the room was full of people we're now closer to and can name, and a bad one if it wasn't — and at the moment we don't know which, because nobody has been asked to find out."

The second sentence is the whole point. A board that hears only the ratio will either panic or defend, and both are wrong. A board that is asked which prospects moved will answer the question the gala actually exists to answer.

B.3 A revenue architecture for $850,000 net, 400 guests.

Built with $25,000 of margin against the $850,000 target, because a gala's revenue is a forecast and its costs are a contract.

What I would cut first if short: production and décor, which is the largest discretionary line and sits in the bottom row of Chapter 29's notice ranking. Then print. What I would not cut, in any circumstance: the auctioneer, the time spent securing lead gifts, or the seating design — those three are the revenue, and cutting them to save $16,000 is how a gala loses $100,000.

B.5 A paddle-raise ladder, 250 guests, top prospect $15,000.

138 of 250 guests raise a paddle — 55%, which is a good room and not an impossible one.

The two numbers secured in advance: the $15,000 and one of the $10,000s. They are 17% of the total and they are the reason the other 83% happens. Ask both privately, three weeks out, and tell each of them exactly when they will be asked to raise the paddle. The descending ladder only works if the top rung lands immediately — a five-second silence at $15,000 costs the auctioneer the room, and the recovery is to drop a level, which loses roughly a rung's worth all the way down.

**And notice the bottom two rungs: 95 paddles for $33,750.** **They are 23% of the money and they are next year's room** — the $250 donor who gave publicly for the first time is the only place major donors come from.

B.7 95 items, $38,000, ~700 volunteer hours, 25 people, 9 of them board members.

Now the cost nobody computes. Those nine board members have something almost nobody else has: the ability to ask a peer for a sponsorship. Two asks each, at about two hours per ask including the follow-up, is 36 hours — and at a plausible 50% success rate on a $15,000 package that is **$135,000.**

The recommendation:

"Replace the silent auction with a wine pull and move the nine board members to sponsorship.

The auction line will fall from $38,000 to about $12,000, and I want to be clear that this is a real and predictable loss of $26,000.** In exchange: nine board members making two asks each, at a 50% strike rate on a $15,000 package, is about $135,000 — **a net gain of roughly $109,000 and 650 volunteer hours returned to the organisation.

The number I am least sure of is the strike rate, and it is the number the whole recommendation turns on. If it is 25% rather than 50%, the gain is $41,500 and the recommendation still holds. If board members will not make the asks at all, the gain is negative and we should know that before we cancel the auction, not after."

The last paragraph is what makes it a recommendation rather than a sales pitch. The chapter's own version of this argument concedes exactly the same weakest assumption, and it should.

B.9 A sponsorship ladder to $300,000, 300 guests.

The double-counting risk: nine of the room's thirty tables are inside sponsorship packages. At $7,500 a table that is **$67,500 of table value — and if the budget also counts thirty tables of ticket revenue, the same $67,500 has been counted twice.**

The second and subtler form: displacement. A company that would have bought a $10,000 table and instead buys a $25,000 sponsorship has given you $15,000 of new money, not $25,000. A board looking at a sponsorship line that grew by $150,000 while the tables line fell by $60,000 is looking at $90,000.

How you present it: show sponsorship gross, then a line called table value included in packages (−$67,500), then net new sponsorship revenue. Show tables at 21 sold rather than 30. And say it out loud in one sentence — "nine of our thirty tables are inside sponsorships, so I've taken them out of the ticket line so we don't count them twice" — because a board that discovers double-counting on its own stops trusting every other number in the deck.

B.11 What you say to the chair.

"I want to flag something five weeks out rather than two. Devrim hasn't sold either of his committed tables, and I don't think they're going to sell — that's $15,000 against a $300,000 ticket target and it's the second year running.

What I'd suggest: you call him, not me, and not about the tables.* Ask how he's doing with it, and give him a way out that isn't humiliating — one table instead of two, or ten individual seats, or a sponsorship introduction instead. What I want to avoid is him not coming, because a board member who is embarrassed about tables stops attending, and then we've lost more than fifteen thousand dollars.***

And separately, for next year:* the committee agreed table commitments in a room, all at once, and everybody said yes. That's the mechanism that produces this. Individual asks with an individual number get individual answers*, and people say no in private, which is much more useful than yes in public."

What you do not do: email him · copy the chair · raise it in a committee meeting · re-forecast the ticket line without telling anybody · or sell his tables out from under him, which ends a relationship the organisation needs for twenty years to recover $15,000 once.

B.13 A bar mitzvah: 220 guests, 55 of them twelve and thirteen.

Supervision plan. Named adults, one per twelve young people — five, minimum, with names on the run sheet and not "the parents will keep an eye." One at the entrance to wherever the young people are · one whose sole job is the doors and the outside, which is where the problems are · one in the dancing · and two floating. A named adult owns the phones-and-photographs question, decided by the family in advance and communicated to parents in writing. Alcohol is served nowhere near the young people's space and every bartender is briefed by name. And the parents of every young person get, in writing: what the plan is, what time it ends, who is supervising, and how to reach somebody — because that is what lets them decide whether to stay.

Two-arc programme design. The event is genuinely two events sharing a room — the adults' evening and the young people's — and pretending it is one produces an event that serves neither. Arc one: the service, the family moments, the meal, the speeches, the blessing — front-loaded, because the young people will not sit through 9:30. Arc two: from roughly 8:15, a separate space with its own music, its own food (served late and again later), and activity that does not require dancing, since a substantial fraction of thirteen-year-olds will not dance and currently believe this is a personal failing. The two arcs touch three times, deliberately: the candle-lighting or family moment, one dance the young people are actually invited into, and the close.

The three questions you ask the young person — and you ask them, alone, without their parent answering.

1. "What do you want the evening to feel like?" — the design question, and their answer will be one word. 2. "Is there any part of this you're dreading?" — the most valuable question available, and the answer is almost always a specific public moment: a speech, a dance, a spotlight, being sung to. Once you know, you can remove it or shrink it, and nobody else will ever know it was removed. 3. "Who do you most want there, and where should they be sitting?" — which produces the seating plan for their tables and finds the friend whose absence would ruin it.

🚪 The subject of a social celebration is a child and the client is their parent. The most beautifully executed bar mitzvah in the city can be an event about a family, held for adults, at which the young person had a difficult evening — and nobody would know, because nobody asked them anything.

B.15 The gala nets $170,000 at $0.45 — a gross of $309,091 and a cost of $139,091. The membership programme raises $480,000 at $0.11 — a cost of $52,800 and a net of $427,200.

"On the numbers alone, the membership programme is four times the net for a third of the cost, and if the gala's only purpose is money, the recommendation is to stop holding it and put the $139,000 and — more importantly — the staff time into membership.

But the ratio isn't the whole question, and there's one thing I need you to answer before we decide.* A gala can do four things a membership programme cannot: it puts major-gift prospects in a room, it lets somebody who has been helped speak in person, it makes giving public, and it gives your board a reason to ask their friends for something. If your gala is doing those things, forty-five cents is defensible and the number to fix is the cost, not the event. If it is not doing them — if the room is the same two hundred loyal supporters every year and no prospect has ever moved because of it — then it is an expensive way to raise $170,000 and you should stop.***

I don't know which it is, and neither does anybody in this room, because nobody has ever been asked to track it. That's the first thing I'd fix, and it costs nothing.

And I should say the obvious thing about my own position: I'm paid to produce your gala. If you stop holding it, I lose the fee.* So weight my advice accordingly — and if it helps, I'm happy to be paid for this analysis separately, so that the recommendation doesn't depend on which way it goes."***

The last paragraph is not decoration. A planner recommending a gala has a conflict of interest that the client can see, and naming it first is the only thing that makes the rest of the advice usable. The same disclosure appears in §35.9 and for the same reason.

C.1 Rubric. Report what the annual report actually contains: total fundraising expense and total contributions, from which one aggregate ratio can be computed. The gala's own number is almost never separately disclosed, and that is the finding — special-events revenue is sometimes reported gross with direct costs netted, sometimes as a separate line, and sometimes not at all. Say what you could not determine and why, which is a more useful report than a confident number built on an assumption.

C.3 Rubric. Record the latency. A development professional who has the number at hand answers in under five seconds; the common response is a pause, then gross, then net, then an offer to find out. The interesting finding is not the number but whether it is a number the organisation uses, and the answer is usually that gross is reported to the board and the ratio is computed by nobody.

C.5 Rubric. Count hours honestly and include procurement, sorting, cataloguing, display, setup, monitoring, checkout, and the follow-up on unpaid items — checkout and follow-up are the ones always omitted and they are large. Then ask the three volunteers what else they could have done. Expect two answers: "nothing, I enjoy it" — which is a real and legitimate answer and should be reported as such — and, from board members, a pause. The second pause is the chapter's argument in miniature.

D.1 Rubric — take a position, and both are defensible.

The case that it is having it both ways: the chapter opens with a ratio designed to shock, uses it to establish credibility as a truth-teller, and then spends nine sections explaining why the shocking number does not matter. That is a rhetorical structure, not an argument, and a reader could reasonably say the chapter wants the authority of the critique and the business of the galas.

The case that it is honest: the ratio and the defence are claims about different things — cost per dollar raised is a fact and the pipeline argument is a purpose — and the chapter says explicitly that if the pipeline argument does not apply, the honest advice is not to hold a gala. A book that made the critique and then refused to say when a gala is justified would be less honest, not more.

The strongest version of the answer notices the test: the chapter is having it both ways only if it never reaches the conclusion "don't hold one." It does reach it, in §32.2 and in B.15. That is the thing to check, and it is the thing to demand of anybody who makes this argument.

D.3 Rubric. The assumption is that a board member's silent-auction hours are convertible to solicitation hours, and it is the weakest link in §32.6's argument. Attacks worth making: the two activities need different people — the trustee who sorts items may be the one who will never ask · willingness is not fungible, and an unwilling asker produces a bad ask that damages a relationship · asking has an emotional cost that sorting does not, which is precisely why the sorting is popular · and some board members' value is their name, not their access.

What survives: at Fairhaven, eleven were asked individually and seven delivered — so the conversion is neither 100% nor zero. The defensible version of the claim is that some fraction converts, that nobody knows the fraction until they ask individually, and that the general appeal to a committee reliably produces zero. State the claim at that strength and it holds.

D.5 Rubric. The opposing case is genuinely strong: gross is what the room did together. Net is an artefact of how an organisation chooses to allocate its costs, and it is not comparable between organisations or between years. Announcing "we raised nine hundred thousand dollars tonight" is true, it is what everybody in the room contributed to, and telling them the net is telling them what your overheads are at the moment they are feeling generous.

Then decide, and a defensible decision is: announce gross from the stage, report net and the ratio to the board, and never let the two be confused. The chapter's objection is not to the word gross but to a board that believes gross is the result — and the failure mode it is guarding against is real: an organisation that celebrates $906,000 and never computes $0.373 will run the same gala for a decade. A strong answer holds both: the stage is not the place for accounting, and the boardroom is not the place for applause.

D.7 Rubric. The advice — that a planner should offer to risk their own fee against the event's performance — is easy to give and hard to take, and a planner with two months of runway cannot take it at all.

What would make it realistic: a partial stake rather than the whole fee (a defined bonus above a defined net, with the base fee intact) · a floor that covers the planner's direct costs · a threshold based on something the planner controls, not on gross, since gross depends on a board's asks · a cap, so the client is not exposed to an unbounded success fee · and enough working capital to survive the downside, which is the real constraint and is a Chapter 36 question rather than a Chapter 32 one.

And the honest note: an incentive tied to gross gives the planner a reason to push for a bigger, more expensive event, which is the exact conflict §32.9 warns about. Tie it to net, or to the ratio, or do not tie it at all.

M.1 The objective discipline applies in full: write down what has to be true afterwards, and name who will be asked. Fairhaven's took two more meetings and came out as move major-gift prospects one step closer; net at least $900,000; report both, and report the first in April of the following year.

Two things are different. The gala has two objectives that operate on different clocks — money on the night, and pipeline over eighteen months — and the second is the real one while the first is the one the board discusses. And the accountable person is a board, not an individual, which means the objective must survive a room rather than one sponsor: a committee can dilute an objective in a way a single sponsor cannot.

M.3 The alcohol tension: an open bar makes a room generous and warm and it also makes the ask at 9:40 land in a room that has been drinking for four hours — and generosity from a room like that produces regret and a donor-relations problem in the morning.

The resolution is timing, not prohibition. Move the ask to 7:50 — before the main course and before the bar has done its work — and the tension disappears without anybody being asked to close a bar at a party.

Unchanged from Chapter 15: the consumption model · the 15–25% who are not drinking, which at a gala includes people in recovery who are in the room precisely because the organisation helped them, and for whom the non-alcoholic option is not a courtesy · staffing ratios · and the fact that the bar is a queue, which is a Chapter 29 friction point.

M.5 The praise problem transfers and gets worse, because at a gala everybody has a reason not to report.

Who cannot report what: the board cannot say the evening was too long, because they approved it. The staff cannot say the board did not sell tables, because they work for the board. The donors cannot say the film was too long, because the film was about the mission. And the volunteers cannot say the auction was not worth it, because they made it.

What replaces the question: the numbers, which cannot be polite — cost per dollar raised, revenue by stream against target, paddle counts by rung, the time of the ask, attendance by segment — plus specific factual questions to people at the edges: what time did you leave, and why? Which table were you at, and did anybody ask you for anything? And the twelve-month row, which is the only instrument that answers the actual objective: how many of the prospects in the room moved.

M.7 Three times, and it is the same principle each time. The paddle raise: spotters with assigned sightlines and a recorder — one person, one section, one job, because a paddle nobody saw is a gift that did not happen. The committee: individual asks with individual names and individual numbers — eleven trustees asked individually, seven delivered, where the same eleven asked collectively delivered nothing. And the young person's event in §32.10: five named adults with named zones, rather than "the parents will keep an eye."

In all three the failure mode is identical: a task addressed to a group is addressed to nobody.

M.9 The specific overrun risk in a social celebration is the guest list, and it comes from a different place than at a wedding. A wedding's list is bounded by two families' judgment; a bar mitzvah's or a quinceañera's is bounded by a school year — and "we can't invite twenty-two of the class and leave out four" is both true and unanswerable, and it arrives after the venue is booked.

When the conversation should happen: at the venue conversation, not after it — the same rule as Chapter 5. The question is not "how many are you thinking?" but "is there a group where you'd have to invite all of them or none of them, and how big is it?" Ask it once, in month one, and the entire overrun disappears — because the number the family gives in month one is a hope and the number that group produces is arithmetic.

E.1 Rubric. The §32.9 report has gross, cost, cost per dollar raised, revenue by stream against target, volunteer hours, attendance by segment, and the twelve-month row: which major-gift prospects were in the room and where they are now.

What you will not find, and should report as findings rather than gaps: volunteer hours are almost never recorded · attendance by segment usually does not exist because nobody categorised the guest list · and the twelve-month row exists nowhere, because it requires somebody in April to look back at a list from the previous October. That is the chapter's central claim confirmed by absence: the number that would justify the whole event is the one nobody keeps.

E.3 Rubric. The strongest objection must be stated at full strength, not softened: a paddle raise is a public, escalating, socially-observed solicitation, conducted by a professional, in a room where declining is visible. It uses peer pressure deliberately, it is designed by descending anchor to make each level feel modest against the last, and the people most susceptible are not the wealthiest — they are the ones who feel least secure about belonging in the room. Calling that "energy" does not make it not manipulation.

Serious engagement means conceding most of that and then locating the actual line. Available distinctions worth defending: the mechanism is transparent — everyone in the room knows exactly what is happening, which is not true of most persuasion · the ask is for a real thing with a stated unit · nobody is deceived about where the money goes · and giving is voluntary and revocable in practice. Available distinctions that do not survive scrutiny: "it's for a good cause" (a justification, not a defence) and "people enjoy it" (some do; the relevant people are the ones who do not).

A defensible position, stated to a donor who asked: "Yes, it's designed to make giving easier by making it social, and that is a form of pressure. I'd defend the parts that are honest — you know what it's for, you know what it costs, you can put your hand down — and I wouldn't defend running the ladder down to $100 in a room where somebody's boss is watching." The unusable answer is that it is not manipulative.

E.5 Rubric. Ask what makes it hard and then stop talking. Expect three things the chapter does not address: that selling a table means asking friends to spend $7,500 on dinner and the board member knows what the dinner is worth · the reciprocity ledger — everybody they ask will ask them, for their cause, next year, and the board member is managing a personal balance sheet the organisation never sees · and that they were recruited to the board for their expertise and discovered afterwards that the job was selling tables, which nobody told them.

Report verbatim, and note which are fixable by the organisation. The third one is entirely fixable and is fixed at recruitment, in one honest sentence.

Chapter 33 — Destination Events

A.1 🚪 Distance does not add new problems — it removes your ability to solve them by turning up.

A.4 A local partner is a planner or coordinator in the destination who executes on the ground: vendor management day to day, local logistics, permits, transport, and the physical event.

What they are not: your client's planner. They never manage the couple, they do not own the design or the guest communication, and — critically — they should not be the contractual counterparty with the vendors.

They occupy Chapter 28's category D: not replaceable, and the event does not work without them. Which is the argument for vetting one person as carefully as you would vet eight, and for asking the Ximena question — "who covers you if you're ill?" — in month one, when it is a routine question, rather than in month eleven, when it is not.

A.6 Because a partner who goes silent takes every relationship with them.

When Ximena went silent — genuinely ill, a small firm with no cover, and the person who would normally have told you was her — the planner had eleven vendors' names, numbers, and countersigned agreements, because a decision made in month two put the couple, not Ximena, on every contract. So the planner rang the caterer directly and asked who else in Playa could coordinate. The caterer named two people. One took it.

The version where the contracts sat with the partner is a wedding that does not happen, and the difference is one clause and a decision nobody wanted to make in month two because it felt like distrust.

A.9 Batch, do not drip — one structured message a day beats eleven questions. Number every question. State the deadline in their time zone, never "end of day." One scheduled call a week, same slot, in the diary for the year, surviving the weeks with nothing to discuss. Written follow-up within an hour, from you, inviting correction. A shared living document with a change log, not a thread.

The habit that doubles your effective iteration rate: numbering every question, because it makes "1 yes, 2 no, 3 I'll check Tuesday" a complete answer. Unnumbered questions get partial answers and each round trip costs a day.

A.11 Marry legally at home; hold the ceremony at the destination as a symbolic one.

Couples resist because it feels like the real wedding is being demoted to paperwork. The reframe that persuades them is that it is the opposite: the paperwork is got out of the way so that the ceremony can be about what it is about — nobody in the meadow needs to be checking that a document is valid, and the ceremony is freed from the requirements of a jurisdiction. Most couples relax immediately once it is put that way, and many describe the courthouse morning afterwards as one of their favourite parts of the whole thing.

A.14 FX spread on transfers · wire fees, both sending and receiving · FX movement between contract and final payment · and card fees where cards are used, including cross-border loading.

The third is an exposure rather than a cost — it is not a fee, it is the rate at final payment not being the rate at contract, and it can move in your favour. The others are certain and payable. The distinction matters because you manage an exposure differently from a cost: you reduce a cost by shopping, and you manage an exposure by choosing a contracting currency deliberately, or by fixing the rate with a forward contract where the amount justifies it.

A.16 🚪 Your guests are on holiday, and it is a holiday they paid for. Unprogrammed time is not a gap in the schedule — it is the thing they bought.

Four schedule rules: one completely empty day, minimum, said out loud in the invitation · offer optional activities, do not organise them · keep the rehearsal dinner to the rehearsal party rather than expanding it to everybody · and hold a recovery brunch, which is cheap, informal, and the thing guests actually talk about afterwards.

A.19 Visit one is for judgment: the partner, the vendors, the site, the light at the right hour, the distances, and the things a video cannot carry — noise, smell, gradient, how long the walk actually takes. Visit two, a week out, is for agreement and detail.

What you should do on visit one that nobody does: settle the day itself, in person, with the partner — who runs vendors, who runs people, who wins when those collide, and where each of you is if you cannot find the other. Written down afterwards and sent to them, ending in "does that match how you'd do it?" A handoff proposed and not agreed is not a handoff, and the commonest destination failure is two planners in one room at 4:15 each deferring to the other.

B.1 A distance audit — six removals and their substitutes.

B.3 The seven vetting questions and what a bad answer sounds like.

B.5 The day-of handoff script, for a partner whose style you do not know.

"Before we get into the timings, I want to settle how you and I work on the day itself — because I've seen this go wrong and it goes wrong quietly rather than loudly.

What I'd propose: you run the vendors.* Everything with a truck, a crew, or an invoice is yours. I won't speak to any of them directly on the day unless you ask me to* — if I need something from the caterer, I ask you.

I run the family and the schedule. The couple, their parents, the wedding party, the guests, and what time things happen.

When those collide — and they will — you win on anything physical and I win on anything about a person. If the tent has to move, that's yours. If the bride's grandmother has to be somewhere, that's mine.

And if we can't find each other: you're back of house, I'm front of house. That's where we look first.

Now — does that match how you'd do it?"

The last question is the entire script. A partner who works differently will tell you if asked and will not if told, and the version of this conversation that ends in a full stop produces two planners in a room at 4:15 each waiting for the other.

B.7 What you say about a legal beach ceremony abroad.

"I want to give you the recommendation I give everybody, and then the reasoning, because most couples argue with it for about two minutes and then feel relieved.

Do the legal part at home, before you go, in a registry office with two witnesses — and have the ceremony on the beach as a symbolic one, exactly as you've imagined it.

Here's why.* Marrying legally abroad usually means a residency period, documents translated and apostilled, an official who must be present and whose availability is not yours to control, sometimes blood tests, and a civil ceremony that has to happen in a specific building at a specific time with specific words in it. None of that is impossible. All of it has to be right, and if one document is wrong you find out three days before.***

And the part that actually matters: it puts a legal procedure inside the thing you're doing.* Somebody in that ceremony will be checking that a form was completed. If the legal part is already done, your ceremony on that beach can be about exactly what you want it to be about, and nothing else* — you can write every word of it, anybody can officiate it, and it can be twenty minutes or five.

People worry it demotes the real wedding to paperwork. It's the opposite. The paperwork gets out of the way."

If they still want it: you do it, properly, and you say so without sulking. Then: verify the requirements yourself from the civil registry and the consulate — not from a wedding blog, and not only from the partner · establish the residency period and build the travel around it · collect and apostille every document three months early, because that is where it fails · confirm the official in writing with a named person and a fallback · and tell the couple, once, in writing, what happens if a document is rejected — so that the decision is theirs and is made with the facts. It is their wedding and their jurisdiction to navigate; your job is that they choose it knowing.

B.9 Cross-border money costs — $95,000 over 16 months, 60% in local currency ($57,000).

The FX movement is an exposure, not a cost. It is not a fee anybody charges; it is the rate at final payment not being the rate at contract, and over sixteen months it is the largest single number in the table and it can move either way.

Three moves: contract in one currency, deliberately chosen — and if the couple's income is in dollars, that is an argument for contracting in dollars and letting the vendor price the risk, which they will do more cheaply than the couple can carry it · use a specialist transfer service rather than a retail bank, worth 1.5–3% on $57,000 · **and put the whole table in the budget as a line called *cross-border costs* at $3,000**, because the alternative is that it appears as eleven small mysteries over sixteen months.

B.11 A five-day schedule for 80 guests.

DAY 1  Arrivals across the day. Airport transfers ARRANGED — the one
       logistical thing worth organising centrally.
       Evening: welcome drinks, 2 hours, drop-in, no seating plan.

DAY 2  ★ COMPLETELY EMPTY. Nothing is organised. Nothing is expected.
       A one-page list of what there is to do, with prices, in the room.

DAY 3  Morning free. Rehearsal at 5, for the wedding party only.
       Rehearsal dinner: the rehearsal party. NOT everybody.
       (An optional bar meet-up for everyone else at 9, unhosted.)

DAY 4  THE WEDDING. Nothing else on this day at all.

DAY 5  Recovery brunch, 10:00–13:00, drop-in, cheap, informal.
       Departures from noon.

The empty day, defended in one sentence: "Your guests have paid two and a half thousand dollars each and taken a week of their annual leave to be here, and the day they will thank you for is the one where you asked nothing of them."

Offer versus organise. Offer: a list of what there is to do, with real prices and honest travel times, and one line about which is worth it. Organise: the airport transfers, and nothing else. The distinction matters because an organised activity is an obligation with a smile on it — a guest who has been booked onto a catamaran cannot decline without explaining themselves, and a guest who has been told about a catamaran can simply not go.

And one line in the invitation that most couples never think to include: permission to come for two days instead of five. Many will, and they will be grateful, and they will come.

B.13 The hurricane-season conversation, before booking.

First, look it up. NOAA's historical hurricane tracks database is free and searchable by location and date, and it gives you the actual record for that place in that week rather than a season-long generality. Do not use a resort's answer to this question.

"Before you fall in love with the second week of September, I want to give you the real numbers, because it's the cheapest week of the year there and it's cheap for a reason.

I've looked at the historical record for that stretch of coast in that specific week. [Suppose it comes back as: in the last fifty years, tropical-storm-force winds or worse have affected that area in that week roughly one year in six.*] So: about a one-in-six chance of weather that matters, and it's important you understand what "matters" means here — it isn't rain on your wedding.***

A hurricane doesn't rain on your wedding. It closes an airport for three days.* The realistic bad outcome is that forty of your guests can't get there, or can't get home, or your flowers are on a plane that didn't land. The wedding itself is often fine.***

If you want that week — and it will save you something like thirty per cent — here's what we do about it, and all three have to happen at booking rather than later.* One: insurance, bought now, because named-storm exclusions attach the moment a storm is named and a policy bought in August is worth nothing. Two: a date-change clause negotiated into the venue and vendor contracts now, while they want your booking — asking for one during a crisis is asking for a favour. Three: we tell your guests the truth in the invitation*, including the recommendation that they buy their own travel insurance.

With those three, September is a defensible choice and I'll happily plan it. Without them it isn't, and I'd say so."

B.15 An incentive trip: 90 employees, five days, a resort.

The schedule rule you enforce: content occupies mornings only, and no more than three of them. Everything else is the reward, and the reward is the objective.

And you enforce it against the client, because they will push against it — an organisation spending several hundred thousand dollars feels the pull to fill the days, and the commonest failure in incentive travel is a schedule that uses the destination as a backdrop for content. A five-day meeting in a hot place is not a reward, and the people it is meant to retain will read it accurately.

Three duty-of-care items you raise with the client — and you raise them, because they are the client's obligations and not yours to solve:

1. Medical and emergency cover. What happens when somebody is seriously ill or injured: which hospital, what the insurance covers, who authorises treatment, who calls the family, and repatriation cover. A 24-hour contact who is a named person, not a policy number. 2. Attendance is effectively compulsory, and that changes everything. Nobody chose to be there — which means accessibility, dietary, religious observance, and alcohol expectations are not preferences but obligations, and it means the "optional" evening activity is not optional when the CEO is at it. Ask explicitly what happens to somebody who cannot travel — pregnancy, a medical condition, caring responsibilities, a passport problem — and make sure the answer is not "they miss out on the reward." 3. The tax question. An incentive trip is a taxable benefit in many jurisdictions, sometimes including the partner's travel. Not your problem to solve and very much your problem to raise — in writing, early, to somebody in finance. A planner who does not raise it is the reason ninety people get an unexpected tax bill in April.

C.1 Rubric. Report the requirements as the civil registry and the consulate state them, with the date you checked and the source. Report how long it took — expect two to six hours across several attempts, in a second language, with at least one authoritative-looking source contradicting another.

And report what you could not establish, which is the real finding. The commonest irreducible unknowns: how long an apostille actually takes in practice as opposed to officially · whether a particular official will be available · and whether a requirement stated on a page from 2019 is current. This exercise exists to demonstrate why the chapter gives no country's requirements: they change, they vary within countries, and a book that stated them would be confidently wrong for years.

C.3 Rubric. Report the ratio. Expect most not to name their local partners, and be careful about the inference: the honest reading is commercial rather than sinister — a named partner can be contacted directly by the next couple. But it also means the partner is invisible to the client, cannot be checked, and gets no credit, and a planner who never names anyone should be asked why in an interview. The best version of this report gives both readings and says which the evidence supports.

C.5 Rubric. Verbatim, because the paraphrase loses it. Expect: assuming things work at the same speed · assuming a written contract means the same thing here · not visiting · treating a supplier's yes as agreement · arriving two days before the wedding · asking for something at 48 hours' notice that needed three weeks · and — the one that stings — treating the local planner as a supplier rather than a colleague. If you get the last one, it is worth more than the rest of the exercise.

D.2 Rubric. It is not defeatism — it is the only honest position — and a strong answer proves it with arithmetic rather than asserting it. Cross-border enforcement over a $6,000 deposit means a foreign lawyer, a foreign court, a foreign language, and a judgment that then has to be enforced against assets in a jurisdiction you are not in. The cost exceeds the claim before anybody files anything, and both sides know this.

What would change it: a large enough amount (at $200,000 the arithmetic reverses) · an arbitration clause with a named seat and institution, which is cheaper and faster than litigation and is enforceable across borders under the New York Convention · a counterparty with assets or a reputation in your jurisdiction · or a payment structure where you hold the money, which is not a legal remedy but is the practical one.

And the point the chapter makes and should be restated: assuming you will not litigate does not weaken the contract, it changes its job. It becomes a specification and a schedule — what, when, to what standard, photographed at milestones — which is more useful in the 99% of cases that never go near a court.

D.4 Rubric. The other side is strong: Chapter 27's fourth clause exempts people from the "don't tell them" rule, and this is not a problem, it is a risk to eighty people's travel. A guest who books a flight on Tuesday without knowing about a depression that closes the airport on Friday has been deprived of a decision that was theirs.

Where the line actually is, and it is a good line: the distinction is not problem-versus-person, it is whether there is a decision the other party can still make. A 40% depression 900 miles out changes nothing anybody can act on — the couple cannot move the wedding, the guests have booked, and the information produces four days of anxiety and no decision. But if guests have not yet booked flights, there is a decision, and it is theirs, and withholding it is indefensible.

So the rule that survives: tell them when there is an action available to them, and at the point it becomes available. Which also means telling them earlier than the storm — at booking, which is what B.13's conversation is for. A planner who has had the September conversation properly in month one has almost nothing to decide in month fourteen.

D.6 Rubric. The objection is correct on its face: one partner is a single point of failure and the chapter concentrates risk while calling it simplification. Ximena is the proof — the whole wedding hung on one person's health.

What survives, and it is a real argument rather than a relabelling: the alternative is not eight independent points of failure, it is eight relationships you cannot maintain from 3,000 miles away. A planner managing eight foreign vendors directly has eight relationships, all thin, none of them able to solve a problem by walking down the road — and the Chapter 28 category-D count goes up rather than down, because in practice several of those eight become unsubstitutable.

And the mitigation is where the real answer sits: concentration is acceptable when the failure mode is covered. Ask the cover question in month one · put the contracts with the couple · hold 20–30% back until after · and know two other names in that town before you need them. Concentration plus cover beats dispersion without it, and a strong answer says the chapter is right about the structure and under-emphasises how much work the mitigations are doing.

D.8 Rubric. The case is genuinely uncomfortable and should be stated properly: at −16 days, with your client's wedding at risk, you have a phone and the resort has a manager. Not ringing them is a procedural nicety dressed up as respect for the partner's territory. You work for the couple, not for the handoff agreement.

What answers it — and only partly. The reason not to ring is not etiquette, it is efficacy: a resort that has a relationship with a local coordinator it will work with for twenty years answers her differently than it answers a foreign planner it will deal with once. Going round the partner spends the asset you bought. And it damages the one relationship on which the next sixteen days depend, at the point where you need it most.

Where the line is: you do not ring instead of the partner; you may ring with them. "Can we do this call together?" And if the partner will not act at all — not slowly, but not at all — then the handoff has failed, that is a different situation, and you ring. A strong answer identifies the trigger in advance, because the version decided at −16 days under pressure is the one that goes wrong.

M.1 Vetting becomes the selection of one person rather than the checking of eight, and the questions change from are you competent? to have you done this specific job — with a foreign planner — before?

The asset you are actually buying is their vendor relationships. "Which of your vendors have you worked with more than five times?" The answer to that question is what you cannot obtain any other way, and it is the entire reason for the engagement: a caterer who has worked with your partner twenty times will take her call at 6 a.m. and will not take yours.

M.3 It generalises from culture-as-tradition to culture-as-professional-practice. Chapter 21 said you are not the authority on anybody's religious or family tradition; Chapter 33 extends it to commercial and legal culture — how business is done, what a yes means, what a contract is for, what timescales mean, what is polite to ask.

And the specific, load-bearing instance: in some professional cultures a direct no to a client is close to unsayable. Which means a planner can read three months of agreement and discover that nothing was agreed — not because anybody lied, but because "is that possible?" has only one answerable form. Hence the reframe: not "is that possible?" but "what would have to happen for that to work?" — a question whose answer cannot be yes.

M.5 The guest who cannot afford to come says the dates do not work. Never "I cannot afford this."

Which means a destination guest list is filtered by wealth while appearing to be filtered by availability — and a couple reading their declines will conclude something false and permanent about who cares about them.

What a planner can do is limited and real: make sure a genuinely cheap accommodation option exists rather than a cheapest-of-the-expensive one · state the total cost early and precisely, so the decision is made once instead of agonised over for four months · give explicit permission to come for two days · and raise with the couple — once, privately — that they may wish to quietly cover a specific person's flight. That last is not the planner's decision and it is the planner's job to raise it, because the couple will usually not have thought of it and will often want to.

M.7 It becomes a bilingual document with an owner column and a language column, and three things change.

Every document has a stated governing language, so that a discrepancy between two versions has a resolution rather than an argument. Recipients are listed by name and role in the language they work in — a run sheet that reaches a crew chief who cannot read it has not been distributed. And the matrix itself gains a row that does not exist domestically: who translates, and by when, because translation is a task with a duration and it is always discovered at −4 days.

And one practical rule worth more than the matrix: numbers, times, and quantities are written identically in both versions. Names and times survive translation; instructions do not.

M.10 The cascade acquires a failure mode with no domestic equivalent: an input that cannot be replaced locally and cannot arrive faster than a plane.

Domestically, a late or missing item has a substitute within driving distance — Chapter 25's float absorbs it and the cascade continues. Across a border, an item held at customs is not late, it is absent, and no amount of float fixes it: there is no second delivery, no local equivalent, and no way to turn up and collect it.

Which produces the rule: nothing on the critical path travels with you or after you. Anything essential either exists in the destination or arrives with three days of margin and a customs broker — and the planner's version of this rule is that the dress, the rings, and the documents travel in hand luggage, on the couple's own bodies, and are never checked.

E.1 Rubric. The one-pager compares, for each destination: residency period · documents required, with apostille and translation requirements · who may officiate · civil versus religious recognition · timescale from application to ceremony · cost · and whether the resulting marriage is recognised in the couple's home jurisdiction, which is the row people forget and the only one that ultimately matters.

Report which was hardest and why. The usual answer is not the most bureaucratic country but the one whose requirements vary by municipality, where the national page is correct and useless. And note where you had to rely on a single source — that is the row you would verify twice before advising a client.

E.3 Rubric. The essay must take a position and be specific, and both defensible positions exist.

The case against: a destination wedding transfers cost from the couple to the guests — $1,700–3,900 and a week of leave each — while appearing to cost less; it filters the guest list by wealth and reports the result as scheduling; and its environmental cost is dominated by flights, where a single long-haul return is 1,800–3,500 kg CO₂e per person and eighty of them dwarf every other choice on the event combined (Ch.35).

The case for: the guests chose, knowing; the same guests fly for holidays without a wedding attached; a smaller guest list is a real reduction; and a four-day event with people you love is, per guest-hour, arguably better value than a six-hour wedding at home.

What makes it a strong essay is the specificity of what you would still do. For example: I will plan them, and I will not pretend they are cheaper or greener. I will state the total guest cost in writing before the date is set. I will insist on a genuinely cheap accommodation option and explicit permission to come for two days. I will raise the flight arithmetic once, honestly, with the emissions number attached — and then I will do the job well, because it is their decision and my disclosure is not a veto. A position that refuses all destination weddings is coherent; a position that plans them while never saying any of this is not.

E.5 Rubric. A usable register has six rows and three columns, and the exercise's real content is the last line.

The mitigations that cost nothing: the cover question · contracting the vendors to the couple · numbering your questions · agreeing the day-of handoff in person · knowing where the hospital is · and asking what the partner's three unbookable days are. Six of the most valuable items in the register are conversations, which is the chapter's argument compressed: distance is not expensive to manage, it is expensive to manage late.

Chapter 34 — Large-Scale and Multi-Day Production

A.1 🚪 An event becomes a supply chain the moment two crews need the same space at different times and neither can be moved.

What changes about what you are scheduling: you stop sequencing tasks against a clock and start allocating a scarce physical resource — the dock, the room, the lift, the hour — among parties who each need all of it. A timeline answers when does this happen? A production schedule answers who has the loading bay between 10 and noon, and where does everybody else wait?

A.3

The last row is the important one. Below the line almost everything can be bought or absorbed; above it, physics does not negotiate — and you find out on site, with eleven trucks in a lane, at an hour when nothing can be changed.

A.6 A dependency map is a directed graph of what must be finished before what — floor before staging, staging before AV, power before anything — drawn before the calendar, in about forty minutes.

Three things it tells you that a list cannot. The critical path — the longest chain of dependencies, which is the true duration of the build and is never the sum of the items. The choke point — the resource that appears in the most chains, usually the dock or the lift, which is where delay propagates. And what is not on the path, which is the single most useful output: when a build runs late, the only things you can move are the things nothing is waiting for, and without the map you will move the wrong ones.

A.8 Minimum call: the shortest period a crew member can be booked and paid for, typically ~4 hours. Turnaround: the minimum rest between the end of one call and the start of the next, typically 8–10 hours. The meal rule: a break within roughly five hours of the call, with a penalty per half-hour per person after it.

What minimum call implies about sequencing: batching beats shortening. A ninety-minute job costs four hours, so three ninety-minute jobs scattered across a day cost twelve hours of crew and the same three jobs run consecutively cost four and a half. Which means the schedule is built around getting all of a discipline's work into one call, and a schedule optimised to finish each element as early as possible is usually the most expensive schedule available.

A.11 Water, free and everywhere, always · shade or shelter · a crew room with somewhere to sit that is not a flight case · toilets the crew may actually use · real food at the meal break · and the two that get skipped: somewhere to change and lock a bag, and a named person whose job includes crew welfare.

The argument that is not moral: a tired, dehydrated, unfed crew makes mistakes on a rigging deck. Every one of those mistakes is a safety incident with your name near it — and the second-order version is cheaper still: a crew that is looked after tells you things. The house electrician who volunteered, in a corridor, that the kitchen and the ballroom share a distribution board did not have to say anything.

A.13 "How does it get out?"

A planner asks whether the vehicle will fit and whether it can get in. A production manager asks how it leaves — because a yard that can be entered and not exited is a yard containing one truck and ten waiting ones, and every subsequent delivery is now a queue on a public road. It is always worse than it looks, and it is one of the seven threshold diagnostics for exactly that reason.

A.16 Up to 4 hours, no alcohol: 1 unit per 100–120. 4–6 hours with alcohol: 1 per 75. Over 6 hours or multi-day: 1 per 50–60, plus servicing.

Chapter 29's rule that applies: distance is provision. At least one accessible unit and at least 5% of the total — and a compliant accessible unit 90 metres away across grass is not provision, it is a unit on a plan. The same logic that makes a 26-inch gap a wall makes a distant toilet an absence.

A.18 1. The two circulation systems do not cross — not rarely, do not. 2. The service road is one-way, because a two-way service road on a constrained site is a road that will block. 3. The emergency lane is 4 metres, unobstructed, and it is nobody's overflow parking — it gets marked, it gets briefed, and somebody's job includes walking it.

A.20 Venue house crew · union labour · riggers · licensed contractors (electrical, structural, LPG) · security and stewards.

The operating principle: you do not direct them, you sequence them. You provide the schedule, the space, and the information; their supervisor directs the work.

And what "no" means: it means the system is functioning. A rigger, an electrician, or a steward saying no is not an obstacle to be escalated — it is a licensed professional with legal responsibility discharging it. The correct response is "what would make it possible?", and the incorrect one — which planners from the wedding side reach for instinctively — is to find somebody more senior.

B.1 Rubric. Run all seven honestly and report the count: load-in over one working day · more than three suppliers at the same access point · crew larger than the guest-facing team · any element requiring another to finish first · a vehicle that cannot leave once it has arrived · overnight occupation · hiring labour rather than booking suppliers.

Two is the threshold. Most readers doing this on a 200–250-guest marquee wedding find four, and the honest report says which method they actually used. The commonest single trigger is the third supplier at one access point, and the commonest surprise is the last one — a planner who hires two casual staff has entered a different legal and welfare relationship and usually has not noticed.

B.3 Two-day production schedule, 300-person gala, ballroom handed over 20:00 the night before.

      DAY 0                          SPACE
20:00 Ballroom handover. WALK IT     Ballroom
      with the venue, photographed    (Ch.13's 20 photographs)
20:30 Floor: dance floor, cable       Ballroom
      ramps, tape                     Truck 1 at dock
23:00 ── DARK ──────────────────────────────────────
      ★ Nothing overnight. Turnaround 8-10 hrs and
        a security cost we are not paying

      DAY 1                          SPACE
07:00 Crew call, 4-hr minimum.       Dock (exclusive)
      INDUCTION, 5 min, everybody     — Truck 2 (staging)
07:15 Staging and risers              Ballroom north
10:00 Truck 3 (AV) — dock free        Dock
10:15 AV rig: audio, lighting,        Ballroom (AV has
      screen. FLOOR AND STAGING          the room)
      MUST BE DONE — they are
      upstream on the map
12:00 MEAL. Fixed point. 30 min.      Crew room ★ a room
      Work moves around it               that is not the
                                         green room
12:30 AV continues; rentals arrive    Ballroom / dock
      to the CORRIDOR, not the room
15:00 Tables and chairs set           Ballroom (AV out)
17:00 Linen, glass, centrepieces      Ballroom
18:30 Focus and levels — LIGHTS       Ballroom, dark
      DOWN, room cleared of setters
19:30 Rehearsal: auctioneer, AV,      Ballroom
      the paddle-raise cues
21:00 Crew released. ROOM LOCKED      —
      ── DARK ──────────────────────────────────────

      DAY 2 — EVENT
07:00 Second crew call (turnaround    Ballroom
      satisfied from 21:00)
      Snag list, replace, re-focus
11:00 Room complete — 45 min before
      anybody arrives (Ch.13)
...
23:30 STRIKE. 40-60% of build, not    Ballroom + dock
      25%. Non-critical strike began
      at 22:30 with the bar still open

The dark period is marked because it is a decision, not a gap. Turnaround is 8–10 hours and it is a rule rather than a preference, and an overnight build carries a security cost, an insurance question, and a second load-in day. The space column is the document's whole reason for existing — and note the row that catches the chapter's own error: the crew meal needs a room, and the room it is usually given is somebody else's green room.

B.5 18 crew, call 08:00, meal rule five hours, penalty $18 per half-hour per person, rig finishes 14:15 if the meal is skipped.

The meal is due at 13:00. Working through to 14:15 is 1 hour 15 minutes past the rule — three half-hour increments on the usual "or part thereof" basis.

18 × 3 × $18 = $972. (At a strict 2.5 increments it is $810; get the wording in writing, because the schedule is what triggers the cost.)

What you actually do: break at 12:30, take the full thirty minutes, and finish at 14:45.

You are trading thirty minutes of schedule against $972 and a crew that has been worked through its meal on day one of a three-day build. The thirty minutes is almost always available and the goodwill is not purchasable at any price — and the chapter's rule is the one to say out loud in the meeting: the meal is an obligation and the rig is a preference.

And the real finding is upstream: a rig that lands at 14:15 was scheduled with no margin against a 13:00 fixed point. The penalty is a symptom. Crew rules are triggered by the schedule, which means they belong in the schedule at the point it is drawn, not discovered at 12:45.

B.7 Power for 600 people outdoors.

Specify a 250 kVA set — the next standard size above the requirement, which is headroom rather than waste, since the load you were told about is never the whole load. Plus a second set with automatic transfer, because a backup that requires somebody to start it is eleven minutes of darkness (Ch.18).

What goes on a separate leg: the AV. 62 kW × 1.25 = 77.5 kW ≈ 97 kVA — its own 100 kVA set.

Why: catering and site loads are thermostatic and motor-driven — hot boxes cycling, fridges starting, a coffee urn drawing hard for two minutes. Every one of those is a voltage dip, and a voltage dip on a shared leg shows up as flicker on an LED wall and as audible noise in an audio chain, in front of six hundred people, at the moment somebody is speaking. It is also the failure that is hardest to diagnose on the night and easiest to prevent at the specification.

And the thing to ask that is not on any drawing: what else shares the distribution board. The Cascadia's kitchen and ballroom shared one, an LED wall flickered during dinner service, the hotel had known for two years, and it appeared on no document — it was volunteered by the house electrician in a corridor.

B.9 Rubric — the drawing must show all six things, and one road access is the hard case.

        ROAD IN ──▶ ═══════════ SERVICE (ONE-WAY) ═══════▶ OUT
                        │            │           │
                     [DOCK]       [WASTE]     [CREW BREAK]
        ┌───────────────┴────────────┴───────────┴──────┐
        │                  BACK OF HOUSE                │
        ├───────────────────────────────────────────────┤
        │                   MAIN SPACE                  │
        └──────────────────────┬────────────────────────┘
             ·········· GUEST ROUTE (dotted) ··········
        GUEST DROP-OFF ●                    ● PARKING
        ═══ EMERGENCY LANE, 4 m, UNOBSTRUCTED ═══ (separate,
             marked, briefed, walked by a named person)

With one road access the two systems must be separated by time as well as by space — service traffic before a stated hour and after a stated hour, guest traffic between — and that hour is a hard cue on the run sheet with a named person on the gate, not a hope. The commonest failure is a supplier arriving at 17:40 into a guest arrival, and it is prevented at the marshalling schedule, not at the gate.

Two things that belong on the drawing and usually are not: where waste accumulates — a real footprint that grows through the event — and where crew break, because a crew with nowhere to sit will sit somewhere a guest can see.

B.11 Production meeting agenda, −6 weeks, three-day event.

1  SITE AND ACCESS CHANGES since last week          5 min
2  THE DEPENDENCY MAP — what has moved              10 min
     and what that does to the critical path
3  SCHEDULE WALK, BY HOUR, WITH THE SPACE           25 min
     COLUMN ON THE SCREEN  ★ the meeting
4  VEHICLES: marshalling, dock, and how each        10 min
     one gets OUT
5  CREW: calls, meals, turnaround, welfare          5 min
6  SAFETY: documents outstanding, by supplier,       5 min
     with a name and a date
7  OPEN ITEMS: owner and due date, out loud          5 min

The opening:

"Before we start — the purpose of this meeting is to find the collisions while they're still cheap. If you have a problem with the schedule, this is the room and this is the hour. Nothing that is said here counts against anybody, and something that turns up on site because it wasn't said here counts against all of us.

We are going to walk the schedule by hour, with the space column up, and I'm going to ask each of you to say out loud where you are and what you need. Please interrupt me."

And when two suppliers claim the same hour:

"Right — Halvorsen needs the dock at ten and Rimasauskas needs it at ten. Let's not settle this by who asked first or who's biggest.**

On the dependency map, staging is upstream of AV — AV can't rig into a room without a deck. So the dock goes to staging at ten, and AV at twelve-fifteen.* Denis, that pushes your rig by two and a quarter hours: does that break your call, and do you need more crew or a later finish?* Tell me now and it's a schedule change; tell me on Tuesday and it's a problem."

Three things about that. The conflict is resolved by the physics, not by seniority — which is why it does not become personal. The cost is surfaced immediately and named as somebody's specific problem. And the alternative is stated out loud: now it is a schedule change, later it is a failure — which is the sentence that makes people speak up in the room rather than in the car park.

B.13 A rigger refuses to hang 400 kg from a point you were told was rated. The first ten minutes.

0–1 min. "Understood. We're not hanging it." Said immediately, plainly, in front of whoever is standing there. Nothing else in the first minute. The rigger has just done their job and the first thing they hear must not be a question about whether they are sure.

1–3 min. "Tell me what you're seeing." Listen, and write it down. A rigger's objection is usually specific — the point is not what the drawing says, the structure is not what the survey assumed, the load is dynamic rather than static, or there is no documentation for the point at all.

3–5 min. "What would make it possible?" — the chapter's question and the only useful one. A ground-support tower. A different point. A structural engineer's sign-off. A lighter element. Sometimes the answer is nothing, and that is an answer.

5–8 min. Establish the schedule consequence and who else it touches — what is downstream on the dependency map, whose call it affects, and whether the room is now free for somebody else's work. Reassign the crew rather than letting eleven people stand still.

8–10 min. Tell the client's decision-maker, in §28.7's order: it's handled, here is the fact in one sentence, here is what we are doing, here is what I need from you — usually a decision between a ground-support tower at a cost and a design change at no cost.

What you do not do, in any of the ten minutes: ask them to reconsider · look for a more senior person at their company · suggest that it hung fine last year · or ask whether they could do it "as a favour." A rigger who says no is a licensed trade with legal responsibility for what hangs over people's heads, and the escalation you are contemplating is asking a professional to accept personal liability for your schedule.

B.15 What Chapter 26's production book needs to become a production schedule.

Unchanged and carried over intact: the contact block · the emergency page · the run sheet for the event itself · the distribution matrix · the floor plans · and every cue relating to a person.

Added:

The one-sentence version: the production book says what happens and to whom; the production schedule adds where, with what crew, in what order, and who is waiting.

C.1 Rubric. Report all four figures, and report which of them the venue had to go and check — that is the exercise. The usual result: dock height and width are known, turning circle is a guess, and whether a 53-ft trailer can leave is not known by the person you are speaking to and often not by anybody at the venue.

Which is the finding. The last question is the one that matters most and is the one nobody has an answer to — and a planner who has asked it once has more information about that venue than the venue's own sales sheet contains.

C.3 Rubric. Time it door to door: arrival, positioning, first item off, last item off, vehicle away. Compare to 45–90 minutes at a dock and 2–4 hours on a tail-lift. Report the variables that actually drove it — usually not the crew size but whether the route from the tailgate to the room had a step, a turn, or a lift, which is the thing no ratio captures and every experienced crew asks about first.

C.5 Rubric. Verbatim. Expect: no space column · a schedule built from what suppliers asked for · not knowing what is on the critical path · treating strike as an afterthought · promising the client changes on site without asking what they cost in crew-hours · no dock plan · and — most commonly — a planner who is in the room during the build and is neither directing nor absent. The last one is worth sitting with.

C.7 Rubric. Count both. A healthy meeting surfaces most conflicts in the room; an unhealthy one produces a corridor afterwards where the real schedule is negotiated. The ratio is a measure of the chair, not of the suppliers — and the fix is the opening script in B.11, which explicitly makes the room the cheap place to raise a problem.

D.1 Rubric. The threshold is not about size and the chapter's own diagnostic proves it — none of the seven conditions mentions a guest count. A 250-guest marquee wedding on a bare field satisfies four; a 600-person conference in a purpose-built hotel with a dock, a lift, and a house crew may satisfy one.

A better diagnostic, and any of these is defensible: does any element require another to be finished first? (the purest test, and it is the definition of a supply chain) · is there a resource that more than two parties need simultaneously and that cannot be duplicated? · or the operational version: could a delay in one supplier's arrival make another supplier's work impossible rather than merely late? That last one is the whole distinction between float and physics, and it is answerable in one minute for any event.

D.3 Rubric. The client's objection is legitimate and specific: you are charging me for a day of a ballroom, a day of security, and in some cases a day of crew, and the deliverable for that day is nothing.

The honest attack goes further: the dark day's value is insurance against schedule risk, and insurance can be over-bought. On a well-mapped build with real margin, the dark day may be buying protection against a risk that has already been engineered out — and "worth more than an extra crew" is asserted, not costed. A dark day at a hotel ballroom can be $8,000–20,000 all-in, and an extra four-person crew call is $2,000–3,500. On those numbers the claim is straightforwardly false in some cases, and a strong answer says so.

What survives: the dark day buys something an extra crew cannot — turnaround compliance, a rested crew on the event day, and a schedule that can absorb a failure without an overnight. The defensible statement is conditional: where the build's critical path has less than about 15% margin, or where an overnight would breach turnaround, the dark day is cheaper than the alternative. Otherwise it is a preference, and it should be sold as one.

D.5 Rubric. The case that it is the wrong call is strong. Speaker rehearsal is where general sessions actually fail (Ch.31), an executive who flew in has already spent more than the rehearsal costs, and sacrificing it protects décor — which sits in the bottom row of Chapter 29's notice ranking. "We cut the thing that determines whether the general session works, in order to protect the thing nobody will remember" is a sentence that ought to stop the meeting.

The counter-case: doors is a contractual and reputational hard point with 400 people behind it; décor at that scale is often already installed and its removal costs crew-hours rather than saving them; and the rehearsal was recoverable — which is exactly what happened, and it moved to Wednesday morning off the critical path, where attendance went from 3 of 6 to 6 of 6.

A defensible decision: the chapter's outcome was right and its reasoning in the moment was wrong. The rehearsal should not have been sacrificed; it should have been moved, and moved deliberately, at the point the map was drawn — which is the general lesson. When a schedule is short, the question is not what to cut but what is not on the critical path, and the answer in this case was the rehearsal, in a better slot, for free.

D.7 Rubric. The framing — an event plus a reset — is useful and it is a physical framing, and what it misses is everything that degrades without being reset.

Failure modes not on the list of six, any of which is a strong answer: the crew's fatigue compounds and day three's error rate is not day one's, which no reset addresses · the client's decision-making degrades too, and day-two decisions are made by tired people who were fresh when the plan was written · information decays — a change agreed on day one is known to the people who were in the room on day one, and the day-two crew is not the same crew · the delegates' behaviour changes, and a room that was punctual on day one is not on day three, which breaks every transition assumption · and consumables are scoped per day and bought once, which is the chapter's own tape error.

The best answers notice that the reset framing addresses the room and not the people, and that most day-two failures are about people.

M.1 Chapter 13 asked will it fit? — dimensions, capacities, whether the truck can get in, whether the item goes through the door.

Here the access question becomes how does it get out, and what is waiting behind it? — a sequencing question rather than a dimensional one. The question Chapter 13 did not ask is the exit, and it is the difference between a yard with a truck in it and a yard with a truck in it and ten on a public road. Add: what else needs this access point in this hour, and what is upstream of this delivery on the dependency map.

M.3 Same physics, three new problems: distance (cable runs, voltage drop, and the fact that a 200-metre run is a different specification from a 20-metre one) · power quality (shared distribution, motor loads, and the dips that appear as flicker and audible noise) · and rigging — anything hung over people, which introduces load calculations, structural sign-off, and a licensed trade.

The governance change: sign-off moves from you to a licensed person. Below the line the planner decides what the lighting looks like; above it a rigger and an electrician decide what is permitted, their sign-off is a legal document and yours is an opinion, and the correct response to their "no" is what would make it possible?

M.5 The build sweep is the same instrument as Chapter 27's and it is walked at least twice a day.

The route: the gate and the marshalling area · the dock · the service road · the main space · back of house · the crew room · the toilets the crew are actually using · the waste point · and the emergency lane, end to end.

What you are looking for is different from the event sweep. On the event day you are looking for guests; on a build you are looking for: things blocking the emergency lane (the commonest single finding) · a vehicle that cannot leave · crew with nowhere to sit or nothing to drink · two disciplines in one space · trip hazards and untaped cable · waste accumulating outside its footprint · and people on site who did not attend the induction. The last one is a safety finding and it is found only by walking.

M.7 The two that get much worse are arriving and finding a seat.

Arriving becomes the badge queue, which does not exist at a wedding and which §34.6's arithmetic sizes: 280 arrivals with 40% in the peak half-hour is four staffed desks or two self-serve kiosks. Finding a seat becomes a repeated, several-times-daily, in-the-dark problem rather than a single event.

What §34.6 does about them: it separates circulation. Guests and service never cross, which removes the case where an arriving delegate meets a forklift; the emergency lane is kept clear so egress is real rather than drawn; and the site plan puts arrival, registration, and the first room in one continuous sightline, which is the only reliable fix for finding a seat. A sign is what you add when the sightline cannot be fixed.

M.10 Two things become impossible at distance and each has a substitute.

1. Standing in the space and seeing the collision. The space column is a document; the conflict is physical, and at home you resolve it by walking the route. Substitute: the local partner walks it, on a scheduled call, with the plan on screen and you asking specific questions — "stand at the dock and tell me what you can see; now walk the route the tables take." A generic video tour will not find it; a directed one will.

2. Being in the production meeting where the conflicts surface. The corridor conversation after the meeting is where the real schedule is negotiated and you are not in the corridor. Substitute: the numbered, batched, written protocol from §33.3a — every conflict logged with a number and an owner, and a weekly call that survives the weeks with nothing to discuss, because that call is the corridor.

And the row that does not change: you are there for the build. Three to five days early is not a nicety at this scale — it is the whole of the mitigation, and a planner who arrives two days before a large build has removed both substitutes and kept neither.

E.1 Rubric. The submission must contain all eight artefacts, and the dependency map must be drawn before the schedule — the ordering is checkable, since a schedule drawn first almost always sequences AV before staging, which is backwards.

When a production manager reviews it, expect their first three questions to be: where does the second truck wait? · what is your strike time and did you use 25%? · and who signs off the rig? A submission that answers all three without looking anything up has understood the chapter. Report their comments verbatim — including the ones that are about tone rather than content, since the most common one is "this reads like a plan rather than a schedule."

E.3 Rubric. The essay's argument is that schedule pressure is the mechanism by which safety degrades, and the two examples are the two ends of it.

The meal penalty is pressure meeting a rule that is enforced by money, and it resolves correctly almost every time — precisely because somebody attached a number to it. The rigger is pressure meeting a rule enforced by a licensed person, and it resolves correctly because that person has personal legal liability and cannot be overruled. The interesting territory is everything with neither: taping a cable, walking the emergency lane, the induction for the two people who arrived late, the second pair of hands on an awkward lift. None of those has a penalty or a licence attached, and they are where schedule pressure actually cashes out.

A position worth defending: a planner's obligation is not to make safety decisions — they are not competent to and the licensed trades exist for that reason — but to build a schedule in which the safe option is not also the expensive one. Which is a design obligation discharged weeks earlier, at the dependency map. A rig that lands at 14:15 against a 13:00 meal was made unsafe in a spreadsheet in week six, and by 12:45 the only available choices are bad ones.

E.5 Rubric. Five minutes, delivered to every person who comes on site, including the ones who have been on site all week and the ones who "are just dropping something off."

It contains, and in this order: where the exits are and where the assembly point is · where first aid is and who the named first-aider is · the channel plan and who is on which channel · who can stop work (one named person, known to everybody, said out loud — because with eleven contractors "everybody is responsible for safety" means nobody stops anything) · where the toilets, water, and crew room are · and the one site-specific hazard, which there always is.

Then deliver it and time it. The usual finding is that it takes seven or eight minutes on the first attempt and that the last two items get dropped, which is the wrong two — welfare and the site-specific hazard are the ones people remember. Cut the preamble instead.

Chapter 35 — Sustainability

A.1 🚪 The visible choices and the significant choices are almost entirely different sets.

They are not on standard checklists because they do not look like sustainability choices. "How many people and how far" is a guest-list conversation, held in month one, usually about money; "beef or chicken" is a menu conversation held with a caterer. Neither is filed under sustainability by anybody, while bamboo cutlery, recycled paper, and a wildflower seed favour all are — and those three together are under 1% of the answer. A checklist is a list of things that are legible as environmental, and legibility is not correlated with size.

A.3 One long-haul return flight (≈1,800–3,500 kg CO₂e) ≈ 400 beef dinners ≈ 150,000 disposable plastic forks.

A.5 Boundary · guests · travel factors · food by cover · energy · freight · materials and waste as one small line · rank and stop.

Steps 2 and 4 — guests and food — are 80–95% of the answer and take about twenty minutes. The ranking is the output; the total is decoration, and a planner who spends three hours refining the freight line has spent three hours on 0.4% of the number.

A.7 In order of size: the protein · the quantity, including over-preparation · the dairy · and last, and by a long way, the transport.

Clients and vendors talk most about the last one. "Local and seasonal" is the entire public conversation about food and the environment, and transport is typically under 10% of a food item's footprint. Beef → chicken across 100 guests saves about 400 kg — one short-haul return flight — and usually costs less, and nobody describes that as a sustainability measure.

A.10

Use carbon to decide where the effort goes, and judgment about everything else once you are there.

A.12 The real obstacle is almost never the law. It is the belief about the law — "we're not allowed to donate food" is usually a reflex rather than a rule, and it is repeated by caterers, venues, and planners who have never checked.

What you must establish first, in writing, before promising anything: that a recipient organisation exists, will accept this kind of food, and can collect it at the time it becomes available — which for a wedding is 11 p.m. on a Saturday and is the actual constraint. Then: temperature control, transport, and containers.

What is not waived: food safety. Good-faith donation protections — in the US the Bill Emerson Good Samaritan Food Donation Act and its 2023 amendment, with analogues in many countries — protect a donor acting in good faith; they do not permit donating food that has been sitting on a buffet at ambient temperature for four hours. The protection has conditions and they are about handling.

A.15 Six that cost nothing or save money: a smaller guest list · a venue closer to where guests are · a plant-forward menu · a realistic guarantee (over-preparation is a cost and a waste stream) · local and seasonal foliage instead of imported stems · and reusable or rented rather than bought.

The argument that works with a client: "I'm not asking you to spend money on the environment. I'm pointing out that the three decisions with the largest environmental effect on this wedding are also the three that save you the most money, improve your turnout, and get your guests home at a reasonable hour." You are not selling a trade-off, because at the top of the list there is not one.

A.17 Plainly: a planner's income scales with the size, distance, and expense of the event, and the most sustainable version of most events is a smaller one, closer to home. A percentage-fee planner recommending a shorter guest list is recommending their own pay cut.

The practical resolution is not to refuse work and it is not to keep quiet. It is to make sure the client hears the largest levers early, in plain terms, in month one — once — and then to build whatever they choose, well. You supply the arithmetic; they supply the decision. And say the conflict out loud when it is relevant, which costs nothing and is the only thing that makes the advice usable.

A.19 Scope 3 is the category in the GHG Protocol covering a company's indirect emissions outside its own operations and energy — its supply chain, its business travel, and its events. Your event is a line inside somebody's Scope 3.

Send the underlying activity data, not emissions: passenger-kilometres by mode, room-nights, covers by menu type, kWh consumed, vehicle-kilometres of freight, and waste by stream. Let their team apply their own factors, boundary, and methodology.

Why: a number you produced in an afternoon becomes a line in a disclosure with legal weight, computed on a different boundary with different factors from the ones their auditor requires. Activity data is what they need and cannot get; emissions are what they can compute and must own.

B.1 Rubric. Twenty minutes on steps 2 and 4, and then stop. Report the ranking, not the total — and report what the ranking tells you to stop doing, which is the exercise's real output.

The overwhelmingly common result: travel is 50–90%, food is 5–30%, and everything else combined is under 5%. What it tells most planners to stop doing: refining the materials line, agonising over cutlery, and describing a wedding as sustainable on the basis of decisions worth 0.5% of its footprint. If your event comes out differently — a local wedding where everybody walks, for instance — say so, because the ranking is the point and not the expected answer.

B.3 A 300-person conference: 40 long-haul, 95 short-haul, 110 driving 70 km each way, 55 by rail (~400 km), two days, 140 room-nights.

Forty people are 70% of the footprint.

The single change worth more than everything else: whether those forty travel at all. A high-quality hybrid track for the long-haul cohort — or, better, a decision to hold the event where they already are — is worth more than every other measure on the event combined, by an order of magnitude.

And the honest structural point: that decision belongs to the programme owner and the sponsor, it is made before a planner is engaged, and it is not a sustainability decision in anybody's mind when it is made (Ch.31). Which is exactly why raising it early, once, factually, is the highest-value act available. Removing every disposable item at this conference is worth perhaps 200 kg — one long-haul passenger is 2,600.

B.5 A six-tier diversion plan — rural marquee, no waste infrastructure, 10 a.m. handback.

Two rural-specific realities. There is no collection on a Sunday morning, so anything not removed by midnight leaves in somebody's car — and that person must be named at −2 weeks. And one contaminated bin fails the whole load, which makes the bin placement more important than the bin labels: three bins at the four generation points beats a beautiful sorting station forty metres away that nobody walks to.

B.7 Three claims through the five questions.

"Our packaging is 100% compostable." — Compared to what? Compostable versus what it replaced, which may have been reusable. Who verified it? A certification standard, or the manufacturer? What share of your total? Packaging is a fraction of a percent of an event's footprint. What happens to it afterwards — the decisive one: most such items are commercially compostable, requiring an industrial facility, and in landfill they behave approximately like plastic. Show me the number. Verdict: not a false claim and not a meaningful one, and it becomes false the moment there is no facility within collection distance.

"We've reduced our carbon by 40%." — Compared to what baseline, and in what year? A 40% cut from an unusually bad year is a different claim from a 40% cut from an industry norm. Who verified it? What share of your total is that? — the killer here: 40% of what scope? A caterer who has decarbonised their office electricity has changed perhaps 3% of their operation. Show me the number. Verdict: unassessable as stated, and the second and third questions usually end it.

"All our flowers are sustainably sourced." — Compared to what? Who verified it, and against which standard? — several exist and they vary enormously in rigour. What share — all stems, or the ones on the website? What happens afterwards — floral foam, single-use plastic wrap, and where the arrangements go at 11 p.m. Show me the number — or, better here, "where were these grown, and when were they cut?" Verdict: the vaguest of the three, and the one where the substantive alternative is easiest to check: a florist who grows their own foliage or buys from a grower eleven miles away can name the field.

And the counterweight that belongs in the answer: many vendors doing genuine, expensive, unglamorous work describe it badly or not at all. Ask what they do, not what they claim.

B.9 What you send a corporate sustainability team.

The data pack — a spreadsheet with one tab per category and a source column:

TRAVEL      origin city/airport · destination · mode · return trip? ·
            passenger count · great-circle or road km · SOURCE
            (registration form / travel agent / estimated)
ACCOMMODATION  room-nights by hotel · nights · occupancy
CATERING    covers by service · menu type per cover
            (beef / other red meat / poultry / fish / vegetarian / vegan)
ENERGY      venue kWh where separately metered · generator litres of fuel
FREIGHT     vehicle-km by vehicle type · number of trips
WASTE       kg by stream · destination of each stream
ESTIMATES   every figure that is an estimate, flagged, with the method

The covering note:

"Attached is the activity data for the October conference, in the categories your team asked for.

I've deliberately not applied emissions factors or produced a CO₂e total.* You'll be using a specific factor set, boundary, and methodology for your disclosure, and a number I produced with a different set would be wrong for your purposes and hard to unpick later. The underlying data is the part you can't get anywhere else; the conversion is yours.***

Where a figure is estimated rather than measured, it's flagged in the source column with the method — the largest estimates are the road distances for drive-in attendees and the venue's electricity, which isn't separately metered for our space.

One thing worth flagging for your own analysis: 70% of this event's travel emissions come from 40 long-haul attendees. If reduction is a goal for next year, that's where it is, and the decision is a programme decision rather than a production one."

B.11 $25,000 at a 900-person conference: 2,100 tonnes, 88% aviation.

Aviation is 1,848 tonnes. Everything else combined is 252. Start by saying what $25,000 cannot do:** at credible removal prices of ~$150/tonne it buys 40 tonnes — 1.9% of the footprint. There is no allocation of $25,000 that materially reduces this event's emissions**, and any plan that implies otherwise is dishonest.

So allocate it to the things that change next year and to the things that are true:

The claim the client can actually make:

"We measured this event's footprint: 2,100 tonnes CO₂e, of which 88% was attendee aviation, and we've published the figure and the method. We did not reduce it much — we couldn't, having chosen the location and format before we measured. We've made three changes for next year: a produced remote track, mode data captured at registration, and plant-forward menu defaults. And we purchased verified removals covering 40 tonnes — about two per cent — which we are describing as compensation rather than as a reduction, because that is what it is."**

The claim the client cannot make: carbon neutral. A footprint that is 88% aviation is not neutralised by 1.9% of removals, and the honest version of that sentence is the one above.

B.13 Imported stems with a lower carbon footprint than local greenhouse-grown ones.

The carbon comparison is probably correct. Field-grown flowers flown from a warm country can carry less carbon than flowers grown in a heated glasshouse in a cold one — the heating dominates, and transport is a small share. A planner who reflexively answers "local is better" is wrong on the number.

But carbon is one axis and it is not the decision.

How to work the decision: carbon ranks where the effort goes and it does not adjudicate between two options within a small line. Floral is typically 1–3% of an event's footprint, so the carbon difference here is a fraction of a fraction — and the impacts carbon does not capture are, in this specific case, larger than the impact it does.

The defensible answer: ask the questions you can actually verify, and prefer the chain you can see. And say the honest part to the client: "the imported stems are probably lower carbon, and I'd still recommend the local grower, and here is why — it isn't the carbon." A planner who claims the local option wins on carbon has told a client something untrue in order to reach a decision that was defensible anyway.

C.1 Rubric. Report the two totals and the percentage gap. Expect 20–100% disagreement, and expect most of it to come from three places: the aviation factor (whether radiative forcing is included roughly doubles it) · the boundary (does hotel accommodation count?) · and food factors.

What it means for reporting: never report a total without the method, and never report a total to a party who will use it in a disclosure — send activity data (§35.8a). The disagreement also validates the chapter's central practice: the ranking is stable across calculators even when the total is not. Both will tell you travel dominates. That is the durable output.

C.3 Rubric. Report what the protection covers and — more usefully — its conditions. Common structure: it protects a good-faith donor from civil and criminal liability for the condition of donated food, provided the food met safety standards when donated and the donation was made to a nonprofit for distribution to people in need.

What it does not cover: gross negligence or intentional misconduct · food that was already unsafe · and, in most cases, it says nothing about the practical requirements — temperature control, transport, and whether an organisation will actually collect at 11 p.m. Report the gap between "legally permitted" and "operationally possible," because that gap is where every real donation plan fails.

C.5 Rubric. Report which answers were substantive, using the five questions as the test. The pattern is consistent and worth reporting: the most substantive answers usually come from people who do not use the word sustainability — a rental company describing their repair workshop, a caterer who can quote their food-waste percentage before and after, a florist who names the field. The least substantive come with a page on a website.

C.7 Rubric. Weigh or estimate by stream, compute the diversion rate honestly — and the honesty is the exercise: contaminated streams count as landfill, and material you hoped was composted counts as landfill unless you can name the facility.

Then compute the CO₂e and expect to be deflated: it will be small, likely under 2% of the event. Report both numbers together. The correct conclusion is not "waste doesn't matter" — it is that waste is a real obligation for reasons the carbon number does not see, and that the carbon argument for it is weak and should not be the one you make.

D.2 Rubric. The objection is strong: a professional who knows that one decision dominates every other, and who mentions it once and then falls silent, has optimised for their own comfort. Doctors do not mention smoking once.

What can be said in reply, honestly: the planner's knowledge is arithmetic and the decision is a values decision — where to hold a wedding involves family, obligation, and meaning that the planner has no standing over · the analogy to a doctor fails on the consent relationship, since a patient asked for health advice and a couple asked for a wedding · and repeated advocacy is ineffective, converting the planner into a person the client stops telling things to.

Where the line actually is, and this is the useful part: "mention it once" is too weak, and the correct standard is make sure they understood it. Which means: say it early, say it with the number attached, say it in a form they can act on, check that it landed, put it in writing once — and then drop it. The obligation is to the transfer of the information, not to the outcome. A planner who mentioned it in month one in a sentence nobody registered has not discharged anything.

D.3 Rubric. Disclosure is not a solution and the chapter should not be read as claiming it is. Naming a conflict does not remove it — the incentive still operates, and there is a real literature suggesting disclosure can increase biased advice by making the adviser feel licensed.

What solving it would look like, in ascending order of seriousness: a flat fee rather than a percentage, which removes the direct scaling · a fee agreed before scope, so that later reductions do not cost the planner · an explicit fee floor, so a planner is not punished for a smaller event · being paid for the advice separately from the production (the B.15 move in Chapter 32) · and, structurally, charging for capacity — Saturdays — rather than for event size, which is Chapter 37's model and which genuinely decouples the planner's income from the scale of any one event.

That last one is the real answer and it is worth noticing that this book already recommends it for unrelated reasons. A defensible conclusion: disclosure is the minimum, the fee structure is the fix, and the chapter is honest about the first while under-selling the second.

D.5 Rubric. The reading is available: 83% diversion produced about 15 kg CO₂e of saving, which is roughly one guest driving 100 km. On carbon alone, the whole waste programme is a rounding error.

The answer is that carbon is the wrong instrument for this decision, and the section says so and does not say so loudly enough. Waste matters for the impacts a carbon number does not capture — plastic persistence, local pollution, the material itself — and for reasons that are not environmental at all: it is what the client and the guests can see, it is where a venue's own obligations sit, and it is the tier-one measures (prevention: the guarantee, the over-preparation percentage) that carry the actual money.

What the section should have emphasised more: tiers one to three, and specifically that most event sustainability effort starts at tier four. The saving is in not producing the waste — a guarantee set at the confirmed number, over-preparation at 10% instead of 20% — and that is a catering conversation with real money in it, not a bin.

D.7 Rubric. The objection is legitimate: a client asked for a carbon-neutral event, that is their stated goal, and a planner who refuses to use the term has substituted their judgment for the client's on a matter of the client's own communications.

And the counter is about a different obligation: using the term is not a preference, it is a claim made publicly on the client's behalf, and in a growing number of jurisdictions an unsupportable environmental claim is a regulatory exposure for the client. The planner is not refusing the goal; they are refusing to write a sentence that is false.

Decide, and this is defensible: do not refuse the goal, refuse the word, and offer the sentence that is true. "We measured, we published, we reduced X, we compensated for Y with verified removals, and we're describing that as compensation rather than neutrality." Then, if the client insists on "carbon neutral," say once in writing that you believe the claim is not supportable and why — and let them make it. It is their communication. What a planner cannot do is put the phrase in the copy they write and then say it was the client's decision.

M.1 The guarantee is a waste measure because it is the number the caterer buys and cooks to. A guarantee set at the invited number rather than the confirmed number buys food for people who are not coming, and over-preparation of 10–20% is then applied on top of an already inflated base. It is tier one — prevention — and it is worth more than every bin at the event.

What Chapter 30's reconciliation reveals: what the guarantee actually cost versus what was eaten — and the fourth column, what it should have been. This is the only mechanism that improves the next guarantee, and without it a planner repeats the same 15% over-order for a decade and calls it experience.

M.3 §35.2 says a destination event's footprint is dominated by guest aviation to a degree that makes every other decision on it approximately irrelevant — one transatlantic guest is 400 beef dinners.

What it does to Chapter 33's E.3: it removes the option of arguing that a well-run destination wedding is environmentally defensible on the strength of its choices. It is not the flowers, the food, the waste, or the local sourcing — it is eighty flights, and no amount of good practice inside the event touches them. A strong E.3 answer must therefore argue on other grounds — guest choice, the smaller list, the value per guest-hour — or concede. What it cannot do is argue on carbon.

M.5 Three times, and each time in a different domain — which is why it is the book's most reinforced threshold concept.

§35.2: the guest count multiplies travel, which is 50–90% of the footprint. §35.4: it multiplies covers, which is the second-largest term. And §35.10's closing observation: the Reyes–Whitfield guest-list cap, decided in Chapter 5 for money, was the largest environmental decision made on the wedding — worth about twelve times everything else combined — and it was never described as an environmental measure by anybody involved.

Chapter 5 said guest count is the master variable for cost and logistics. This chapter adds emissions as a third domain governed by the same number.

M.7 It is the sponsor's conversation, not the planner's and not the programme owner's.

Chapter 31's rule: only the sponsor can change the programme. A hybrid track changes who attends, what the agenda is for, how the objective is measured, and how the event is sold internally — and a planner who proposes it to the programme owner will get agreement and no change, because the programme owner cannot authorise it. The planner's job is to bring the arithmetic — forty long-haul attendees are 70% of this event's footprint — and hand it to the person who will be asked in April.

M.9 Because a supplier who goes out of business takes their practice with them, and the practices that matter are slow, unglamorous, and unprofitable to acquire.

A rental company's whole business model is reuse. A florist who grows their own foliage has spent years building beds. A caterer who has cut food waste from 18% to 7% did it over four seasons. None of those is replaceable by procurement — a new supplier starts at the industry default — and all of them are fragile businesses in a seasonal market.

Chapter 12's argument was relational and commercial: pay on time, brief properly, do not squeeze the margin to nothing. This chapter adds that those behaviours are also the mechanism by which the good environmental practice in your supply chain continues to exist. The most sustainable thing a planner does for a supplier is keep using them and pay them promptly.

E.1 Rubric. The analysis must include the eight steps and the §35.8a activity-data pack — and the exercise's real test is the last instruction: send the pack to somebody and ask whether they could use it.

Expect the answer to be no, at first, and expect the reasons to be specific: origin cities recorded as country not airport · return trips not distinguished from one-way · covers recorded as "veg: 14" with no breakdown of the other 86 · no source column, so nothing can be audited · and estimates presented as measurements. Every one of those is fixable at registration and none is fixable afterwards, which is E.5's point arriving early.

E.3 Rubric. A position, stated as you would state it to a client, and specific about what you would still take. Both positions are defensible and the unserious answer is the one that stays general.

Available position A — no, and here is why: it is the client's decision, a planner declining does not prevent the event, the refusal is symbolic and costs the client nothing but costs you the ability to influence anything, and the honest lever is disclosure rather than veto.

Available position B — yes, at some point, and here is the point: every professional has work they will not do, the line is not about the client's values but about what you are willing to have your name and craft attached to, and a planner who claims no line has simply not been offered enough money yet.

What makes it strong is the specificity of the second half. For example: I would take a destination wedding, a large gala, and a conference with heavy air travel — all of them — and I would put the arithmetic in front of the client once, in writing, early. What I would not take is an event whose environmental claims I would have to write and know to be false, or one that requires me to describe an offset purchase as neutrality. That line is about honesty rather than emissions, it is enforceable, and a client can be told it in one sentence.

E.5 Rubric. The design is mostly a registration form, and the cost is mostly in the friction it adds.

Capture at registration: origin city or airport code, not country · mode, as a choice (air / rail / car / coach / local) · return or one-way · for car, whether shared and with how many · menu selection by type, not by "dietary requirement" · and nights of accommodation and where. Capture at the venue: metered kWh where possible, generator fuel by litre, freight vehicle-km from the marshalling schedule — which already exists (Ch.34) — and waste by stream, weighed at collection.

Cost it honestly, which is the part most submissions skip. Four extra registration fields cost perhaps 20 seconds per attendee — at 900 attendees that is five hours of other people's time, and it measurably reduces registration completion, which is a real cost to the client. Setup is a few hours; the annual maintenance is small; the weighing at collection needs a named person and about an hour. Total realistic: 8–12 hours of planner time per event plus a small drop in registration conversion.

And the honest conclusion: it is worth it only if somebody uses the output. A data pack nobody reads is 12 hours a year spent on measurement in place of reduction — which is the failure mode this chapter warns about in every other section, and it applies here too.

Chapter 36 — Starting Your Planning Business

A.1 Take-home you need · plus tax · plus fixed costs · = revenue required · ÷ billable hours · = your floor.

Everybody gets step five wrong, by dividing by hours worked rather than hours sellable. A billable ratio of 35–50% in year one and 55–65% established means the error understates the true rate by roughly 65% — a planner who divides by 2,000 worked hours instead of ~1,200 billable ones computes a floor that is about 40% of the real number, and then wonders why a year of full diaries produced no money.

A.3 The market price is a constraint; your cost of an hour is a floor. The market tells you what can be charged; your arithmetic tells you what must be.

If the floor is above the constraint, you have a positioning problem, not a pricing problem. The answer is not to charge above the market and wait — it is to change what you sell, to whom, or how many hours it takes: a different service level, a different client, a narrower niche, or fewer and larger engagements. A floor above the market is arithmetic telling you that the business as currently designed does not work, and no amount of pricing courage fixes a design.

A.6 Deferred revenue is money you have been paid for work you have not yet done — every deposit sitting in your account for an event in eleven months.

It is dangerous because it looks exactly like profit in a bank balance. A planner with $34,000 in the account may have $31,000 of other people's weddings in it, and the arithmetic that says otherwise never gets done.

The fix: a separate account for client funds, or at minimum a single line in the cash-flow forecast that shows how much of the balance is committed. A planner who cannot say in ten seconds how much of their balance is theirs does not know whether they are solvent.

A.8 Because the money arrives in a shape unrelated to when the work happens. Deposits come eleven months early, balances come at −14 days, corporate invoices come at 60 days, and the fixed costs and drawings come monthly all year. The worked year in §36.5 makes $4,200 of profit and is $5,200 down in June, and it is a normal, well-run business.

Four defences: a monthly twelve-month cash-flow forecast · deposits that match your own outgoings (never fund a client's vendor deposit from your account) · milestone billing rather than one final invoice · and runway — three to six months of personal and business costs, in cash, before you start.

The fifth, structural one: where possible, have the client pay vendors directly. It removes the largest cash-flow exposure entirely and removes you as a credit risk — and Chapter 33 argued for exactly the same arrangement on completely unrelated grounds.

A.10 It is a phone call rather than an email, and it carries an offer to restructure rather than a demand.

The call works because most late payment is not refusal — it is somebody who has not opened your email, or somebody who cannot pay this week and is avoiding you. The offer to restructure removes the reason for the avoidance, converts a silence into a plan, and it is the only version of the conversation that preserves the relationship you will need for a referral in two years. Automatic reminders have already done most of the work by day 14; what is left is the cases reminders cannot reach.

A.13 A client contract · a proposal template · an onboarding pack · invoice and payment terms · a planning-document template set (budget, timeline, run sheet, guest list, vendor tracker) · the debrief and finding log — plus the two that complete the eight: a discovery questionnaire and a vendor brief.

Must not be a template: the client contract. It is the one document that must be reviewed by a lawyer in your jurisdiction, and it is the one where a downloaded template is actively worse than nothing, because it produces confidence without protection.

The two people make and should not: a brochure, which nobody reads and which dates instantly, and a published price list, which Chapter 37 argues about at length and which should be a deliberate decision rather than a default.

A.15 1. People who already know you. 2. Vendor and venue referrals. 3. Past clients — which you do not have yet. 4. Approximately nothing else. Advertising produces essentially none of the first ten.

The instruction it produces: spend year one on venues and vendors, not on a website. Eleven minutes with a venue coordinator is worth more than a month of content, and the correct year-one marketing budget is mostly petrol and coffee.

A.17 Because a styled shoot demonstrates aesthetic taste, and almost nobody hires a planner for aesthetic taste. They hire a planner because somebody told them to. Four days and $1,200 of beautiful images published on a blog generate enquiries at a rate indistinguishable from zero.

What makes it worth doing anyway: the relationships. A day spent working alongside a photographer, a florist, and a venue produces the referral relationships that are the actual channel (§36.7) — and the images are a byproduct for a website that needs them. Do it for the people, count the photographs as change.

A.19 🚪 Your billable ratio is a function of how many clients you have, not how much work you do.

The arithmetic: every client carries 12–18 unbillable hours regardless of fee — enquiry, consultation, proposal, contracting, onboarding, invoicing, chasing, debrief. Twenty-six coordinations carry roughly 390 hours of overhead. Seven full plannings carry 105. That 285-hour difference is nearly a quarter of a year's billable capacity, and it is spent before any work happens — which is the strongest argument in the chapter for fewer, larger engagements, and it has nothing to do with prestige.

B.1 Rubric, with a worked shape.

1  Take-home needed                              $42,000
2  + tax (illustrative 25% effective)            $14,000
3  + fixed costs (the list below)                $12,600
4  = REVENUE REQUIRED                            $68,600
5  ÷ billable hours: 2,000 worked × 50%           1,000
6  = COST OF AN HOUR                              $68.60

A real fixed-cost list, and it must be researched rather than guessed: insurance (liability and professional indemnity) · accountant · the tool stack, items 1–4 · phone and internet share · vehicle and fuel · professional membership if you have one · website and domain · bank charges and payment processing · and the category everybody omits: unbillable travel to site visits and vendor meetings.

Then state the rate below which you are working for nothing — and note what that sentence actually means. At $68.60/hour, a $1,500 coordination that takes 45 hours pays $33.33 and is a loss against the floor, not a small profit. Report your own number and then look at your actual last three engagements against it.

B.3 Rubric. Research at least four lines for real — insurance, accountancy, the tool stack, and one local line such as a professional membership or vehicle costs — and report which surprised you.

The three that most commonly surprise: insurance, which is usually cheaper than expected and has limits lower than a venue requires · payment processing at 2.5–3.5% of everything, which nobody budgets and which on $60,000 of client money passing through your account is $1,500–2,100 · and the accountant, which is usually more than expected and is nearly always worth it. Report the annual total and divide it by your event count, because that is the number that belongs in a fee.

B.5 Twelve-month cash flow — five weddings at $6,000 (40% deposit at booking, balance at −14 days) and one corporate event at $12,000, net 60 days.

Fixed costs $1,050/month; drawings $2,000/month; opening cash $6,000.

The year earns $42,000 against $12,600 of fixed costs and $24,000 of drawings — a profit of $5,400 — and ends $600 overdrawn.

The negative month is December, and it is caused by a single invoice on 60-day terms. The $12,000 was earned in November and arrives at the end of January.** **Nothing about this business is unprofitable; it has simply been asked to fund seven weeks of somebody else's payment terms out of a $6,000 buffer.

April, July, November, and December are all structurally thin — the pattern is the same one every seasonal business has: money arrives when events happen, and events do not happen in the winter.

What I would do about it, in order. Negotiate the corporate terms before signing — 30 days, or 50% on completion and 50% at 60 days; this is the single highest-value action available and it takes one conversation. Move the wedding balances from −14 days to −30 days, which shifts three of them into an earlier month and costs the client nothing. Add a mid-point instalment so a $6,000 fee arrives as 40/30/30 rather than 40/60. **Hold a genuine buffer of three months' costs — $9,150 — rather than $6,000. And do not book work in November whose payment lands in the following tax year without knowing that is what you are doing.**

B.7 The day-3, day-14, and suspension messages.

Day 3 — automatic, and it does most of the work.

Subject: Invoice 0114 — just a nudge

Hi Bea — invoice 0114 for $2,400 was due on the 12th and I don't think it's come through yet. It may well have gone to spam or be sitting with somebody else; the link's below and I'm happy to resend it anywhere useful. Thanks! — Noor

Day 14 — a phone call, not an email, and it carries an offer.

"Hi Bea, it's Noor — nothing dramatic, I'm just ringing about the instalment that was due a fortnight ago. I wanted to check nothing's gone wrong at your end.

And if the timing's difficult, tell me — I'd much rather split it across two months than have this be a thing between us. What would work?"

Then stop talking. The offer is what makes the call effective, because the commonest reason for a fortnight's silence is not refusal but embarrassment, and the person avoiding you cannot resolve it without a route back that does not require an apology.

The work-suspension message — written, calm, specific, and never a threat.

Subject: Invoice 0114 — pausing work from Friday

Hi Bea,

Following our call on the 26th, invoice 0114 ($2,400, due 12 March) is still outstanding and I haven't been able to reach you since.

Under clause 6 of our agreement I'll be pausing work on the wedding from Friday 5 April until the account is settled.* In practice that means I won't be confirming the marquee balance or issuing the final numbers to Marguerite, both of which have deadlines of 19 April* — and I want to be clear about that date because after it, some of those bookings become difficult to hold.

This is entirely fixable and I would much rather fix it. If a payment plan helps, say the word and I'll write one today.

Noor

Three properties. It cites the clause, which is why the clause exists. It names the specific operational consequence and the date it bites — which is information the client needs, not leverage. And it repeats the offer, because the aim is payment and a wedding, not a position.

B.9 Rebuilding an unownable niche.

"Luxury weddings" fails the test: somebody who met you once cannot describe you accurately in one sentence three months later, and every planner in the market says it.

Rebuild it from one of the three real sources — here, from a competence most planners lack:

"I plan weddings at raw sites — fields, barns, farms, private land. If there's no kitchen, no power, and no loo, that's my job."

The working. It comes from something true — eleven of the planner's fourteen events have been at bare-field sites. It is describable by a stranger: a venue coordinator at a barn can repeat it verbatim and will, because it solves a problem they have. It is disqualifying in a useful direction — hotel weddings go elsewhere, which is the point. It implies a competence with evidence attached: power calculations, generators, water, sanitation, access, weather (Ch.13, 18, 34). And it names a referral network that is not competing with you: every raw-site venue in the region needs somebody they can hand a couple to, and they have nobody.

The other two sources, for comparison: what you have done — "I ran conferences for eleven years and now I plan weddings, so nothing about a hundred and forty moving parts frightens me." A community you belong to — genuinely belong to, not a market you have identified, which is the failure mode: a planner who is not part of a community and announces themselves as its specialist is recognised as an outsider immediately and permanently.

B.11 Rubric. Do §36.8a's arithmetic with your own market's fees and your own honest hours estimate. The structure:

required revenue ÷ billable hours = required rate
hours per event × required rate = REQUIRED FEE
compare to your market's actual range

In the chapter's illustration — 1,200 billable hours, $68.25 required — full planning needs $10,920 against a market of $4,000–12,000, partial needs $5,119 against $2,000–5,500, and coordination needs $3,071 against $1,200–3,000. Only full planning fits, and only at the top of its range.

Report which level fits in your market, and expect the answer to be uncomfortable. The common finding is that coordination — the level everybody starts with because it looks like the easy entry — is the level where the arithmetic works worst, since it is less work per event and not less work per dollar.

B.13 Four questions for a venue coordinator, and what you should expect back.

1. "What do planners do here that makes your life harder?" — Predicted answer: late final numbers, changes on the day that were decided a week ago, not reading the venue's own supplier requirements, and arriving without having told the venue who is coming. You will get a real answer because nobody has ever asked.

2. "What catches planners out at this venue specifically?" — Predicted: the access, the parking, a curfew, a shared lift, the fact that the office is closed on Saturdays. This is the venue file (Ch.39) being built for free, and the answers are worth more than any site visit.

3. "When a couple asks you to recommend a planner, what happens?" — Predicted: either a list of three, or "we're not allowed to recommend, but we say who's been here." Both answers are useful and they are completely different mechanisms.

4. "What would make you comfortable giving them my name?" — the one that matters. Predicted: "see you work here once." That is the honest answer and it is why the fastest route onto a venue's list is to be second-shooting, assisting, or running a small event there — and why the answer to a venue that says no is "can I come and watch one?"

C.1 Rubric. Report the actual structures available in your jurisdiction, the setup cost, the annual maintenance cost, and the annual filing obligations. Do not report what a US or UK textbook says unless that is your jurisdiction.

Two things to report explicitly because they are the ones that matter: whether the structure protects personal assets and against what — and the answer is never "everything," since limited liability does not protect you from your own negligence, insurance does — and what it costs to close. Almost nobody asks the last one, and it is the difference between a structure you can leave and one you are stuck maintaining.

C.3 Rubric. Report the fee and the deliverables, and report what they need from you, which is the more useful half: usually a separate business bank account, records kept monthly rather than annually, receipts retained in a specific form, and a decision about your structure before the year starts rather than after it.

The common finding: an accountant costs less than a year-one planner expects and needs more discipline than they expect. And the most valuable single sentence you will get is which expenses are deductible in your jurisdiction, which is a list nobody can guess.

C.5 Rubric. Ask three working planners their billable ratio. Note how many have ever computed it — the usual answer is none — and note what they estimate when asked to guess. Estimates cluster around 80%, and the real figure is 35–65%.

The gap is the exercise. A planner who believes 80% of their hours are sellable has computed a cost of an hour that is roughly half the true one, and every fee they have quoted for a decade contains that error.

C.7 Rubric. Price items 1–4 for real, in your market, in your currency. Expect roughly $45–100/month for the four. Report the monthly total and multiply by twelve — and then note that the planning platform everybody buys first is item 5, costs more than the other four combined, and is genuinely worse than a spreadsheet until client four or five.

D.2 Rubric. The hours arithmetic favours fewer, larger engagements. Build the case for coordination-only anyway, and there is a real one:

Cash cycle — a coordination is contracted and paid within weeks rather than eleven months, which is a materially better cash-flow business (see B.5) and does not require the same runway. Risk — twenty-six small engagements are a portfolio; seven large ones mean one cancellation is 14% of your year. Skill acquisition — twenty-six event days a year is three years of day-of experience compressed into one, and day-of judgment is the hardest thing to buy. Referral surface — twenty-six weddings means twenty-six sets of vendors watching you work. Lifestyle — coordination is bounded, it does not colonise weekday evenings, and it is compatible with another job or with caring responsibilities. And market access: a couple who cannot afford full planning is a client you can actually get in year one.

What the arithmetic still says, and the honest answer must concede it: twenty-six Saturdays. Chapter 41 counts what that costs, and it is the constraint that eventually forces the change. The defensible position is that coordination is an excellent way to start and a difficult way to stay — and that the transition is a deliberate act, not something that happens.

D.4 Rubric. The objection is real and worth stating properly: a four-day contract role is how a business quietly dies. The one day left goes on admin, no marketing happens, no venue relationships get built, and in eighteen months you are an employee with a dormant company and a story about how you tried.

And the counter is that the alternative kills faster. Runway is the constraint that ends most new businesses, and a planner without three to six months of costs in cash is making pricing decisions from fear — taking the $1,500 coordination, discounting to close, and saying yes to work that is below their floor. The contract role buys the ability to say no, which is the single most valuable asset a year-one planner can have.

Decide, and this is defensible: take it, and put a hard boundary and an exit condition on it. A stated end date, or a stated trigger — "I leave when I have four events contracted and deposited for next season" — written down, with a date on which you check. The failure mode is not the contract role; it is the contract role without a stopping condition, which is Chapter 41's argument arriving three years early.

D.6 Rubric. The vendor's case is fair: a planner running four events on spreadsheets builds four events' worth of bad habits, then imports the mess. Good process is cheaper to adopt than to retrofit.

The answer has three parts. A platform's process is a generic process, and it will not fit your service level — a tool built for full planning applied to coordination silently changes what you do (§39.4's question: what does it not do that I will therefore stop doing?). A planner who has never built a run sheet does not know what they need a platform to do, so they choose on the demo rather than on the requirement, and switching later costs more than the year saved. And the documents in §36.6 are the process — they are not a substitute for a platform, they are what a platform automates, and you cannot automate a process you have not got.

What the vendor is right about, and a strong answer concedes it: the accounting and e-signature tools should be bought before client one, precisely for the retrofit reason. The argument for waiting applies to the platform, not to the stack.

D.8 Rubric — they are in tension only if you conflate two different variables, and untangling them is the exercise.

Chapter 35's concern is with the size and distance of the event: guest count, travel, budget. Chapter 36's argument is about the number of clients: unbillable overhead scales per client, not per dollar. These are different axes, and the resolution is that a planner can hold fewer engagements without those engagements being larger events.

Fewer clients, same size events, higher fee per engagement is entirely consistent with Chapter 35 — and the model that most cleanly resolves it is Chapter 37's: price capacity (Saturdays) rather than event size, which removes the incentive to grow the event while keeping the incentive to hold fewer of them.

A strong answer also concedes the residual tension honestly: in practice, the way most planners achieve fewer engagements is by moving upmarket, and upmarket events are larger and more travelled. The tension is not logical, it is commercial — and naming that is better than resolving it too neatly.

M.1 Chapter 2 described service levels as a description of the client's progress and the planner's scope. §36.8a makes them a business decision with an arithmetic answer: hours per event × required rate = required fee, compared against what the market will pay.

Where unpaid hours live: in the 12–18 hours per client that exist regardless of fee — enquiry, consultation, proposal, contract, onboarding, invoicing, chasing, debrief — and in everything before the contract. Twenty-six coordinations carry 390 hours of it; seven full plannings carry 105. The unpaid hours attach to clients, not to events, which is why the cheapest-looking service level is the most expensive to run.

M.3 Chapter 9 argued insurance from the event's point of view: the claim, the limits, the exclusions, the venue's requirements. §36.2 adds the business point of view and one hard structural fact: limited liability does not protect you from your own negligence — insurance does.

The container and the protection are different things. A company structure limits the business's contractual exposure; it does not stand between you and a claim arising from your own professional error, and it does not survive commingling — a personal account used for business money makes the container decorative. The practical trio: the structure, the insurance, and a separate bank account, and the third is what makes the first real.

M.5 Because year one is the year with the most findings and the least memory.

A planner running their first four events makes more discoveries than they will in the following four years, and none of them will survive to year two without a document. The finding log is the mechanism by which year three is year three rather than year one repeated three times — and the compounding is the point: every finding converted to a template change is a permanent improvement, and every finding merely felt is a lesson that will be re-learned at a client's expense.

It also costs nothing, needs no software, and is the one professional practice available to somebody with no clients yet.

M.7 Chapter 33 said a destination event does not cost the planner less and frequently costs more — travel days, time-zone overhead, two site visits, and a coordination burden that does not shrink with the guest list.

This chapter's arithmetic explains why, and it is the billable-hours argument. A 60-guest destination wedding carries the same 12–18 hours of per-client overhead as a 200-guest local one, plus five to eight travel days that are billable to nobody, plus the asynchronous communication load. The event is smaller and the client count is identical, so the fee cannot scale with the guest list without the engagement becoming a loss. Which is why destination work is priced on the engagement, not on the event.

M.9 It is §29.5's principle applied to a colleague: ask rather than provide, and never require somebody to classify themselves.

Somebody starting out will not ring and say "I don't know what I'm doing and I can't afford advice." They will ask one small, specific, safe question — usually about a contract clause or a rate — because the small question is the version that does not require them to admit anything. Answering it kindly, and answering the question behind it without naming it, is the same move the chapter makes for a guest who cannot walk 200 metres: you provide, and you do not make them ask.

E.1 Rubric. The plan must contain all eight components and the numbers must connect — the cost of an hour must be the one used in the fee arithmetic, and the fee arithmetic must be the one driving the cash-flow forecast. The commonest failure is three internally-inconsistent spreadsheets.

Then show the cash-flow forecast to somebody who runs a business — any business — and record what they say. Expect: "where's your tax?" · "what happens if one of these cancels?" · "why is this month empty?" · and "that isn't a salary." Every one of those is a legitimate finding and none requires knowledge of events, which is exactly why the exercise sends you outside the industry.

E.3 Rubric. A position, argued from the arithmetic rather than from sentiment.

The case that it is not sustainable: a billable ratio of 35–65% means a headline fee is roughly half of what it appears · only one service level's required fee sits inside the market range, and only at the top of it · the market cannot distinguish competent from excellent (Ch.41 §41.8a), so quality does not command a reliable premium · the Saturday constraint caps volume at 10–18 events regardless of skill · and the work is seasonal, so a bad six weeks is a bad year. Chapter 37's arithmetic adds that the celebrated findings in this book's own case study were performed at $10.18/hour.

The case that it is: the constraint is soluble by design rather than by effort — fewer, larger engagements; capacity pricing; corporate work that pays in a different currency of hours; and a stated ceiling — and the planners in Chapter 41's year eleven earn twice what year four earns from nine events instead of fourteen. The economics are hostile to the default configuration and workable in a designed one.

What makes it strong: naming who the economics are not sustainable for. They are worst for a new planner without capital, worst in coordination, and worst for anybody who cannot absorb a thin winter — which is a statement about who the industry admits, and that is the honest conclusion of the essay.

E.5 Rubric. Fifteen minutes, monthly, and it surfaces three things or it is not the instrument.

CASH        Balance today. Of which committed (deferred revenue):
            Money that is mine:
            Lowest projected balance in the next 3 months:

THE HOUR    Hours worked this month:  Billable:  Ratio:
            Revenue this month ÷ billable hours = $
            (Against my floor of $____)

PIPELINE    Enquiries:      Proposals out:      Booked:
            Contracted revenue for the next 12 months:
            Saturdays sold / Saturdays available:

ONE THING   The finding I am converting to a change this month:

Design constraints that make it survive: it must be completable from the accounting tool and a calendar in fifteen minutes — anything requiring reconstruction will not be done twice — it must have no reflection box, and it must be attached to something already obligatory, such as the monthly bookkeeping. A practice that depends on discipline fails; a practice attached to an existing obligation survives (Ch.39, Ch.30 E.3).

Chapter 37 — Pricing Your Services

A.1 Flat fee: you absorb all the uncertainty. Percentage: it is shared, badly. Hourly: the client absorbs it.

Most planners choose the flat fee — the model that transfers every hour of scope risk to them — and then price it as though there were none, at the median of their own hours rather than the 75th percentile. What follows is that the errors are asymmetrical and cumulative: the events that run long run very long, the events that run short save you a few hours, and a year of correctly-estimated medians still loses money.

A.3 The first problem with percentage pricing is the client's — the perverse incentive, since every recommendation that raises spend raises your fee. The second problem is the planner's: you are exposed to a variable you do not control.

Work it. A $60,000 wedding at 15% is a $9,000 fee. The couple's circumstances change and the budget becomes $38,000. **The fee falls to $5,700 — a loss of $3,300, 37% of your income from that engagement.**

And the work did not fall by 37%. It rose. A budget cut in month six means renegotiating vendors, rebuilding the budget, revisiting decisions already made, and managing two disappointed people — which is the hardest month of that engagement, and you have just been paid $3,300 less for it.

The fix: a floor, a defined base (percentage of what, agreed in writing), and a clause that the fee does not fall below the fee at contract.

A.5 A flat fee is a bet that you estimated the hours correctly — and the error distribution is asymmetrical. An event that goes well saves you perhaps 10–15 hours; an event that goes badly costs 60 or 100. The downside tail is far longer than the upside one, so pricing at your median hours guarantees a loss over a career.

Five things that make it survivable: price at the 75th percentile of your own tracked hours, not the median · a written exclusions list · an out-of-scope rate (which converts a refusal into a price) · scope defined by countable things, phases, or named deliverables rather than by "level of involvement" · and tracked hours from Chapter 30's reconciliation, without which none of the other four have any data to stand on.

A.7 🚪 You are not pricing the event; you are pricing your capacity.

Saturdays in a year                                    52
In the prime season — say May to October               26
Plus workable shoulder dates                       +8 = 34
Less holidays, family, illness, one per weekend    −6 = 28
Less your realistic delivery ceiling with quality    → 16
SELLABLE SATURDAYS                                     16

Required revenue (Ch.36)                         $80,850
÷ 16
MINIMUM VIABLE FEE PER SATURDAY                   $5,053

And the sentence that reorganises everything: a $1,700 coordination consumes a Saturday worth $5,053. It is not a small job at a small price — it is a $5,053 asset sold for $1,700, and no amount of it being easy work changes the arithmetic.

A.9 Because the Saturday is the scarce resource and the hour is not. Sixteen Saturdays are non-renewable; weekday hours are comparatively abundant — so weekday work is being sold from surplus and Saturday work from scarcity, and the two cannot be priced against the same rate.

Applied to Noor Haddadi: a Tuesday-to-Thursday corporate event at a day rate below her Saturday-equivalent is worth taking, because it consumes none of the sixteen. It fills the winter, it smooths the cash flow, it is paid on invoice rather than eleven months in advance, and it leaves every prime Saturday available. A planner who applies one rate to both will decline exactly the work that costs them nothing.

A.11 Couple A — both work ordinary hours and could have done much of it themselves. They are buying convenience. Couple B — both surgeons, time worth several hundred dollars an hour and none of it available. They are buying their own capacity back. Couple C — two families who do not agree, a religious requirement nobody understands, and a mother who has already made two people cry. They are buying a way through.

The same 150 hours. And you may only price against a value the client has stated out loud — which is what keeps this from being a licence to charge whatever a client looks like they can pay.

A.13 A tier boundary holds when a client and you could not disagree about whether something is included.

Four that hold: a count (six vendors) · a phase (we start at −6 months) · a named deliverable (a floor plan, a run sheet, a rehearsal) · and a named event day (we are there for the rehearsal and the wedding).

Four that do not: "level of involvement" · "more support" · "as needed" · "unlimited email." Every one will be moved by the client, not dishonestly but inevitably, and every inch of movement is unbilled.

A.15 The true hourly cost method: (fee − event costs − a share of fixed costs) ÷ all hours including pre-engagement.

"All hours" is where it bites — enquiry, consultation, the proposal you wrote before you were hired, travel, the evening calls, the debrief. Most planners find a number 40–60% below what they believed, and the reconstruction in Case Study 37.2 came out at $10.18 an hour on an engagement everybody involved considered a success.

A.17 Besides revenue: hours fall · the per-client overhead burden falls, because there are fewer clients · the effective hourly rate rises by the full percentage of the increase · and Saturdays come back, which is the one that has a life attached to it rather than a number.

A.19 Below your minimum viable fee on a Saturday (unless named as a deliberate exception) · a budget that cannot deliver what the client wants, from somebody who does not want to hear it · a client you already do not trust · and a date you cannot deliver properly — two weddings in a weekend, or work outside your competence.

The fifth, which is harder: an enquiry you want, at a price that does not work, from somebody you like.

A.21 Year 1–2: selling availability and effort; price set by the market's floor. Year 3–5: selling reliability; price set by cost plus a real margin — this is where the arithmetic starts working. Year 5–10: selling judgment; price set by value and by demand, because you are turning work down. Year 10+: selling scarcity, or running a business rather than a job.

The transition people miss is between phase two and phase three, and it is not about skill. It happens when you start declining work — and it cannot happen before, because a planner who takes everything has no pricing power by definition. You do not raise prices because you are busy; you become busy at a higher price because you raised them and declined the difference.

B.1 Rubric. Show every deduction, in this order and with your own numbers: Saturdays in a year · your market's prime season · workable shoulder dates · dates you will not work (holidays, family, illness, and one wedding per weekend) · your realistic delivery ceiling.

State the ceiling honestly, because it is where people flatter themselves. Sixteen full plannings is a hard year for a solo planner delivering at quality; twenty-two is a claim that requires evidence. Then: required revenue ÷ sellable Saturdays = minimum viable fee, and hold that number next to the last three fees you actually quoted.

B.3 Rubric, with the two rules that decide whether it works.

Boundaries must be countable, phased, or named deliverables. A worked shape from a $5,053 minimum:

The effective rate must rise as the tier falls. Every tier carries the same 12–18 hours of per-client overhead against fewer billable hours, so a coordination priced at the full-planning hourly rate loses money. A tier structure whose rates fall as the tiers fall is arithmetically upside-down and is the commonest error in published pricing.

And note the second consequence: every tier clears $5,053, because every tier consumes a Saturday. If your bottom tier cannot clear it, you do not have a bottom tier — you have a weekday product or a decision to make.

B.5 Exclusions for a partial-planning tier — eight, phrased so a client could not reasonably disagree.

What this package does not include, and which I'm happy to do at $95/hour or to quote separately:

1. Vendors beyond the six named in the agreement. Additional vendor searches, briefs, and management are out of scope. 2. Anything before the −6 month start date, including venue search and venue visits. 3. Design services — mood boards, styling concepts, colour direction, and physical décor sourcing. 4. Guest-list management, RSVP tracking, and dietary collection, which remain yours. (I will provide the templates.) 5. Accommodation, transport, and travel arrangements for you or your guests, including room blocks. 6. Any event other than the wedding day and its rehearsal — welcome drinks, rehearsal dinner, and next-day brunch are separately quoted. 7. Attendance at appointments beyond the four included consultations. 8. Stationery design, printing, addressing, and postage. 9. On-site presence beyond 12 hours on the wedding day, charged at $95/hour thereafter. 10. Re-planning following a date change or a venue change after contracts are signed.

Two properties. Every line is a countable, nameable thing — no line says "extensive" or "significant." And every exclusion has a price attached, which is what converts "that's not included" from a refusal into an offer. A planner with an out-of-scope rate can say yes to everything.

B.7 A 35% rise.

Loss tolerance = 1 − 1 ÷ 1.35 = 25.9%. You can lose a quarter of your clients and stand still.

Modelled at a 25% loss, from a base of 12 clients at $5,000, 135 hours each (120 delivery + 15 overhead):

Revenue up $750. Hours down 405 — ten working weeks. Effective rate up 35%. And three Saturdays back.

The three Saturdays are the finding. The revenue is a rounding error and the arithmetic is not really about revenue at all — it is that the same money can be earned in three-quarters of the time, and the difference is a life rather than a margin.

And the warning §37.10 attaches: this only happens if you decline the difference. A planner who raises fees and then quietly discounts for the three clients who push back has done the arithmetic and none of the act.

B.9 The full quoting sequence.

1. The consultation (45–60 minutes), in this order. What are you imagining? — let them talk, without pricing anything. Who is involved and who decides? (Ch.3). What have you booked already? What's the date, and is it fixed? And then, plainly: "have you thought about a budget for the wedding overall?" — asked once, without apology. You do not quote in this meeting.

2. The gap. 48 to 72 hours. Long enough to have thought, short enough to be keen. Its real function is that it converts the price from a reaction into a considered document.

3. The proposal's section order, and the order is the whole trick.

1  What you told me you want          ← their words, quoted back
2  What I understand the challenges to be  ← proves you listened
3  What I'll do — by phase, with deliverables
4  What's not included
5  THE FEE
6  How payment works
7  What happens next

The fee is on page four of seven and it arrives after the value, not before it. A proposal that opens with a number is a price list.

4. The number-lands script, for the moment they see it:

"The fee for that scope is eighty-four hundred, in three payments. I know that's a real number, so — take a few days with it. If it's more than you were expecting, tell me, because there's a version of this at a smaller scope that's genuinely good and I'd rather build you that than give you this one at a discount and have us both feel it in month four."**

Then stop talking. The silence after a number is the client thinking, and the planner who fills it discounts.

B.11 The four declines, each ending in a referral.

On price:

"I'd love to, and I don't think I'm the right fit at that number — and I'd rather say so than quote you something that works for neither of us. My full planning starts at eighty-four hundred. If that's not where you are, that's completely fine. Two people I'd recommend are Adaeze Ubuka and Ronan Petrosyan — Adaeze particularly, because she's brilliant with barn venues and she's cheaper than me. Tell her I sent you."**

On a budget that cannot deliver:

"Can I be straight, because it'll save us both time? A hundred and forty people, that venue, and the finish in those photographs is realistically thirty-five to forty-five thousand, and you've said twenty-two. That's not me saying it can't be done for twenty-two — it's me saying it can't be that, for twenty-two, and there are genuinely lovely versions of a twenty-two thousand dollar wedding. If you want to build that version, I'd talk to Ronan — he does more of it than I do and he's very good at it. And if you'd rather come back to me when you've decided, my door's open."

On a client you do not trust — and this one is short, because explanation invites negotiation:

"Thank you for thinking of me. Having talked it through, I don't think I'm the right planner for this one and I'd rather be honest early than six months in. I'd suggest Adaeze Ubuka or Kwabena Mensah — both are excellent. I hope it's a wonderful day."

On a date you cannot deliver:

"I'm already committed on the 14th and I won't take two weddings in a weekend — not because I'm precious about it, but because the second one gets a tired planner and that's not what you'd be paying for. Kwabena Mensah is free that weekend as far as I know and he's genuinely as good as anyone I'd recommend. Would you like me to introduce you?"**

Note the last line. An introduction you make is worth ten times a name you give, it costs one email, and it is the mechanism by which a job you did not take becomes a relationship.

B.13 What a friend discount actually costs.

Your fee is $6,000; you charge a friend $3,000.

In cash: $3,000. In capacity: one of sixteen Saturdays — 6.25% of your annual delivery.

And the version that makes it real: your required revenue is $80,850.** **If one Saturday returns $3,000 instead of $5,053, the other fifteen must produce $77,850 — $5,190 each, up from $5,053. The discount does not come out of profit; it is redistributed onto every other client you have, at $137 each.

Now the version that is clean, and it is not a smaller discount.

"I'd love to do this, and I want to do it properly, so let me say how. This is my present to you — the full service, and there's no invoice. I'm not doing a cheap version and I'm not doing a favour I'll resent in August.

What I'd ask in return is one thing: on the working questions, treat me as your planner rather than as your friend.* If I say I need final numbers by the 12th, I need them by the 12th — because the thing that wrecks these is not the money, it's that neither of us knows which relationship we're in."***

Why the gift is cleaner than the discount. A discount makes them a client with unclear obligations in both directions — they feel they cannot chase you, you feel you cannot chase them, and the resentment accrues to whoever is quieter. A gift is unambiguous, it is a real and generous thing, and it can be declined. And if you cannot afford to give it, the honest answer is the full fee and a different present — which is a sentence a real friend can hear.

B.15 Re-solving the four enquiries at a $3,200 minimum viable fee.

At $5,053, only C ($11,000) clears; A ($5,000) is marginally under, D ($4,200) is under, B ($2,800) is far under. At $3,200: A, C, and D all clear. B still does not.

Does the answer change? No. You still take C — and the reason is the exercise.

The minimum viable fee is a floor, not a ranking. It tells you what you cannot take; it never tells you what to take. With one Saturday and four bidders, the decision is always the highest value you can actually deliver, and $11,000 is more than double the next-best offer. A lower floor changes nothing about that comparison.

What does change is the character of the other three decisions. At $5,053, declining A and D is arithmetic** — they are below the floor and the conversation is closed. **At $3,200, both are viable engagements and declining them is an opportunity-cost choice, which is harder, feels worse, and must be made deliberately: "I'm turning down $4,200 from my best referrer's sister because the same Saturday is worth $11,000." That sentence has to be said out loud, and then acted on — with a real introduction to somebody good, and a note to the past client explaining that you found her sister a planner rather than that you were busy.

And the one thing that does not change at either floor: B. $2,800 fails both, and it is still the hardest refusal, because the venue relationship behind it is worth more than the fee. Which is why the answer to B is not a decline but a redirect: "I can't do the 12th — do you have anything in October? And can I take you for coffee anyway?"

C.1 Rubric. Report the range, how many of the six publish at all — usually two or three of six — and what is included at each level. The most useful finding is not the prices but the boundaries: count how many use countable, phased, or named-deliverable boundaries versus "level of involvement." The second group is the majority, and every one of them is quietly absorbing scope.

C.3 Rubric. Count the prime Saturdays honestly, then ask a working planner how many weddings they deliver. Expect the count to be 26–34 and the delivery to be 10–18 — and expect the planner's first answer to be a good year rather than a typical one. Ask what their busiest year was and what it cost them, and you will usually get Chapter 41's material three chapters early.

C.5 Rubric. Track every hour from the first enquiry, including the proposal written before you were hired, travel, and the ten-minute phone calls. Report the total against your estimate. The expected finding is 40–60% more hours than estimated, and the largest single omission is almost always the pre-contract hours, which most planners do not count as work at all.

C.7 Rubric. Two sources, and report the range. Expect wide dispersion and expect the two sources to disagree, usually because one is quoting a freelance day rate and the other an agency rate with overhead in it. Report which is which — and note that a corporate day rate is a weekday rate, which is why §37.5's second corollary makes it more valuable to a solo planner than the headline suggests.

D.2 Rubric. The Saturday argument does imply a coordination business is unviable at a $5,053 minimum, and the case for one anyway is real.

The strongest version: coordination need not consume a prime Saturday every time — mid-week, Friday, and Sunday events are a growing share and are exactly where coordination sells · the required revenue is not fixed, and a planner with lower fixed costs or another income has a lower floor · volume produces judgment faster than any other route, and day-of judgment is the least purchasable skill in the profession · the cash cycle is enormously better (Ch.36) · and the arithmetic assumes solo delivery — a coordination business is the one service level that genuinely scales with trained associates, because the deliverable is standardised.

That last point is the strongest and the chapter under-weights it. Full planning is hard to delegate because it is a relationship; coordination is a documented procedure, which is precisely what can be handed to somebody else. The defensible conclusion: coordination is unviable as a solo Saturday business and is the most viable of the three as a business with employees.

D.3 Rubric. State the unfairness properly: charging couple C $11,000 and couple A $6,000 for identical work means the price is set by what the planner believes the buyer can bear. In a domestic, emotional, once-in-a-lifetime purchase, that is closer to exploitation than to pricing.

Then answer it, and the answer has three parts and one concession. The work is not identical — C's engagement contains research, family mediation, and risk that A's does not, and pricing the difficulty is not pricing the buyer. The chapter's own constraint does real work: you may only price against a value the client has stated out loud — which excludes pricing from the postcode, the car, or the venue. And there is no "true" price to deviate from; cost sets a floor and every price above it is a judgment.

The concession that a strong answer must make: those three defences do not cover the pure case — couple B, the surgeons, buying identical work at a higher price purely because their time is worth more. That is value pricing with nothing else attached, and the honest defence is that it is normal in professional services and that the alternative — one price for everyone — means A subsidises B. Say that plainly rather than pretending the case does not exist.

D.5 Rubric. The assumption that clients are interchangeable is the arithmetic's weak point, and the attack is straightforward: the 23% you lose are not a random 23%.

You lose the most price-sensitive, which correlates with smaller budgets, which correlates with simpler events and — often — with more decisive couples. You may be losing your easiest work and keeping your hardest at a 30% premium. You also lose the ones who were referred by the venues that serve that price point, which damages a referral channel rather than a client. And you lose them unevenly across the calendar — the cheap dates go first, so the losses concentrate in the shoulder season you were relying on.

What survives: the arithmetic is a sufficiency test, not a forecast — it tells you that a 30% rise does not require you to keep everybody, which is the thing planners get wrong. What it cannot tell you is which clients leave, and the honest use of it is as a floor on courage rather than as a model of your business.

D.7 Rubric — it is neither, and the answer is that it is cheap and it compounds.

What it costs: almost nothing. You have already declined the work, so the referral gives away nothing you had. The only real cost is reputational risk — if the person you refer is bad, that reflects on you — which is an argument for referring carefully, not for not referring.

What it actually buys, in ascending order: the client remembers you as the person who helped rather than the person who was too expensive, and they will say so to others · the planner you referred to owes you one, and reciprocates, which is the mechanism by which most planners fill their diaries · the venue or vendor who sent you the enquiry sees that the enquiry was handled, which is the thing that keeps referrals coming · and it is the cheapest possible marketing at a CPA of approximately zero (Ch.38).

The naive version is real and worth naming: referring to somebody who will undercut you into your own venue relationships is not generosity, it is a transfer. The discipline is to refer to people who are genuinely good and genuinely different from you — a different price point, a different specialism, a different diary. Done that way it is a network; done carelessly it is training your replacement.

M.1 Chapter 2 defined the service levels descriptively — what each includes and what the client has already done. This chapter makes them a pricing decision and gives them an arithmetic: hours per event × required rate against what the market pays.

The counter-intuitive finding that belongs to both: "month-of" coordination is the hardest level to make work, not the easiest. Chapter 2 said "day-of" is never day-of — it is 35–60 hours of reading contracts, rebuilding a timeline, and confirming vendors somebody else chose. This chapter adds why that matters commercially: it consumes a full Saturday, carries the same per-client overhead as a full planning, and sells for a third of the price. The entry-level product is the one whose economics are worst.

M.3 The hour: required revenue ÷ billable hours = $68.25.** **The Saturday: required revenue ÷ sellable Saturdays = $5,053. A fee must clear both, and they fail differently.

A fee that satisfies the hour and fails the Saturday: a $2,400 coordination taking 32 hours.** That is **$75 an hour — above the hourly floor — and it consumes a $5,053 Saturday. It looks profitable on a timesheet and is a loss against capacity.

And the reverse: a $9,000 full planning taking 220 hours** clears the Saturday comfortably at $9,000 and returns $40.91 an hour, less than two-thirds of the hourly floor. It looks like the best job of the year and is being subsidised by your evenings.**

M.5 Because a corporate day rate prices a unit of your availability rather than a unit of your output — you are selling a day, whatever happens in it, exactly as a Saturday fee sells a Saturday.

It is capacity pricing with the calendar unit changed, and the two useful consequences follow directly: the rate must clear a floor derived from required revenue divided by sellable days, and days that do not compete with Saturdays are worth taking at a lower effective rate because they consume no scarce inventory. Which is why a $1,600 Tuesday is a better piece of business for a solo planner than a $2,800 Saturday, and why almost nobody prices it that way.

M.7 The reconciliation — specifically its fourth column, what it should have been.

Flat-fee pricing is a bet on your own hours estimate, and an estimate improves only by being compared with the outcome, in writing, repeatedly. The reconciliation is the only instrument in this book that produces that comparison — and without it, the instruction to "price at the 75th percentile of your tracked hours" is unusable, because there are no tracked hours.

Which produces the ordering: the debrief is a pricing tool. A planner who has run four seasons of reconciliations can price a flat fee with confidence; one who has not is pricing from memory, and memory systematically under-counts the events that went badly.

M.9 The client you already do not trust — and Chapter 3 says to decline at the enquiry stage, before anything is written and before a proposal exists.

The reason is that it never improves. Chapter 3's material on the family system, the decision-maker who is not in the room, and the client who is unpleasant to a vendor on the first call — all of it is diagnostic, all of it is visible in the first conversation, and all of it gets worse under pressure. The cost of declining at enquiry is one email. The cost of declining in month seven is a refund, a reputation conversation, and a Saturday you can no longer sell.

E.1 Rubric. The system must contain all six components and they must be arithmetically connected — the tiers must derive from the Saturday number, the out-of-scope rate must relate to the hourly floor, and the travel policy must state a boundary in miles or hours rather than in judgment.

When a working planner critiques it, expect three things: "your bottom tier is too cheap" (usually right) · "you'll never get that in this market" (sometimes right, and worth testing against C.1's published data rather than accepting) · and "what happens when they ask for a discount?" — which is the question the system must answer in advance, because the answer improvised in the meeting is always yes.

E.3 Rubric. Engage with D.3 seriously, which means stating the objection at its strongest and conceding the part that is true.

The essay's territory: emotional investment raises willingness to pay, and a pricing model that harvests that is charging more precisely because the purchase matters. In a wedding, "what it's worth to you" is not an economic quantity — it is a family, a mother, a promise.

The strongest defensible position is a bounded one. Value pricing is defensible when the value being priced is difficulty, risk, or scope that you can name — couple C's two families and religious requirement — and much harder to defend when the only variable is the client's wealth. The chapter's constraint that you may only price against a value the client has stated out loud is the practical version of that line, and it is doing more work than its single sentence suggests.

And what you would say to a client who asked directly, which is the test: "Yes — my fee varies, and it varies with what the engagement involves rather than with what I think you can afford. Yours is higher than my base because of the two-venue arrangement and the number of families involved, and I'll show you the hours if you want them." If you cannot say your answer out loud to the client, that is the finding.

E.5 Rubric. Thirty minutes, annually, in the same month every year — the month matters more than the content, because a review scheduled for "when things are quiet" happens in no year.

1  COSTS        Fixed costs this year vs last. Insurance,
                accountant, tools, travel, assistant rates.
                → New required revenue

2  SATURDAYS    Sellable Saturdays, recomputed honestly.
                Delivered last year: ___ of ___
                → New minimum viable fee

3  TRUE HOURLY  Three real events, all hours, including
                pre-contract.  $___ /hr, $___ /hr, $___ /hr
                → Which tier is losing money?

4  MARKET       Six competitors' published prices, if any.
                Where do I sit, and is that where I intend to?

5  THE DECISION Fees for next year: [ ] hold  [ ] raise __%
                Loss tolerance at that rise: ____%
                → and what I will DECLINE to make it real

Line 5's second half is the whole instrument. A pricing review that raises the number and does not name the work being declined has changed a document, not a business — which is §37.10's argument, in a box, once a year.

Chapter 38 — Marketing and Getting Your First Clients

A.1 🚪 You are not marketing to couples. You are marketing to the people who get asked the question.

A recommender outweighs a client because of frequency. A couple hires a planner roughly once in their life. A venue coordinator recommends one thirty times a year, a photographer perhaps twenty, a caterer more. One relationship is worth thirty transactions, it renews annually, and it costs a conversation.

A.3

$29,400 for six hours — and the six hours are not sales calls. They are doing your job well in front of somebody who is watching, which you were doing anyway. The marketing activity is the work.

A.5 Do the work well in front of them · make their job easier · send them photographs of their own venue · refer work to them · ask once, directly · and stay visible.

Doing the work well in front of them is about 70% of it and has no substitute. Delphine's four reasons contain no reference to taste, portfolio, or design — they are "she sends me the run sheet on the Wednesday," "he finished a load-out at half eleven," "she rang me in February to ask what catches planners out," and "he sent me forty photographs of the orangery." Seventeen planners have emailed asking to be added and none is on the list, because an email contains no information about whether you are any good.

A.7 Because a referral given is costless to you and valuable to them, and a referral asked for is the reverse.

The asymmetry: you give away an enquiry you were not going to take — wrong date, wrong price, wrong fit — and the recipient receives a real, warm, converting lead. You have transferred something of genuine value at approximately zero cost, and the obligation created is real. Asked-for referrals invert it: you receive the value and the other party carries the cost, including the reputational risk of vouching for you.

Which produces the chapter's least intuitive claim: your competitors are the second-best referral source in this industry, and the mechanism is that you go first.

A.9 Because a tablescape is a florist's work and a stylist's work, and it demonstrates aesthetic taste — which is not what a planner is hired for. A portfolio of beautiful rooms competes on the one axis where a planner adds least and where every competitor looks identical.

The caption that works describes a decision:

"The ceremony was moved indoors at one o'clock on a decision deadline set six weeks earlier. Ninety-eight guests, and the couple found out by text while they were getting ready. The dancing started on time."

What it sells: judgment under pressure, preparation, and calm — the three things a couple actually needs and cannot see in a photograph. It is also the only kind of caption a venue coordinator screenshots.

A.11 For publishing: it filters, it saves the nine hours §37.9 describes, it signals confidence, and couples overwhelmingly say they want it. Against: it invites comparison on the one axis where you are least differentiated, it prevents value-based pricing (§37.5a), and it is quoted back to you eighteen months later.

The chapter's position: a starting-from figure, not a price list. "Full planning from $8,400; coordination from $3,600." It filters at the top of the funnel — which is where the saving is — without pricing an engagement you have not scoped, and it can be said in an email in one line, which is where most of the work happens anyway.

A.13 Roughly none. Of a new planner's first ten clients, social media typically produces zero to one.

Which makes it a credibility channel, not an acquisition channel. Its job is to be there when a referred couple looks you up, and to be screenshottable by a coordinator — not to generate enquiries. Which means it should be capped rather than optimised: a post that four hundred planners like has performed, and a post that one coordinator screenshots has converted, and only the second one matters.

A.15 CPA = (cash spent + hours × your rate) ÷ bookings produced. The hours are the whole method — a channel that costs no money and forty hours a month is not free.

Most expensive: Instagram — and it is also the one that appears free, because its cost is entirely in hours nobody counts. Cheapest: past-client referrals, and they are the only channel that improves with time.

A.17 1. Reply within hours. 2. Qualify before you meet — three lines. 3. A 20–30 minute discovery call. 4. The consultation. 5. A gap of one to three days. 6. The proposal, fee last. 7. A follow-up conversation, not an email. 8. One follow-up if you hear nothing, then stop.

Step 2 is the highest-value item. Three lines establishing date, scale, and service end roughly a third of enquiries before anybody spends an hour — which saves the nine hours Chapter 37 costs out, and does it in ninety seconds.

A.19 Specificity. "Amazing, couldn't have done it without her" travels nowhere; it is what every review says. A review that contains a thing that happened travels, because it can be repeated by the person who read it.

And you can ask for it:

"If you're happy to write something, the most useful thing you could do is mention one specific thing that happened. People read a lot of reviews that say lovely things and they all sound the same — the ones that help are the ones with a detail in them. Anything at all, even something small."

B.1 Rubric. The map is a table, not a list, and it must have a named person and a next specific action in every row:

VENUE / VENDOR      THE PERSON WHO GETS ASKED       NEXT ACTION
Wildrye Farm        Sara Beaumont (events)          Ask what catches
                    ★ and the Saturday contact      planners out — call
Marbury Hall        Delphine Mbeki                  Send the 40 orangery
                                                    photographs
Sundown Provisions  Marguerite Osei                 Coffee. Nothing else
[photographer]      [name]                          Second-shoot day?
[busier planner]    [name]                          Offer to assist, paid

Two things make it work. A named person, not an enquiries address — C.1 exists because finding out who actually gets asked is harder than it sounds and is most of the value. And an action that is not a request: "is there anything about the site that catches planners out?" is a question that gives something (attention, and the implication that they know things), where "could you add me to your list?" asks before offering and is what the seventeen unsuccessful emails all did.

B.3 Six months of touches for one venue relationship — none of them a request.

Total time: under two hours across six months. And the request — "if a couple ever asks, I'd love to be one of the names" — is made once, directly, at month six, when it is a formality rather than an ask.

B.5 A one-page website that answers the four questions.

First screen copy:

Noor Haddadi

Wedding planning for raw sites — fields, barns, farms, and private land.

If your venue has no kitchen, no power, and no loo, that is my job.

I plan and run about a dozen weddings a year within ninety minutes of [city]. Full planning from $8,400**; coordination from **$3,600.

[ Check my dates ]

It answers the four questions in the first six lines: what do you do · for whom · roughly what does it cost · and how do I start.

The five form fields — and five is the maximum:

Name
Email
Date (or "not fixed yet")
Venue, or "still looking"
Roughly how many guests?

No message box, no phone number, no budget dropdown, no "how did you hear about us" dropdown. (The attribution question is asked by a human on the call — a dropdown gets "Google" from everybody.) Every additional field costs completions, and the qualifying happens in the reply, which is step 2 and takes ninety seconds.

B.7 A qualifying reply — 134 words.

Hi Priyanka — thanks for getting in touch, and congratulations. The 14th of September is free at the moment.**

Before we set up a call, three quick things so I can be useful:

Roughly how many guests are you expecting?

Have you chosen a venue, or is that part of what you'd want help with?

And are you thinking about full planning — where I'd be involved from now — or coordination in the last couple of months?* Full planning starts at $8,400 and coordination at $3,600, so knowing which will help me point you at the right thing* rather than sending you a proposal for something you didn't want.

No rush at all — whenever suits.

Noor

The four things: confirms availability (what they actually asked) · qualifies on scale and service · states price early without a price list · and is warm, which matters more than the other three combined.

B.9 The follow-up call, naming the three objections.

"I wanted to check the proposal made sense — and honestly, to give you the chance to ask me the awkward question rather than emailing it.**

In my experience it's usually one of three things: it's more than you wanted to spend, or you're not sure you need that much help, or you're weighing me up against somebody else. Any of those?"

Then the three answers:

"It's more than we wanted to spend." — "That's completely fair. Let me tell you what I'd do rather than discount it, because a discount just means I'd give you less and call it the same thing. The partial package is $6,200 and starts at six months — it covers the six vendors that matter most and you'd do the rest. That's a genuinely good service, not a lesser one. Would that be closer?"

"We're not sure we need that much help." — "Possibly not! Tell me what you've already got booked. [Listen.] Honestly, from that — you've done the hard part and I'd say coordination rather than full planning. That's $3,600 and it starts eight weeks out. I'd rather sell you the right thing and be there in ten years than sell you the big one now."

"We're talking to somebody else." — "Good — you should be. Can I ask who? [If good:] Adaeze's excellent, genuinely. The difference is probably that I do more raw-site work and she's stronger on hotels, so it may come down to your venue. Whatever you decide, I'd be glad to know — and if it's her, I'll be pleased for you."

All three do the same thing: they answer without defending and without discounting, and two of them offer a smaller version. The follow-up's purpose is to find the objection, not to close — a planner who hears the objection has a business decision to make, and one who hears silence has nothing.

B.11 200 non-billable hours and $2,500.

Dropped entirely: the wedding fair stand ($1,773 CPA), the directory listing ($2,004), and paid search ($1,808).** **Together they would consume the entire $2,500 and most of the hours, and they are the three most expensive channels in the table.

And the honest note: this allocation is only defensible because the CPA table was computed. A planner who has not computed theirs is allocating on the same intuitions that produce the $4,080 number.

B.13 The two messages.

To the competitor:

Hi Adaeze — I've got an enquiry I can't take and I think it's a good one for you.

Priyanka and Tom, 14 September, 110 guests at Marbury Hall, full planning, budget's realistic and they've said $7,000 for planning.* They seem lovely and decisive on the phone. I can't do it — I'm already committed that weekend and I won't run two.***

I've told them I'd introduce you and that I rate you. Want me to connect you, or would you rather email her yourself? Her address is below either way.

Noor

To the enquiry:

Hi Priyanka,

I'm afraid I can't take the 14th — I'm already committed that weekend, and I don't run two weddings in a weekend because the second one gets a tired planner and that isn't what you'd be paying for. I'm sorry; I'd have liked this one.

What I can do is introduce you to somebody I'd genuinely recommend.* Adaeze Ubuka has worked at Marbury a lot and is very good — I've told her about you and she's expecting to hear from me. Would you like me to put you two together?***

And if the date ever moves, do come back to me.

Noor

Note that the referral is an introduction rather than a name. A name is a search result; an introduction is a warm lead, and the difference is one email. It is also the whole mechanism of §38.2a: Adaeze now owes you one, and the next enquiry she cannot take has somewhere to go.

B.15 The consultation hour, block by block.

0–5    Warmth. Nothing operational. Ask about the proposal —
       theirs, not yours
5–20   THEIR DAY. Open question, then listen. Do not price
       anything, do not solve anything, write everything down
20–35  THE FACTS: date, venue, numbers, what's booked, who is
       involved, who decides (Ch.3), what has already been
       difficult
35–45  ★ THE ONE SPECIFIC OBSERVATION
45–55  How I work, what the levels are, what happens next.
       Exclusions mentioned, warmly
55–60  The gap: "I'll send something in a couple of days"
       — NEVER a number in the room

The 35–45 block is the whole consultation, and it must contain one specific, non-obvious, correct observation about their event. For example:

"Can I flag one thing while it's cheap to change? You've got the ceremony at four and dinner at six-thirty, and the walk from the meadow back to the barn is about two hundred metres on grass. That's fine for most people and it's about ten minutes with a hundred guests. But you mentioned your grandmother's coming, and there'll be others — so somewhere in there we need either a car doing runs from the gate or a different route. It costs nothing if we plan it now and it's the single most common thing that goes wrong at a field wedding."

Why it is the whole consultation. It demonstrates competence rather than claiming it — Chapter 37's credence-good problem, solved for sixty seconds. It is about their wedding, not your portfolio. It gives them something usable whether or not they hire you, which is the most persuasive thing available. And it is the sentence they repeat to each other in the car, which is where the decision is actually made.

C.1 Rubric. Report the three names and — the instructive half — how you found out. The usual answer is that you cannot find it on the website, and the methods that work are: ring and ask "who looks after weddings here?" · ask a photographer or caterer who works there · or go to an open day and notice who the couples are talking to.

The finding worth reporting: at a large venue the person who gets asked is often not the sales manager but the coordinator or the operations person, because the question "do you know a good planner?" is asked at month eight, not at booking. Marketing to the wrong person at the right venue is one of the commonest wasted efforts in this chapter.

C.3 Rubric. The same three questions to a photographer and a caterer, and compare rather than average.

The predictable difference: a venue coordinator recommends to protect the venue's experience; a photographer recommends to protect their own day — a bad planner costs them light and family photographs — and a caterer recommends to protect their service times. All three are asked frequently and all three want different things from you, which means the thing that gets you onto each list is different. Report which of your behaviours matters to which of them.

C.5 Rubric. Price both for real, then ask two planners who used each what it produced — and ask for the number of bookings, not the number of enquiries, because a fair produces many of the first and almost none of the second.

Expect: a stand at $600–2,500 and a directory listing at $500–3,000 a year, and expect the planners to report one booking, none, or "it's about the visibility." Compute the CPA with their time included and put it next to $278. The exercise is not to prove these channels never work — for some planners in some markets they do — but to establish that the comparison is available and almost nobody makes it.

C.7 Rubric. Twenty reviews, and count how many contain a specific thing that happened — a decision, an hour, an event, a name. The usual ratio is two or three of twenty. The other seventeen are interchangeable and could be moved between planners without anybody noticing, which is the point: they are evidence of satisfaction and not evidence of competence, and a couple reading them learns nothing that distinguishes one planner from another. That is the credence-good problem in a review column.

D.2 Rubric. The case against the chapter's dismissiveness is real and should be built properly.

Social media demonstrably works for some planners, and the pattern is identifiable rather than lucky: those whose work is genuinely visual and distinctive (a designer as much as a planner) · those in destination markets, where the buyer is not local and cannot be reached through venue relationships at all · those who built an audience before the business and converted it · and those in markets where couples do search rather than ask.

And a second, stronger argument: the CPA table measures acquisition and social media's return is largely in conversion. A referred couple who looks you up and finds nothing is a lost booking that will be attributed to the referral channel, not to the absence of the feed. The table cannot see that, and it is a real effect.

What survives of the chapter's position: for a new, local, relationship-market planner, it is not an acquisition channel and the hours are better spent elsewhere. A strong answer states the conditions under which the chapter is wrong rather than simply asserting that it is.

D.4 Rubric. In a genuinely small market with a fixed amount of work, referring out is a direct transfer to a competitor and the naivety objection has force. The reciprocity argument requires the other party to reciprocate, and in a two-planner town there may be no norm of reciprocation at all.

What survives, and it is enough: you are referring work you cannot take — a date you are committed on, a price below your floor, a fit you have judged wrong. That work was never yours, so the transfer is of something you did not have. The alternative is not keeping it; the alternative is the enquiry going to a search result, which produces no obligation at all.

Where the objection genuinely bites, and a strong answer concedes it: referring work you could have taken at a lower price, in a market where volume is scarce, is a real cost — and the chapter does not distinguish carefully enough between cannot take and chose not to take. Decide on that line: refer everything you cannot take, refer selectively what you chose not to take, and know which one you are doing.

D.6 Rubric. The line is between reporting work that occurred and arranging for work to be visible.

A case clearly on the right side: the ceremony moved indoors at 1:00 on a decision deadline set six weeks earlier; the planner describes it afterwards, factually, in a caption. The work happened, the visibility is retrospective, and nothing about the event was shaped by the telling.

A case clearly on the wrong side: a planner who delays telling the couple about a solved problem so that it can be solved in front of them; or who leaves a small thing unfixed until the client is in the room. This is not hypothetical and it is more common than the industry admits.

The line, stated usefully: if the decision about when something happens is affected by who is watching, you have crossed it. And the boundary case worth arguing — telling the couple during the day about a problem you have already solved — is on the wrong side, because Chapter 27's fourth clause says problems are reported afterwards, and a planner reporting one in the moment has chosen visibility over the client's day.

D.8 Rubric. Chapter 37's claim is that the market cannot distinguish competent from excellent — a credence good. This chapter offers four partial fixes, and each should be evaluated on whether it actually transmits information to a buyer who cannot evaluate it.

Captions that describe decisions — partially works. It converts an invisible judgment into a legible artefact. Its limit: a caption can be written by somebody who did none of it, and the buyer cannot verify it. Naming the work at the debrief — works, and it is the strongest of the four, because it reaches the couple with the evidence in front of them, and because they will repeat it. A niche — works indirectly. It does not demonstrate excellence; it narrows the comparison set so that "competent at raw sites" is a more informative claim than "excellent at weddings." Specific reviews — works partially, and it is the only one that transmits to strangers, which is its whole advantage; its limit is that specificity can be manufactured.

The honest verdict: none closes the gap and two of them (captions, reviews) are forgeable, which is exactly why they do not close it — in a credence market, any signal that can be imitated cheaply will be. The only signal that is expensive to fake is the one Delphine uses: watching somebody work. Which is why §38.2's 70% is 70%, and why the chapter's marketing advice keeps collapsing back into doing the job well in front of people.

M.1 They are the same activity because the people you manage are the people who recommend you. Chapter 12's vendor management — clear briefs, final numbers on time, paying promptly, a vendor meal, not blaming anybody on the day — is, from the vendor's side, indistinguishable from marketing. Delphine's four reasons are all Chapter 12 behaviours.

The uncomfortable corollary: everything you do badly is also marketing. A late final number, a load-out that overran, a brief that had to be chased — those travel exactly as far as the good version does, through the same people, with your name on them. And they travel further, because a complaint is more repeatable than a compliment.

M.3 Chapter 36 ranked the first ten clients: people who already know you, then vendor and venue referrals, then past clients, then approximately nothing. This chapter adds the mechanism and corrects the emphasis.

The correction: Chapter 36's "four to six from people who already know you" is a description of who can start this business easily, and it quietly disadvantages anybody whose network does not contain people getting married expensively. This chapter says so out loud and gives the four ways in for everybody else — work for somebody else first, be the paid second planner, enter through a community you belong to, or enter through a competence most planners lack — and states that advertising your way in is not one of them.

M.5 A niche does not make excellence visible; it narrows the field within which the buyer is comparing.

"She's excellent" is uncheckable. "She's the one who does raw sites" is checkable and is repeatable by a stranger — which is the test §36.7 sets. The niche substitutes a verifiable claim for an unverifiable one, and it gives the recommender a sentence they can say without staking their own credibility on your quality. Delphine can say "she does field weddings" to a couple with a field, and that costs her nothing if she is wrong. That is why niches propagate through referrers and general excellence does not.

M.7 It protects Chapter 27's fourth clause: problems are reported afterwards, not during.

The visibility problem creates a standing temptation to let the client see the save — and the moment that temptation shapes timing, the couple's day is being spent on the planner's marketing. Putting visibility at the debrief resolves it structurally: there is a designated place where the work is named, it is after the event, and it is factual. The planner gets the credit and the couple gets the day, and nothing about the wedding is arranged around who is watching.

M.9 It has appeared at least twice, in the same shape.

Chapter 35, most sharply: effort concentrated on materials and waste — under 5% of an event's footprint — while travel, at 50–90%, is barely discussed. And Chapter 29's notice ranking: budget concentrated on the bottom row (linen, arrangements, palette consistency) while the top row — being fed, hearing, sitting, being spoken to — is where every guest's experience is decided.

The general form: effort follows legibility rather than magnitude. The 27% is optimised because it is visible, countable, and feels like work; the 73% is ignored because it was decided elsewhere, by somebody else, before anybody was paying attention. Which is also, exactly, why this chapter's first instruction is to compute a CPA table before allocating a single hour.

E.1 Rubric. The plan must contain all seven components and the allocation must follow from the CPA table rather than from preference — the commonest failure is a beautifully-argued plan that still gives social media forty hours a month.

Then show it to a venue coordinator, which is the exercise. Expect: "nobody has ever shown me one of these" · a correction about who at their venue actually gets asked · and — most valuably — a specific, small, unglamorous thing you could do that is not on your plan, usually about run sheets, timings, or the load-out. Add it, and note that it took eleven minutes to obtain and would not have appeared from any amount of desk work.

E.3 Rubric. Use Chapter 37's credence-good framing: the buyer cannot evaluate the service before purchase, cannot fully evaluate it afterwards (they have no counterfactual — they do not know what would have gone wrong), and buys roughly once, so there is no learning. That is a market in which marketing claims are, structurally, unverifiable.

The ethical consequence, and the essay should reach it: in a credence market the usual defence — "the market will punish false claims" — does not operate, so the constraint has to be internal.

A defensible position about which claims are defensible: claims about what you will do (a scope, a schedule, an availability) — verifiable, and therefore fair game. Claims about what you have done — "I have run forty weddings" — verifiable in principle and fair. Claims about outcomes you controlled — "the dancing started on time" — fair, and this is where the caption strategy sits. Claims about relative quality — "the best planner in the city" — unverifiable by the buyer and unfalsifiable by anybody, and therefore not defensible even if you believe it. And claims about counterfactuals — "I saved that wedding" — the most tempting and least defensible of all, because the buyer has no way to check and the planner has an obvious interest.

The essay is strongest if it ends where §38.9 does: the honest response to an unverifiable market is not better claims but more expensive signals — doing the work in front of people who will vouch for you, which cannot be faked cheaply.

E.5 Rubric. Ten minutes a week, and it must survive a busy September — which is the real design constraint and the reason most attribution systems fail in their first season.

ONE SPREADSHEET, ONE ROW PER ENQUIRY
  date · name · date of event · source ("how did you find me?")
  · WHO MENTIONED MY NAME · status · fee if booked

TWO QUESTIONS, ASKED BY A HUMAN, ON THE FIRST CALL
  "How did you come across me?"
  "Do you remember who mentioned my name?"     ← the second one
                                                 is the valuable one

WEEKLY, 10 MINUTES, SAME SLOT
  Update statuses. Send the one follow-up that is due.
  Thank anybody who referred somebody — that week, not later.

Why it survives September: it is one file, the questions are asked in a conversation that is already happening, and the weekly slot is ten minutes with a hard stop. A CRM will not survive September; a spreadsheet with seven columns will.

And the single highest-value field is who mentioned my name — because it converts an anonymous channel ("word of mouth," which is what most planners record) into a named person you can thank, and thanking a referrer that week is the entire maintenance cost of the $278 channel.

Chapter 39 — Technology and Systems

A.1 🚪 A system is not software. It is the mechanism by which a finding becomes a change.

Five reasons a written finding produces no change: found and fixed are the same column — the log records that you noticed and nothing more · the change lands in the wrong artefact, so a run-sheet finding is written into a debrief document nobody opens · the artefact is not opened before the next event — a brilliant template attached to intention rather than to a trigger · it is filed under the wrong heading, and cannot be found by the person who needs it · and there are too many, which is the one nobody admits and is why §39.11 is a ranking rather than a to-do list.

A.3 Artefacts · triggers · conventions · a closing loop.

None of them is software. Software is a delivery mechanism for the four, not a fifth component — and a platform bought without them is an empty container with a subscription, which is why Chapter 36 said buy it fourth.

A.5 A trigger is a moment at which a document must be opened. Intention is not a trigger: "I'll check the insurance certificates nearer the time" is a hope. "−8 weeks" as a recurring dated task attached to every event, appearing without being remembered, is a trigger.

The threshold trigger is where Chapter 5's master variable actually gets managed — because a guest count drifting from 100 to 118 across nine months triggers nothing, and it changes the catering, the floor plan, the seating, the transport, and the guarantee.

A.7 Six of the ten:

−12 months — venue file opened; save-the-date carrying the access text (Ch.29). −9 months — category D vendor check (Ch.28); permissions: granted to whom, and extendable? −6 months — the access asking, sent by a family member (Ch.29); rain plan drafted. −8 weeks — decision protocol agreed (Ch.27); insurance certificates checked against dates (Ch.9). −72 hours — emergency page distributed; weather review, all four kinds. +12 months — the query nobody runs (Ch.32).

Ten triggers, applied from a template at signing, take about four minutes per event — and every row is a finding from an earlier chapter that would otherwise depend on somebody remembering.

A.9 1. What are the three things I do most, and does it do them faster? 2. What does it force me to do differently, and is that better? 3. What happens to my data if I leave? 4. Does the client-facing part improve their experience or mine? 5. What does it not do that I will therefore stop doing? 6. Can I run one real event in it, in parallel, before deciding?

Question 5 matters most, and nobody asks it. A tool silently subtracts from your practice: a platform with no floor-plan capability means you will stop drawing floor plans — and Chapter 11 established what that costs, in 36-inch gaps that are invisible on a screen and are walls in a room. Every other question is about what the tool adds; only the fifth is about what it removes, and removal is the effect that arrives quietly and permanently.

A.11 Four conventions: one place (every document for an event in one folder tree) · date first, version last (2026-03-14_runsheet_v4) · an archive folder for every superseded version · and the same tree for every event, forever.

2026-09-12_Reyes-Whitfield/
  01_client/      contract, proposal, correspondence log
  02_budget/      budget sheet, invoices, reconciliation
  03_vendors/     contracts, briefs, contact sheet
  04_venue/       site notes, drawings, photographs, permissions
  05_planning/    timeline, run sheet, guest list, floor plans
  06_day/         production book, emergency page, assignments
  07_after/       finding log, debrief, wrap-up, photographs
  _archive/       every superseded version

Ten minutes to define, and worth more than any software decision — because the tree survives changing platforms and the platform does not survive changing your mind.

A.13 A correspondence log is a dated, one-line-per-entry record of every substantive exchange with a client — what was discussed, what was agreed, and when.

Three things it is for. Answering "what did we decide about the flowers in March?" without searching four hundred emails. Establishing a factual record if anything is ever disputed, which is a Chapter 8 matter and is worth its whole existence once. And — the one nobody expects — showing a client the shape of their own engagement, because the Reyes–Whitfield log ran to about forty entries and "we've had forty conversations about this wedding" is a fact that reframes a fee.

A.15 A venue file contains: access · power · capacities, with the unit written next to every number · people, including the Saturday contact who is not the office · rules · drawings, with known errors flagged · and — the section nobody writes — what goes wrong here.

It closes Chapter 34's finding directly: the questions a production manager asks that a planner does not — how does a truck get out, what shares the distribution board, who has a key on Sunday. Those answers are obtained once, at a cost of one site visit and a few conversations, and they are then permanent. The Wildrye file exists because the same venue was worked twice and nothing from the first time had been written down.

A.17 Found · artefact · owner · due · closed.

The second field is load-bearing. The artefact is what converts a feeling into a change: "be more careful with capacities" cannot be closed, and "add the unit to every capacity line in the venue file template" can. A log without the artefact column is a diary — ninety-one entries and four changes — and a log of unclosed findings is worse than no log at all, because it documents that you knew.

A.19 A system should absorb everything repeatable, everything that depends on somebody remembering, and everything whose failure is expensive and whose prevention is cheap.

What it cannot absorb: judgment, relationships, and the decisions of the day. No system decides whether to move a ceremony indoors at one o'clock, whether Rosa should be walked to her car, or what to say to a mother at 9:40 p.m.

The ranked list of what to systematise: triggers first (highest return, four minutes per event) · then document conventions and the folder tree · then the template library · then the venue files · then the finding log and closing loop · then the client-facing sequence · and last, and only then, a platform. The order is by return per hour invested, and it is almost exactly the reverse of the order most planners buy things in.

A.21 The automation test: a tool may draft anything and decide nothing.

May draft: proposals and contracts from a template and a dataset · vendor briefs · timelines from a structure · guest information · a summary of your own notes · a guest list reformatted into a seating chart into a caterer's format · payment reminders.

May not decide: anything client-facing that should be a person — Chapter 32's forty-second board-member call, Chapter 30's Monday message, a condolence. An automated version of any of those is worse than nothing, because it signals that the moment was processed rather than noticed. And nothing about safety, money above your authority, or a person.

B.1 Rubric. Convert each entry to found · artefact · owner · due · closed, and name the artefact for every one.

The instructive part is the last instruction: note which entries cannot be assigned an artefact. Expect between a fifth and a third, and expect them to look like "I was slow to make decisions in the afternoon" or "I should have been firmer with the mother of the bride."

Those are real findings and they are not systems findings. The correct handling is to say so explicitly rather than to invent an artefact — a fake artefact ("add 'be firmer' to the run sheet") is worse than an honest note, because it will never be closed and it pollutes the log. A well-kept log has a short second section headed findings with no artefact, reviewed annually, and most of them turn out to be Chapter 41's material rather than Chapter 39's.

B.3 Three threshold triggers.

The first is the required one and it is the one Chapter 5 has been waiting for. A guest count is the master variable and it moves silently, ten at a time, across nine months, and nothing in a normal planning process ever looks at it as a change.

B.5 Rubric. Answer all six against a real platform, and the exercise stands or falls on question 5.

Honest answers to question 5 look like: "it has no floor-plan tool, so I would stop drawing floor plans and start relying on the venue's drawing" — which Chapter 27 found to be wrong at Wildrye — or "its budget module has no contingency line, so I would stop tracking contingency separately," or "it has no venue-file concept, so venue knowledge would live in event folders and die with each event."

A submission that answers question 5 with "nothing" has not done the exercise. Every tool subtracts something; the only question is whether you noticed before or after.

B.7 Rubric. Five numbers with their units and assumptions written next to them. Worked examples of the form:

89          →  89 — SEATED DINNER @ 12 sq ft. Ceremony in rows: 211
$5,053      →  $5,053 — MINIMUM VIABLE FEE PER SATURDAY, at 16
                sellable Saturdays and $80,850 required revenue
1 per 75    →  1 per 75 GUESTS — 4-6 hr event WITH alcohol.
                Multi-day is 1 per 50-60 plus servicing
$68.25      →  $68.25 — COST OF AN HOUR at a 60% billable ratio.
                At the 45% I actually achieved, it is $91
2 hours     →  2 hours — TAIL-LIFT unload, 53-ft trailer, 4 crew,
                NO DOCK. At a dock it is 45-90 minutes

And at least one should surprise you. The commonest surprise is the billable ratio, because the assumption underneath a cost-of-an-hour figure is usually a number the planner has never measured. The second commonest is a capacity.

B.9 A data position, 268 words.

What I collect. Names and contact details for you and for anybody you ask me to deal with; your guest list, including addresses where relevant, and any dietary or access information your guests give us; contracts and payment records; and photographs of your event.

Where it lives. In one cloud folder per event, on [service], protected by two-factor authentication, plus my accounting system for invoices. It is not stored on my phone, other than photographs, which are moved and deleted within a week.

What I share, and with whom. Guest numbers and dietary requirements go to your caterer; names and table numbers go to your caterer and your venue; access requirements go only to the specific people who need to act on them. I do not share your guest list with anybody else, ever, and I do not use your information for marketing.

Dietary and access information is health information, so I share the requirement and not the reason, I name a person only where the plate has to reach them, and I destroy those records within 30 days of your event.

Retention. Contracts and financial records for seven years, because I am required to. Guest lists, dietary and access data: 30 days after the event. Photographs: indefinitely, unless you ask me not to — and you can ask at any time.

Your rights. You can ask me for a copy of everything I hold about you, ask me to correct it, or ask me to delete it, and I will do it within 30 days. Just email me.

B.11 Three decision records.

DR-03  2026-02-14  CEREMONY TIME: 16:25
  Decided by: Alicia and Sam, on the planner's recommendation
  Why: sunset 19:48. Photography needs the 60 minutes before it.
       Ceremony 36 min + 200 m walk + family photographs 40 min
       → 16:25 is the latest time that leaves golden hour intact.
  Considered and rejected: 17:00 (loses the family combinations),
       16:00 (guests arriving from the city cannot make it)
  Revisit if: sunset assumption changes, or the ceremony
       lengthens past 40 minutes

DR-05  2026-05-09  DECISION PROTOCOL AND SPENDING AUTHORITY
  Decided by: Alicia and Sam
  What: planner may spend up to $200 without asking; may change
       HOW something happens, not WHAT; asks Sam, not Alicia
       — "unless it's about a person," added by Alicia
  Why: Alicia's own words: "I'll be a mess." Agreed in May,
       in six minutes, when nobody was under pressure.

DR-06  2026-06-21  NO CEREMONY ARCH
  Decided by: Alicia, after seeing the quote
  Why: $1,150 against a $677.69 total floral line. The meadow
       has its own backdrop; Ch.16's through-line is that
       nothing was bought for a wedding.
  NOTE: this is the decision most likely to be revisited in
       August after seeing photographs on the internet.
       This record exists so the reasoning survives the doubt.

Six per wedding is the realistic number, and the format's whole value is the why — because the question that arrives in month eight is never what did we decide but why did we decide that, and the answer has left everybody's memory.

B.13 Rubric. Rank ten findings, choose four, defer six with dates, and justify both lists.

The ranking criteria, in order: expected cost of the error prevented × likelihood · then the time to implement · then whether it compounds across future events. A cheap fix for a rare and catastrophic error outranks an expensive fix for a common and trivial one — which is how the insurance-certificate trigger (four minutes, prevents a venue refusing entry) beats a template redesign that takes a day.

The justification of the deferred list is the harder half and the one that must not be skipped. Six findings with dates is a decision; six findings without dates is a list that dies. And say out loud which of the six you expect never to do — a change you decided not to make is a decision; a change you forgot is a finding that died.

C.1 Rubric. Time it. Under thirty seconds means a convention exists; two minutes means there is a folder somewhere; "I'll have to look" means the template lives in the last event's folder and is copied forward with that event's details still in it, which is the commonest system in this profession and is not a system.

The follow-up question worth asking: "is that the newest one?" — and watch the pause.

C.3 Rubric. Two numbers per planner: entries, and entries that became changes.

Expect: most planners keep no log; those who do report a ratio far below what they expect to report. Ninety-one and four is the chapter's illustrative figure and it is not a caricature. Report both numbers and the ratio, and ask the one diagnostic question: "where does a change actually get written?" — if the answer is not a named file, the ratio is the explanation.

C.5 Rubric. Try the export, do not read about it. Report the format — CSV, JSON, a zip of PDFs, or a printout — and whether it is usable, which means: does it contain your documents or only your data, does it preserve which event each thing belongs to, and could you rebuild a run sheet from it?

The common finding: the export contains the structured data and not the documents, so eleven months of notes, drawings, and correspondence come out as an unlabelled list. Question 3 of the six should be asked second, not last, and this exercise is why.

C.7 Rubric. Ask what the migration actually cost — in hours, not in dollars — and what they stopped doing. Expect 20–80 hours, most of it re-entering historical events, and expect them to say they abandoned the historical data partway through.

The second question is the valuable one and it is question 5 answered retrospectively: "what did you stop doing?" Expect specific losses — a floor plan, a budget structure, a tracking column — that were never decided to be dropped and simply had nowhere to go in the new tool.

D.2 Rubric. It is coherent, and the coherence needs stating precisely rather than assumed.

The claim is not that software is unimportant — it is that software is a delivery mechanism for the four components rather than a fifth component. A stack section is therefore consistent: once you have artefacts, triggers, conventions, and a loop, the tools that deliver them faster are worth choosing well.

Where the objection has force, and a good answer concedes it: the chapter's own stack section is organised by function and immediately becomes a shopping list, and question 5 exists precisely because tools do reshape practice — which is an admission that software is not neutral, and a neutral delivery mechanism was what the argument claimed.

The sharpest version of the resolution: software cannot supply a system and can destroy one. That is asymmetric, it is consistent with both sections, and it is a stronger claim than the chapter makes.

D.3 Rubric. The charge of defeatism is fair on its face — three or four a season across a twenty-year career is sixty to eighty changes, which is not obviously enough — and a determined person working through a slow January could plausibly implement twelve small template edits in a week.

What the number is actually about: not the edit but the bedding in. A change is implemented when it has survived a real event and been used correctly under pressure — and twelve simultaneous changes to a production process mean twelve untested modifications arriving at the same wedding, which is how a system produces its own failure. The constraint is verification, not effort.

Decide, and this is defensible: twelve edits are possible and three or four changes are. Batch the mechanical ones — a unit written next to a number, a field added, a trigger inserted — and treat them as one change with one verification. Reserve the count for anything that alters how the day is run. Which preserves the discipline and answers the objection, and it is a better rule than the chapter's.

D.5 Rubric. The rule draft anything, decide nothing is admirably clean and is too conservative in at least one respect, and the exercise is to name a decision you would genuinely delegate.

Defensible candidates, all of which share a property: sending a payment reminder on day 3 — a decision with a rule, a trivial downside, and a reversal cost of one apology · flagging that a guest count has crossed a threshold (this is a decision to raise something, and the human still decides what to do) · choosing which of two file versions is current, by date · rejecting a proposal for a date already booked.

The property they share: a stated rule, a cheap error, and a reversible outcome. Which suggests a better formulation than the chapter's: a tool may decide anything where the rule is written, the error is cheap, and the decision is reversible — and may decide nothing about a person, about safety, or about money above your authority. That is more useful than the blanket version and it survives the counterexamples.

D.7 Rubric. Realistically, a solo planner cannot achieve full formal compliance with a modern data regime — there will be no data-protection officer, no record of processing activities, no formal impact assessment, and no lawful-basis analysis — and pretending otherwise helps nobody.

The minimum defensible position, and it is achievable in an afternoon: collect only what you need · know where it is — one place, not four devices · two-factor authentication and a device passcode · a written retention rule with short periods for guest data and destruction actually performed · treat dietary and access data as health information: share the requirement, not the reason, and only with people who must act on it · a plain-language paragraph the client sees (B.9) · a named process for responding to a request for a copy or a deletion · and don't email spreadsheets of guest lists to vendors who asked for a headcount.

That is not compliance and it is a defensible practice, and it addresses the failures that actually happen — a lost laptop, a guest list emailed to the wrong caterer, dietary information circulated with names attached. Say so honestly rather than claiming a standard you do not meet.

M.1 The production book was a document; this chapter makes it a document with triggers, conventions, and a closing loop attached — a version convention so there is one current run sheet rather than three, a folder tree so it can be found, and dated triggers so it is opened at −2 weeks rather than when somebody thinks of it.

The direct closure: Chapter 26 found that the emergency page belonged to no chapter and therefore did not exist — discovered at chapter twenty-five of a twenty-five-chapter process. §39.2a's trigger set puts it at −72 hours, on every event, forever. The finding that a document had no owner is closed by giving the document a moment instead.

M.3 Buy the platform fourth because a platform without artefacts, triggers, conventions, and a loop is an empty container with a subscription — and because until you have run three or four events on documents you made, you do not know which two things you need it to do, so you choose on the demonstration rather than on the requirement.

The question §39.4 adds that Chapter 36 did not have: what does it not do that I will therefore stop doing? Chapter 36's argument was about readiness — you are not ready to choose. This one is about subtraction — the tool will quietly remove a practice, and the removal is invisible at the point of purchase and permanent afterwards.

M.5 Four errors, one form.

The common form: a quantity that is correct for one question, used to answer a different question. Nothing is miscalculated in any of the four; every number is right and every number is being asked the wrong thing.

And all four are fixed by four words: write the unit next to the number. 89 — seated dinner @ 12 sq ft · $962.69 — contingency remaining, NOT net of line drift · 140 bottles — supply, not demand · 18 rolls — PER DAY.

M.7 Because both are statements about which part of the job is transferable.

Chapter 27 said a planner's day is a sequence of fifteen-second decisions and that almost none of them are about tasks — the task can be handed to anybody with a run sheet; the judgment about whether to hold the ceremony six minutes cannot. §39.10 says the same thing about systems: a system should absorb everything repeatable and cannot absorb judgment.

The consequence for a planner is the same in both chapters and is genuinely reassuring: systematising aggressively does not make you replaceable. It makes you replaceable on the tasks — which is the point of Chapter 40's absence test — and it protects the thing that is not. A planner who resists systems to remain essential has it exactly backwards: they have made themselves essential to the run sheet and unavailable for the decisions.

M.9 The −8 week trigger: insurance certificates checked against dates.

And "against dates" is doing the work. A certificate that exists is not a certificate that is valid on the day of the event — the commonest failure is a certificate obtained in January for a policy that renews in July, filed, ticked, and expired. The trigger fires eight weeks out, which is early enough to obtain a renewed certificate and, if the vendor's cover has lapsed, early enough to replace the vendor (Ch.28's categories). At −1 week it is a venue refusing entry to a supplier on the morning of the wedding.

E.1 Rubric. The audit must include every change this book produced, ranked by expected cost prevented × likelihood, then time to implement, then whether it compounds. Four chosen, the rest deferred with dates, and the deferred dates actually entered in a calendar — which is the last instruction and the one that distinguishes this from an essay.

Expect roughly twenty-two changes (Case Study 39.2 totalled them for the first time and found ~19 hours of work). Expect the top four to be cheap and preventative rather than large and impressive — the insurance trigger at four minutes, the guest-count threshold at thirty. And expect at least two findings that cannot be assigned an artefact at all, which belong in Chapter 41's territory, not this one.

E.3 Rubric. The essay must take the objection seriously: most systems literature is written for organisations, where a system persists because several people depend on it and somebody's job is to maintain it. A solo planner has no such enforcement, and every practice in this chapter competes directly with billable work in a business with no slack.

The case that it does not transfer: no redundancy, no colleague to notice a lapse, seasonal pressure that arrives exactly when the loop should close, and the fact that a system's benefit accrues months later to a person who is currently exhausted.

The case that it does, and it is the stronger one if argued specifically: the components are individually tiny — four minutes of triggers, ten minutes of folder tree, five fields in a log — and the chapter's own concession that a planner implements three or four changes a season is the adaptation to solo scale rather than a failure of it. The enforcement problem is real and the answer is Chapter 30's: attach the practice to something already obligatory (the invoice, the reconciliation, the final numbers call), because a practice that depends on discipline fails and one attached to an existing obligation survives.

A defensible conclusion: "systems" as organisations use the word does not transfer, and the four components do — and the honest test is whether the version you are proposing takes minutes or days, because anything that takes days will not happen in September and therefore will not happen.

E.5 Rubric. Ninety minutes, annually, on a fixed date, producing four changes and a dated deferred list.

0–15   THE LOG. Read every finding from the season, out loud
       if alone. No editing, no ranking yet.
15–30  ASSIGN ARTEFACTS. For each finding: which file changes?
       Findings with no artefact go to a separate list — do
       not invent one.
30–45  RANK. Expected cost × likelihood, then time to implement,
       then does it compound.
45–60  CHOOSE FOUR. Write the four edits into the actual files
       NOW, in this session, or they will not happen.
60–75  DEFER THE REST, WITH DATES. Each gets a month. Enter
       them in the calendar in this session.
75–85  THE STACK AND THE ARCHITECTURE. Anything to add,
       remove, or export? Question 5 on anything new.
85–90  THE DATA POSITION. Retention actually performed?
       Anything deleted that should have been?

Two design properties that decide whether it survives. The four changes are made in the session, not scheduled — a systems audit that outputs a to-do list has produced findings, not changes, which is the failure it exists to fix. And the deferred list is diarised in the session, for the same reason.

And one honest line at the end of the template: findings I have decided not to act on. Naming them is a decision; leaving them on a list is a slow way of forgetting them while feeling responsible.

Chapter 40 — Capstone

A.1

A.3 The walk · seating · speaking · timing · medical · the rain variant.

One item each: the walk — a car from the gate, 16:00–16:15, named driver, six named guests. Seating — rows 1–2 reserved, 14 seats, name cards. Speaking — Rosa is seated and the officiant brings the microphone to her; her cue is Elena touching her arm, because she cannot hear one. Timing — six minutes of float, held for the track. Medical — an ambulance reaches the barn door, not the meadow. The rain variant — festoon off until 19:20, so the cue survives the move.

A.5 1. A category-B vendor fails — tests whether the degradation ladder exists. 2. A condition at the decision deadline — tests the rain plan's five parts, the decider, and the evidence. 3. A category-D vendor fails — tests whether the preparation that must exist in advance actually exists. 4. A person fails — tests whether tasks assigned to named non-professionals have second names. 5. You fail — the absence test, which tests whether the plan is a document or a memory.

They escalate deliberately: each one removes something less replaceable than the last.

A.7 Five steps: find somebody competent who was not involved · give them the production book and nothing else · ask them the six questions · write down every question they have to ask you · fix the gaps.

The six questions: What happens at 16:25? · Who do I ring if the caterer does not arrive? · Where does everybody go if it rains? · Who is allowed to spend money, and how much? · Somebody has collapsed — what do you do, in order? · And: what would you not have known?

Step two is the discipline: no conversation, no context, and you answer nothing. The moment you answer, you have destroyed the instrument — because the questions are the output.

A.9 1. What went wrong · 2. the reconciliation · 3. the finding log · 4. the injections that were real · 5. vendor debriefs · 6. guest findings · 7. the systems changes · 8. the deferred list, dated · 9. what you would do differently, and what you would do again.

What went wrong comes first, and it is Chapter 30's going-first at the level of a document. It sets the credibility of everything after it — a report that opens with successes is read as marketing, and a report that opens with four errors named without hedging is read as true, including the parts that are flattering.

B.1 Rubric. Ten sections, and the deliverable includes what you could not fill in, which is the exercise's actual output.

The sections that reliably come out thin, and what the gap means: 02 — the contingency, if it is not tracked net of line drift (Ch.30's error, and most books contain it) · 04 — capacities without units, and permissions without granted to whom · 05 — the ceremony hour, which almost nobody has as an artefact · 07 — the rain plan's crew, which is the part of the five that is always missing · 08 — the alone column and the access column, if the asking happened at −3 weeks instead of −6 months · and 09, which does not exist at all until after the event and should be a heading with a date under it.

Report the gaps as findings, with artefacts and dates. A book assembled with six visible holes and a dated plan for them is a better deliverable than one where the holes were filled with plausible text.

B.3 Rubric. One page, six blocks, and the test is that every line names a person or a time.

A line that fails the test: "ensure elderly guests are looked after." A line that passes: "Car from gate 16:00–16:15 — DANNY — 6 named guests."

Two checks worth running on your own sheet. Does anything on it depend on a person hearing something? — Rosa's cue is a touch on the arm precisely because a spoken cue would fail her. And does the rain variant preserve the cues, or only the furniture? — the festoon-off-until-19:20 line exists because the move to the barn would otherwise have destroyed a lighting cue that took a chapter to design.

B.5 Rubric. Trace it hour by hour and do not solve until step 5 — the discipline is the method, and a reader who starts solving at 14:25 will never find the collision.

The trace, as the chapter ran it. 14:20, van immobilised, flowers 11 miles away. Not urgent yet. 15:00, still not urgent. 15:40 — the point where it becomes irreversible, because the ceremony is at 16:25 and a round trip is 40 minutes. So the decision must be made by roughly 15:00.

Then the finding, and then the second finding. First: nobody is named to collect. Second, and better: the obvious candidate — Danny — is on the gate at 15:40 running the car from the car park, which is a Chapter 29 job created three chapters earlier. A good injection finds a gap and then finds a collision, and the collision is the part a read-through cannot reach.

And record honestly whether the book answered it or you did. In this case the book answered where the flowers are and when the ceremony is, and the planner answered who could go — which is the mark, and it is why Tomás's name is now written on the line.

B.7 The four-sentence category-D script — an officiant failing at −90 minutes.

Chapter 28's four elements: what has to exist in advance is a second number, a named alternate, the legal position, and a form of words.

1. "Rev. Castellanos has been taken ill and cannot be here. Fr. Emmanuel Rusike is on his way and will be here by four o'clock" — or, if not — "we are going to hold the ceremony at 16:25 as planned, and Elena is going to lead it." 2. "The legal registration is not affected by who stands at the front today — that was completed on Thursday" — or, where it is affected — "the legal part will be signed on Monday at the parish office, and today is the wedding." 3. "Nothing about the timing changes. The music, the readings, the vows and the ring exchange are all exactly as we rehearsed, and Rosa still speaks after the second reading." 4. "Rosa, I'll come and find you at twenty past and walk through it with you. Elena, Beatriz — I need you both for ninety seconds now."

What each sentence is doing: naming the fact without hedging · removing the legal fear, which is the first thing both families will think about · confirming that the shape of the day is intact · and assigning the two people whose jobs just changed.

And the honest note: the alternate must have been confirmed at −3 weeks and the permission must have been checked for granted to whom, and extendable? at −9 months. The script is four sentences and the preparation behind it is two triggers.

B.9 Rubric. Report the count and every question verbatim. Do not defend, do not explain, do not say "oh, that's because."

Expect eight to fifteen questions on a book that is genuinely good. The Reyes–Whitfield book — assembled across thirty-nine chapters — produced eleven, and the instructive property is that none was a criticism of the plan. Every one was something the planner knew and had not written down.

The categories to expect, because they recur: a person named repeatedly and described nowhere ("who is Beatriz?") · two versions of something with no convention saying which is current · a constraint that appears as a cue and never as a rule with a source ("what's the curfew and who enforces it?") · a protocol that lives in your head (the card box) · an authority gap — the decision protocol covered spending and not the authority to move the ceremony · and a phone number that exists only in a phone.

If you get fewer than five questions, check whether you answered anything.

B.11 Rubric. Every task assigned to a named non-professional gets a second name — and then the check against the assignment sheet is the point of the exercise, because that is where the collisions live.

The known collisions on the Reyes–Whitfield wedding, as a worked example. Danny is on the gate 16:00–16:15 and is the obvious collector for the flowers at 15:40 — he cannot be both, and Tomás takes the collection. Danny is also the card-box owner at 21:30 and walks Rosa to her car at 21:10 — twenty minutes apart, which works and is worth knowing. Elena has three tasks and had no second name against any of them after four audits — and Rosa's cue is a touch on the arm from a person who might not be there. Beatriz is the second name for two of Elena's three, which is eleven words at the rehearsal and closes injection 4.

The general finding: family members accumulate tasks across chapters and nobody ever lays one person's day out on a single line. Do that — one row per person, times across the top — and the collisions become visible in about four minutes.

B.13 Rubric. Ten minutes, your own event, your own documents, and the honest mark at the end.

The method: pick the injection, set a timer for ten minutes, and work only from the book. Every time you supply something from memory, write a mark in the margin. The marks are the output — the resolution is not.

A simulated ten minutes with no marks was not run honestly, and the two commonest hidden marks are a phone number you know and a name you can picture. Both are exactly what the absence test finds, and both are invisible when the person running the simulation is the person who wrote the book.

C.1 Rubric. Section 04 from measurements, not from a website — and the report is what the website was wrong about.

The near-universal findings: a capacity figure with no activity attached to it (Chapter 28's error, published) · a room dimension that includes a bar, a column, or a fire exit that cannot be blocked · "ample parking" · a stated access time that turns out to be negotiable, or not · and a doorway. Measure the doorway.

And the two that appear on no website at any venue: how a vehicle gets out, and who is contactable on a Saturday.

C.3 Rubric. Ninety minutes, somebody who has run events, lunch bought, and the instruction that matters: take notes and do not defend.

The failure mode is entirely predictable and almost universal. They ask "which floor plan is current?" and you say "oh, the second one — I know, I need to archive the other." You have just answered the question, converted a gap into a conversation, and lost the finding. The correct response to every question is to write it down and say nothing.

It is uncomfortable for ninety minutes and it is the most efficient ninety minutes in this book.

C.5 Rubric. Get a real failure, then check the five injections honestly against it.

Expect a substantial hit rate — perhaps three in five — and expect the misses to be the interesting part. The injections are designed around this book's own material, so a failure that looks like a vendor, the weather, a category-D supplier, a family member, or the planner will be caught. What escapes: an institutional failure (a venue's sales team double-booking a room), a legal or regulatory change, a failure that begins months before the injection window, and anything involving a person acting badly on purpose.

Report the misses as an answer to D.2.

C.7 Rubric. Run one injection on somebody else's plan, with permission, and report both what it found and how they reacted — the second is the finding about injections rather than about the plan.

Expect one of three reactions. Defence ("that wouldn't happen") — which is information about the planner rather than the plan. Solving immediately, before the trace is complete, which is the commonest and which skips the step where the collision appears. Or the productive one: a pause, and then "actually, who would do that?" Note which you got, and note that a colleague who defends the first injection will accept the third, which is why the set escalates.

D.2 Rubric. Design an injection the book genuinely cannot answer. Strong candidates share a property: they are outside the planner's decision space entirely.

Examples that work: the venue is served with a closure notice eight days before — not a Chapter 28 vendor failure but a regulatory event with no substitute for 100 people on a September Saturday · the couple separate at −5 weeks, which the book addresses commercially in Chapter 8 and not at all as a human situation with vendors, families, and a hundred guests attached · a guest is arrested at the wedding · the planner's own family emergency lands at −2 days, when nobody can be briefed and the absence test's substitute has a wedding of their own · a public event — a strike, an outbreak, a national day of mourning — that changes what is appropriate rather than what is possible.

What it reveals: the injection set is built from failures with a substitution structure — something is missing, and the method finds who or what replaces it. The failures it cannot address are the ones where the question is not who does this instead? but should this happen at all, and in what form? Those are §28.8's territory — the crisis that cannot be solved — and the honest reading is that the capstone tests the plan's mechanics thoroughly and its judgment not at all, which is D.8's question arriving early.

D.4 Rubric. The objection is strong and largely correct: "the couple wanted it and it does no harm" will accept any decision whatever, because a couple can be said to have wanted almost anything they agreed to, and "no harm" is unfalsifiable at the level of a napkin.

What limits it, and the limits must be argued rather than assumed. §40.5a requires it to be recorded as such — labelled explicitly as not a defence — which means a book full of them is visibly a book full of them, and that visibility is the mechanism. A design defended by constraint, principle, or consequence is a decision; one defended by the fourth form is a preference, and the audit's value is the ratio.

And "no harm" can be tightened into something with teeth: does it consume budget, attention, or time that a higher-ranked item needed? Under that test the fourth form fails for the forty-first floral arrangement (Ch.29's row four against row one) and passes for a colour nobody paid extra for.

A defensible conclusion: as written it is a loophole; with the recording requirement enforced and "no harm" defined as opportunity cost, it becomes a legitimate and narrow category. The chapter should have said the second thing.

D.6 Rubric. Honestly: most readers will not do twelve hours plus somebody else's ninety minutes. A defensible answer says so and then does the useful work of naming the minimum version.

The minimum that retains most of the value, in about two and a half hours: (1) the one page — 20 minutes, and it forces the five numbers · (2) injection 5, the absence test — 90 minutes of somebody else's time, and it is the highest-yield item by a wide margin · (3) one other injection, chosen as the thing you are least confident about — 20 minutes · (4) the units pass: write the unit next to every number in the book — 20 minutes, and it catches the class of error that produced four separate failures in this book.

What is lost: the completeness audit, the defence, the simulated day, and the report. What is kept: the two instruments that find things no amount of re-reading will find — somebody else's questions, and one removal traced forward. That trade is worth stating plainly, because the alternative to a two-hour version is not a twelve-hour version, it is nothing.

D.8 Rubric. The observation is correct and is the sharpest available criticism of the chapter: every instrument here tests the artefact. The absence test asks whether the book survives the planner's removal; it says nothing about whether the planner can do the four things the book cannot.

What a test of the planner would look like: a simulated day with no book — the four judgment calls from Case Study 40.2, presented cold, in real time, with somebody playing the father, the mother, and the caterer · a decision log reviewed by a peer, judging the decisions rather than the outcomes (Ch.40's own defence discipline, turned on the person) · the §28.8 conversation, rehearsed, which is the one competence nobody practises and everybody eventually needs · and a review of the finding log's ratio: what fraction of your findings are about you, and has it changed?

Should the book have included one? A defensible yes — with the reason it did not stated honestly: a test of judgment cannot be self-administered or self-scored, it requires a person to play the room, and it is the part of this profession that is transmitted by working next to somebody rather than by reading. Which is exactly what Chapter 41 says about the eleven days of assisting, and it means the answer to D.8 is: the test exists, it is called an apprenticeship, and this book cannot administer it.

M.1 Cost — Chapter 5. Every per-head line multiplies: catering, bar, rentals, stationery, favours, transport. Guest count is the only variable that moves nearly every line at once.

Logistics — Chapters 11, 13, 14, 19, 29. Space per person, chairs, circulation, sanitation, service staff, transport, and the seating chart. Capacity is a constraint, not a cost, and it fails discontinuously: 100 guests fit and 110 do not.

Emissions — Chapter 35. Travel is 50–90% of an event's footprint and it is guest count × distance. Food is covers × factor. The Reyes–Whitfield guest-list cap, decided in Chapter 5 for money, was the largest environmental decision on the wedding — worth about twelve times everything else combined, and nobody involved described it as one.

The mechanism is identical in all three: guest count is a multiplier, not a line.

M.3 A read-through finds contradictions — two documents that disagree, a time that appears twice, a name that changed. Four competent reviewers found eight of them in Case Study 40.1.

It cannot find fragility, because everything in a plan looks fine when nothing has gone wrong. The lead-gift donor was upstairs, nobody knew what he looked like, and there was no second lead gift — and none of that is a contradiction. It is a plan with a single point of failure that reads perfectly.

Injections find fragility, by removing something and tracing forward. And the third instrument is the absence test, which finds a third set: what is true but unwritten. Reviews find what is wrong, injections find what is fragile, the absence test finds what is in your head — and the Reyes–Whitfield book demonstrates that all three are disjoint. No instrument found what another found.

M.5

In all three the shape is the same: silence is read as satisfaction and is evidence of nothing — and in all three the fix is a specific question about an event rather than a general question about experience.

M.7 $42,000 is what was authorised. $299.22 is what came back. $10.18 is what the planner earned per hour.

They reconcile precisely: the wedding cost $41,700.78 of a $42,000 budget, returning $299.22 — and the planner's fee was inside that budget, unchanged, while the hours behind it were 293. Nothing is inconsistent. All three are true simultaneously.

What each reveals that the others cannot. $42,000 reveals the client's priorities** — it is a priority statement in dollars, and the ranking behind it (food, guest comfort, the ceremony) explains every allocation. **$299.22 reveals the planner's integrity and the system's blind spots at once — the return is the reputational asset of the whole engagement, and getting to it required finding $437.31 that had been outside every line since month one and $964.78 of drift that no tracker was netting. **$10.18 reveals what the other two cannot see: that every celebrated finding in this book — the barn capacity, the ceremony hour, the access asking, the reconciliation itself — was performed unpaid**, and that a professional standard maintained at $10.18 an hour is a fact about the person, not about the business.

Put together they are the book's central tension in three numbers: the work was done well, the client was served honestly, and the economics were not viable — which is why Chapters 36–41 exist.

M.9

Two of the four are not planners, which is the point. Going first is not a technique for managing clients; it is the general mechanism by which a room becomes one where difficult things can be said — and it works only when the person with the most to lose does it. A planner who goes first at a debrief and a chair who makes the first ask are performing the same act.

M.11 Chapter 2: a description problem — what the levels contain, and the warning that "day-of" is never day-of. Chapter 36: a business problem — hours per event against billable capacity, and the finding that unbillable overhead attaches to clients rather than to events, so twenty-six coordinations carry 390 hours where seven full plannings carry 105. Chapter 37: a pricing problem — required revenue ÷ sellable Saturdays, and the finding that a coordination consumes a $5,053 Saturday.

All three arrive at the same conclusion by independent routes, which is why the book states it three times: the entry-level service is the hardest one to survive on.

E.1 Rubric. All eight project-checkpoint items on a real event, and the two required outputs are the total hours and the gaps found — reported honestly, including the items you skipped and why.

Realistic expectations: eleven to fourteen hours plus ninety minutes of somebody else's time, and between fifteen and thirty gaps on a first full run. Most gaps will be in sections 04, 05, and 08 — the venue file, the ceremony hour, and the guest columns — because those are the three that require going somewhere or asking somebody, and every other section can be written at a desk.

Report the hours honestly even if they embarrass the method. A capstone that took twenty hours is a finding about the capstone.

E.3 Rubric. Use §40.5's eleven questions as evidence, and the essay must engage with the fact that the book being tested was excellent — thirty-nine chapters of deliberate construction — and still had eleven gaps.

The case that an irreducible fraction is always in one head: all eleven were things the planner knew; four audits had not found them; and the reason is structural — you cannot search for what you do not know is missing, so the fraction can be reduced by an external test and never driven to zero by an internal one. Case Study 40.2 supports it: even with an excellent book, four judgment calls arose in seventeen hours and all four were about people.

The case that it can be made robust: every one of the eleven was fixable in minutes once named, so the irreducible part is not the content but the discovery mechanism — and a practice that runs an absence test every event drives the residue asymptotically down. The four judgment calls are not gaps in the plan; they are the job.

The strongest position synthesises the two: what is irreducible is not information but judgment, and the two are constantly mistaken for each other. Everything in the eleven questions was information and all of it was writable. The four calls in Case Study 40.2 were judgment and none of it was. A plan can be made fully robust to the absence of the planner's knowledge and cannot be made robust to the absence of their judgment — which is exactly why the substitute needed to be reachable by phone, and why the honest limit is that a planner in surgery produces four unanswered questions.

E.5 Rubric. One page, applied by somebody else, without you present.

COMPLETENESS AUDIT — apply to the book, not to the planner
□  Can I find the date, venue, and start time in under 10 sec?
□  Are there five phone numbers on the first page, and is one
   of them the venue's SATURDAY contact?
□  Does every capacity figure have a UNIT and an ACTIVITY?
□  Is there exactly one current version of every document?
□  Does every named non-professional task have a SECOND name?
□  Is there a rain plan with all five parts — including the CREW?
□  Is there a decision protocol, and does it cover AUTHORITY
   as well as money?
□  Can I find the couple's phone number?
□  Is every person named in the book described somewhere —
   surname, role, phone?
□  Is there an emergency page, and does it say where an
   ambulance can actually reach?
□  Does the guest list have dietary, access, and ALONE columns?
□  Is there a card-box protocol with a name and a time?
□  For every constraint that appears as a cue (curfew, handback),
   is the SOURCE and the ENFORCER stated?
□  Could I run the ceremony hour from one page?

SCORING: every □ you cannot tick from the book alone is a gap.
Do not ask the planner. Write the question down instead.

Then have them do it, and note two things: how many they could not tick, and how many times you were tempted to answer. The second number is the more interesting one.

Chapter 41 — The Planning Career

A.1 1. Solo, small, indefinitely · 2. small firm · 3. agency or larger production company · 4. in-house · 5. venue-side · 6. supplier-side · 7. adjacent (teaching, association work, consultancy, writing, venue development).

Three have no Saturdays: in-house, agency (largely), and adjacent — and destination 5, venue-side, has all of them.

What follows is the chapter's most under-told fact: the largest cost of this career belongs to four of the seven destinations rather than to the industry. A planner who has decided that sixteen Saturdays a year is unsustainable has not decided to leave the profession — they have decided against three or four of its seven destinations. Almost nobody entering it is told that the map has this shape, and the ones who burn out often believe the choice was the work or nothing.

A.3 Certifications produce structure, a peer network, and credibility with institutional buyers. They do not produce clients. They are fourth in the ranking of what a newcomer's money buys and are frequently bought first.

Three questions for deciding. What will I be able to do afterwards that I cannot do now? — if the answer is "have letters after my name," that is a marketing purchase and should be judged as one. Who is on the other side of it? — the peer network is usually the real product, so ask two current members what they got. And does anybody who hires people I want to work for require it? — for corporate and association buyers the CMP genuinely appears in specifications; for wedding clients no certification is known to a single couple in the market.

A.5 In order: how they make decisions · how they talk to clients · how they talk to vendors · their documents · their pricing and how they arrived at it · and their mistakes.

The question almost nobody asks: "can you tell me why you did that?" It is the difference between three years of labour and three years of an apprenticeship — and it is worth agreeing in advance, before you start, along with what you may use in your portfolio and whether you may take your own clients.

A.7

Most planners' instinct is the second planner; most planners' answer is part-time admin. Because the instinct is about the visible constraint (Saturdays) and the answer is about the measurable one (the billable ratio) — and admin is cheaper, lower-risk, reversible, and available immediately.

A.9 1. Delegating tasks and not decisions — which is not capacity, it is a person doing what you say. 2. Correcting in front of a client or a vendor — it destroys their authority and it is permanent. 3. No stated standard, so "that's not how I'd have done it" is measured against something that exists only in your head. 4. Being the escalation for everything — a bottleneck with a salary attached. 5. Not paying properly or on time, which in this industry is the commonest and the worst.

And the one that is not a failure and feels like one: they will do it differently and it will be fine. "It was slower and warmer than mine and about ten minutes longer, and two of the family said it was the first thing all year that hadn't felt rushed."

A.11 Saturdays · attention · the body · emotional labour.

Three are invisible. Saturdays are countable — sixteen a year for eleven years is a hundred and seventy-six — and the other three are not. Attention is Chapter 27's scarcest resource applied across a season, and what it costs is the attention you would otherwise have given to your own people, in exactly the months they need it. The body is cumulative and silent — backs, knees, and voices — and nobody notices the accumulation until it is a diagnosis. And emotional labour is Chapter 27's "never look worried," which is a real cost borne by a real person and the one nobody counts at all.

A.13 🚪 A career with no natural stopping point expands to fill whatever a person will give it.

"Not too many" is not a limit because it cannot be violated. A limit is something you can be shown to have exceeded, in November, on paper, by somebody who is not you. "Fourteen weddings" can be exceeded; "not too many" adjusts itself to whatever you did.

And the second reason, which is Halina's: a habit formed in year three when every enquiry mattered is correct in year three and expires silently. Nothing ever announces that a constraint has lifted — a number can be reviewed annually and found to be wrong; a habit cannot.

A.15 Finish what you have contracted or hand it over properly — Chapter 40's book is what makes that possible. Tell your recommenders, because a planner who disappears costs Delphine a recommendation and a relationship. Refer your enquiries out, deliberately, to named people — the last and best deposit you will make in that network. Keep the venue files and the finding log, because you may come back and destinations 5 and 6 want exactly what you know. And say why, to somebody — the industry's silence about people leaving is why the ones who leave think they failed.

A.17 Year four is the volume peak: fourteen events, $31,000, and it is the top of the volume strategy.** **Year five is the inflection: thirteen events, $34,000, and the change is the first real price rise — a pricing decision, not a market one, and it is Chapter 37's arithmetic applied once.

The first four years total $87,000** — $11,000 + $19,000 + $26,000 + $31,000 — **and year eleven alone is $63,000 from nine events. The first three years together earn $56,000, which is less than year eleven earns by itself.

Which is the honest shape: this career pays badly for a long time and then pays reasonably, and the people who leave in years three and four are leaving at the worst possible moment, without knowing that the curve turns.

A.19 The off-season is for the three annual reviews on one afternoon — the fee review (Ch.37), the systems audit (Ch.39), and the five-year plan (§41.8) · the debriefs you did not do · Chapter 38's relationship work, which is the only time of year there is time for it · learning a skill rather than a certification · and four weeks of nothing, defended as hard as a wedding date.

The order matters: rest first, then the reviews. A systems audit run by somebody who has not recovered produces a list written in exhaustion — and Chapter 39's ranking discipline, which is about deciding what not to do, requires a working brain. An exhausted planner ranks everything as urgent and then does none of it.

B.1 Rubric. Rank all seven against four constraints — money, geography, Saturdays, and what you are actually good at — and the honesty is in the fourth column.

Two checks that make it useful. Does your top-ranked destination contradict your Saturday constraint? Case Study 41.2's finding is that it usually does, because destination 1 or 2 is chosen for how it sounds and the Saturday answer is in questions 2 and 6. And what would you have to be good at that you currently are not? — destination 3 requires selling, destination 4 requires institutional politics, destination 6 is a different trade entirely.

B.3 The three to negotiate before assisting somebody.

On portfolio: "Can we agree now what I'd be able to use in my own portfolio afterwards, and whose permission we'd need? I'd rather sort it at the start than ask you awkwardly in two years — and I know it can't be got retrospectively."

On your own clients: "If somebody approaches me directly about their own wedding, what would you want to happen? I'm completely happy either way — I just want to know the line before I'm standing on it."

On being told why: "The thing I most want out of this isn't the hours — it's being able to ask you why you did something. Not on the day, obviously. Would you be up for ten minutes in the car afterwards, sometimes?"

The third is the one that converts three years of labour into three years of an apprenticeship, and it costs the person you are asking about ten minutes a month.

B.5 Rubric. A number, with reasoning that connects to Chapter 37's Saturday arithmetic and to the three kinds of Saturday Halina discovered: events, setup and rehearsals, and recovery.

A worked example of the reasoning: "Twelve events. Not fourteen. Twelve events is about twenty-six actual Saturdays once rehearsals and site visits are counted, and I am not available on more than twenty-six. At my current fee twelve clears the required revenue with $4,000 of margin**, and the thirteenth and fourteenth are worth about $9,000 and cost eight Saturdays."

And the sentence for 11 p.m. in February, which must be short enough to say when tired:

"I'd love to and I'm full for September. I cap at twelve a year and I hit it in January — it's not a negotiating position, it's just the number. Can I introduce you to Adaeze? She's genuinely as good as anyone I'd send you to."**

Note that it gives a number and a reason and offers a referral, and that it does not apologise or explain further. The version that fails is the one that says "I'm quite busy," which invites the follow-up that ends with thirteen.

B.6 Rubric. One page, all seven questions, and question seven is compulsory because it is the one everybody omits.

1  WHICH DESTINATION?  (of the seven — and answered last,
                        despite being written first)
2  WHAT IS THE CEILING? A NUMBER.
3  WHAT IS THE SECOND LINE — the work that is not Saturdays?
4  WHAT MUST THE MONEY BE, by year five?
5  WHO COVERS ME? (named, both directions, asked)
6  WHAT IS IN THE YEAR THAT IS NOT THE JOB?
7  WHAT WOULD MAKE ME STOP?

The ordering finding, which the exercise exists to reproduce: question 1 is answered first, most confidently, and most wrongly. Questions 2, 6, and 7 turn out to be load-bearing — and a destination that contradicts the ceiling was chosen for how it sounds. Noor wrote "small firm" and what she actually wanted was in questions 2 and 6.

And question seven is not for triggering an exit. Almost nobody's ever fires. It is so that a bad November has something to measure itself against — Noor's told her she was at the warning and not the point, which converted a fortnight of formless unease into one bad year against a two-year threshold. Without one, Halina's mortgage form is the only instrument available and it arrives in year eleven.

B.8 Rubric. Dates in a diary now, and the order is rest first.

NOV 1–28   FOUR WEEKS. Nothing. Defended like a wedding date.
           ★ Diarised in JANUARY, when not tired
DEC 2      THE AFTERNOON: fee review (Ch.37) · systems audit
           (Ch.39) · five-year plan (§41.8). Same day, every year
DEC 3–10   The debriefs that did not happen. Badly is fine
DEC 11–19  Relationship work — the venue files, the photographs,
           the two touches. Ch.38's six actions
JAN        The skill. Not a certification: floral, lighting,
           book-keeping, a language, a rigging course

The defence against the off-season that fills is a diary entry made in January for the following November — the same mechanism as Chapter 39's triggers, applied to your own year, and it must be made when you are not tired, because a November decision made in November is made by somebody who has just finished a season and will fill it.

B.10 Rubric. Work all three offers against your own seven questions rather than against their attractiveness — and the distinction the exercise is testing is between right and appealing.

An offer is appealing when it flatters the destination in question 1 — a bigger firm, a better name, a larger event. It is right when it satisfies questions 2, 3, 5, and 6: does it respect the ceiling, does it build a second line that is not Saturdays, does it leave cover intact, does it leave anything in the year that is not the job.

Report which you would take and which of the seven questions decided it. If question 1 decided it, look again — that is the finding of Case Study 41.2, and it is the reason the plan is one page with seven questions rather than one question.

B.12 Rubric. Identify who covers you, and then actually ask them, in both directions — which is the instruction people skip and is the entire exercise.

What to agree, and it takes one conversation: what "cover" means (the day only, or the last fortnight too) · how they would be paid, agreed now rather than in a crisis · where your production book lives and whether they can get to it without you · and that it runs both ways, which is what makes it askable.

It costs nothing until it is needed and it is one of the six things the ones who stay have in common. And the honest note from Chapter 40: cover requires the book. A colleague who would cover you cannot cover you from a plan that lives in your head.

C.1 Rubric. Seven conversations, one question each: what do you trade?

Report which destination surprised you, and the common surprises are worth predicting. In-house planners often report missing the variety more than they expected and the Saturdays not at all. Venue-side planners report that one building forever is either the best or worst thing about it, with almost nobody in between. And solo planners — destination 1, the most under-respected of the seven — frequently report the highest satisfaction and the lowest income, which is the finding that most complicates the chapter's arithmetic and should be reported honestly.

C.3 Rubric. Three planners in year eight or beyond, one question: what changed at the inflection?

Expect pricing to be the most common answer and expect it to be incomplete. The usual full answer is pricing plus a refusal — a category of work dropped, a service level discontinued, a ceiling stated — which is §37.10's claim confirmed in the field: the arithmetic and the refusals are the same act. Report anybody who says the market changed, and ask what they did differently in response, because the answer is almost always something they decided.

C.5 Rubric. Verbatim, and the answers cluster tightly. Expect: "watching them do it differently" · "I hired for the wrong thing" · "I was still the bottleneck" · "paying them in a bad month" · and "I didn't have anything written down, so I couldn't tell them what good looked like."

The last one is Chapter 39 arriving as an employment problem — your artefacts become the product the moment somebody else depends on them, and every gap now costs somebody else's afternoon rather than your own.

C.7 Rubric. Ask somebody ten or more years in about the six: age, loneliness, other people's happiest days, the industry's silence, comparison, and the fact that being excellent is not protective.

Report how many they recognised, and expect four or more. The most useful thing you will get is not the count but the response to the fourth — the industry's silence — because the common reaction is relief at hearing them named at all. Which is the section's own argument demonstrated: every planner who struggles with these concludes they are uniquely failing at something everybody else has solved. They have not solved it. They are not discussing it.

D.2 Rubric. The survivorship objection is correct and the chapter half-concedes it. The table is one person who stayed eleven years, and every planner who left in year three is invisible in it — which is precisely the population the claim is about.

What the same table would look like for the people who left: years one to three broadly identical — $11,000, $19,000, $26,000 — and then it stops. The interesting version has a fourth column: what they earned in the year after leaving, which for many is higher immediately, which is the strongest argument against the chapter's "the curve turns" consolation.

What survives, if stated carefully: the claim is not that everybody's curve turns. It is that the shape of the return is back-loaded and the decision to leave is usually made at the point of least information. That is defensible and it is weaker than the chapter's phrasing. What would settle it: longitudinal income data by cohort with attrition tracked, which does not exist in this industry — and a good answer says that the absence of that data is itself one of §41.8a's silences.

D.4 Rubric. The objection is strong and largely lands. Look at the six: a stated ceiling (requires being able to turn down money) · a second line that is not Saturdays (requires time to build it) · somebody who covers you (requires a network, which requires years) · four real weeks off (requires savings) · a relationship with money that is not anxiety (requires not being in financial danger) · and something in the year that is not the job (requires both time and money).

At least four of the six are materially easier with a cushion, and the chapter presents them as decisions, which quietly recodes an economic position as a character trait.

What survives, and it must be argued rather than asserted: the ceiling can be stated at any income level, and it is free — Halina's problem was not that she could not afford twelve; by year eight she could, and no signal ever arrived. The cover arrangement is free and reciprocal. And "something in the year that is not the job" does not have to cost money. Three of six are available to anybody; three are not.

A strong answer says which three and stops pretending the other three are decisions — and notes that this is E.3's question and that the honest version of §41.6 would have had a column headed what this costs.

D.6 Rubric. The objection is real: a stopping condition written at thirty-five encodes what mattered to a person at thirty-five, and a person at forty-one has different obligations, a different body, and possibly a different idea of what the work is for. Treating an old document as binding is a way of letting your younger self make a decision they were not qualified to make.

What survives: the stopping condition was never meant to bind — §41.8 says explicitly that its purpose is to give a bad November something to measure itself against, and Noor's told her she was at the warning and not the point, which is a diagnostic function rather than a binding one.

Where the line is, and this is the useful output: a stopping condition should be reviewed annually, in November, with the other two reviews — and changing it is a legitimate outcome of that review. What is not legitimate is changing it in the moment it would otherwise fire, which is the whole reason for having written it down. Reviewed in November: a decision. Revised in the bad fortnight: a rationalisation. A strong answer states that test.

D.8 Rubric. The observation is sharp and the honest answer is that it does not undermine the book, and the reason has to be specific rather than defensive.

What forty-one chapters transmit: everything that can be written down — the arithmetic, the artefacts, the sequences, the failure modes, the scripts, and the questions worth asking. That is genuinely most of the job and it is unavailable anywhere else in this form.

What eleven days of assisting transmit and this book cannot: the things that are only observable. How a room feels at 6:40 when the dinner is late. What a planner's face does when they are worried, and how it does not show. The pace of a real load-out. What it is like to be tired at 11 p.m. and still be pleasant. Those are not withheld by the book — they are not writable.

The strongest version notices that the book says this about itself repeatedly: Chapter 40 D.8's finding that it tests the plan and not the planner; §41.2's ranking that puts eleven days of assisting above every certification; and Chapter 29's instruction to read first-person accounts by disabled people because the chapter cannot substitute for them. A book that told you it was sufficient would be the one to distrust.

M.1

One number, four domains, and the same mechanism each time: it is a multiplier, not a line.

What it means for a career: the single most useful professional habit in this book is asking early and precisely about a number everybody treats as provisional. And the career version of the same insight is Chapter 37's — a planner's own guest count is their client count, and every one of them multiplies overhead, Saturdays, and attention in exactly the same way.

M.3

Three of the five are not about clients and two are not planners. The general form: the person with the most to lose goes first, and what they buy is a room in which the true thing can be said.

M.5 Ch.24 — first mention: Elena is given family tasks at the rehearsal, and Chapter 24's rule — one owner, and lay one person's day on one page — finds that she has eight.

Ch.27 — the day: Elena is a named cue-holder, and the run sheet carries "ELENA touches her arm" as Rosa's cue, because Rosa cannot hear one.

Ch.29 — the guest walk: the access asking, sent by Elena and Sam's mother rather than by the planner, produces eleven replies in four days — including Rosa's June sentence arriving at last. Elena is now both a task-holder and the channel through which the guest information came.

Ch.40 — injection 4: Elena does not answer her phone. Four audits had not found that she had no second name against any of her three tasks, and Rosa's cue is a touch on the arm from a person who is not there. Eleven words at the rehearsal closes it: Beatriz is the second name.

What was noticed, and by which instrument: the over-assignment by Chapter 24's one-page check; the cue's dependency by the run-sheet build; the access information by the asking; and the single point of failure by an injection — because a read-through cannot find it. What remained fragile after all four: Beatriz herself, who is named in six places and described in none — and that was found by the absence test, not by the injection. Two instruments, two different findings, about the same two people.

M.7 Ch.18 — invention. The festoon and the 12 uplighters, and the $12 inline switch at the DJ table — the cheapest item in the lighting plan and the one that makes a cue possible at all.

Ch.22 — the moment. The cue acquires a time and a purpose: 19:20, as the light drops and before the dancing, which is a decision about the evening's arc rather than about lighting.

Ch.28 — protection. The rain plan's first part carries "FESTOON OFF UNTIL 19:20 — uplighters only", because a move to the barn would otherwise have burned the cue by having every light on from six o'clock. The contingency protects a design decision, which is not what contingency planning is usually understood to do.

Ch.40 — transmission. In a four-minute phone call from an ambulance at 06:44, the 19:20 switch is one of three things the departing planner says out loud — because it is in the book and is not salient in it. A stranger ran the cue correctly that evening.

Four chapters: an object, a moment, a defence, and a sentence. And the whole chain exists to produce twelve seconds that no guest will ever consciously notice.

M.9 The same principle in four registers, and each chapter adds a domain.

Ch.21 — tradition. You are not the authority on anyone's tradition. Establish what is required versus what is custom, from the authority, and then propose nothing.

Ch.29 — the body and the person. Ask, do not provide — and never ask anybody to classify themselves. State the facts, offer a specific solution, give a private channel.

Ch.33 — commercial and legal culture. Generalised again: you are not the authority on how business is done here, which produces the question whose answer cannot be yes — "what would have to happen for that to work?"

Ch.38 — your own market. "What do planners get wrong here?" and "what would make you comfortable giving them my name?" — asking the person who knows, instead of assuming.

The single underlying rule: the person in front of you knows something you do not, and the only reliable way to get it is a question that does not require them to explain themselves. Every version fails the same way, too — by a planner providing what they assume is wanted, kindly, and being wrong.

E.1 Rubric. Five people, six identical questions, and the pattern is the deliverable rather than the transcripts.

Ask the same six of everybody, and these work: what do you actually do on a Tuesday in February? · how many Saturdays did you work last year — all three kinds? · what changed at your inflection point? · what would make you stop? · what do you wish somebody had told you? · and who covers you?

Expect the assistant and the fifteen-year planner to give the most similar answers to the last question — both "nobody" — for opposite reasons. Expect the person who left to be the most useful interview and the hardest to get, and to say something close to "I thought I'd failed." Report the pattern, and report anything all five said.

E.3 Rubric. A thousand words, and the arithmetic must be specific rather than gestured at.

The case that it is not viable without a cushion, built from the book's own numbers: runway of three to six months of personal and business costs before you start (Ch.36) · year-one take-home around $11,000 and year three around $26,000 (§41.6a) · a billable ratio of 35–50% in year one, so headline fees are roughly half what they appear · a cash cycle that is negative in December even in a profitable year (Ch.36 B.5) · the first-ten-clients ranking, which advantages anybody whose network already contains people getting married expensively · and four of the six retention factors requiring money or time that a person without a cushion does not have (D.4).

What would have to change, and the essay is strongest here: paid assistantship as a norm rather than unpaid "experience" · a second line of work from year one rather than year seven, which the chapter treats as a maturity marker and which is actually the entry mechanism for anybody without capital · corporate and weekday work early, since it pays on invoice rather than eleven months in advance · coordination as an employed role rather than a solo product (Ch.37 D.2) · and an industry norm of publishing real income data, which is §41.8a's silence and which would let people decide with information rather than with hope.

A defensible conclusion: it is viable, and the standard route is not. The standard route — solo, self-funded, weddings only, from year one — selects for people with a cushion and calls the result talent.

E.5 Rubric. There is no model answer to this one and it should not be marked.

What makes it worth doing: it is written before the experience that will change it, and its value is entirely in being read three years later by somebody who has that experience. Date it, seal it, diary the opening — the diary entry is the part people skip and is the whole exercise.

Two things worth including, because they are what three-years-later most wants to see: what you think the job is for, in your own words rather than the book's, and what you are afraid of. The second is usually the more accurate document.

And the chapter's own version, offered as one answer and not the answer: at 22:16 on the second Saturday in September, nine people were sitting in a lit tent, and two of them would have gone home at nine. They were there because of a paragraph about keeping a tent lit after dinner — which cost nothing, which nobody asked for, and which the couple will never know about.

A hundred small decisions, made months earlier, by somebody paying attention, whose outcome is that a person had a slightly better evening and does not know why. The market does not pay for it and you cannot easily make it visible. So it has to be enough on its own, or it is not enough — and that is the sentence your own version has to answer.