Chapter 34: Large-Scale and Multi-Day Production — Load-In, Crew, and Logistics at Volume

"It's a big wedding." — a planner, about an event with nine trucks

Chapter Overview

Nine trucks are arriving on Tuesday.

Two of them are 53-foot semi-trailers and there is one loading dock. The dock is 3.6 metres wide, it is the only vehicle access to the building, and it is also the route the caterer's van uses, and the route the waste is removed by, and the route the fire brigade would use.

The staging company needs the dock from 07:00. The AV company needs it from 07:00. Neither of them knows about the other, because both of them were booked by somebody who was thinking about what they would build rather than about how they would get in.

And the moment those two facts sit in the same document, the event has stopped being a plan.

This chapter is about what happens above that line, and the line arrives earlier than anybody expects — routinely at events of two hundred people, and sometimes at eighty.

Below it, you schedule tasks: the flowers at ten, the band at four.

Above it, you schedule space, access, and people — and the tasks arrange themselves around what the space will allow. That is a different job with a different document, a different meeting, and a different failure mode.

In this chapter, you will learn to:

• Recognise the threshold, and change method when you cross it
• Build a production schedule with crew calls and a truck marshalling plan
• Size a crew, apply labour rules, and plan welfare properly
• Specify power, water, sanitation, and comms at volume
• Draw a site plan with two circulation systems and an emergency lane
• Run a production meeting that is worth the eleven people in it
• Survive day two, which is where multi-day events actually fail

🏃 Fast Track: Read §34.1 (the threshold), §34.4 (marshalling), and §34.9 (day two) in full. Those three are what a planner crossing into production most needs. Then do B.2, B.6, and D.1.

📖 Standard: Everything.

🔬 Deep Dive: case-study-02.md scales the Northwind production book to three days and finds that the load-in was eleven hours short before anybody had drawn it.

34.1 The Threshold

🚪 Threshold Concept: an event becomes a supply chain the moment two crews need the same space at different times and neither can be moved

Below the line, a conflict is resolved by asking somebody to come later.

Above it, "come later" is not available, because the AV cannot go in until the staging is built, the staging cannot be built until the floor is protected, the floor cannot be protected until the room is empty, and the room is not empty until Monday at six.

What you are scheduling has changed. You are no longer sequencing tasks against a clock; you are allocating a scarce physical resource — the dock, the room, the lift, the hour — among parties who each need all of it.

⚡ Quick Reference: the diagnostic — you have crossed the line when any two are true

Load-in exceeds one working day
More than three suppliers need the same access point	The commonest single trigger
The crew is larger than the guest-facing team
Any element requires another element to be finished first	Staging before AV, floor before staging, power before anything
A vehicle cannot leave the site once it has arrived	A yard problem, and it is always worse than it looks
The event occupies the space overnight	Security, insurance, and a second load-in day
You are hiring labour rather than booking suppliers	A different legal and welfare relationship entirely

A 250-guest marquee wedding routinely satisfies four of these. The size at which this chapter starts applying is much smaller than the word "large-scale" suggests, and a planner who waits for a festival to change method will produce their first supply-chain failure at a wedding.

🎓 Advanced: what actually changes

	Below the line	Above it
The document	A run sheet	A production schedule — §34.2
The unit	A task	A crew, a truck, and an hour of access
The critical path	The guest experience	The build
Who you talk to	Vendors' salespeople	Vendors' production managers. Different people, and they will not be the ones who sold it to you
The meeting	A phone call	§34.7
The failure mode	Something is late	Something cannot happen at all, and you find out on site

The last row is the important one. Below the line, almost everything is recoverable with money or with float. Above it, a load-in that does not fit does not fit, and no amount of anything on the day changes a room that has two crews in it and space for one.

34.2 The Production Schedule

Not a run sheet. A different document with a different shape, covering the days the guests never see.

⚡ The five phases

