samber/dev-event-organizer-skills / skills/event-risk-management
event-risk-management
VerifiedBuild and maintain the standing risk register for a technical event - risks named by category, scored on a likelihood x impact matrix adapted to a dated one-shot deliverable, split into prevention, contingency or insurance, the insurance stack including the communicable-disease buy-back, internal go/no-go decision dates set against the venue's escalating cancellation-fee curve, and the on-site emergency plan. Use whenever the user mentions event insurance, cancelling or postponing an event, a go/no-go call, an emergency or evacuation plan, weather or speaker-dropout contingency, or a risk register - even if they never say "risk". Not legal or insurance advice. Do NOT use for day-of live incident handling - use samber/dev-event-organizer-skills@event-run-of-show instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.3 KB |
| evals/evals.json | config | 37.4 KB |
| references/cancellation-case-studies.md | markdown | 7.3 KB |
| references/emergency-plan-and-review-cadence.md | markdown | 4.4 KB |
| references/go-no-go-and-force-majeure.md | markdown | 5.8 KB |
| references/insurance-coverage-types.md | markdown | 7.4 KB |
| references/risk-taxonomy-and-scoring.md | markdown | 9.7 KB |
references/go-no-go-and-force-majeure.md
View on GitHub# Go/no-go decision dates and force-majeure practice
The liability curve the decision dates hang on, the polling mechanic, and what post-COVID contract practice established about clause language.
**Not legal advice.** The case outcomes below illustrate why clause wording decides money.
They are not a rule you can apply to your contract. Send the actual clause to counsel.
## The escalating liability curve
Venue and hotel cancellation clauses use a tiered, days-out sliding scale. Representative structures - every contract negotiates its own, so read yours rather than assuming these:
- 90+ days out ≈ 50% of expected revenue; 30-90 days ≈ 70%; under 30 days ≈ 90%.
- Another real clause: 0-29 days = 100% of estimated event cost; 30+ days = 75%.
Useful negotiating pushback: hotel room profit margin runs around 75%, so a flat 100% cancellation fee is hard to defend as liquidated damages except very close to the date. A penalty with no relationship to actual harm is generally unenforceable, though that turns on jurisdiction.
**This curve is the entire reason decision dates exist.** The fee is not a smooth function of time; it steps. Every step is a date on which waiting got materially more expensive.
## Placing the decision dates
Track every scheduled fee step-up in the contract and set an internal go/no-go decision date **just before** each one - never at the event date, and never at a round-number interval that happens to fall after a step-up.
The tension this manages is explicit: waiting longer lets facts develop that might support a force-majeure claim, but risks incurring an escalated cancellation penalty if the clause ultimately does not apply. Because the legal outcome is never guaranteed, cancelling earlier and accepting a lower step-up fee can beat waiting for certainty.
### Room-block attrition is a second, parallel cliff
Where the contract includes a room block, an attrition clause (for example, 80% pickup required on 100 room nights) creates its own financial trigger on its own schedule. Two practices worth adopting: negotiate **cumulative** attrition rather than day-by-day, and monitor registration pace closely enough to renegotiate the block size _before_ the penalty triggers rather than arguing it after.
## The polled go/no-go call
The format - each area owner votes go or no-go, a single no-go halts the sequence - comes from mission-control practice and is recommended for events by several operational-readiness practitioners.
Its value is procedural, not terminological: **the thresholds are fixed before the meeting**, so that emotional outcomes and sunk cost cannot move the goalposts once everyone is in the room. That is the whole mechanic. A go/no-go call where the criteria are agreed in the call is just a meeting.
Areas typically polled:
- Registration or ticket pace against break-even
- Room-block pickup against the attrition threshold
- Speaker and sponsor confirmation status
- Permit and regulatory status
- Safety, security and travel conditions
- Contractual exposure: which cancellation deadlines and attrition dates have already passed
- Payment integrity: can we actually collect and refund
- Brand and public-image exposure
### Conditions that should move the decision toward no-go
- Registration pace below break-even inside the last affordable fee window.
- Room-block pickup below the attrition threshold, with no realistic resale prospect.
- Loss of an uninsured marquee speaker.
- A credible governmental restriction or safety threat.
- A force-majeure event whose contract language does not clearly guarantee a refund.
## Force-majeure clause practice after 2020
### The refund outcome turns on one sentence
A New York court ordered a full deposit refund because the clause expressly stated the venue "shall refund all payments". A Hawaii case denied a refund on essentially the same fact pattern because the clause was silent on returning deposits. The pair is the canonical illustration that force-majeure protection is only as good as the specific words negotiated in advance.
Practical consequence for an organizer: insist on explicit refund language when the contract is being negotiated. Do not assume the phrase "force majeure" alone settles anything.
### Foreseeability forced named carve-outs
Industry contract guidance since 2020 holds that because disease epidemics, terrorism, labor disputes and hazardous weather are now _foreseeable_, they must be named in the contract - otherwise a court may find the organizer accepted the risk by not naming it. This is why pandemic and communicable-disease carve-outs became explicitly negotiated clauses rather than being left to generic "acts of God" language.
The forward-looking implication matters more than the pandemic example: a force-majeure event list is not boilerplate. Review and update it as new foreseeable risks emerge, the same way "pandemic" had to be added.
### Credit-versus-refund and rebooking became a negotiated line item
Organizers now push for rebooking clauses - for example, applying 100% of fees paid as a one-time credit toward a future event within 12 months - alongside attrition and cancellation relief. Some organizers use generous cancellation terms (full refunds up to 90 days out, nominal cancellation fees) deliberately as a trust-building sales posture rather than only as a legal fallback.
Frustration-of-purpose arguments rarely rescue an organizer where the contract already allocated the risk or contains explicit no-refund language. The credit or rebooking clause has to be negotiated up front, not argued afterward.
### The same shift reached sponsor and speaker agreements
Force-majeure definitions in sponsor agreements expanded to cover governmental restrictions and regulations explicitly, with refund or credit treatment specified rather than left implicit. The discipline is identical across contract types: name the foreseeable risk, then specify the money outcome.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |