Case Study 2: One Injury, Seven Parties

⚖️ Educational material, not legal or insurance advice. This traces how a claim typically unfolds in general terms. Liability rules, comparative fault regimes, dram shop statutes, and policy language vary enormously by jurisdiction and by policy. Nothing here states what would happen anywhere. This is a map of the structure, not a prediction.

🔬 Deep Dive. One incident, followed through every party's contract and coverage, to show where responsibility actually lands and why. If you read one thing in this chapter twice, read the "what actually determined the outcome" section.

Tier 3 — Illustrative. The Sørensen–Batra wedding and all parties are composites created for teaching.

The Incident

10:42 p.m. A guest — call her Ms. R, 61, a friend of the bride's mother — steps off the edge of the dance floor onto the grass, catches her heel where the dance-floor edging has lifted about an inch and a half, and falls. Fractured wrist, and a head laceration requiring six stitches.

The planner's assistant reaches her in nine seconds. An ambulance is called at 10:44 and arrives at 10:58. Ms. R goes to hospital, is treated, and is discharged at 3 a.m.

Eleven months later, a claim is filed.

The Facts, as They Emerged

Who Got Named

⚡ The seven, and the theory against each

Party	Theory
Ledgeworth Farm LLC	Premises liability — owned and controlled the property; uneven ground; inadequate lighting
Hollis Event Rentals	Supplied and installed a defective or improperly maintained dance floor
The lighting company	Designed and installed lighting that left a transition area effectively unlit
The bar service	Over-service, if Ms. R was visibly intoxicated
The caterer	Named because their staff crossed the area repeatedly and might have observed the lifted trim
The planner	Operational control; had inspected the area; arguably assumed a duty by doing so
The couple	Hosts; social host theory, jurisdiction-dependent

All seven were named. Four were dismissed within eight months. The couple, the caterer, and the bar service were released — the bar service after producing service records and staff certification, which is the entire reason those documents exist.

Three remained: the venue, the rental company, and the lighting company.

What Each Party's Paperwork Actually Did

This is the useful part.

Ledgeworth Farm LLC — the venue

Coverage: commercial general liability, $2M/$4M.

Contract position: their agreement required every vendor to carry $1M/$2M naming Ledgeworth as additional insured (Chapter 8 §8.5, Chapter 9 §9.4).

What that bought them: the venue tendered the claim to Hollis's insurer and the lighting company's insurer under the additional insured endorsements. Both accepted the tender in part.

The effect: the venue's own policy was not the primary payer, and its own aggregate was not consumed. The additional-insured requirement, which costs a venue nothing to demand and costs a vendor a small endorsement, moved a substantial share of a claim off their balance sheet.

This is why venues insist on it, and why "the venue is being difficult about certificates" is a misreading. They are being rational.

Hollis Event Rentals

