Case Study 1: The Truck That Arrived First

Tier 3 — Illustrative. Havershill Meadow, the Lindqvist–Oyelaran wedding, and all vendors and figures are composites created for teaching. The failure — a correct list executed in the wrong order — is the most common load-in failure there is.

The Setup

Havershill Meadow. A hired field with a farm track, a water standpipe, and nothing else. 165 guests. Ceremony 5:00 p.m. in the meadow; dinner and dancing under a 40 × 80 tent.

Access from 8:00 a.m. Guests from 4:30. Eight and a half hours, which is generous.

The planner built a load-in schedule. It was thorough, it listed every vendor, and it was written as a list.

The schedule as written

Time	Vendor
08:00	Tent company
08:00	Rental — tables, chairs, flooring, dance floor
10:00	Generator
10:00	Restroom trailer
11:00	Lighting
12:00	Linens (rental, second drop)
13:00	Caterer
13:00	Bar
14:00	Florist
15:00	Band
16:00	Final check
16:30	Guests

Every vendor is there. Every one has a time. Nothing is wrong with this document except the thing that matters.

What Happened

07:52. The rental truck arrived — eight minutes early, which is a good rental company.

08:04. The tent company arrived.

And the rental crew, following a schedule that said 08:00, began unloading flooring, tables, and chairs onto the ground where the tent was about to be erected.

08:20. The tent lead asked the rental lead to move it. The rental lead pointed out, correctly, that his schedule said eight o'clock and his truck had another delivery at eleven. They moved it — 165 chairs, 21 tables, and 2,400 square feet of flooring, sixty feet to the edge of the field, by hand, in the rain that had started at 8:15.

That took fifty minutes and two people who then had to leave.

09:10. The rental truck departed with the crew, leaving everything stacked at the field edge on wet ground.

09:10 – 13:30. The tent crew erected a 40 × 80 frame tent. Five hours, unaffected.

13:30. Tent complete. And now nobody was there to lay the flooring, because the rental crew had gone.

The planner called the rental company at 13:32. They could send two people at 4:00 p.m.

She and her two assistants laid 2,400 square feet of flooring themselves, in a tent, in the rain, from 13:40 to 16:20. Then they placed 21 tables and 165 chairs, which they finished at 17:05.

The ceremony was at 5:00.

The Downstream Collapse

Everything after the flooring was on the critical path behind it.

💰 Run the Numbers: what the sequence cost

Rental crew return visit, emergency, 2 people	$340
Eleven linens damaged, replacement cost	$610
Florist standby, 3 hrs	$420
Band overtime, ceremony 40 min late, event ran to 11:40	$600
Caterer's additional staff hour, service compressed	$190
Direct cost	$2,160

And the costs with no invoice:

• The ceremony started forty minutes late, in front of 165 people
• Guests arrived to a wedding visibly being built
• The planner and two assistants did four hours of manual labour and then worked a fourteen-hour event exhausted, which is where day-of judgment fails (Chapter 27)
• The florist, the band, and the caterer all had a bad day caused by the planner's schedule, and all three will remember (Chapter 12 §12.8)

The Diagnosis

The schedule was a list of arrival times. It contained no dependencies.

Read it again with the dependency chain from §13.4 in mind:

   TENT ──────────────────────┐
     ↓                        │
 FLOORING                  LIGHTING
     ↓                        │
TABLES + CHAIRS               │
     ↓                        │
  LINENS                      │
     ↓                        │
CENTERPIECES ←────────────────┘

Every single arrival time in the written schedule violated it.

Not one vendor was scheduled after the thing it needed. And the schedule looked completely reasonable, because a list sorted by time always does.

⚠️ Common Pitfall: the list that sorts by time

A load-in written as a time-ordered list has a specific and dangerous property: it always looks plausible. Every vendor has a slot, the slots are spread across the day, nothing overlaps visibly, and the whole thing fits between access and guests.

The dependencies are invisible in that format, and they are the only thing that determines whether it works.

The fix is not more care. It is a different representation: draw it as a chain, with arrows, and ask of every item what must have finished before it can start. Conflicts that are undetectable in a list are unmissable in a diagram — which is exactly what §13.4's Wildrye chain demonstrates.

The Second Failure

The first was the schedule. The second was at 08:20, in the field, and it is the more interesting one.

When the tent lead asked the rental crew to move the flooring, the planner was not there. She arrived at 08:45, after it had been moved.

Two crews, each following a schedule they had been given, resolved a conflict between themselves in the only way available to them — by doing the physical work — and neither of them had the authority or the information to make the better decision, which was for the rental crew to leave and return at 13:30.

🎤 From the Field: be there for the first hour

The first hour of a load-in is when every conflict in the schedule becomes visible, and it is the hour planners most often skip because "nothing is happening yet."

Everything is happening. Trucks are arriving, crews are deciding where to put things, and every one of those decisions is expensive to reverse.

What being there buys:

• You see the conflict at 08:04 instead of hearing about it at 09:10
• You have the authority to send a crew away and bring them back, which no crew lead has
• You can renegotiate a delivery window on the phone while the truck is still loaded
• Crews meet you, which matters for the next fourteen hours (Chapter 12 §12.1 — borrowed authority)

**In this case, one person present at 08:04 saves $2,160 and forty minutes of ceremony.** The decision available at that moment — *"go and come back at one-thirty, and I'll pay the second trip"* — costs $180 and takes ninety seconds.

What It Should Have Looked Like