1. Load-in	Vehicles arrive, goods come off, nothing is built yet	Marshalled (§34.4)
2. Build	Staging, rig, power, floor, décor, dressing	Sequenced by dependency, not by convenience
3. Tech and rehearsal	Focus, programme, sound-check, run the show	The phase that gets cut, and it is the one that pays for itself
4. Show	Chapter 26's run sheet takes over
5. Load-out	Reverse of 1 and 2, compressed into a fraction of the time	Ch.30, at volume

And the phase nobody schedules: the dark day. A day inside the build with nothing on it, used for the things that ran over. On a three-day build it is worth more than an extra crew — and it is the first thing a client asks you to remove.

🕐 From the Run Sheet: a production schedule, two-day build, 400-person event

		Crew	Space
MON 18:00	Room handed over. Previous event out	—	The gate that everything hangs on
TUE 06:00	Floor protection down	House ×4	Ballroom
TUE 06:30	Truck 1 (staging) at dock. 90-min window	Staging ×8	Dock
TUE 07:00	Staging build begins	Staging ×8	Ballroom
TUE 08:00	Truck 2 (AV) at dock. 120-min window	AV ×6	Dock
TUE 09:00	Power distro in. Everything else waits	Electrical ×2	Ballroom — exclusive
TUE 11:00	Rig begins — staging must be at trim height	AV ×10	Ballroom
TUE 12:30	Crew meal 1. All crews. Room is empty for 30 min	—
TUE 17:00	Truck 3 (décor)	Décor ×5	Dock
TUE 19:00	Day 1 ends. Room secured
WED 07:00	Screens and LED	AV ×10	Ballroom
WED 08:00	Breakout rooms — 8 rooms, parallel, different crew	AV ×6	Breakouts
WED 13:00	DARK PERIOD — 3 hours, nothing scheduled		The thing the client asked to remove
WED 16:00	Focus and programme	AV ×4	Ballroom
WED 18:00	Sound check	AV ×4	Ballroom
WED 19:00	Speaker rehearsal — Ch.31	AV ×4 + producer	Ballroom
WED 22:00	Room locked, set
THU 06:00	Doors

Note what the right-hand column is doing. It is a booking system for a room, and every row that says "Ballroom" is a row where nobody else can be in there.

34.2a The Dependency Map

Before a schedule can be written, the order has to be discovered — and the order is a property of the physics, not of anybody's preference.

🎓 Advanced: build the map before the calendar

List every element. For each, ask one question: what must be finished before this can start?

Then draw it. It takes forty minutes and it is the only way to find the critical path.

Room handover ──► Floor protection ──► Staging build ──┬──► Rig / trim │ Power distro ───────────────────┴──► AV install │ │ └──► Catering equipment ├──► Focus ├──► Programme Décor delivery ──► Dressing ◄────────────┤ └──► Sound check │ Speaker rehearsal ◄┘ │ DOORS

Alt-text: a dependency diagram for an event build. Room handover leads to floor protection, then staging build, then rigging. Power distribution branches to both AV installation and catering equipment. AV installation leads to focus, programme, and sound check, which lead to speaker rehearsal and then to doors. Décor delivery and dressing join the chain before sound check.

Three things this drawing tells you that a list cannot.

The critical path is room handover → floor → staging → rig → AV → focus → sound check → rehearsal → doors. Nine sequential steps, and every one of them is somebody else's crew.

Power distro is a choke point serving two branches, which means it must be early and it must be exclusive — and it is routinely scheduled as though it were parallel with everything else.

And dressing is not on the critical path. Which is why décor, which everybody thinks about first, is the element that can move — and it is the one clients most want to protect. The conversation about what gets cut when a build runs late is much easier if this drawing exists.

⚠️ Common Pitfall: the schedule written from the suppliers' preferences

Every supplier is asked when they would like to arrive. Every one of them says early.

The result is a Tuesday morning with five crews in a room where two can work, and by eleven the staging crew is standing still because the AV company has stacked cases where the deck goes.

