Run this 48 hours before every event — not the morning of. Items you can't check off need time to fix. Completing this list in advance is what separates teams that compete confidently from teams that scramble at inspection.
READINESS0%
⚙ ROBOT
Robot passes full inspection rules
Size, weight, motor count, legal parts
All screws tight, no loose hardware
Shake the robot — nothing rattles
Wiring secured, no bare cables at risk
Every cable routed and zip-tied
Battery fully charged and tested
Run a full match sim on fresh battery
Backup battery and radio checked
Backup battery powers field-legal LED
Controller fully charged
Both primary and partner controller
🔃 AUTONOMOUS
Auton tested 10+ times with 8+ successes
80% minimum before calling it competition-ready
IMU calibration verified after last robot change
48-inch straight-line drift under 1 degree
Auton selector tested on correct routine
Confirm the selector scrolls and locks correctly
Skills autonomous tested and logged
Best run score documented
Code uploaded from clean build
No lingering debug prints or test configs
📝 NOTEBOOK
Every entry dated and in chronological order
Judges check version history and timestamps
Decision matrix for main design choice documented
Problem → Options → Criteria → Selection → Conclusion
At least 2 test data entries with measurements
Specific numbers, not just "it worked better"
Season timeline or milestone page present
Shows project management over the season
BOM or parts list with costs in Appendix
Required for Engineering Award consideration
Student ownership clear — student-written entries
No AI-generated text passed off as student work
🎤 INTERVIEW
Every team member knows their notebook entry
Each person explains their strongest section out loud
EDP explanation practised — all 5 phases
Problem → Brainstorm → Design → Build → Test → Improve
Biggest challenge story ready with outcome
What failed, what you did, what you learned
Outreach entry ready to explain
Who, what, measurable impact
🏆 COMPETITION DAY
Pit kit packed — tools, spare screws, zip ties
Hex keys, star drivers, spare motors, battery
Roles assigned for arrival, inspection, pits
Who does what at each stage of the event
Scouting sheet ready (or app loaded)
Log opponent auton and driver score every match
Match debrief protocol agreed
What you'll say in the 30 seconds after each match
📝
Notebook entry tip:Build & Program — Orange slide (Appendix) — Screenshot this checklist with your check marks as a pre-competition audit entry. Date it and write one sentence about what you found and what you fixed. Judges see documented pre-event preparation as evidence of systematic engineering process.
🎤
How to use this: Read the sample answer to understand what Expert looks like. Write your own version using your actual robot and notebook details. Mark it done when you can say it out loud without reading. The goal is not to memorize — it is to internalize so you speak confidently under pressure.
Grade your notebook before judges do. Score each criterion honestly. Emerging = you have it but it is weak. Proficient = solid but not standout. Expert = judges will cite this as the example. The score matters less than knowing exactly what to improve.
CS concepts behind your robot. Judges ask about the engineering behind your code — not just what it does. Each mission gives you the concept, an analogy, and your interview answer. Mark it done when you can explain it in your own words without notes.