CyberPatriot · Competition Day Guide
Competition Day Guide
A complete operational guide for the hours before the round, the opening minutes, the main work period, the final checks, and the post-round debrief.
The goal is not to memorize one rigid sequence. The goal is to create a competition rhythm that protects required functionality, keeps the team coordinated, and becomes more conservative as recovery time disappears.
Section Snapshot
Competition-day rhythm
The operating model changes as the day progresses
Before arrival
Protect sleep, confirm equipment, and avoid unnecessary changes to working competition devices.
Before the clock
Set roles, references, communication, and the shared status system.
Opening
Read the scenario, identify constraints, baseline systems, and rank priorities.
Main round
Work in controlled platform cycles with continuous evidence, verification, and documentation.
Late round
Lower risk, finish high-confidence work, and protect known-good state.
After round
Debrief quickly while the details are still fresh and turn lessons into future practice.
Core principles
Eight rules that should survive every competition format
Mission before hardening
Ownership before parallel work
Evidence before remediation
Narrow changes before broad changes
Verification after high-impact work
Documentation while context is fresh
Lower risk as time decreases
Debrief while details are fresh
12-guide pathway
From the night before to the post-round debrief
The cards will become clickable after all twelve guide pages are created and checked so incomplete routes do not produce 404s.
Night-Before Preparation
Focus
Equipment, accounts, chargers, notes, local references, sleep, arrival plan, and avoiding unnecessary last-minute changes.
Outcome
Show up ready to compete instead of spending the morning fixing preventable setup problems.
Arrival & Workspace Setup
Focus
Organize the team area, verify power and networking, place references, assign seats, and prepare the shared status system.
Outcome
Create a calm workspace where every teammate can begin quickly and communicate clearly.
Team Roles & Communication Plan
Focus
Platform ownership, team lead duties, escalation paths, verifier roles, and concise status language.
Outcome
Prevent duplicate work and make ownership obvious before the round begins.
First 10 Minutes
Focus
Do not rush into hardening. Read the scenario, identify required services, assign systems, and establish the first baseline.
Outcome
Use the opening minutes to reduce uncertainty and prevent high-cost mistakes.
Mission & README Extraction
Focus
Pull approved users, required services, remote-access needs, prohibited actions, and special scenario requirements into one team view.
Outcome
Turn the competition instructions into concrete technical constraints.
Baseline & Priority Board
Focus
Capture initial users, services, listeners, privileged groups, network state, important evidence, and ranked priorities.
Outcome
Give the team a known starting point and a clear order of work.
Platform Work Cycles
Focus
Use repeatable inspect, decide, change, verify, and document cycles without forcing every platform into one identical procedure.
Outcome
Keep progress controlled while preserving required functionality.
Evidence & Change Log Discipline
Focus
Record original state, evidence, exact remediation, verification, unresolved items, and ownership while the context is fresh.
Outcome
Create a shared operational record the whole team can trust.
Mid-Round Team Sync
Focus
Pause briefly to compare platform health, unresolved risks, duplicate work, dependencies, and the next high-value priorities.
Outcome
Realign the team before small coordination problems become late-round failures.
Final 30 Minutes
Focus
Reduce experimentation, finish high-confidence work, verify mission functions, resolve ownership gaps, and prepare the final sweep.
Outcome
Shift from broad hardening to controlled stabilization.
Final 15 Minutes
Focus
Freeze risky changes, run platform checks, save known-good network state, confirm documentation, and complete final handoffs.
Outcome
Finish stable, verified, and coordinated instead of creating a last-second regression.
Post-Round Debrief
Focus
Review what worked, what broke, which investigations were slow, which references were missing, and what the team should practice next.
Outcome
Turn one competition round into a better plan for the next one.
Start here
Guide 01: Night-Before Preparation
Competition day begins before the competition. Start by eliminating preventable equipment, account, reference, transportation, and sleep-related problems so the team arrives ready to work.
Start Guide 01 →