V5RC allows up to three students in your alliance station during a match. Three students, three jobs — and the right split depends on what game you're playing and what kind of robot you've built. This guide walks through the configurations and recommends what works best for Override.
Per the V5RC game manual (rule G1 / GG1), each team can field up to three drive-team members in their alliance station per match. All three must be students (not adults), all from your own team, and all defined for the match before queue.
Most teams use only one or two of their three slots, and that's a real mistake. An empty third slot is information you're not gathering, decisions you're not making, and physical work the driver has to do alone. If you have the students, fill the seats.
Some hard rules that constrain how you assign roles:
Three patterns work for different teams and seasons. We recommend Configuration C for Override and most load-heavy seasons; B is the lighter alternative; A is rarely the right call for our team.
When to use: Load-heavy season (Override has loaders for cups), competitive team with engineer and strategist students available, robot is single-controller. This is the default we recommend for Spartan teams in Override.
Why this works: The Engineer is the only person on the drive team with the mechanical fluency to spot robot trouble in real time — loading puts them at the field perimeter where they can see the robot constantly. The Strategist is hands-free for analytical work. No overlap between the two non-driver roles.
When to use: Engineer student isn't available for that match, OR the team has a dedicated loader student who isn't the engineer. The Loader still loads, but doesn't have engineering-trained eyes on the robot.
Tradeoff: No dedicated engineer eyes on the robot. The Strategist can catch obvious problems (smoke, dropped piece, big wobble) but won't catch subtle wear/binding the way an Engineer would. Acceptable backup config when needed.
When to use: Robot is complex enough to need TWO controllers (one driver for drive + primary mech, one operator for secondary mechanisms). No match-loaders to staff (rare in V5RC). Mostly seen in older seasons or specialty robots.
For our teams: Override Hero Bot V1.5 is single-controller (8 motors, all on one V5 controller). We won't use Config A this season. Mentioned here because some legacy guides still reference it.
Putting the engineer in the loader slot is non-obvious. Most public V5RC guides default to "Driver / Loader / Caller" with three different students each having a single specialty. The engineer-as-loader pattern is something more competitive teams converge on for specific reasons.
During a match, the driver is focused on execution — their attention is downstream of the robot, on the field. The strategist is watching opponents, score, and time. That leaves no one watching the robot itself for problems unless someone has the trained eye to do it.
An Engineer at the loader sees:
None of these are catastrophic by themselves. All of them, caught early, let the team adjust between matches before the failure cascades. A non-engineer drive-team member won't notice them.
Loading a cup takes about 2 seconds: pick up cup, drop into loader. Per match, even at flood-mode pace, that's under 30 seconds of active loading work in a 1:45 match. The other 60+ seconds, the Engineer's eyes are on the robot. Adding "watch the robot" to their job costs zero extra mental effort.
Calling the timer, tracking score, watching opponent moves, reading alliance partner state, deciding when to switch from offensive to defensive play — this is concentrated decision-making. Asking the strategist to also handle physical loading splits their attention badly. They miss timer marks. They forget which loader they were filling. They drop pieces.
Letting the strategist be hands-free protects the role they're actually best at.
In Config C, the three students do three completely separate things:
That's different from configurations where two students are doing similar "watch the field" jobs and stepping on each other's communication.
Config C only works if both the engineer and the strategist are trained for their match-time roles. Most engineers spend their season on hardware and code — not on game rules and alliance-station conduct. Closing that gap is a real prep step.
Engineering students who've focused all season on building and coding are not automatically ready to be drive-team members. They need rules training before their first competition.
Spartan engineers split into 4 subroles (Mechanical, Electrical, Programming, CAD). For the match-time loader+spotter role, the order of preference:
Strategists already study the game closely, scout opponents, and run match-plan forms. The Caller role builds on what they do. The new piece is the real-time vocal protocol — calling timer marks loud and consistent (":45 remaining"), not letting the driver hear silence when they need a check.
See the "When you're the Caller" section on the Strategist role page for the full call-set and timing protocol.
Walk this decision tree before your first scrimmage. Lock in your config so students can practice it before competition pressure hits.
For Config C (recommended). At every match-time moment, exactly one student owns the action. No ambiguity.
| Moment | Driver | Engineer (Loader) | Strategist (Caller) |
|---|---|---|---|
| Pre-queue prep | Confirms controller paired, batteries fresh | Confirms robot state, sensors zeroed, preload ready | Reviews opponent scouting, sets match plan, briefs alliance partner |
| At the field | Places robot in start zone | Places preload on robot per starting-position rules | Confirms 18″ size, alliance color, auton selection |
| Auton (0:00–0:15) | Hands off controller, watches | Hands clear of field, watches robot for auton execution | Watches opponent auton, notes for the next round |
| Auton-to-Driver gap | Picks up controller, ready | Hands clear, no loading until match resumes | Calls "driver up" when timer starts |
| Early driver (0:15–1:15) | Executes match plan, scores cycles | Loads at steady drip, watches robot health | Tracks score, calls ":45" when 45 sec remain |
| Mid-match adjust | Stays focused on cycles | Reports any robot issues to strategist (whisper) | Decides if score/state needs strategy pivot — tells driver in 2-3 words |
| Late match (1:30–2:00) | Endgame execution per call | Saves last 2–3 loads OR floods, depending on strategist call | Calls endgame mode ("contested zone" / "hold defensive" / "final push") |
| Match end (2:00) | Hands off controller | Stays in alliance station until ref clears | Notes final score, opponent moves, lessons for next match |
| Post-match debrief | Reports controller feel, mechanism state | Reports robot health observations (motors, sensors, mechanical) | Leads debrief, updates scouting, plans next match |
The 5-10 minutes before queue is when the drive team locks in. Every match should feel the same so muscle memory carries the team through pressure.
Done right, this whole sequence is calm. Done wrong, you're rushing at queue, the preload isn't set, the strategist is still typing in scouting notes. Practice the routine in scrimmages so it's automatic at competition.