Contingency Planning

Events fail in predictable ways: equipment problems, late players, missing accounts, network issues, unclear rules, stream audio problems, and conduct incidents. Contingency planning names the failure before it happens.

Contingency Format

Use this structure: risk, signal, owner, response, fallback. The fallback matters because not every problem can be solved in time.

Worked Example

Risk: one station cannot launch the game. Signal: setup test fails by 2:50. Owner: tech lead. Response: restart and test alternate station. Fallback: move match to later slot or convert to analysis station.

Artifact: Risk Register

Create five event risks. Each risk needs a signal, owner, response, and fallback.

Common Failure

Do not write "ask teacher" as every fallback. Escalation is valid, but students should define the first response.

Check

A contingency plan is useful when it reduces panic during the event.