Skip to content

Event Runbook

UOAF Event Checklist DCS

The DCS moderator checklist for standing up the event, staging the briefing, and closing the loop with surveys and debriefs.

DCS Moderator owned AWS hosted Survey driven
  • Some supporting AWS, Drive, and survey documents remain internal and are intentionally not linked publicly from this page.

Roles and Responsibilities

Mission Maker: creates the scenario and briefing products Package Leader: leads the package in game, briefs the mission, and forms the game plan when needed Moderator: executes the checklist, manages event flow, and keeps prebrief and debrief on task

Seven Days Out: Pre-Event Actions

Announce and stage infrastructure

  • Announce the event in Discord as early as possible.
  • Log into AWS sometime before event day and do the following:
  • start DCS_Server.exe and check for updates,
  • start SRS and check for updates,
  • upload the .miz file to the Missions folder,
  • DO NOT forget to shut down the AWS instance once you are done.
  • Use the internal UOAF Google Docs for the detailed AWS operating steps.

Package-lead coordination

  • If the package leader is not already selected, monitor the sign-up sheet for volunteers.
  • If mission complexity requires it, reach out to the chosen package leader by mid-week to form the game plan.
  • If required, distribute updated briefing products they create.
  • If required, coordinate an early meeting of critical roles before event time.
  • If mission complexity does not require this level of pre-coordination, select the package leader before briefing starts.

Survey prep

  • Make sure a survey is ready for the event.
  • Make a copy of UOAF DCS Mission Survey Template.
  • Update the date and title information.
  • DO NOT OVERWRITE TEMPLATE.
  • Be ready to send the survey link by DM after the event.

Event Day: Pre-Briefing

One hour before event time

  • Ping @DCS_Events in #sunday-dcs-events.
  • Include the reminder that marshal is 15 minutes before the hour and the brief starts on the hour.

Thirty minutes before start

  • Join Discord voice and start AWS and log in.
  • Once on the server:
  • start DCS_Server.exe and log in with the UOAF DCS account if prompted,
  • open the DCS Server Web GUI and connect once the server is up,
  • make sure the desired .miz is queued and run it.
  • Use the DCS Server Web GUI correctly:
  • mission pause and restart controls are at the top center of the GUI,
  • server restart controls are in the chat window to the right.

As people join

  • Instruct members in voice to connect to the server and test SRS.
  • Continually remind late joiners to verify:
  • server connection,
  • SRS,
  • keybinds.

On the hour: welcome and frame the day

  • Welcome everyone to the UOAF DCS event.
  • Introduce yourself as the moderator.
  • Introduce the package leader.
  • Introduce and thank the mission maker.
  • Give the room the order of events for the day:
  • Package-level brief.
  • Break into flight-level briefs.
  • Reconvene in the briefing room for package-level questions.
  • Five-minute bio break.
  • Play through the mission.
  • Move to the debrief channel once dead or done for the night.
  • Run an abbreviated debrief from package lead and flight leaders.
  • Announce the official end of the event.
  • Offer the full-length optional Tacview debrief.
  • Ask: Any questions about the order of events for today?

Briefing

Package-level brief

  • Turn things over to the package lead.
  • The package lead should:
  • explain the plan to everyone,
  • brief takeoff and landing order,
  • brief overall package flow and contracts,
  • make sure flight leaders understand tasking and do not have open questions,
  • footstomp critical must complete tasks.
  • Ask: Any package level questions regarding the game-plan?

Flight-level brief

  • Break into channels and complete the flight-level brief.
  • Flight leaders should:
  • explain how their flight fits into the game plan,
  • explain motherhood, threats, weapons, tactics, and contracts,
  • confirm that new players can do what the mission requires.

Reconvene and launch prep

  • Bring members back to Briefing-Voice-Chat after the flight briefs.
  • Have the package lead address any questions that came up during flight briefs.
  • If there are no remaining questions, call a five-minute bio break.
  • Grab a screenshot of attendees for survey follow-up later.
  • Instruct members to mute Discord voice microphones, but not their speakers.
  • Tell members to use in-game chat for technical problems.
  • Instruct members to join debrief once dead or finished.
  • Restart the server mission if required, then declare the event live.

Mission

Live phase

  • Play the mission.
  • Keep moderator attention on flow, timing, and support issues rather than talking over package leadership.

Post-Mission

Debrief and closeout

  • Bring participants to the debrief room as they finish or die.
  • Run the abbreviated debrief promised in the opening remarks.
  • Send the survey link after the event so turnout and quality feedback are preserved.
  • If Tacview or a deeper debrief is offered, explicitly separate it from the official event close.

What Still Lives Outside This Page

  • AWS and server operating instructions in internal Google Docs
  • Mission-specific briefing products and any restricted Drive documents
  • The DCS mission survey template and copied survey instances