In the FIRST Tech Challenge (FTC), a team’s demise rarely happens with a dramatic, mid-match explosion. Instead, it is a slow, quiet process of attrition. It happens when a team arrives at the national tournament in Johannesburg or Cape Town, unpacks their robot, and realizes that a loose USB connection or an unpractised driver has rendered months of work useless.

For South African teams, where hardware budgets are tight, shipping times are long, and load-shedding can cut practice sessions in half, these mistakes are particularly punishing. If you want your team to survive its rookie year and actually compete, you must avoid these six common pitfalls.

1. The "Do-Everything" Robot (Over-scoping)

The game reveal occurs, and the team immediately designs a robot that can intake from the floor, sort game elements by colour, lift them two metres high, and perform a pull-up at the end of the match. This is a fatal mistake. A rookie team that attempts to build a Swiss Army knife robot usually ends up with a machine that does five things poorly and nothing reliably.

The arithmetic of FTC is simple: a robot that can only do one task—such as reliably moving game elements into the low goal—but does it every single match without breaking down, will outscore and out-select a complex, non-functional robot every time. Focus on a simple, robust drivetrain and one scoring mechanism. Master that first.

2. Building Before Understanding the Rules

Many teams start cutting metal and assembling chassis on day one, before the team has thoroughly read Game Manual Part 1 and Part 2. This leads to devastating compliance failures at inspection. If your robot is 46 cm wide instead of the strict 45.7 cm (18-inch) limit, or if you have used non-allowed materials, you will spend your entire practice day hacking your robot apart with a hacksaw instead of tuning your autonomous code.

3. The Week 10 Engineering Portfolio Panic

The Engineering Portfolio is not a book report to be written the weekend before the competition. It is a core component of the judging process. Teams that treat the portfolio as an afterthought forfeit their chance at the most prestigious judged awards, which are often the primary pathway to advancing to the next level of competition.

When you start your season, assign a student to document every meeting, every failure, and every CAD iteration from week one. If you wait until week ten, the design decisions, the math behind your gear ratios, and the lessons from your failed prototypes will be forgotten.

4. The Single Point of Failure: No Spare Control Hub

A Rev Robotics Control Hub is the brain of your robot. In South Africa, a new Control Hub costs upwards of R9,000, which can represent a massive portion of a rookie school's budget. Because of this cost, many teams do not buy a spare. This is a massive gamble.

If a static shock or a wiring short kills your only Control Hub at the competition, your season is over. Electrostatic discharge (ESD) is a frequent topic on online forums, with monthly "disconnect-per-match" threads on r/FTC highlighting how a single disconnected robot can end up being "penalty-farmed" for up to 800 points by the opposing alliance. Having a spare Control Hub is non-negotiable. If you cannot afford a spare, consider partnering with a local school to share a backup pool of critical electronics.

5. Treating Driver Practice as Optional

A mediocre robot with 20 hours of driver practice will almost always beat a magnificent robot with 20 minutes of driver practice. Rookie teams often spend 99% of their time building and programming, leaving the drivers to touch the controllers for the first time in the pit area at the tournament.

Under pressure, drivers who lack muscle memory will drive into walls, tangle with opponent robots, and tip their own machines over. You must freeze your robot design at least three weeks before your first scrimmage to give your drive team dedicated, uninterrupted time on a simulated or partial field.

6. Mentor-Built Subsystems

It is tempting for mentors—especially those with engineering backgrounds—to step in and build complex mechanisms to save time. This is a short-sighted strategy that actively harms the team. As users on r/FTC have pointed out, a "mentor built robot kind of defeats that… creates an uneven playing field."

"mentor built robot kind of defeats that… creates an uneven playing field"

More practically, when a mentor-built intake system breaks during a tense five-minute pit window between qualification matches, the students will not know how to fix it because they did not design or build it. The mentor is not allowed to work on the robot in the pit; the work must be done by the students. If the students do not understand the engineering behind their machine, they cannot repair it under pressure.If you are looking to establish a sustainable, well-supported FTC program that avoids these common organizational traps, you can explore our structured program support at sheenrobotics.co.za/ftc to help guide your team through their first season.