Week 16 · overview
overview
Overview
Week 16 opens Unit 6, the course's capstone unit, by building the four foundational documents every later planning step depends on. Students start by writing a one-paragraph opportunity statement that pins down an event's audience, format, and goal before any logistics get decided. From there, they choose a bracket format and write rules specific enough to prevent mid-event disputes, build a match schedule with real recovery time and buffer instead of back-to-back optimism, and close the week by building a risk register that pairs each realistic event risk with a predefined boundary and response. By the end of this week, every student has the planning backbone their real capstone event will be built on in Weeks 17 and 18.
Learning Goals
- Event Vision and Opportunity Statement
- Rules, Brackets, and Fair Opportunity
- Scheduling, Recovery, and Match Rhythm
- Wellness, Risk, and Boundary Register
Esports Workflow
Define the vision -> Set fair rules -> Schedule with buffer -> Register the risks -> Plan the event on paper
Weekly Work
| Session | Focus | Evidence |
|---|---|---|
| Lesson 1 | Event Vision and Opportunity Statement | Written opportunity statement naming audience, format, and goal |
| Lesson 2 | Rules, Brackets, and Fair Opportunity | Chosen bracket format with justification, plus three dispute-prevention rules |
| Lesson 3 | Scheduling, Recovery, and Match Rhythm | Draft match schedule with buffer blocks marked |
| Lesson 4 | Wellness, Risk, and Boundary Register | Risk register with at least three rows and one written boundary |
| Lab | Applied event planning studio | Combined planning packet: vision, rules, schedule, and risk register |
Professional Standard
Real event producers write these four documents before they book a venue or announce a date, because logistics decided without a vision, fair rules, a realistic schedule, and a risk plan tend to fall apart under real conditions. This week's evidence should show specific, usable documents a team could actually run an event from — not vague intentions.