Key Takeaways — Chapter 9: Insurance, Permits, and Liability

⚖️ Educational summary. Not legal or insurance advice. Work with a licensed broker who writes event coverage, and with an attorney where liability is at stake.

1. A claim names everyone plausibly connected. Seven parties for one wrist. Most will be dismissed; all will have spent money first. Who pays is determined by insurance and contract, not by fault in any intuitive sense.

2. Three consequences. Everybody carries their own — an uninsured vendor pushes the claim onto whoever is insured. Contracts allocate what insurance funds, and neither works alone. And your own exposure is real but bounded by coverage, a liability cap, and discipline.

3. Contracts allocate risk between the people in the room. Insurance responds to the people outside it. A limitation of liability binds the other contracting party; it does nothing about an injured guest who never signed anything. This is why Chapters 8 and 9 are two chapters.

4. Coordinate, do not perform. Serving alcohol, driving a guest, moving heavy or hot equipment, and directing a guest into harm all move you from coordinator to defendant. "Walk it, text it, never touch it" — report what you find to the party responsible, in writing, and let them fix it.

5. Four coverages, and they are not substitutes. General liability — bodily injury and property damage. Liquor liability — a separate coverage, frequently excluded from GL. Professional liability (E&O) — financial loss from your professional error. Event cancellation — sold to the client, named perils, foreseeable perils excluded. A planner needs GL and E&O both.

6. "Wedding insurance" is two products. Event liability (GL for the client) and event cancellation (financial loss). A client who says they "got the wedding insurance" usually bought the first. Ask which, and ask to see it.

7. A certificate is evidence, not a guarantee. Check eight things in order, starting with the named insured against the contracting party, character by character — trading names and dba's produce silent mismatches — and the policy period against the event date. The aggregate can already be consumed by prior claims, and the certificate does not show it.

8. Certificate holder ≠ additional insured. The first is an address and confers nothing. The second requires an endorsement and appears in the Description of Operations box. This looks correct when it is wrong, and it is discovered at load-in or after a claim.

9. Request certificates in month three with the requirement, not the request — the venue's exact legal entity name and address, explicit instruction about the Description of Operations box, the policy period stated as a date, and two deadlines: yours four weeks before the venue's. The margin is the point: a wrong certificate can then be corrected twice.

10. Confirm the venue's exact legal entity name before requesting a single certificate. Six certificates naming a trading name rather than the LLC is an argument waiting to happen, and the fix is one email nobody sends.

11. Build the certificate table from the vendor matrix, not from memory. The categories unconsciously skipped — rentals, transport, tent, lighting, restrooms, generator, parking — are disproportionately the ones with trucks on the property, which is what stops an event.

12. Permits are the raw-site tax. Special event, temporary structure, fire marshal, temporary food service, alcohol, noise, road, parking, generator, propane, sanitation. Lead times of 14–90 days. One named owner and one named date per permit — "the tent company handles it" is an assumption about somebody else's calendar. Use the county's stated lead time, not the vendor's standard practice.

13. Call the county. One sentence describing the event produces a better answer in eleven minutes than hours of searching. Ask the venue first — "has the county ever come out to an event here?" — and verify independently anyway.

14. Occupancy load is not stated capacity. It is set by fire code from square footage, use type, and exits; it changes with the layout; and a tent has its own. The venue's marketing number is not the enforceable one.

15. Alcohol is the most jurisdiction-specific thing at a wedding. Four questions: who holds the licence · who may pour · sale or furnishing · who carries liquor liability. Plus the one nobody asks: who has authority to refuse service? Name them; not the planner, never a family member.

16. Documentation is a defence, and it is the cheapest one available. In the illustrative claim, a bar service was released in two weeks on four documents; a rental company established floor condition with a thirty-second photograph. Four of the six most effective preventive measures cost nothing.

The Certificate Checklist

1. Named insured — exact match to the contracting entity
2. Policy effective and expiration dates — covers the event date
3. Coverage types — GL, plus liquor / auto / workers' comp as applicable
4. Limits — per occurrence and aggregate, against the requirement
5. Certificate holder — confers nothing
6. Additional insured — the one that matters
7. Description of operations — endorsement language, event date, address
8. Cancellation notice

Common Mistakes

• Confusing certificate holder with additional insured — the most consequential error in the chapter
• Not checking the policy expiration against the event date
• Not checking the named insured against the contracting entity
• Checking the per-occurrence limit and not the aggregate
• Assuming GL includes liquor liability — it frequently excludes it
• Assuming E&O and GL are substitutes
• Building the certificate table from memory — five categories get scoped out and one of them has the truck
• Filing permits at the vendor's standard lead time rather than the county's
• Omitting permits and insurance from the budget — $675–$2,800 at a raw site, and in no benchmark
• Letting friends serve alcohol without checking whether that is permitted, and without documenting the conversation
• Helping

Decision Framework — is this vendor cleared to work?

1. Certificate received, and named insured matches the contract exactly?
2. Policy period covers the event date?
3. Limits meet the venue's requirement — both numbers?
4. Venue named as additional insured, with endorsement language?
5. Serving alcohol: liquor liability present, licence on file, service plan with a named refusal authority?
6. Driving or employing: auto and workers' comp as applicable?

A "no" on 1, 2, or 4 is fixable and must be fixed. A vendor who cannot produce a certificate at all is Chapter 8's engagement-stopping signal.

Numbers Worth Remembering

Your Project

You should now have, in Reyes–Whitfield: Section A extracted from the Chapter 8 contract with limits and deadlines, and your own internal deadline justified against §7's dangerously late fourteen days; the vendor tracking table built from the full vendor list; the sample certificate audited with all three problems identified and the correcting email written; a position on the Sundown Provisions entity question; the permit list with owners and filing deadlines and the questions you would ask the county; the one-sentence county call written out; all four alcohol questions answered against §9 of the venue contract, with a named refusal authority and what you say to Alicia about it; and a permits-and-insurance budget line with a stated source of funds.

Part II is complete. Chapter 10 goes back to the venue with everything Part II has taught you.