The dependency map is the answer and the meeting format in §34.7 is how it gets enforced — because a supplier who sees their own row in a walked-forward schedule can tell you it is wrong, and a supplier who was asked "when do you want to come?" has no way of knowing.

34.3 Crew

The largest line, the least understood, and the one with legal and moral obligations attached.

⚡ Quick Reference: the rules that govern crew cost

Minimum call	Typically four hours, sometimes five or eight. A crew booked for ninety minutes costs four hours — so batching work matters more than shortening it
Turnaround	The rest period between the end of one call and the start of the next. Commonly 8–10 hours. Breaking it costs a penalty and, more importantly, produces tired people on a rigging deck
The meal rule	A break within a set number of hours from call — often five. Missing it triggers a meal penalty, which in some agreements escalates per half-hour and gets expensive very quickly
Overtime	After a threshold, usually 8 or 10 hours, at 1.5× and then 2×
Double-time days	Sundays and holidays in many agreements
Travel and per diem	For out-of-town crew

📜 Tier 2 — these are common shapes and every one of them varies by country, by union agreement, by venue, and by supplier. Get the specific terms in writing before you build a schedule around them, because the schedule is what triggers the costs.

💰 Run the Numbers: the meal penalty that ate a budget

A build day. 24 crew across three suppliers. Call at 07:00. Meal rule: a break within five hours.

The rig runs long and the planner, wanting to finish, pushes the meal to 13:30.

Meal due	12:00
Meal taken	13:30
Penalty period	90 minutes, or 3 half-hour increments
Penalty, illustrative, at $15 per half-hour per person** | **24 × 3 × $15 = $1,080
Time actually gained	90 minutes of one crew's work

And the second cost, which does not appear on an invoice: 24 people found out that this planner will push their meal, and every subsequent negotiation on that site is now harder.

The correct move is Chapter 25's: the meal is a fixed point in the schedule and the work moves around it, because the meal is a legal obligation and the rig is a preference.

Sizing a crew

⚡ Rough planning ratios — Tier 2, and every one is a starting point for a conversation with a production manager

Unloading a 53-ft trailer, dock height	4 crew, 45–90 minutes
Same trailer, no dock, tail-lift	4 crew, 2–4 hours. This is the single most under-estimated figure in the chapter
Setting 400 chairs	2 crew, 60–75 min
Setting and dressing 40 rounds	4 crew, 2–3 hours
Ballroom floor protection, 800 m²	4 crew, 60–90 min
Breakout room, standard AV set	2 crew, 45 min per room
Strike is 40–60% of build time, and everybody plans 25%

✅ Best Practice: crew welfare is not a soft topic

Water, available and free, everywhere on site, always. Shade or shelter. A crew room with somewhere to sit that is not a flight case. Toilets the crew may actually use — not "the ones through the ballroom" during a build.

Real food at the meal break, not sandwiches at hour eleven.

And the two that get skipped: somewhere to change and lock a bag · and a named person whose job includes the crew's welfare, which on a large build is a role and not an afterthought.

The argument is moral first and it is also entirely practical. A tired, dehydrated, unfed crew makes mistakes on a rigging deck, and every one of those mistakes is a safety incident with your name near it.

🔄 Retrieval Practice

Without looking back:

1. State the supply-chain threshold, and name three diagnostic conditions.
2. What are the five phases of a production schedule, and what is the phase nobody schedules?
3. Why is a crew booked for ninety minutes expensive, and what does that imply about how you sequence work?

Check

1. Two crews need the same space at different times and neither can be moved. Any three of: load-in over a day · more than three suppliers at one access point · crew larger than the guest-facing team · dependency chains · a vehicle that cannot leave · overnight occupation · hiring labour rather than booking suppliers.
2. Load-in · build · tech and rehearsal · show · load-out. The dark day — a day inside the build with nothing on it, worth more than an extra crew, and the first thing a client asks you to remove.
3. Minimum call, typically four hours — so it costs four. Which means batching work beats shortening it, and a schedule with four separate one-hour visits from the same supplier costs sixteen hours.

