Your job is not to move the robot — it is to score points under pressure, adapt in real time, and execute the plan your team built together.
The driver is the interface between the robot and the game. Your job is not just to move the robot — it is to score points under pressure, adapt in real time, and execute a plan that your engineer built and your strategist designed. All three roles have to work for you to win.
The REC Foundation publishes an official Drive Team Training Course every season. It covers the game rules every drive team member must know — including what referees watch for, how to handle disputes, and alliance station conduct rules.
Every drive team member should complete this before their first competition. It takes about 90 minutes. Covers game rules, safety, alliance station conduct, and how to advocate for your team with referees.
🔗 RECF Drive Team Training Course →These are not suggestions — they are game manual rules. Violations result in warnings or disqualification.
VRC allows three drive team members per alliance station. Most teams use only one or two — that is a mistake. Each person should have a defined job before the match starts. Ambiguity in the alliance station creates hesitation, and hesitation loses matches.
Controls driving and scoring. Eyes on the game piece and field position. Does not watch the timer — that is the caller's job. Does not think about the score — that is also the caller's job. Full attention on executing cycles.
Controls secondary mechanisms — intake toggle, endgame deployment, PTO shift. Frees the main driver to focus purely on movement and positioning. Only used when your robot has enough complexity to justify splitting. Not every robot needs this.
Watches the whole field. Calls the timer at :45, :30, and :15. Tracks the score. Communicates with the alliance partner. Spots opponent positioning and calls defensive moves. The driver should never have to check the timer — the caller tells them.
Decide your communication protocol before queue. During the match there is no time to figure it out.
| Date | Drills Run | Sim Score 1 | Sim Score 2 | Target Metric | Hit Target? | Next Focus | Feel |
|---|
Practice structured. Now make sure your controller mapping is locked and competition-ready.
🎮 V5 Controller Guide →SG12) — no climb, no park.0:00 (per SC5b/SC6) — this drill builds the motor skill of winning that 10-second pushing match. Drill in pairs and alternate roles (push vs. resist) so both drivers learn both halves of the contest.SC7), tracks AWP completion. Critical because Override AWP requires NO violations (SC8 + GG13) — running side-by-side surfaces the routes that brush perimeter or cross the auton line. Strategist tracks: which alliance won the bonus, which (if any) earned AWP, where each robot ended.The #1 beginner failure mode is losing track of which way the robot is facing when it is far from you. These drills fix that.
Drive the robot to the far corner of the field. Without moving, identify which side is the robot's front. Call it out loud. Turn 90°. Call front again. Repeat. Do this until you can identify robot orientation instantly at any distance.
Drive robot behind an obstacle or to the far end. Close your eyes for 3 seconds. Open and immediately drive back to start tile in minimum moves. Trains muscle memory for robot orientation without visual confirmation.
Have a partner stand on the opposite side of the field — their perspective is your robot's "red alliance" view. They call out "left" or "right" commands. You must execute them correctly from your perspective. This forces you to translate robot-relative directions in real time, exactly like a real match when the robot faces you vs faces away.
Drive a cycle. Mid-cycle, your partner says "freeze." You must immediately call the robot's position on the field (e.g., "near post, facing alliance wall"). Builds active field awareness — you should always know where the robot is without looking directly at it.
A driver who can only run their practiced route will max out at a ceiling score. A driver who reads the field in real time adjusts to what the game is giving them and consistently outperforms their practice scores in real matches.
Where are pieces clustered? Which zones are depleted? Are there pieces your opponent has set up that you can intercept? Eyes on the field, not on your robot.
Where is the opponent robot? Are they setting up for endgame early? Are they playing defense on your partner? You do not need to stare at them — a glance every 5 seconds is enough.
Your caller handles the scoreboard. Listen to them. If they say "we are down by 8" you need to know whether to take more risks or protect what you have. This is a conversation, not a decision you make alone.
At :45 you should know whether you have time for one more full cycle or should start working toward endgame. At :25 if endgame is not started you are probably starting it right now. Your caller calls these — but you should already feel the rhythm.
| Situation | Default action | Override if |
|---|---|---|
| Up by 10+ with :30 left | Protect — endgame | Endgame already done |
| Down by 5–10 with :45 left | Score aggressively | Robot is damaged |
| Down by 15+ with :30 left | Defense + endgame | High-value play available |
| Tied at :25 | Endgame first | Endgame risky/unreliable |
| Opponent playing defense on you | Switch zones | Your zone has more pieces |
Run these with your drive team. Nothing should surprise you in a real match.
Call it to your engineer. Pivot to defense or alternate scoring. Keep moving — a stopped robot scores zero.
Know where you need to be at 0:00. Driver control starts wherever you land. Have a recovery plan for every auton scenario.
Agree on zones before the match. If they are in your zone, switch — do not fight. Communicate, pivot, keep scoring.
Decide before the match, not at :30. Your caller tells you the time. You already know the plan. Execute it.
Defense is correct when the math supports it. Ask yourself: will blocking their next cycle change the match outcome more than scoring my own?
Defensive play is legal but referees will not give you the benefit of the doubt. Know these rules before you play defense.
Position your robot in the most valuable zone before the opponent gets there. You are not chasing them — you are making their best move unavailable. Requires reading the field 2–3 seconds ahead.
Follow the opponent robot without contact, staying between them and their scoring target. Slow them down without risking a foul. Works best when you are faster than them.
In the last 10 seconds, contest the midfield to deny opponent center-goal yellow points (SG12). Push to keep them outside the midfield boundary; under SC5b, the alliance with more robots in the midfield owns yellow pins scored in the center goal. High risk — only do this if your own midfield position is secure and the point differential justifies it.
One robot drives offensive cycles. Your job is to stay within 12 inches of them at all times without contact. 90 seconds. If they score, they win. Forces you to read their movement, not react to it.
Pin an opponent against the wall. Count 4 seconds in your head. Release. Repeat. This trains the 5-second pin rule into muscle memory before a match where you will not be counting consciously.
Driver skills is a solo run — no alliance, no opponent interference, no communication pressure. It is a timed test of your route efficiency and consistency. Most drivers treat it like a fast match. Top teams treat it like a discipline of its own.
Draw the field. Mark every game piece. Draw your path with a pencil. Calculate approximate time per cycle. Check total estimated score before you drive it once.
Drive the route at 60% speed first. Get the path right before you add speed. A fast wrong route scores less than a slow correct route.
Score and time each run. Note where you lost time or missed pieces. After 10 runs you will see the pattern — fix the worst point in the route, then repeat.
A route you score 80% consistently beats a route you score 100% on 1 in 5 runs. VEX Forum consensus: repetition is what separates elite skills drivers. Run it hundreds of times.
VEX now has official Virtual Driving Skills — connect your real V5 controller to Chrome and practice on the Hero Bot field. Same controller, different environment. Great for practicing the route when the physical field is not available.
🔗 VEX Virtual Driving Skills →The driver owns auton calibration — not the engineer. The engineer writes the code. The driver confirms it works on this specific field, at this battery level, today.
Every match is data. Run a 2-minute debrief with your drive team after each match before returning to the pit.
VEX Forum veterans have said this for years: the gap between good and great drivers is rarely mechanical skill. It is mental composure. A driver who executes at 80% of their practice speed consistently will beat a driver who peaks at 100% but shakes in elimination matches.
Elite drivers in motorsport, esports, and traditional sports all use pre-performance routines to get to the same mental state every time. Build yours and do it exactly the same before every match — qualifier, elimination, and skills.
Before queue, agree with your strategist on the match plan. One sentence: "We score left side, they score right, endgame at :25." Everyone on your drive team repeats it back.
Shake out your hands, take two slow breaths, loosen your grip on the controller. Tension in your hands telegraphs to the joysticks. Smooth hands, smooth robot.
During disabled, study the field. Where are the game pieces? Where is the opponent robot positioned? What does their setup tell you about their auton? Use every second of disabled time.
Know exactly what your first action is when driver control starts. No hesitation at the whistle. The first 5 seconds set the rhythm for the whole match.
Every driver makes mistakes in a match. The best ones recover in under 3 seconds. The worst ones are still thinking about the mistake 20 seconds later while the opponent scores.
Do not replay the mistake. Do not apologize to your teammate mid-match. Process it after, not during. Your team needs you present right now.
In Formula One the car is configured around the driver — not the other way around. EZ Template and PROS give you the same tools. Every setting here directly changes how the robot feels in your hands. Tuning is not a programmer task — it is a driver task that requires a programmer to implement.
Left stick = left side. Right stick = right side. More precise turning — you control each side independently. Higher skill ceiling. Most top competitive drivers use tank.
Left stick = forward/back. Right stick = turn. More intuitive for new drivers. Curvature drive adds speed-proportional turning for smoother arcs at competition speed.
A linear joystick maps 50% stick deflection to 50% motor speed. An exponential curve maps 50% stick to ~25% speed — giving you finer control at low speeds while still reaching 100% at full deflection.
The third parameter enables exponential scaling. Start with the LemLib default curve value and adjust based on driver feedback. The driver must drive with it — not just code it.
Robot jerks at slow speeds. Overshoots targets. Driver fighting the robot constantly.
Fine control near targets. Full speed feels natural. Driver is not correcting constantly.
Robot feels sluggish to respond. Hard to reach max speed quickly. Driver pushes stick further than needed.
Joysticks do not perfectly return to zero. Without a deadband, your robot drifts slowly when no one is touching the controller. The LemLib expo drive implementation includes joystick and drivetrain deadbands — make sure both are set.
A slew rate limiter caps how fast the motor speed can change per loop cycle. Prevents wheel spin on fast starts, reduces stress on gears, and makes the robot feel smoother. Most important for heavy robots or aggressive drivers.
A macro is a button that executes a sequence of actions — intake toggle, endgame deployment, arm position preset. The goal is to reduce the driver's mental load so they can focus on field awareness, not mechanism management.
The action you fire 20+ times per match goes on R2 or L2 — your index fingers. Actions used once per match go on face buttons. Map by frequency, not by what feels logical.
Under pressure at :25, you will not hit a two-button combo reliably. Endgame deployment is a single button. If your engineer says "we need a safety," add a hold requirement, not a combo.
Ask the driver which hand position feels natural for each action, then code it. A programmer who maps controls without asking the driver is building a robot that fights its operator.
Use these benchmarks to set practice goals. If you do not know what score to aim for, you will not know when you are ready to compete.
| Level | Driver Skills Target | Consistency Bar | Notes |
|---|---|---|---|
| First competition | Any complete run | Finish without stopping | Route completion is the goal |
| Regional competitive | Top 20% regional | 7/10 runs hit target | Consistent route, known weakpoints |
| State qualifier | Top 10% state | 8/10 runs hit target | Route optimized, no wasted seconds |
| State championship | Top 5% state | 9/10 runs hit target | Near-max route, sub-second timing |
| Worlds caliber | Top 50 global | 10/10 near-max | 100s of hours — SigBots level |
The best drivers in any sport watch film. VRC matches are short — a 2-minute match can be reviewed in 6 minutes if you know what to look for.
Any second where the robot is not moving toward a game piece or scoring position is dead time. Timestamp every pause. These become your drill targets — what caused the hesitation?
Count every game piece the robot drove over or past without picking up. Note the angle of approach. Most missed pickups happen at the same approach angle — that is a drill.
When did endgame start? When did it finish? How many seconds were left when it completed? If endgame completed with 8+ seconds to spare you started too early. If it was close, you started too late.
Where was the opponent scoring from? What zones did they own? If you face them again at eliminations you need to know their route. 10 seconds of study per match is enough.
A long competition day is 8–12 matches over 6–8 hours. Hand fatigue, grip tension, and focus degradation are real and rarely discussed.
Click a drill to load its target time into the countdown above. Press Start to begin.
Full drill descriptions — when to use each, metrics, targets — live in the Drill Library.