Week 16 · lesson
Event Operations Lab
Build the operations packet for your capstone event or organization.
Required Packet
Include:
- run-of-show
- bracket or format plan
- result-reporting procedure
- risk register
- owner list
Inspect a Completed Operations Slice
The packet below shows how a run-of-show and response plan make an event recoverable. The names are roles, not required people.
| Time or trigger | Action | Owner | Evidence or response |
|---|---|---|---|
| 3:30 p.m. | Check competitors, format, and equipment. | Operations lead | Checklist is signed before the first match. |
| Match start | Announce the rule version and result-reporting path. | Rules lead | Rule version and reporting channel are visible. |
| Late player | Hold the match for the published grace period, then apply the stated bracket rule. | Operations lead | Record the start time and ruling. |
| Disputed result | Pause bracket advancement, collect the claim and available record, then issue a ruling. | Rules lead and adult lead | Add the ruling to the dispute log. |
| Equipment failure | Stop the affected match, document the interruption, and resume or reschedule under the published rule. | Operations lead | Record the failure and recovery decision. |
Stress Test
Test your packet against one late player, one disputed result, and one equipment failure. Write the response for each.
Quality Bar
A strong packet lets the event continue without improvising every decision.