Designing the org chart
An org chart is a diagram of who is responsible for what and who reports to whom. Even a small team should draw one, because the exercise forces you to name every job that needs doing.
Common technical sub-teams
- Mechanical, or build, designs and fabricates the chassis, drivetrain, and game-piece mechanisms.
- Electrical handles wiring, the Power Distribution Hub (PDH) or the older Power Distribution Panel (PDP), motor controllers, pneumatics, and the control system (roboRIO).
- Software, sometimes called programming, writes the robot code (usually Java, C++, or Python with WPILib), the driver controls, and the autonomous routines.
- CAD, or design, models the robot in tools like Onshape or SolidWorks before anything is cut.
The business & operations sub-team
The business sub-team usually owns several separate functions. On a larger team each one becomes its own sub-group with a lead:
- Finance covers budgeting, purchase tracking, and reimbursements.
- Sponsorship and fundraising handles sponsor outreach, grant applications, and sponsor relations.
- Outreach and community runs demos, mentors younger teams, and puts on events.
- Marketing and media owns the website, social media, photography, branding, and the team logo and uniforms.
- Awards and documentation covers the Impact Award submission, the business plan, and the team portfolio.
- Logistics handles travel, hotels, food, registration deadlines, and pit organization at events.
That split lines up with how FIRST and veteran teams describe business: managing fundraising and sponsorships, applying for grants, handling order schedules and sub-system budgets, social media and public relations, travel itineraries, competition document submissions, and team uniforms.
Where business sits
A common misconception is that business sits "below" engineering. On healthy teams, the business and technical sub-teams are peers under one student leadership layer (captains) and one mentor layer. Business raises the money that pays for engineering, tells the team's story, and wins the awards that earn championship advancement.
A sample structure
Lead Mentors (adults)
|
Team Captain(s) (students)
/ \
Technical Lead Business Lead
| | | | | | | |
Mech Elec SW CAD Fin Spon Out Media
Sizing it to your team
On a 12-person rookie team, one person may wear the finance, sponsorship, and media hats at once. A 60-person team may have a dozen people in business alone. The principle holds at both sizes: name every function, give it an owner, and write it down so the role survives the person.
Key takeaways
- Technical sub-teams (mechanical, electrical, software, CAD) build the robot; business handles money, story, and logistics.
- Business commonly splits into finance, sponsorship, outreach, media/marketing, awards/documentation, and logistics.
- Business and technical should be organizational peers, not a hierarchy.
- Scale the number of roles to your team size, but always assign a named owner to each function.
Keep going
Take the quiz · +10 XP with an accountMore in Team Structure & Leadership
Sources & corrections
This lesson is AI-assisted: drafted from primary sources, then reviewed and edited by hand. Errors still get through. When one is reported we fix it and write down what changed — publicly, in the corrections log.
Sources and further reading
- FRC Team Structure Discussion (Chief Delphi General Forum)chiefdelphi.com
- FRC 167 Team Administrationdocs.iowacityrobotics.org
Read next
Articles on this, for competition day
The lesson covers how it works. These cover what to do when it breaks.
- 19 min read
FRC PDH: The Power Distribution Hub Explained (Channels, Fuses & Wiring)
A complete guide to the REV PDH (Power Distribution Hub): all 24 channels, breaker and fuse sizing, clean wiring, the switchable channel, CAN telemetry, and PDH vs PDP.
Read - 13 min read
FRC Awards Explained: Every FIRST Robotics Competition Award (Impact, EI, Autonomous & More)
A complete guide to every FIRST Robotics Competition award — Impact, Engineering Inspiration, Autonomous, Innovation in Control, Dean's List and more — with judged criteria and how to win.
Read - 8 min read
The FRC Control System Explained: roboRIO, PDH, Radio, and Everything Between
The FRC control system explained: how the roboRIO, REV PDH, radio, motor controllers, and CAN bus connect to make your robot drive — a plain-English electronics board tour.
Read
Lesson quiz
RequiredAll 3 right completes the lesson. Miss one and only that question comes back — anything you already answered correctly stays banked.
0 of 3 answered
01.Which is a common technical sub-team on a typical FRC team?
02.Which task is primarily the responsibility of the software/programming sub-team?
03.In a healthy FRC team org chart, where does the business sub-team sit relative to the technical sub-teams?
Answer every question to submit.
All 49 lessons in Business, Operations & Fundraising
- Not started:Mini-Project 1: A Working Season Budget Model
- Not started:Mini-Project 2: A Sponsor CRM in a Spreadsheet
- Not started:Mini-Project 3: A Grant Pipeline & Deadline Tracker
- Not started:Mini-Project 4: Auto-Generate a Sponsor Impact Report from The Blue Alliance API
- Not started:Mini-Project 5: A Competition Travel & Logistics Planner
- Not started:Should Your Team Become a 501(c)(3)? Structure Deep-Dive
- Not started:Multi-Year Financial Modeling: Reserves, Runway & Endowments
- Not started:Scaling Impact: From Local Outreach to Systemic Advocacy
- Not started:Case Study: Hall of Fame Programs Decoded
- Not started:Governance, Risk & Compliance for a Mature Program