Selecting and Building Your Drive Team

Choose for the match, not for seniority

The drive team should be selected because they are the best people for the job under pressure, not because they have the most seniority or built the most parts. FIRST publishes an official resource, the Guide to Selecting Drive Team Members (updated October 2025), precisely because picking by politics instead of performance is a common mistake.

Run real tryouts

The most reliable selection method is a structured tryout that mirrors competition. FIRST's Improving Driving Performance resource recommends having interested members run the same course with a set number of goals and measuring who completes it most efficiently. Concrete tryout ideas:

• A slalom / obstacle course to test precision driving and spatial awareness.
• A timed scoring cycle: pick up N game pieces and score them; record time and errors.
• A defense/evasion drill where a candidate must complete a task while another robot interferes.

Drills do double duty: they reveal natural talent and they are how you train whoever you pick. Run tryouts on the practice robot or the real robot so candidates feel the actual controls.

Traits to evaluate

The official selection guidance weighs talent over raw experience and looks for:

• Composure under pressure — staying calm in the last 20 seconds.
• Communication — taking direction cleanly and giving clear status back.
• Coachability — accepting feedback without ego.
• Spatial reasoning and reflexes — for drivers and human players especially.
• Positive team interactions — the drive team is a small, high-stress group; one toxic member poisons it.

Build the unit, then keep it stable

Once chosen, the drive team should practice together as a fixed unit whenever possible. Communication shorthand, timing, and trust are built through repetition with the same people. Constantly swapping members resets that progress.

That said, plan for backups. People get sick, graduate, or have conflicts at events. Cross-train a second driver and operator so a single absence doesn't sink your competition. Document your control mappings and callout vocabulary so a backup can step in quickly.

Set expectations early

Make the roles and the chain of command explicit before your first event: coach decides, driver/operator execute, human player feeds/scores, technician keeps the robot ready. Writing this down prevents the mid-match confusion that costs matches.