Part III: Venue, Space, and Vendors

Chapters 10–13

Part I was conversations. Part II was documents. Part III is the first part of this book where something physically exists.

By Chapter 13 there is a tent on a field, a floor inside it, a generator behind a hedge, seventeen tables through a thirty-two-inch doorway, and a crew of six who arrived at seven in the morning. Everything before this was preparation for the moment when a wedding stops being a plan and becomes an object.

And the object is where all the earlier decisions come due. Chapter 10's venue constraints arrive as line items. Chapter 11's floor plan arrives as a delivery. Chapter 12's vetting arrives as whether the truck comes. Nothing in Part III can be fixed by talking to anyone.

What this part covers

Chapter 10 — Venue Selection treats the venue as what it is: the highest-leverage decision in planning, made first, fastest, and most emotionally. A venue is a set of constraints wearing a pretty dress, and what it lacks determines the budget more than what it has. The seven-step all-in method, the survey visit, the scorecard, and the six conditions under which you say no.

Chapter 11 — Floor Plans, Layouts, and Flow turns measurements into a room. Working capacity, table geometry as a social decision, the five fixed points, three flows that must not cross, and the seating chart — where Chapter 3's decision-rights map finally earns its keep.

Chapter 12 — Vendor Management assembles the temporary company. Eighteen businesses, forty to fifty people, none of whom report to you. Sourcing through networks, the vendor matrix everything else descends from, the failure question, and the RFP that makes three proposals comparable.

Chapter 13 — Rentals and Production builds it. The order line by line, the tent's four subsystems, the power arithmetic, and the load-in as a dependency graph with a deadline.

The idea underneath

Part I's principle was surface it early. Part II's was verify the specific thing against a written standard.

Part III's is: measure it, and then draw it.

Chapter What is measured What the measurement reveals
10 The rain plan's square footage It seats 60 of 140
10 The compass bearing at 4:30 p.m. The guests squint through the vows
10 The doorway The bar must be built inside
11 Mean seat-to-dance-floor distance 43 ft, and nobody dances until 9:40
11 Bar throughput against demand A 158-drink backlog that never clears
12 Loaded rate across three caterers 2.7% apart, and the cheapest menu is not the cheapest
13 Tent + flooring + furniture hours Nine hours in an eight-hour window
13 Watts against usable amperage 9,525 required, 3,840 available

Every one of these is invisible until somebody computes it, and every one of them is available months before it becomes a crisis. None requires expertise beyond arithmetic and a tape measure.

The second half of the principle matters as much: draw it. Case Study 1 of Chapter 13 is a load-in that was correct as a list and impossible as a chain — and the difference was entirely representational. A time-ordered list always looks plausible. A dependency diagram cannot hide a conflict.

What you should have built

If you have done the Project Checkpoints, the Reyes–Whitfield folder now contains:

  • Wildrye Farm priced all-in and scored retrospectively against alternatives, with an honest two-version answer about whether you would have recommended it
  • The rain plan measured — 36 × 54, less the plating area, seating 89 against 100 expected
  • The sun located for a 4:30 p.m. September ceremony, and the aisle rotated because rotation is free
  • A floor plan to scale for both scenarios, with three flows traced and not crossing
  • A seating chart for 100 placing Dennis and Marie Whitfield not-in-the-sightline, Rosa Reyes, and fourteen Midwest relatives who know nobody
  • A vendor matrix of fourteen-plus businesses built from a walk through the day
  • A catering RFP, three proposals compared on cost, scope, and risk, and Sundown selected
  • A complete rental order, a power budget, and a load-in drawn as a dependency chain that finishes at 3:15

The two things Part III could not solve

The barn seats 89 and 100 people are expected. The rain plan does not hold the guest count. A 40 × 50 tent now covers the reception, and if it rains, the barn is still the fallback and it is still eleven people short. That is Chapter 28's problem and it has been sitting in this project since Chapter 10 measured it.

And the allocation was wrong from the beginning. Chapter 13's rental order came in massively over budget — not because it was extravagant, but because venue plus rentals at a raw site is 38% of this budget against Chapter 6's 18–30% band, and nobody ran the check. It takes eleven seconds and it appeared in Chapter 6 as a caution rather than as a line on a worksheet.

That is an honest failure and it is left in the book on purpose. A rule that lives in a paragraph gets read; a rule that lives in a worksheet gets used.

What's next

Part IV is the part people came for. Food, drink, design, flowers, light, and paper — the six chapters where a wedding acquires the qualities a guest will actually describe afterward.

It is also where Part III's constraints stop being abstract. The menu is limited by a field kitchen. The bar plan is limited by a licence and a 10:30 curfew. The lighting design is limited by a generator and a no-open-flame clause. The floral order is limited by September and by a florist who needs the linens down before she can start.

Everything beautiful in Part IV is built inside something specified in Part III. That is not a constraint on the design; it is the design's actual medium, and the planners who are best at Part IV are the ones who understood Part III first.

Chapters in This Part