Mission Goal
Build a simple, reliable Ops Run Sheet for a one-session “micro-mission” (a short demo mission your class can run today). Your run sheet must coordinate the room: who does what, in what order, and what to do when something goes wrong.
Why it matters
Real missions don’t fail because people are stupid — they fail because teams are unsynchronised. Command & Control is the art of turning a plan into coordinated action under time pressure.
Inputs from other teams
- Comms Team: how messages/callouts will be sent (verbal call signs, radio-style protocol, or a shared board).
- Data/Telemetry Team: what “success data” looks like (what will be logged, even if it’s just a checklist).
- Payload/Build Team: what the payload does and the key “do not break it” constraints.
- Launch/Platform Team: the launch moment + the critical “go/no-go” checks.
What you must produce (deliverables)
- 1-page Ops Run Sheet (printable): roles, timeline, callouts, and contingencies.
- Role cards (mini): at least 4 roles with one-line responsibilities.
- Go/No-Go checklist (minimum 6 checks) that can be run in under 2 minutes.
Step-by-step
- Name the mission: a 10–15 minute demo mission (e.g., “Sensor Beacon Test”, “Weather Snapshot”, “Camera Burst”).
- Define 4–6 roles: Ops Coordinator, Comms, Data Logger, Payload Lead, Safety, Timekeeper (combine roles if needed).
- Write the timeline: T-10 to T+10 in simple steps (max 12 steps).
- Add callouts: what gets said out loud at key moments (“T-2: final go/no-go”; “T-0: execute”).
- Add contingencies: 3 common issues + what to do (e.g., sensor not reading, comms confusion, missing file).
- Dry run: run it once without hardware (tabletop rehearsal) and fix unclear steps.
Success criteria
- Another team can pick up your run sheet and run the mission with no extra explanation.
- The timeline fits on one page and is readable from 1–2 metres away.
- At least 3 contingencies are included and are actionable (“If X, do Y”).
Evidence checklist
- Photo/scan of the 1-page Ops Run Sheet.
- Role cards (photo or typed list).
- Completed go/no-go checklist from a dry run (tick marks + date).
- One sentence: “Biggest confusion we fixed was…”
Safety & ethics
- No unsafe improvisation. If your run sheet can’t proceed safely, it must include a clear stop rule.
- Comms must be respectful and unambiguous — no shouting, no blame language.
- Data integrity: don’t “pretend” readings; label any simulated/test data clearly.
Common failure modes
- Too long: a run sheet that becomes an essay (ops must be scannable).
- Missing contingencies: everything works “in theory” only.
- Role confusion: two people think they own the same decision.
- No stop rule: the team continues despite unsafe conditions.
Stretch goals
- Add a one-line mission success statement (“We succeed if…”).
- Add a comms script (exact words) for the 3 key callouts.
- Add a “handover” line: how the next team inherits your artefacts.
Scaffolding Example (optional)
You are allowed to reuse structures and formats from other teams — but not their decisions.
Example: “Mission Control Lite” setup
- Roles: Flight Director, CapCom, Safety/Range, Data Recorder, Timekeeper.
- Tools: stopwatch, clipboard, one shared “mission status” sheet, simple whiteboard.
- Callouts: “T-30”, “Range clear?”, “Go/No-Go poll”, “Hold”, “Abort”, “Recover”.
Example: Go/No-Go poll script (30 seconds)
- Flight: “Stations, report Go/No-Go.”
- Each station: “(Role) is Go.” or “(Role) is No-Go because …”
- Flight: “We are Go for proceed / Hold / Abort.”
Example: Minimal mission log fields
- Date, mission name, weather, configuration version, key decisions, outcomes, lessons learned.