overview

Overview

Week 17 shifts from planning documents to live execution. Students build a production runbook that turns the Week 16 schedule into a scene-by-scene script with clear command flow, then build a staffing plan and escalation path so every role knows what it can decide alone and who backs it up when a problem is bigger than one role. The week continues into audience-facing communication — writing and delivering clear announcements about delays, results, and rules — and closes by turning post-event data and feedback into a short, specific, prioritized action list instead of a forgotten survey. Together, these four documents are what a real event team relies on once the event actually starts.

Learning Goals

• Production Runbook Command Flow
• Staffing Plan and Escalation Paths
• Audience Communication and Match Announcements
• Post-Event Data and Feedback Synthesis

Esports Workflow

Script the broadcast -> Staff the roles -> Escalate what's bigger than one role -> Communicate to the audience -> Synthesize what happened

Weekly Work

Professional Standard

Live event production rewards preparation over improvisation. This week's evidence should show a runbook and staffing plan specific enough that someone unfamiliar with the event could step into a role using only the documents, and a feedback synthesis specific enough that it changes something about how the next event is run.