Organizing an FRC Build Season with Sub-teams and Projects
Last updated 2026-11-16
Kickoff to first event is only a few weeks. Teams that finish on time rarely work harder; they decide earlier, split the work clearly and see problems sooner.
The shape of a season
The game is revealed at kickoff in early January. There has been no fixed "stop build" day since 2020, so teams keep improving the robot between events, but the first event still sets a hard deadline: the robot needs to work, and the drive team needs practice, before you load the trailer.
Work backwards from that date. If your first event is in early March, the robot should be driving well before then so drivers can practice and programmers can tune autonomous. Many teams aim for a working robot with a week or two to spare.
Set up sub-teams
Sub-teams let a large group work in parallel. Common ones are:
- Mechanical / build: drivetrain and mechanisms.
- Electrical: wiring, power distribution and sensors.
- Programming: robot code, autonomous and driver controls.
- CAD / design: the robot model and drawings for manufacturing.
- Strategy and scouting: game analysis, then scouting at events.
- Business, outreach and media: sponsors, the website, photos and award submissions.
Give each sub-team a student lead and a mentor. Leads plan the work and speak for the group; mentors teach and unblock rather than build it themselves. Cross-train where you can, so one illness or exam week doesn't stop a whole system.
Week one: decide before you build
The first week is for understanding the game, not cutting metal. Read the manual as a team, quiz each other on the rules, and decide what your robot must do, what it should do, and what it will not attempt. Prototype the riskiest ideas quickly and cheaply. By the end of the week you should have a strategy, a list of priorities, and a rough robot architecture.
Write these decisions down. In week four, when someone proposes a new mechanism, the priority list is what keeps the team focused.
Break the robot into projects
A project is a piece of the robot, or of the season, that one group owns from start to finish: the drivetrain, the intake, the scoring mechanism, the endgame mechanism, the electrical board, autonomous routines, the pit display. Each project needs:
- An owner, usually a sub-team and a named student lead.
- A definition of done, for example "intake picks up a game piece from the floor in under a second, ten times in a row".
- A target date that fits the backwards plan.
- Dependencies: CAD before machining, a working mechanism before programming can test it.
Turn projects into tasks
Tasks are the units of work people pick up at a meeting: "machine the intake side plates", "wire the drivetrain motor controllers", "write the arm position control". Good tasks are small enough to finish in a meeting or two, have one person responsible, and have a clear due date.
A short stand-up at the start of each meeting helps: each sub-team says what it finished, what it is doing today and what is blocking it. A visible task board (columns for to do, in progress and done, on a whiteboard or in an app) shows at a glance where work is piling up.
Watch the critical path
Some work blocks everything after it. If the drivetrain is late, programming cannot test autonomous, and drivers cannot practice. Identify those items in week one and give them the most attention. Order long-lead parts early, and have a fallback for any mechanism that might not work in time.
Review the timeline weekly. A slip noticed in week three is a small adjustment; noticed in week six, it is a crisis.
Parts and inventory
Know what is on the shelf before you order, and use one path for part requests so nothing is ordered twice and every purchase has an approval. Note lead times: some parts take weeks to arrive, which matters more than price in a short season.
Document as you go
Photos and short notes written during the season are worth far more than a summary reconstructed in March. A build log helps new members catch up, gives the business team material for sponsors and award submissions, and records why decisions were made. Make posting a habit: a photo and two sentences at the end of each meeting is enough.
Keep people safe and the pace sustainable
Train every student on each tool before they use it, require safety glasses in the shop, and make one person responsible for safety at every meeting. Long nights feel productive but lead to mistakes and burnout; a steady schedule with clear goals usually gets more done than heroics in the final week.
How Team 4456 does it
Our recurring problem was projects getting lost between sub-teams and forgotten after meetings. We now track them in AUTON's projects tools: tasks and projects are scheduled and assigned to specific members, and the links and files they need are saved alongside them, so every member can see what needs doing and get it done on time.
Whiteboards and shared documents work too. The plan matters more than the tool: owners, dates and a weekly look at the critical path.