// PATTERN B · OPERATIONS DASHBOARD · PRE-COMP
Competition Prep Checklist
Consolidated pre-comp checklist across T-14, T-7, T-1, day-of, and post-event phases. Replaces scattered "what do I do before a comp" tribal knowledge. Each item has an owner and a target completion date relative to the event.
Last updated: 2026-05-12 · Owner: Coach + Team Leads · Companion to /mission-control
How to use this page: work backwards from your next event. If the event is on a Saturday, T-14 phase covers items due by the Saturday two weeks before. Each item has an owner role; that role checks the box. If an item is blocked, escalate in
/season-hq instead of letting it slide.
T-14Two weeks out
Engineering · Inspection-ready check
- Every active bot passes a full inspection rehearsal (R1-R30 walkthrough). Fix issues now, not the night before.EngineerRECURRING
- Polycarbonate piece count audited per bot — R24 compliance verified.EngineerRECURRING
- Pneumatic system pressure-tested per bot (if equipped) — no leaks, regulator set, dump valve verified.EngineerRECURRING
- Spare parts kit inventoried — motors, gear cartridges, screws, zip ties, batteries (3+ per bot).EngineerRECURRING
Notebook · Draft submission
- Notebook draft for the event submitted to coach for review. Covers current sprint + all phases through current.NotebookRECURRING
- Judge interview talking points written and rehearsed by 2 students minimum.Notebook + StrategistRECURRING
Strategy · Match data prep
- Opponent scouting sheet template printed and rehearsed (one strategist per pair of matches).StrategistRECURRING
- Pick list template prepared — tiers based on observed strengths from prior events.StrategistRECURRING
T-7One week out
Programming · Code freeze
- Code freeze on competition branch. No new features after T-7. Only bug fixes for known regressions.ProgrammerRECURRING
- All autonomous routines verified in scrimmage conditions. AWP routines tested 5+ times each.Programmer + DriverRECURRING
- Sensor calibration values committed to repo; no last-minute tweaks at the venue.ProgrammerRECURRING
- Auton selector tested — UI changes locked.ProgrammerRECURRING
Driver · Practice ladder complete
- Per-bot driver practice ladder completed — minimum 4 sessions in the week before the event.DriverRECURRING
- Assigned drills from match-analysis are run to completion (8/10 pass rate).DriverRECURRING
- 2 mock-match scrimmages run with full alliance coordination practice.Driver + CoachRECURRING
Logistics · Travel + packing
- Travel plan confirmed — vehicle, departure time, ETA at venue. Email to all parents.CoachRECURRING
- Packing list reviewed; team members confirm individual items (lunch, water, layers, charger).Coach + TeamRECURRING
- Robot transport plan: which bots, what crates, weight check on vehicle.EngineerRECURRING
T-1Day before
Engineering · Final inspection
- Final inspection pass on every competing bot. Tighten everything. Photo of pass complete.Engineer + CoachRECURRING
- Charge all 3+ batteries per bot. Label each with bot assignment.EngineerRECURRING
- Charge controllers + tablets. Confirm wireless tethering works.Programmer + DriverRECURRING
Programming · Code state lock
- Final code committed and tagged. Brain downloads verified one last time.ProgrammerRECURRING
- Bring laptop with PROS environment intact and spare USB-C cable.ProgrammerRECURRING
Notebook · Final binding
- Notebook printed and bound (or digital copy ready on judging tablet).NotebookRECURRING
- Interview team rehearses one final time. Includes recent build photos.Notebook + Strategist + CoachRECURRING
Logistics · Day-of details
- Wake time set; breakfast plan. Coach's pre-departure call sheet.CoachRECURRING
DAY-OFEvent day execution
Arrival · First 90 minutes
- On-time arrival; pit setup complete by 30 min after doors open.AllRECURRING
- Inspection queue — engineer escorts each bot.EngineerRECURRING
- Pit sign posted with team name, school, sponsors.CoachRECURRING
- Practice fields visited — one warmup run per bot before qualifying.Driver + EngineerRECURRING
Qualifying matches
- Pre-match alliance comms (radio or face-to-face) for every match before the queue.Driver + StrategistRECURRING
- Scouting captures opponent observations per match — goes into /scouting-center.StrategistRECURRING
- Post-match: 2-min triage on bot — loose screws, motor warmth check, battery swap.EngineerRECURRING
- Quick "what happened" debrief between driver and strategist after each match (under 3 min).Driver + StrategistRECURRING
Judging
- Notebook ready in pit; interview team available throughout the day.NotebookRECURRING
- Judges visiting the pit — all members present, robot demo ready.AllRECURRING
Alliance selection · Eliminations
- Pick list finalized by end of qualifying. Strategist + Coach + Driver align.Strategist + CoachRECURRING
- If picked or picking: alliance partner intro + match plan discussion.Coach + StrategistRECURRING
Day-of failure mode to watch: the panic-rebuild loop. If a bot has a major mechanical failure, repair to just-functional, not to "improved." Improvements introduce new failure modes mid-event. Use the spare bot if available.
POSTPost-event retrospective
Same-day or next-morning
- All match observations entered into /match-analysis within 24 hours.Strategist + DriverRECURRING
- Mechanical issues observed during event → logged in /season-hq build queue.EngineerRECURRING
Within the week
- Trend tracker reviewed in match-analysis — patterns across the event identified.Strategist + CoachRECURRING
- New drill prescriptions added to the practice plan based on event review.Coach + DriverRECURRING
- Notebook updated with event reflection (judges' feedback, scoring observations, lessons).NotebookRECURRING
- If this was a qualifying event: post-event team meeting to discuss what to change before next event.AllRECURRING
Using this page
This is a template. Before each event, copy this checklist into a per-event tracker (or print it) and check off items as the team progresses. The list lives here as the canonical source — if something needs adding, edit this page so the next event benefits.
The owner column tells you who's accountable. If you're a Driver looking at "code freeze on competition branch" — that's not your check, but if you don't see it shipped by T-7, escalate to the Programmer.