34.4 Trucks and Marshalling

The specific discipline that distinguishes production from planning, and the one that has no wedding equivalent.

🚪 Marshalling is the scheduling of vehicles, not of deliveries

A delivery schedule says the staging arrives Tuesday morning.

A marshalling plan says: truck 1, 53-ft, arrives 06:30, holds at the marshalling point on Bexley Road, called forward at 06:25 by radio, at the dock 06:30–08:00, departs empty, and the driver's number is +…

The difference is that the second one is a plan for a physical object that occupies space and cannot be put down.

⚡ Quick Reference: what a marshalling plan contains

Every vehicle, listed — size, contents, supplier, driver's mobile	Including the small ones. A florist's van in a dock at the wrong moment stops a semi-trailer
A dock or bay window for each, with a duration	And the durations are real, from §34.3's ratios
A marshalling point off site	A street, a car park, a lay-by where vehicles wait until called. Without one they queue on the road and you acquire a police problem
Who calls them forward, and how	One named person with a radio and the list. Nobody else releases a truck
The empty-vehicle plan	Where does a 53-ft trailer go after it unloads? If the answer is "it drives away," check that it can turn around
A contingency slot	One window, unallocated, in the middle of the day

🚨 When It Goes Wrong: the yard that had no exit

A courtyard venue. Two trucks in, unloaded, and the courtyard is a dead end.

Truck 1 unloads first and is now behind truck 2, which cannot leave until truck 1 does, and truck 1 cannot reverse out past the marquee stakes that went in at nine.

Three hours, a crane hire quote that was declined, and eventually the marquee's guy lines were slackened and re-set.

The site visit had measured the courtyard. Nobody had asked whether a vehicle could turn around in it, because the question a planner asks is "will it fit?" and the question a production manager asks is "how does it get out?"

💰 Run the Numbers: why the no-dock figure matters

Two 53-ft trailers, 4 crew each.

	Dock	No dock, tail-lift
Unload time each	75 min	180 min
Both trucks, sequential (one bay)	2.5 hrs	6 hrs
Crew hours (4 crew × elapsed)	10	24
At $52/hr loaded** | **$520	$1,248
And the schedule impact		3.5 extra hours on the critical path, which pushes the rig into the second day

The money is the smaller problem. The 3.5 hours is the problem, and it was decided when somebody booked a venue without asking about dock height.

34.5 Infrastructure

Chapter 18 taught power at a wedding. This is the same physics with a different order of magnitude and three more utilities.

⚡ Quick Reference: the four

		The question nobody asks
Power	Load, distribution, redundancy	"Is it clean?" — a generator sharing with a kitchen produces sags that AV does not like
Water	Potable and grey	"Where does the waste go?" A catering tent produces a lot of it
Sanitation	Ratios, servicing, accessibility	"Who services them mid-event, and can the truck get in?"
Comms	Radios, channels, and connectivity	"How many channels, and who is on which?"

💰 Run the Numbers: sizing power for a 400-person, three-day build

	Load
