How to Prepare for a MakeX Competition: A Practical Guide for Coaches and Students
By Makeblock | Published: 2026-09-10
Category: How-to Guides
A step-by-step MakeX competition guide for coaches and students, covering rules study, robot kit practice, pit setup, and match-day checkpoints.
Quick answer
Start by reading the current season's MakeX rules and scoring sheet before you touch a robot, then build a practice schedule that mirrors real match conditions. Assign clear roles, log every practice run, and treat the pit checklist as seriously as the robot build. Teams that rehearse the full match loop, not just driving, are the ones that stay calm when the clock starts.
MakeX rewards preparation more than raw building skill. The teams that look effortless on the field usually spent weeks rehearsing the same loop: read the rules, run the match, review the score, adjust the robot, repeat.
This guide walks coaches and students through an ordered preparation process, from the first rules read to the final pit check. Each step includes the mistake that most often costs teams points, so you can spot it before it happens.
1. Read the rules like a scoring judge, not a builder
Before you design anything, print the current season's rulebook and scoring sheet. Highlight every action that earns points, every action that loses points, and every constraint on robot size, motors, or sensors. Coaches should read this once alone, then walk the team through it line by line so students can explain the scoring back to you.
The common mistake is skimming for the robot build section and skipping penalties, autonomous periods, and field setup rules. Those details decide close matches. Keep a one-page summary of scoring actions taped inside the pit box so anyone on the team can check it mid-event.
- Checkpoint: every student can name three ways to score and two ways to lose points without looking at the rulebook.
2. Choose and set up a practice robot kit
Pick a kit that matches the season's task and your team's experience level, then build the stock configuration first. A stock build teaches the mechanical and electronic basics before anyone starts customizing. Once the base robot runs reliably, add one modification at a time and test it against the scoring sheet.
The common mistake is jumping straight to a custom design borrowed from a video. If it fails, the team cannot tell whether the problem is the design, the build, or the code. Keep a stock robot as your known-good reference and change only one variable per practice session.
- Checkpoint: the stock robot completes the core scoring action five times in a row before you modify anything.
3. Build a practice schedule that mirrors match conditions
Set a recurring practice block with a fixed structure: warm-up, timed runs, review, and one change. Use a stopwatch and score each run exactly as a judge would. Rotate roles so every student drives, codes, and acts as the field reset person at least once during the season.
The common mistake is practicing without a clock or score sheet. Untimed practice hides slow routines and shaky autonomous starts. Ten timed runs with honest scoring teach more than an hour of casual driving.
- Checkpoint: log every timed run in a shared notebook with score, time, and one thing to fix next session.
4. Assign match-day roles and rehearse them
Decide who drives, who coaches from the field edge, who handles the robot at the pit table, and who tracks the score sheet. Write the roles on a card and practice them during scrimmages. The pit person should know where every spare part and tool lives without searching.
The common mistake is letting the loudest student make every call. A quiet driver with a calm coach often outperforms a chaotic team. Rehearse a short pre-match routine: check battery, check firmware, confirm the autonomous routine, then hands off the robot.
- Checkpoint: run a full mock match with roles assigned and no adult intervention.
5. Prepare the pit, spares, and power plan
Pack a pit box with spare fasteners, cables, tools, charged batteries, and a printed copy of the rules and scoring sheet. Label everything. Bring a power strip and check the venue's charging rules in advance, because outlet access is often limited at larger events.
The common mistake is assuming you can buy a replacement part on site. Vendors may not stock your specific module. Carry at least one spare of every part that has failed during practice, and note which parts have never failed so you can pack lighter.
- Checkpoint: the pit box closes with every listed item ticked off before you leave for the venue.
6. Plan the final week and match-day morning
In the last week, stop adding features. Freeze the robot design, run full timed matches, and practice the pit routine. Charge every battery, update firmware, and pack the night before. On match morning, arrive early, walk the field, and confirm the field setup matches your practice setup.
The common mistake is a last-minute rebuild the night before. It rarely improves the robot and often introduces a loose cable or a firmware mismatch. If something must change, make it small, test it three times, and write down what changed.
- Checkpoint: the robot completes three clean timed runs on the frozen design before match day.
MakeX preparation checklist
- Study the current rules and scoring sheet: Print the season's rulebook, highlight scoring actions and penalties, and have each student explain the scoring back to you. Checkpoint: students can name three scoring actions and two penalties unaided.
- Build and validate a stock robot: Assemble the kit's default configuration and run the core scoring action repeatedly before customizing. Checkpoint: five clean runs on the stock build.
- Run timed practices with honest scoring: Use a stopwatch and score sheet every session, rotate roles, and log one fix per session. Checkpoint: a written log of timed runs with scores.
- Rehearse match-day roles: Assign driver, coach, pit handler, and scorekeeper, then run a full mock match with no adult help. Checkpoint: one complete mock match with roles unchanged.
- Pack and label the pit box: Include spares of every part that has failed in practice, charged batteries, tools, and a printed rulebook. Checkpoint: every item ticked off before departure.
- Freeze the design in the final week: Stop adding features, run full timed matches, and charge and pack the night before. Checkpoint: three clean timed runs on the frozen design.
Kits and parts that support MakeX preparation
- mBot-S Educational STEM Classroom Kits for Schools & Groups: Engage 1-2 students per pack with 1 robot, with expandable building components, electronics, and toolkit included, and a one-stop solution for teaching programming, electronics, and robotics. Useful for coaches running a school team or club, because one pack covers a small student group and the expandable parts let you add mechanisms as the season's task changes.
- Mini Pan-Tilt Kit for Robot Project: Enables a project to rotate 180 degrees both horizontally and vertically, and can be combined with a Gripper or an Ultrasonic Sensor or IR detector for obstacle detection. A practical add-on when your MakeX task involves aiming, scanning, or grabbing, and a low-risk way to test one new mechanism without rebuilding the whole robot.
- MakerSpace Kits - Electronic Modules 1: Includes Auriga Me BaseBoard, Megapi Pro Me BaseBoard, and other electronic modules, designed for schools to create a MakerSpace and combine parts for maker events or robotics competitions. Suits schools that need a shared electronics pool for multiple teams, so spare controllers and modules are available when a practice robot fails.
MakeX preparation is a repeatable process: know the rules, keep a known-good robot, practice under match conditions, and rehearse roles and pit routines. Coaches who build that loop early give their students the best chance to perform when it counts.


![[Conference] NJTEEA 2024 Annual Conference (New Jersey Technology & Engineering Educators Association)](https://makeblockeun.com/api/image-optimizer?src=%2Fuploads%2Fsites%2F3993%2Fimport-1788944420733-822618999.png&w=400&q=82)
