Skip to content

samber/dev-event-organizer-skills / skills/event-risk-management

event-risk-management

Verified

Build 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.

references/emergency-plan-and-review-cadence.md

View on GitHub
# Emergency plan and review cadence

Two things the register does not do by itself: the printed document the on-site team acts from, and the schedule that stops the register going stale.

## The emergency plan is a separate document

Keep it separate from the register on purpose. The register is a planning artifact read at decision points by the organizing team; the emergency plan is an operational artifact read under pressure by whoever is standing there, including volunteers who never saw the register.

### Named scenarios, written one by one

Write a specific instruction for each, rather than a general "safety incident" section:

- Fire in the venue, including evacuation route and assembly point
- Electrical or power failure, including which circuits the event is actually overloading
- A medical emergency involving an attendee
- Theft of equipment (attendee laptops, event networking or AV gear)
- Evacuation for any other reason, including who confirms the building is clear

These are not ranked and should not be. Their relative priority is set by the venue's own construction, the event format and local emergency-services protocol, not by any value-per-effort calculation. Plan all of them, or state explicitly which ones the venue's own procedures already own.

### Emergency contacts section

- Venue or campus security, with the number that actually reaches a human on the day.
- The **non-emergency** police line, explicitly labeled as distinct from the emergency number, which stays reserved for time-critical situations.
- Every lead organizer, with the specific hours each will be on-site and reachable - not just a name and a number.
- The venue's own on-call contact, and the first-aid provider if one is contracted.

### Distribution - where this document usually fails

Every volunteer needs access, and **a physical printed copy must exist on site**. A contingency plan that lives only in a shared drive fails at exactly the moment its failure modes - power loss, connectivity loss, dead phones, evacuation - are what triggered the need for it. Print it.

### Two practices beyond the document

- **Notify local emergency services in advance** that a large event with many non-local attendees is running. They have their own large-event protocols and may staff on-site or on-call coverage for the duration.
- **At least one organizer must be awake and alert on site at all times** for the full duration of any overnight event. This is a standing operational rule, not a document field, and it needs a rota written before the event, not improvised at 3am.

The honest limit, stated by the source guide itself: it is impossible to prepare for every scenario. The value here is the habit of contingency planning and the contact and distribution mechanics - not an exhaustive scenario list to copy verbatim.

## Review cadence for the register

Scores are time-phased, so a cadence is not administrative hygiene - it is the mechanism that keeps the numbers true.

**Bind the re-score to the decision dates**, so it happens whether or not anyone remembers. At each internal go/no-go date, before the decision:

1. Re-score likelihood and impact for every row at today's distance from the event. Risks that were remote at T-6 months routinely move two bands by T-4 weeks.
2. Close rows that can no longer fire (the venue contract is signed and the deposit paid; that risk is now realized or gone).
3. Open rows for exposure the last period created - every new signed commitment adds one.
4. Check that every orange and red row still has a live owner who knows they own it.
5. Confirm the coverage decisions still match the exposure. Committed spend that has grown past the trigger you set is the most common reason a coverage rung should be promoted mid-cycle.

Between decision dates, the band sets the frequency:

- **Green** rows: checked when the cadence comes round.
- **Yellow** rows: a pre-defined trigger raises them without waiting.
- **Orange** rows: a tightened review interval.
- **Red** rows: reviewed at the highest frequency until they close.

### After the event

Run one closing pass while memory is fresh. Record which risks materialized, which of those had a register row, and which did not. The rows that were missing are the taxonomy gaps to carry into the next edition - that list is the single most valuable artifact this discipline produces, and it only exists if someone writes it down within a week of doors closing.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall