Key Takeaways: Large-Scale and Multi-Day Production
The one thing
An event becomes a supply chain the moment two crews need the same space at different times and neither can be moved.
Below that line you schedule tasks.
Above it you schedule space, access, and people — and the tasks arrange themselves around what the space will allow.
The ten claims
1. The line arrives earlier than "large-scale" suggests. A 250-guest marquee wedding routinely satisfies four of the seven diagnostics. A planner who waits for a festival to change method will produce their first supply-chain failure at a wedding.
2. What changes most is the failure mode. Below the line almost everything is recoverable with money or float. Above it, a load-in that does not fit does not fit, and you find out on site.
3. Draw the dependency map before the calendar. Forty minutes. It finds the critical path, the choke point, and — crucially — what is not on the path, which is what can move when a build runs late.
4. A schedule built from suppliers' preferences is wrong, because every supplier says early. The order is a property of the physics.
5. Crew rules are triggered by the schedule. Minimum call means a ninety-minute job costs four hours, so batching beats shortening. The meal is a fixed point and the work moves around it — the meal is an obligation and the rig is a preference.
6. Strike is 40–60% of build time. Everybody plans 25%.
7. Marshalling schedules vehicles, not deliveries — objects that occupy space and cannot be put down. And the question a production manager asks that a planner does not is how does it get out?
8. A trailer without a dock takes 2–4 hours instead of 45–90 minutes, and the schedule impact is worse than the money.
9. Two circulation systems that do not cross, a one-way service road, and a four-metre emergency lane that is nobody's overflow parking.
10. A multi-day event is an event plus a reset, and the reset is unscheduled. A staffed, named overnight reset run by people who did not work the day fixes four of the six failure modes.
Threshold concepts
🚪 An event becomes a supply chain the moment two crews need the same space at different times and neither can be moved.
🚪 Marshalling is the scheduling of vehicles, not of deliveries.
🚪 A multi-day event is not one event repeated. It is an event plus a reset — and the reset is unscheduled.
🚪 Nobody improvises authority on a rigging deck.
With eleven contractors and ninety people, "everybody is responsible for safety" means nobody stops anything. One named person, known to everybody, assigned in advance, out loud, at the induction.
The numbers to carry
| 53-ft trailer, dock | 4 crew, 45–90 min |
| 53-ft trailer, no dock | 4 crew, 2–4 hours |
| Strike | 40–60% of build |
| Minimum call | ~4 hours |
| Turnaround | 8–10 hours |
| Meal rule | within ~5 hours of call, penalty per half-hour per person |
| Power diversity factor | ×1.25 |
| Sanitation, 4–6 hrs with alcohol | 1 per 75 |
| Sanitation, multi-day | 1 per 50–60, plus servicing |
| Emergency lane | 4 m, unobstructed |
| Breakout room AV set | 2 crew, 45 min |
All Tier 2 planning figures. Get the specific terms in writing before building a schedule around them, because the schedule is what triggers the costs.
What this chapter added
Northwind satisfied seven of seven diagnostics, and until week thirty-one its production document was a delivery schedule with eleven rows.
The dependency map took fifty minutes and found that the critical path totalled 29 hours against 29 available — zero margin, arrived at by coincidence.
And the shortfall was in two different units that do not add: four hours of missing path contingency, and seven crew-hours of Wednesday capacity consumed by a certification session added in Chapter 31, against an AV quote written for the old agenda. "Eleven hours short" was the shorthand, and it was two different elevens added together by people in a hurry — which is this chapter's own recurring error, committed in its own case study.
Four changes, none of which cost the client anything. The room handover moved from 18:00 to 15:30 on one phone call, and it had been available all along because nobody had asked. Breakout AV moved to Tuesday, returning seven crew-hours of Wednesday. The truck order was inverted — AV had been first because AV is the biggest supplier, and the dependency map says floor, then staging, then AV. And the speaker rehearsal moved to a worse slot on Wednesday morning, off the critical path — where attendance went from 3 of 6 to 6 of 6, because at 19:00 a rehearsal competes with dinner and at 08:00 it competes with breakfast.
The house electrician volunteered, in a corridor, that the Cascadia's kitchen and ballroom share a distribution board and that an LED wall flickers during dinner service. The hotel has known for two years and it is on no document.
And three things went wrong anyway: gaffer tape ordered at a one-day rate for a three-day build · two breakout rooms double-booked by the hotel's own sales team, resolved in twenty minutes because a signed room list existed · and the crew break room and the speakers' green room colliding, because the space column covered every room where work happened and none of the rooms where people rest.
What is still open
| Goes to | |
|---|---|
| A venue's institutional knowledge lives in individuals and a planner benefits by accident. A per-venue file, forever | Ch.39 |
| Quantity derived from the wrong unit — tape per day rather than per crew-hour. Third instance in three chapters | Ch.39, Ch.40 |
| An instrument's gaps are invisible from inside it. The space column allocated work, never rest | Ch.40 |
| The first production meeting should happen when the largest technical supplier is appointed, not at −6 weeks | Ch.39 |
Spaced review
From Chapter 13: access becomes a marshalling plan, and Chapter 13's question was "will it fit?" where a production manager asks "how does it get out?"
From Chapter 26: the run sheet covers the show and its unit is a cue; the production schedule covers the days guests never see and its unit is a crew, a truck, and an hour of access. What is added is a space column — a booking system for a room.
From Chapter 18: same physics, three new problems — quality (AV on its own leg), fuel (a consumable with an owner), and automatic transfer — plus a governance change: a licensed contractor's sign-off is a legal document where yours is an opinion.
From Chapter 28: the rigger who says no is the system functioning, and the correct response is to ask what would make it possible, not to escalate.
From Chapter 27: the sweep, in a hard hat, every morning before the call, with the schedule in hand.
Before Chapter 35
Chapter 35 is sustainability, and it closes Part VII by asking what all of this costs something other than money.
Bring this chapter's arithmetic. Chapter 35's argument is that most event sustainability is theatre, that the real numbers are dominated by two things nobody puts on a checklist — and that a planner who knows which two can do more in a single decision than in a hundred compostable forks.