Coverage: GL $1M/$2M. Certificate on file, correct entity, venue as additional insured, correct endorsement language. (In this composite, Case Study 1's lesson had been learned.)

Contract position: their agreement had no remedy clause and a liability cap at amounts paid — Chapter 8's Contract A. Irrelevant here, because the claim was from a third party rather than from the client, and a cap in a client contract does not limit a stranger's claim.

🔍 Why Does This Work? This is the distinction that most confuses people, and it is worth stating plainly.

A limitation of liability in a contract limits what the other contracting party can recover. It does nothing about a third party who was never party to the contract.

Ms. R never signed anything. She is not bound by the cap in Hollis's agreement with the couple, or by the indemnification in Ledgeworth's agreement with anyone.

Contracts allocate risk between the people in the room. Insurance is what responds to the people outside it. This is why Chapter 8 and Chapter 9 are two chapters rather than one, and why a planner with excellent contracts and no insurance has protected themselves against exactly the wrong party.

What actually mattered for Hollis: whether the trim was defective on delivery, and whether their installation was proper. Their crew's install checklist — a photograph taken at completion showing the floor and edging intact at 1:15 p.m. — did substantial work.

The lighting company

Coverage: GL $1M/$1M. The venue required $1M/$2M. The certificate had been accepted anyway, because the venue manager checked the per-occurrence limit and not the aggregate.

The consequence: the lighting company had had an unrelated $340,000 claim earlier in the policy year. Their remaining aggregate was $660,000.

In the event, the total claim resolved below that. But it did not have to.

⚠️ Common Pitfall: checking the per-occurrence limit and not the aggregate, and accepting a certificate that does not meet the stated requirement because it "looks close enough." §9.3's eight-point list exists in that order for a reason.

The bar service

Coverage: GL $1M/$2M and liquor liability $1M, separately shown.

What released them: the liquor liability coverage was never called on, because they were dismissed early — and they were dismissed early because they produced, within two weeks: their licence, staff certification records, a written service plan with a stated last call, and an incident log showing that two guests had been refused service that evening.

That last document is why they walked away. A bar service that can demonstrate it refused service to two people that night is a bar service exercising judgment, and it is very difficult to characterize as indifferent.

✅ Best Practice, derived: §9.7's fifth item — a written service plan with a named refusal authority — is not paperwork. In this composite it is the single document that removed a defendant from a case. Ask every bar service for it, keep it in the file, and tell them you are keeping it. A bar service that knows the planner has their service plan on file runs a slightly tighter bar.

The planner

Coverage: GL $1M/$2M and E&O $1M.

The theory against her: she had walked the dance floor edge at 6:15 p.m. and noted nothing, which a claimant characterized as an inspection creating a duty.

What released her: two things.

Her client agreement's limitation of liability (Chapter 8 §8.6) was irrelevant to Ms. R, per the point above — but it did prevent the couple from cross-claiming against her.

What actually mattered was that she had not created the hazard, had not installed the floor, and had no contractual responsibility for its condition. Her 6:15 walkthrough was characterized, correctly, as a coordination check rather than a safety inspection.

But it was argued, and being argued cost her insurer money and cost her nine hours of her own time over eleven months.

🎤 From the Field: the walkthrough problem

There is a real tension here and this book will not pretend otherwise.

Walking the site is good practice. It is what a competent planner does, it catches genuine problems, and Chapter 27 will tell you to do it. It also creates a record of your having looked, which a claimant can characterize as an assumed duty.

The resolution is not to stop walking. It is:

1. Report what you find to the party responsible, in writing, and let them fix it. A text to the rental lead saying "trim's lifted on the west edge, can you sort it" is a coordination act with a paper trail.
2. Do not fix it yourself. §9.1's rule.
3. Do not describe your walkthrough as a safety inspection, in any document, ever. It is a coordination check.
4. Carry E&O and GL, because you will occasionally be argued about regardless.

The planner in this composite did (2) and (4) and had never articulated (1) or (3). Her post-event note read: "walk it, text it, never touch it."

The couple

Coverage: a one-day event liability policy, $1M, purchased for $210 because the venue required it.

They were dismissed at seven months. The policy was never called on beyond a defence cost contribution.

The $210 nonetheless did its job, which was to ensure that when they were named — and hosts are routinely named — there was a defence funded by someone other than them.

What Actually Determined the Outcome

Not fault, in any clean sense. Four things:

1. Who had additional insured status against whom. The venue's requirement moved a large share of the claim onto two vendors' policies before anyone argued about fault.

2. Who could produce documentation quickly. The bar service was released in two weeks on the strength of four documents. The caterer was released because they could show their staff's route did not cross the area after 8 p.m. Documentation is a defence, and it is the cheapest one available.

3. Whether the certificates were correct. The lighting company's inadequate aggregate was accepted by a venue manager who checked one number and not the other, and it created a real exposure that happened not to bite.

4. Who had done the thing rather than coordinated it. The planner was arguable and released; the installer was not.

💰 Run the Numbers: what the paperwork was worth

Party	What they spent on prevention	What it did
Couple	$210 event liability	Funded their defence; dismissed at 7 months
Bar service	Licence, certification, service plan, incident log — cost: staff time	Dismissed at 2 weeks
Venue	Additional-insured requirement — cost: nothing	Tendered to two vendors' policies; own aggregate preserved
Rentals	Install photograph at completion — cost: 30 seconds	Established floor condition at 1:15 p.m.
Planner	GL + E&O premium, ~$900/yr	Defence funded; 9 hrs of her own time regardless
Lighting co.	Accepted an inadequate limit	$660k of remaining aggregate against an open claim

Four of the six most effective preventive measures cost nothing or nearly nothing: the additional-insured requirement, the install photograph, the incident log, and the service plan.

The one that cost real money — the planner's premium — bought a defence but not an absence of trouble. Insurance does not prevent being named. It prevents being ruined by it.

Discussion Questions

1. The planner's 6:15 p.m. walkthrough was used against her. She now says "walk it, text it, never touch it." Is that adequate, or has she over-corrected in a way that will make her worse at the job? What would you do if you found a lifted trim edge at 3:55 p.m. and the rental crew had left?

2. The bar service was released in two weeks because of four documents. Design the standing document request you would send every bar service at booking, and say what you would do if they could not produce an incident log because they do not keep one.

3. The venue's additional-insured requirement cost them nothing and moved a large share of a claim. Is there anything unfair about that? Should a planner advise a client to resist such requirements when the client is the one who ultimately pays for vendors' endorsements?

4. The lighting company's $1M/$1M certificate was accepted by a venue manager who checked one number. Whose job was it to catch that — the venue's, the planner's, or nobody's? What does your answer imply about what a planner is actually verifying and for whom?

5. Ms. R had been drinking and the ground was uneven and the light was poor and the trim was lifted. In a comparative-fault jurisdiction, several of these matter. Without offering a legal opinion, describe how each of the seven parties would want the facts characterized, and what that tells you about why claims take eleven months.

Mini-Project

Build the incident documentation protocol — what you do, in order, when someone is injured at an event.

It must be executable at 10:42 p.m. by a tired person, and it must not interfere with the actual priority, which is the injured guest.

Consider, and sequence: get help first, and do not move anyone · who calls emergency services and from where · who accompanies the guest · who tells the couple, and when · what you photograph, and when · who you notify among the vendors · what you write down that night, before you sleep · what you do not write down · what you send to the venue and when · what the couple should and should not say.

Two hard questions your protocol must answer:

• What do you photograph, and does photographing the hazard help you or hurt you? (Argue it. There is a real tension and the answer is not obvious.)
• What do you write, given that anything you write may be read by seven parties' lawyers eleven months from now?

Then test it: hand it to someone who has never worked an event and ask them to execute it from the top. If any step requires judgment they do not have, rewrite it.

References

Tier 3 — Illustrative. The Sørensen–Batra wedding, Ms. R, and all parties, coverages, and outcomes are composites created for teaching.

⚖️ This case describes the structure of how a multi-party claim tends to unfold. It is not a prediction, not an opinion on liability, and not a description of any jurisdiction's law. Comparative fault regimes, premises liability standards, dram shop and social host statutes, and policy wordings all vary substantially. Nothing here should inform a decision without an attorney.

Related chapters: The chain of liability — Chapter 9 §9.1. Additional insured — Chapter 9 §9.4. Alcohol service and the refusal authority — Chapter 9 §9.7. Contracts allocating risk between parties, insurance responding to third parties — Chapter 8 §8.2. The planner's liability cap — Chapter 8 §8.6. Day-of walkthroughs — Chapter 27. Lighting design at transitions — Chapter 18. Dance floor placement and edge conditions — Chapter 11.