08:00 ─ TENT CREW. Layout, anchor, frame, canopy. (5 hrs)
        │
        │  ⟵ RENTAL: revised window 13:00–14:00,
        │     agreed at contract stage. Second drop 15:00.
        │
10:00 ─ ├─ GENERATOR sited, fuelled, LIVE
10:30 ─ ├─ RESTROOM TRAILER
        │
13:00 ─ ├─ TENT COMPLETE ─────────────────┐
13:00 ─ ├─ RENTAL TRUCK 1 — flooring ─────┘  (2 hrs)
13:00 ─ ├─ LIGHTING (parallel — rigs to frame)
        │
15:00 ─ ├─ FLOORING DONE ──────────────────┐
15:00 ─ ├─ RENTAL TRUCK 2 — tables, chairs ┘  (2 hrs)
15:00 ─ ├─ BAR built in place
15:00 ─ ├─ CATERER — field kitchen
        │
16:00 ─ ├─ LINENS ──┐
16:15 ─ ├─ FLORIST ─┘
16:15 ─ ├─ BAND — set and sound check
        │
16:45 ─ ├─ ALL COMPLETE. Planner walkthrough.
17:00 ─ ├─ Vendors clear; vehicles moved
17:30 ── GUESTS
18:00 ── CEREMONY

Alt-text: The corrected load-in. The tent runs 8 a.m. to 1 p.m. uninterrupted; rentals arrive in two drops at 1 p.m. and 3 p.m.; lighting runs parallel; bar and caterer at 3; linens and florist at 4; everything complete at 4:45 with guests at 5:30.

Note what changed.

The ceremony moved from 5:00 to 6:00, which is the honest consequence and would have been a month-three conversation rather than a day-of failure. At a September wedding this may not have been acceptable for light reasons (Chapter 10 §10.4), in which case the tent goes up the day before — which is the answer, and which costs a few hundred dollars.

The rental delivery split into two drops. $180.

Nothing was scheduled that could not start.

Post-Mortem

Root cause: the load-in was written as a time-ordered list rather than a dependency chain, so every vendor was scheduled before the thing it required.

Contributing causes:

1. The rental delivery window was accepted as offered rather than negotiated to fit the chain (§13.6).
2. The planner was not present for the first hour, so the 08:20 conflict was resolved by two crews with no authority and no information.
3. The flooring and furniture were on one truck, which meant the flooring could not arrive late without the furniture arriving late too. Splitting the delivery was available and cost $180.
4. The linens were delivered at noon and left in the rain, because nobody had asked where they should go if the tables were not ready.
5. The critical path was never computed. Tent 5 + flooring 2 + furniture 2 = 9 hours from an 8 a.m. start is 5 p.m. The schedule was impossible before anyone arrived, and a five-minute calculation would have shown it.

What went right: the planner and her assistants got it done. The wedding happened. Guests reported a lovely evening.

That is worth saying, because it is how this failure survives: the outcome was fine, so the cause is never examined. This planner had used the same list format for four years.

Transferable rules:

1. Compute the critical path before writing any schedule. Tent + flooring + furniture, added up, against the access window. Five minutes.
2. Draw the load-in as a chain, not a list. A time-ordered list always looks plausible.
3. Negotiate delivery windows to fit the chain, at contract stage.
4. Split deliveries when the items are needed at different points. $180 is cheap.
5. Be there for the first hour.
6. Tell every vendor where things go if they arrive before the thing they need — which for linens is "in the van, or under cover, and call me."
7. If the chain does not fit, the answer is the day before, not a faster crew.

Discussion Questions

1. The rental crew moved the flooring by hand rather than leaving and returning. From their position, was that the right decision? What information did they lack, and whose job was it to supply it?

2. The corrected schedule pushes the ceremony from 5:00 to 6:00. At a September wedding that may be unacceptable for light. Work through what you would do — and note that you are now trading photography quality against a day-before tent fee.

3. The planner used this list format for four years without a failure of this severity. What does that suggest about how planners learn, and about how much a good outcome tells you about a good process?

4. "Be there for the first hour" costs the planner an early start on a sixteen-hour day. Construct the argument for arriving at 11 instead, and then say what you would do about the 08:04 problem.

5. The florist sat in her van for three hours. What does that cost, beyond the $420 standby? (Chapter 12 §12.8.)

Mini-Project

Convert three list-format load-ins into dependency chains.

Find or construct three load-in schedules written as time-ordered lists — one for an all-inclusive venue, one for an à la carte venue, and one for a raw site.

For each: draw the dependency chain, mark every item scheduled before its dependency, and compute the critical path against the access window.

Then answer the question that matters: how many of the three actually work as written?

In most planners' files the answer is fewer than you expect — because a list sorts by time and time is not what determines whether a load-in is possible.

References

Tier 3 — Illustrative. Havershill Meadow, the Lindqvist–Oyelaran wedding, and all vendors, timings, and figures are composites created for teaching.

Tier 2 — Attributed practice. Install durations (5 hours for a 40 × 80 frame tent, 2 hours for 2,400 sq ft of flooring, 2–2.5 hours for 21 tables and 165 chairs) are typical figures and vary with crew size, access, and site conditions. Confirm with your own suppliers.

Related chapters: The dependency chain and the 45-minute margin — Chapter 13 §13.4. Delivery windows and site conditions in a rental contract — §13.6. Access windows as a venue-selection finding — Chapter 10. Being present and reading the site on the day — Chapter 27. What vendors value and the cost of a bad day — Chapter 12 §12.8. The timeline this load-in becomes part of — Chapter 25.