👥 Team Ops · All Roles · Start of Season

Team Structure & Roles

Tasks rotate; ownership doesn’t. The roles, how squads cross-train, what changes on event day, and the roster page that proves it to judges.

👥 Ownership, Not Just Tasks

Strong teams separate two things that weak teams blur: tasks (what you’re doing today) and ownership (what you answer for all season). Tasks rotate — everyone should touch the drill, the code, and the scouting sheet. Ownership doesn’t: one person owns the intake, one owns auton, one owns the notebook’s chronology, for the whole season.

Judges probe this directly. “Who owns your autonomous?” has a one-name answer on a well-structured team — followed by that person explaining it in depth. “We all kind of worked on it” is the answer structure that costs interviews.

🃏 The Core Roles

Each role below has a full guide teaching what the role owns, its season rhythm, and how it shows up in the notebook and interview:

🎮 Driver Owns robot operation: practice regimen, controller mapping decisions, match execution, and the driver log.

🔧 Engineer Owns the physical robot: build quality, CAD-to-build fidelity, fabrication, and the build log.

💻 Programmer Owns the code: architecture, autonomous routines, tuning logs, and version control.

🧠 Strategist Owns the game: game analysis, scouting, match strategy, alliance selection, and skills planning.

⭐

Small team? Roles still apply. With three students, each person carries more than one role — that’s fine. What matters is that every role has exactly one named owner, and the roster says who.

🔀 Squads & Cross-Training

Teams that run multiple events (or split between qualifiers and league play) often organize as two squads, pairing each role across squads: the two drivers cross-train together, the two engineers share build standards, and so on. The pairing keeps knowledge from living in one head — if a squad member is out, their counterpart can step in with the same playbook.

Whatever structure you choose, record it: the notebook’s team roster page should show every member, their role, their squad, and what they own — and it should stay current when things change mid-season.

🏟 At Competition

Event day adds a second structure on top of season roles: the drive team (who’s at the field) and the pit crew (who keeps the robot ready between matches). These are assignments, not identities — your season-long Engineer might be event-day pit lead. The Drive Team Roles guide covers field-side positions; the Compete hub covers the rest of match day.

🗓 Running the Season

Structure only works with an operating rhythm around it: a season calendar with build/test/compete phases (Season Planner, Kickoff Week), a task board so tasks visibly move (Project Management), and honest time budgeting (Time Management). Ownership answers “who”; these answer “when.”

📖 In Your Notebook

Roster page Name · grade · role · squad · what they own. First content page after your cover — judges look for it.

Role evidence Each member’s entries should match their ownership: the auton owner writes the tuning logs, the engineer signs the build entries.

Keep it current Mid-season role change? Update the roster with a dated note. A stale roster reads as a prop, not a record.

⚙ STEM Highlight Engineering: How Real Teams Assign Ownership

Industry uses RACI charts — for every work area, who is Responsible, Accountable, Consulted, and Informed. The core insight matches yours: many people can contribute, but exactly one name is accountable per area. Aerospace programs call them “cognizant engineers” — the one person who must be able to answer for a subsystem at review.

🎤 Interview line: “Every subsystem and season function has one named owner on our roster — tasks rotate so everyone learns, but ownership is durable, so in this interview any of us can tell you exactly who to ask about any part of the robot.”

A judge asks “who owns the intake?” Three students helped build it. What’s the strong answer?

⬛ “We all worked on it together”

⬛ The named owner answers — “I own the intake” — then credits the others’ contributions while explaining the design in depth

⬛ Whoever is standing closest to the judge

Related guides

🎮 Driver Role → 🔧 Engineer Role → 💻 Programmer Role → 🧠 Strategist Role → 🏟 Drive Team Roles → 📋 Project Management →