General session AV — LED wall, audio, lighting	48 kW
Breakout rooms × 8	12 kW
Catering — hot boxes, coffee, refrigeration	34 kW
Site lighting, working light, offices	9 kW
Sub-total	103 kW
× 1.25 for diversity and starting current (Ch.18's load factor, at scale)	129 kW
Generator specified	150 kVA — and a second, smaller unit as backup on the AV leg alone

📜 Tier 3 — illustrative loads. Real figures come from each supplier's spec sheet, and a competent electrical contractor sizes the set, not a planner.

Three things worth knowing anyway. AV should be on its own leg or its own generator — a kitchen's compressors cause voltage dips that show up as a flickering screen in front of 400 people. Fuel is a consumable with a delivery schedule, and a three-day event needs a refuelling plan and somebody who owns it. And a backup generator that is not on automatic transfer is a generator that takes eleven minutes to become useful.

⚡ Sanitation, which planners consistently under-provide

	Rough planning guide
Event up to 4 hours, no alcohol	1 unit per 100–120 guests
Event 4–6 hours with alcohol	1 per 75
Over 6 hours, or multi-day	1 per 50–60, plus servicing
Accessible units	At least one, and at least 5% of total — and Chapter 29's distance rule applies: a compliant unit 90 metres away is not provision
Hand-washing	Separate, and more of it than you think
Servicing	Mid-event for anything over 6 hours, with vehicle access that does not cross a guest route

📜 Tier 2 — ratios vary by jurisdiction and many places regulate them. Check the local requirement; it is frequently stricter than these.

⚡ Comms

Radios, not phones — a phone requires you to know who to call and to wait for them to answer. A radio broadcasts to a role.

Channel discipline: channel 1 for production, channel 2 for AV, channel 3 for catering and front of house, channel 4 for security. And one rule: anybody may go to channel 1 and nobody chats on it.

A charged spare for every eight radios, a written channel plan on the wall, and a five-minute briefing at the first crew call that everybody attends — including the people who have used radios for twenty years, because the channel plan is this event's, not theirs.

34.5a Safety, Documented

At this scale safety stops being a matter of care and becomes a matter of paper — and the paper is not bureaucracy, it is how a large site coordinates people who have never met.

⚡ Quick Reference: what a large build actually requires

Risk assessment	Per activity, per contractor	Theirs, not yours — you collect them
Method statement	How a specific task will be done safely. Rigging, working at height, forklift operation	Read them. A method statement you have not read is a document you have collected
Permit to work	For hot work, working at height, confined spaces, and live electrical	A control, not a form
Structural sign-off	Staging, marquees, rigging, temporary structures	A named competent person, in writing
Electrical certification	The temporary installation	Legally required in most jurisdictions
Insurance certificates	Every contractor, current, and checked against the dates	Ch.9, and expiry dates are the thing nobody checks
Site induction	Every person who comes on site. Five minutes: exits, assembly point, first aid, channel plan, who is in charge

📜 Tier 2 — terminology and legal requirements differ by jurisdiction. The concepts are near-universal; the words and thresholds are not. Find out what applies before you build.

🚪 The document that matters most is the one nobody names: a single person who is in charge of the site

Not the planner, necessarily. Not the client. One named person, known to everybody, whose decision stops work.

On a site with eleven contractors and ninety people, "everybody is responsible for safety" means nobody stops anything — because stopping work costs money and nobody wants to be the person who did it on somebody else's judgment.

Chapter 28 said nobody improvises courage at 9:40 p.m. The scale version: nobody improvises authority on a rigging deck at eleven on a Tuesday. It is assigned, in advance, out loud, at the induction.

🔄 Retrieval Practice

Without looking back:

1. What is a marshalling plan, and what question does it answer that a delivery schedule does not?
2. Name the four utilities, and give the question nobody asks about each.
3. Why does "everybody is responsible for safety" fail on a large site?

Check

1. The scheduling of vehicles rather than deliveries — every vehicle, a window with a real duration, an off-site holding point, one named person who releases them, and how does it get out?, which is the question a production manager asks and a planner does not.
2. Power — is it clean? · water — where does the waste go? · sanitation — who services them mid-event, and can the truck get in? · comms — how many channels, and who is on which?
3. Because stopping work costs money and nobody will do it on somebody else's judgment. One named person, known to everybody, whose decision stops work — assigned in advance, out loud, at the induction. Nobody improvises authority on a rigging deck.

34.6 The Site Plan

🪑 On the Floor Plan: two circulation systems that must not touch

┌──────────────── SITE ────────────────┐ │ │ ═══► │ ▓▓▓ SERVICE ROAD (one-way) ▓▓▓ │ ──► exit in │ ↓ ↑ │ │ [DOCK] [WASTE] │ │ ↓ ↑ │ │ ┌────────────────────────────┐ │ │ │ BACK OF HOUSE │ │ │ ├────────────────────────────┤ │ │ │ │ │ │ │ MAIN ROOM │ │ │ │ │ │ │ └──────────┬──────────────────┘ │ │ │ │ │ · · · GUEST ROUTE · · · │ │ │ │ │ [ARRIVAL] │ ╔═══════════════╗ │ │ │ ║ EMERGENCY LANE║ │ ○────┼─────────────┘ ║ 4m, KEPT ║ │ guest │ ║ CLEAR ALWAYS ║ │ drop │ ╚═══════════════╝ │ └───────────────────────────────────────┘

Alt-text: a site plan showing two separate circulation systems. A one-way service road runs along the top of the site, entering at the left and exiting at the right, serving a loading dock and a waste point. Below it sits back of house and then the main room. A guest route, drawn as a dotted line, runs from a guest drop-off at the lower left to the main room and does not cross the service road at any point. A four-metre emergency lane runs separately and is marked to be kept clear at all times.

Three rules and they are the whole of §34.6.

1. The two circulation systems do not cross. Not "rarely cross" — do not cross. Every crossing point is a place where a guest and a forklift are in the same space, and it will happen at the worst moment.

2. The service road is one-way. 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.

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

34.7 The Production Meeting

Weekly from about −8 weeks, then twice weekly, then daily on site. And it is a different meeting from a planning meeting.

⚡ Quick Reference: how it runs

Who	Production managers, not salespeople. The people who will be on site
Length	45 minutes, hard stop
The agenda	The schedule, walked forward in time. Not by supplier — by hour
The output	A revised schedule and a list of actions with names and dates. Circulated within two hours
The rule	Every conflict is surfaced in the room. Nobody resolves a clash privately afterwards, because the third party in the room needs to hear it

Walking the schedule forward by hour rather than by supplier is the whole technique. It is the only format in which two suppliers discover they have both been promised the dock at seven, because it puts them in the same row.

📋 The Planner's Script: opening a production meeting

"Forty-five minutes, and we're walking Tuesday and Wednesday hour by hour.

I'll read out the hour and what I have in it. If that's wrong, say so then — not afterwards.

And the question I want everybody to be asking as I read is not 'can I do my bit.' It's 'is anybody else in my space at the same time.'

Tuesday. Oh six hundred. Floor protection, house crew, four people, ninety minutes, ballroom exclusive."

34.8 People You Do Not Manage

On a large build a meaningful fraction of the workforce is not yours, is not the client's, and does not take instructions from either of you.

🎓 Advanced: who these are and how it works

Venue house crew	Theirs. Often contractually exclusive for certain tasks — rigging, power, forklift operation. Find out at contract, not on site
Union labour	Where it applies, jurisdiction and rules are specific and are not negotiable on the day. The steward is your route, and treating them well is both right and the most practical thing you will do all week
Riggers	A licensed trade with legal responsibility for what hangs over people's heads. A rigger who says no is not negotiating
Licensed contractors — electrical, structural, LPG	Their sign-off is a legal document. Yours is an opinion
Security and stewards	Often a licensed role with statutory duties

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

And the corollary, which planners from the wedding side find hardest: a rigger, an electrician, or a steward saying "no" is the system functioning. The correct response is to ask what would make it possible, not to escalate.

34.9 Multi-Day, and What Breaks on Day Two

🚪 Threshold Concept: a multi-day event is not one event repeated. It is an event plus a reset, and the reset is unscheduled

Day one is planned in detail by people who are fresh.

Day two is the same event run by people who have been on site for fourteen hours, in a room that has been used, with consumables that have been consumed and a schedule that assumed neither.

⚡ Quick Reference: what actually breaks, in order

1	Consumables	Batteries, gaffer, water, coffee, cable ties, printer paper, radio spares, gloves. Day one uses a day's worth. Day two uses more, and nobody ordered three days' worth
2	The reset	The room has to go back to a known state overnight. It takes 90–180 minutes and appears on no schedule
3	People	Turnaround. A crew that wrapped at 23:00 cannot call at 06:00 in most agreements, and should not in any
4	Rubbish	A day's waste has a real footprint and it grows. Somebody empties it overnight or it appears in a photograph
5	Information	Day two's changes have to reach people who were not there for day one's briefing
6	The planner	Chapter 27's attention, across three days rather than one. §34.10

The single fix that addresses four of the six: a scheduled, staffed, named overnight reset, with a checklist, run by people who did not work the day.

🕐 From the Run Sheet: the overnight reset

22:30	Day 1 ends. Guests out
22:45	Reset crew calls — fresh crew, not the day crew	×6
22:45	Room clear, tables re-set, floor cleared
23:15	Consumables restocked from the stores list	The checklist that prevents failure 1
23:30	AV reset to day-2 configuration and tested	Tested, not just reset
23:45	Waste out, bins emptied, back of house tidied
00:15	Walk the room with the day-2 schedule in hand	One person, comparing the room to the document
00:30	Room locked. Day-2 briefing note left for the 06:00 call

Two hours, six people, and it is the difference between a three-day event and one good day followed by two tired ones.

🧩 Productive Struggle

It is 14:20 on the second build day. Doors are at 06:00 tomorrow.

The rig is four hours behind — a motor failed at 09:40 and the replacement arrived at 12:15.

Four things are now true:

• Focus and programme need 2 hours and cannot start until the rig is finished. On the current trajectory the rig finishes at 20:00
• The AV crew called at 07:00. Their turnaround requires 10 hours before a 06:00 call tomorrow, which means they must wrap by 20:00 — and they are the only crew who can do focus
• The speaker rehearsal is at 19:00 and six executives have blocked the time. One flew in for it
• The décor company is due at 17:00 to dress the room, needs 3 hours, and cannot work under an active rig

You have a dark period tomorrow morning from 06:00 to 08:00 that the client does not know about.

Write what you do. Then say which of the four you sacrifice, and how you tell that person.

Think for at least five minutes before opening this

First: the turnaround is not negotiable and everything else arranges around it. It is a rest rule, it is probably contractual, and the people it protects will be on a deck tomorrow. Any solution that starts with "can they stay late" is not a solution.

So the real constraint is: the AV crew has 5 hours 40 left today, the rig needs 5 hours 40, and focus needs 2 more. The arithmetic does not close and no amount of pushing makes it.

What actually resolves it is the dark period you already have. Focus and programme move to 06:00 tomorrow, in the two hours before an 08:00 doors — which requires moving doors from 06:00 to 08:00, which is a client conversation and is the single decision this problem turns on.

Then the rest falls out:

Décor is told at 14:30, not at 17:00 — pushed to 20:00, working after the rig wraps, in a room with no rig activity. They will not like it and it is workable and it is category A: a money problem, if it costs anything.

The speaker rehearsal is the one that gets sacrificed, and it is the right answer even though it is the one with an executive who flew in. Reason: a rehearsal is compressible and a rig is not. It becomes a 45-minute walk-through at 07:00 tomorrow, in the dark period, alongside focus — which is worse than a full rehearsal and is not nothing.

And who you tell, in order, and how fast:

14:25 — the AV production manager, to confirm the plan is physically possible before you sell it to anybody.

14:35 — the client sponsor, and this is the hard one. "The rig lost four hours to a failed motor this morning. I can protect every element of tomorrow if we move doors from six to eight. If we hold six, I lose the speaker rehearsal entirely and I'd be starting the day with a room we haven't tested. I'd like to move doors."

14:45 — the six speakers, once the decision exists. Not before, because six executives given a maybe will produce six opinions.

14:50 — the décor company.

The thing to notice about your own answer: if you tried to keep all four, you were doing arithmetic on a constraint that is not arithmetic. If you sacrificed décor, you protected the visible thing and lost the room's dressing in every photograph — check §34.2a: décor is not on the critical path, which means it can move, not that it can be cut. And if you did not go to the client, you made a decision that costs them two hours of their event without asking — which is Chapter 27's protocol, and this is squarely on the ask side of it.

34.10 Practical Notes

On your own attention. Chapter 27's material, across three days. A planner who works day one at full intensity has nothing for day three. Delegate day one harder than feels comfortable — it is the day you least need to and the only day you can.

On the stores. A locked, indexed, staffed store from load-in. Every large build acquires a pile of things nobody owns, and the pile is where four hours a day goes.

On documentation on site. Printed, and on the wall. Chapter 26's distribution matrix, and at this scale the wall copy is the primary artefact because half the people needing it have no reason to have your email.

On the site walk. Every morning, before the call, with the schedule. Chapter 27's sweep, in a hard hat.

On weather during a build. An outdoor build has a wind limit, a lightning protocol, and a heat plan, and all three belong to the contractor. Chapter 28's §28.5a: their call overrides everybody.

On the thing that is always forgotten: the load-out plan for the client's own belongings. Ch.30's category four, at three-day scale, with eleven trucks leaving.

On pricing. Chapter 37. A production-scale event is not a bigger wedding with a bigger fee — it is more people, more days on site, more liability, and a skill set that is priced differently in the market. Charging a percentage of budget for a build like this is how planners lose money on their largest jobs.

34.11 Summary

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 line arrives earlier than "large-scale" suggests — a 250-guest marquee wedding routinely satisfies four of the seven diagnostics.

And 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.

Five phases: load-in · build · tech and rehearsal · show · load-out — plus the dark day, which is worth more than an extra crew and is the first thing a client asks you to remove.

Crew is governed by rules that the schedule triggers: minimum call, turnaround, the meal rule, overtime. A crew booked for ninety minutes costs four hours, so batching beats shortening — and the meal is a fixed point that the work moves around, because the meal is an obligation and the rig is a preference.

Strike is 40–60% of build time and everybody plans 25%.

Marshalling is the scheduling of vehicles, not deliveries. Every vehicle, a window with a real duration, an off-site marshalling point, one named person with a radio who releases trucks, and an answer to how does it get out? — which is the question a production manager asks and a planner does not.

A trailer without a dock takes two to four hours instead of 75 minutes, and the schedule impact is worse than the money.

Power, water, sanitation, comms — and AV belongs on its own leg, because a kitchen's compressors become a flickering screen in front of 400 people.

Two circulation systems that do not cross. A one-way service road. And a four-metre emergency lane that is nobody's overflow parking.

Run the production meeting by walking the schedule forward hour by hour, never by supplier — because it is the only format in which two suppliers discover they have both been promised the dock at seven.

You do not direct riggers, union labour, or licensed contractors — you sequence them. And one of them saying "no" is the system functioning.

A multi-day event is an event plus a reset, and the reset is unscheduled. Consumables, the room, turnaround, waste, information, and you. The single fix for four of the six is a staffed, named overnight reset run by people who did not work the day.

Spaced Review

From Chapter 13 — deliveries and access. What does it become at this scale?

From Chapter 26 — the run sheet. How does it relate to a production schedule?

From Chapter 18 — power. What is the same and what is new?

📐 Project Checkpoint

Scale the Northwind production book to three days.

400 attendees · the Cascadia Grand · a two-day build into a ballroom that hands over Monday at 18:00 · eight breakout rooms · $121,400 of AV · and a rebuilt agenda with a certification session that did not exist when the AV was quoted.

Produce:

1. The threshold check — which diagnostics does this event satisfy?
2. The production schedule, two-day build, with a space column
3. The crew plan, with meal rules honoured and the strike sized honestly
4. The marshalling plan, every vehicle, with an off-site holding point
5. The site plan — two circulations, one-way service, emergency lane
6. The overnight resets for two nights
7. The production meeting agenda for −6 weeks

case-study-02.md does all seven — and finds that the load-in was eleven hours short before anybody had drawn it.

Looking Ahead

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 one decision than in a hundred compostable forks.