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/cancellation-case-studies.md
View on GitHub# Cancellation case studies
Documented cancellations, what triggered each, and what it cost. Use these to argue a register row is real rather than hypothetical, and to show an organizer what the failure actually looks like.
Confidence varies by case and is flagged per entry. Cite these as evidence that a trigger _category_ is real, not as precise benchmarks.
## COVID-era: the cluster that defined the disease exclusion
### GDC 2020 - postponed 17 days out after exhibitors cascaded
A game-developer conference at 29,000 attendees, 780+ lectures and 550+ exhibitors in its prior year. Following a cascade of exhibitor withdrawals - one platform holder, then a second, then a run of major studios and publishers - organizers postponed the March show on 28 February 2020, under three weeks out. They pledged full refunds to conference and expo attendees and waived cancellation fees on conference-booked hotel rooms.
The instructive detail is where the pain landed: on small exhibitors with no cancellation cover of their own. One indie studio budgeted around £5,000 and recovered roughly half; another reported a loss of around $10,000. Relief funds followed.
**Register lesson: your cancellation decision transfers loss onto every participant who trusted your date, and small exhibitors are uninsured by default.**
Confidence: high - organizer statements and direct quotes from affected exhibitors.
### MWC 2020 - cancelled 12 days out, uninsured, settled with a multi-year credit package
Facing mass exhibitor withdrawal, the organizer cancelled the February show on 12 February 2020, describing it as impossible to hold. It confirmed publicly that its insurance did not cover the loss "due to standard exclusions related to communicable disease", calling the event uninsurable and "probably our worst-case financial scenario".
The initial stance was no refunds, resting on the force-majeure clause of its standard terms. Six weeks later this softened into a compensation package:
- 100% attendee refunds.
- Exhibitors spending under a threshold: a full cash refund, or a 125% three-year fees credit.
- Larger exhibitors: a partial capped cash refund or the credit, stepping down across subsequent editions.
The cash option was withheld from any exhibitor that had withdrawn _before_ the organizer's own cancellation, a deliberate design rewarding those who waited for the organizer's call.
Reported cost:
- As much as 80% of the trade group's annual revenue.
- Roughly 20% of staff cut.
- Non-staff spending pared around 40%.
- A stated three-year recovery.
No completed lawsuit was found; the package appears to have averted a floated class action.
Confidence: mixed. The insurance and staffing statements are organizer-sourced. Barcelona economic-impact and jobs figures widely quoted for this cancellation are _pre-event projections_, not audited losses, and no single audited total was ever disclosed.
**Register lesson: a compensation package is itself a risk-treatment option, and its design (who gets cash, who gets credit) changes participant behavior in the next crisis.**
### SXSW 2020 - cancelled by city order, insured for everything except the actual cause
A large multi-format festival cancelled by municipal order on 6 March 2020, its first cancellation in 34 years. Its chief executive confirmed the event held "a lot of insurance (terrorism, injury, property destruction, weather)" but that "bacterial infections, communicable diseases, viruses and pandemics are not covered".
Critically, **the government order did not rescue coverage** - the exclusion attaches to the peril, not to who ordered the shutdown. Roughly a third of the full-time staff was laid off within days.
The organizer's own post-mortem is the clearest available statement of unpriced tail risk: "We did not anticipate a pandemic. We'd always taken the attitude of, 'Well, we'll never cancel, so that's not going to be an issue.'"
Confidence: high - direct organizer quotes.
**Register lesson: "we have a lot of insurance" is not a risk position. Which perils are excluded is the risk position.**
### E3 - structural decline, not a single cancellation
Distinct in kind: a structural decline across multiple editions rather than a single cancellation.
- 2020: cancelled for COVID, with full refunds and an aborted digital pivot.
- 2021: ran virtually, to mixed reception.
- 2022: cancelled outright.
- 2023: collapsed when major partners declined to attend; the organizer permanently discontinued the show in December 2023.
The stated causes were an evolving marketing landscape, partner withdrawals, and new competitors - publishers had built their own owned announcement channels. Last in-person attendance was 66,100, down from 69,200 the prior year.
**Register lesson: exhibitor defection to owned channels is a risk no insurance policy and no force-majeure clause addresses. It belongs as its own taxonomy row, not folded into "low sales".**
Confidence: high on the sequence and the organizer's stated reasons.
## Since: cancellation risk did not end with the pandemic
### Twin Cities Marathon, 2023 - cancelled hours before the start, insurance actually used
Cancelled on race morning, fully refunding roughly 20,000 registered participants. Organizers stated they funded this from "savings, insurance coverage, and cash reserves" - a rare post-mortem naming an insurance payout as part of the actual response rather than a theoretical backstop. Refunds took up to six weeks to process.
Only the second cancellation in the event's 40-year history - useful as a base rate: even a well-run, decades-old recurring event cancels roughly once a generation, not never.
### Festival International de Louisiane, 2020 - a named, quantified loss
Reported loss of around $500,000 on cancellation. Single-source figure; treat as reported rather than verified if cited.
### Burning Man, August 2025 - an in-progress weather shutdown
Temporarily shut by a dust storm with wind gusts in excess of 45 mph. A different category from the others here: this is interruption of a live event, not a pre-event go/no-go. It is the exposure that parametric weather cover and an in-progress contingency row exist for.
### VidCon, October 2021 - disease resurgence, post-vaccine
Cancelled due to renewed case increases well after the initial 2020 wave and after vaccines existed. Communicable-disease risk did not resolve on a single date; organizers had to keep re-assessing it through subsequent surges.
### UCLA BruinTech Spring Conference, 2024 - organizer discretion, no external trigger named
Cancelled by its board days before the scheduled dates, with no external trigger named in available sources. Useful precisely because of that: organizer discretion is a real, exercised cancellation category, and by definition it leaves the thinnest public paper trail - so a taxonomy built only from well-documented cases omits it.
Confidence for this section: lower than the COVID cluster. These come from trade and local press rather than organizer post-mortems in most cases.
## What the set establishes for a taxonomy
A tech-event cancellation-trigger taxonomy needs, at minimum:
- Communicable disease and public-health restriction.
- Adverse weather, both pre-event and in-progress.
- Organizer financial and payment capability.
- Structural or commercial defection.
- Unstated organizer discretion.
The last two are the ones absent from every generic risk template.
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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |