Master the CS concepts behind your code, prep for judge interviews, build a strong engineering notebook — one mission at a time. All progress saves automatically.
Complete missions in order, practice interview questions, and keep your notebook audit up to date before every competition.
⚠️
Important: This tool helps you understand your work. Never copy content from here into your engineering notebook. The RECF requires all notebook entries to be original student writing. Use Mission Control to learn — then write in your own words.
Team Setup
0/6
Missions Done
0/8
Questions Answered
0%
Notebook Audit
Concept Missions0%
Interview Readiness0%
Notebook Quality0%
💡
Recommended order: Set team info → Team Ownership Map → complete 6 Concept Missions → practice 2 Interview questions per session → update PID Log each practice → run Notebook Audit before every competition.
Team Setup
Ownership Map
Assign each team member their domain. Judges ask everyone — each person should own and be ready to explain their area.
🎤
The interview is like passing a ball. When a judge asks about PID, pass to your programmer. When they ask about sensor mounting, pass to your builder. Practice the hand-off out loud before every competition.
Concept Missions
6 Missions to Master
Each mission: a concept explanation, analogy, exercises, judge-ready language, and a quiz. Complete in order.
Interview Prep
Mock Judge Simulator
8 rubric criteria, real judge questions. Write your answer, self-score, reveal the sample. Practice until it feels natural.
💡
There are 8 rubric points and about 10 minutes. Don't tunnel on one topic — cover all 8 categories. Aim for "Proficient" on every criterion before trying to reach "Expert" on any.
0
Total Score
0/8
Answered
—
Avg /5
Notebook Tool
Entry Builder
Guided prompts to plan your notebook entry. Use this to think — then write in your actual notebook in your own words.
⚠️
Do not paste this output into your notebook. The RECF prohibits AI-generated content. Use this as a thinking scaffold only.
📓
Entry outline ready — use this as a thinking guide. Write the actual entry in your own words, add your data tables, diagrams, and photos.
Notebook Tool
PID Constants Log
Update every time you change a constant. This running log is your single strongest piece of iterative design evidence.
📊
After a competition where autonomous struggled, add an entry explaining what changed and why. Judges love seeing the before/after.
Constants History
Date
Drive kP
Drive kD
Turn kP
Turn kD
Drive err
Turn err
Notes / reason
Notebook Tool
Notebook Audit
Grade your own notebook before judges do. Based directly on the RECF Engineering Notebook Rubric.
0 of 32 checked
0%
⚙ STEM HighlightEngineering: Systems Thinking & Complexity Communication
The judge interview tests your ability to communicate complex systems to non-experts — one of the most valued skills in engineering. Abstractions (like the six judging concepts) are tools for this: instead of explaining every motor PID loop, you explain the concept of feedback control. In systems engineering, hierarchical decomposition means you describe a system at the level of detail appropriate for your audience. Judges are VEX-familiar but not necessarily your robot’s programmers — pitch at that level.
🎤 Interview line: “We prepare for judge interviews by practicing hierarchical explanation — starting at the system level, then decomposing into subsystems as judges ask questions. This mirrors how professional engineers present to stakeholders: executives get the abstraction, engineers get the implementation detail.”
🔬 Check for Understanding
A judge asks “how does your autonomous know where it is on the field?” Your robot uses EZ Template with IMU heading. The best answer is:
“We use EZ Template which handles all the positioning automatically”
“Our robot uses a closed-loop PID controller that corrects heading error using an inertial measurement unit. The IMU integrates angular velocity to track heading, and the PID drives corrections to keep the robot on the commanded path.”
“We don’t use odometry, just drive commands”
“The robot follows a pre-programmed path with exact distances”