10 Common FRC Rookie Mistakes (and How to Avoid Them)

Every veteran FRC team was a rookie once, and almost all of them made the same handful of mistakes in their first season. The good news: those mistakes are well-documented, predictable, and completely avoidable. If you learn what they are now, you can skip months of frustration and show up to your first event with a robot that actually works. Here are the ten that trip up new teams the most, and exactly how to dodge each one.

1. Designing a robot that does too much

The single most common rookie mistake is scope creep: trying to build a machine that scores in every way the game allows. A robot that does one thing reliably beats a robot that does five things poorly, every single time.

The fix: pick one or two scoring objectives and commit. Read the game's scoring breakdown, identify the highest-value action you can realistically build, and design around that. A simple robot you finish and test in week four is worth far more than an ambitious one you're still debugging the night before your event. Start from a known-good base like the official KitBot, then add exactly one mechanism on top.

2. Not reading the game manual carefully

At Kickoff, everyone watches the game animation and skips straight to brainstorming. Then at inspection they discover their robot is over the size limit, the bumpers are illegal, or a mechanism breaks a rule. Illegal bumpers in particular are one of the largest non-compliance issues inspectors see, per FIRST's bumper rule-change guidance.

The fix: assign someone to read the entire game manual, especially the Robot Construction Rules (the "R" rules) and the Game Rules (the "G" rules). In recent seasons the robot has had to fit a fixed frame perimeter, stay under a height limit, and weigh under a set maximum without bumpers and battery — but these numbers change every year (the weight limit itself changed for the 2025 season), so confirm the exact figures in the current Game Manual before you cut a single piece of metal. Print the current season's inspection checklist from the official season materials and check your robot against it weeks before your event, not at the field.

3. No driver practice (or starting it too late)

Teams pour hundreds of hours into building a robot, then hand the controls to someone who has never driven it until their first qualification match. A great robot with an untrained driver loses to an average robot with a practiced one.

The fix: start driving early. You don't need a finished robot — a previous year's robot, a test chassis, or even the bare drivetrain of this year's machine is enough to begin, as FIRST's driver-performance guide notes. Run drills: slalom courses, repeated pickups, and scoring cycles against a timer. At the event, the practice day (usually the day before qualification matches start) exists for exactly this — get inspected first, then run as many practice matches as you can to shake out connection issues.

4. An unreliable drivetrain

If your robot can't move, nothing else matters. Rookie teams often try to design a clever custom drivetrain and end up with chain that throws, wheels that slip, or gearboxes that bind — and they spend the whole season fixing it instead of building scoring mechanisms.

The fix: for your first year, build the AndyMark AM14U6 Kit-of-Parts chassis that ships in the Kickoff kit. It's a proven 6-wheel drop-center base, fully documented, and designed to survive a season of contact. A reliable, boring drivetrain frees your team to spend its energy on the parts of the robot that actually win matches. Learn the mechanical fundamentals in our Mechanical / Build track.

5. Sloppy wiring with no strain relief

Loose connectors, wires under tension, and stray copper "whiskers" cause more mid-match failures than almost anything else. A robot that browns out or loses a motor because a wire popped off during a collision is a robot that can't compete.

The fix: follow the WPILib wiring best practices. Key points:

• Leave enough slack to avoid strain on connectors, then secure cables close to each connection point.
• Pull-test every connection by hand to confirm nothing comes loose.
• Make sure no stray wire whiskers stick out of a terminal.
• Secure snap-in connectors like the SB50 battery connector with clips or cable ties so impacts can't pop them loose.

Treat clean wiring as a competitive feature, not an afterthought. Our Electrical track walks through the full power-distribution layout.

6. Skipping scouting

Rookie teams often treat scouting as optional busywork. Then alliance-selection day arrives, the top-ranked teams start picking partners, and the rookies have no data and no plan — so they either don't get picked or pick blindly.

The fix: scout from match one. The FIRST Introduction to Scouting Guide explains the goal: gather data on what every robot can actually do so you can build a pick list before alliance selection. In the playoffs, the highest-seeded teams become alliance captains and invite partners to form alliances, and good scouting data tells you which partners complement your robot's strengths. Scouting also feeds match strategy — knowing what each robot does lets your drive team assign roles for auto, teleop, and endgame before the match starts.

7. Last-minute, untested changes

The temptation to "just tweak one thing" the night before a match — or worse, between matches — has broken countless robots. An untested change is a gamble, and at competition the stakes are highest.

The fix: adopt a simple rule — no change goes on the robot without a test afterward. Keep the working robot working. If you must modify something at an event, do it early in the day, run it in a practice match, and have a way to revert. Version-control your robot code so you can roll back a bad commit instantly; see our Programming / Software track for setting that up.

8. No documentation

When the one student who wired the robot or wrote the autonomous code is out sick, an undocumented team is stuck. Rookies frequently keep everything in one person's head, then lose all of it when that person graduates.

The fix: write things down as you go. A wiring diagram, a list of CAN IDs and motor-controller assignments, a build log, and a README in your code repository cost almost nothing to maintain and save you constantly. Documentation is also how knowledge survives from one season to the next — it's the difference between a team that improves every year and one that restarts from zero.

9. Blowing the budget early

FRC parts are expensive, and it's easy to spend most of your funds in the first few weeks on motors, pneumatics, and shiny COTS mechanisms — then have nothing left for spares, replacement parts, or travel.

The fix: make a budget before you spend, and hold back a reserve. Prioritize the essentials (drivetrain, control system, battery, bumper materials), buy spares of the parts most likely to fail or get lost, and remember that the Kit of Parts already gives you a huge head start. Note that the rules also cap the value of any single non-kit item you put on the robot — there's a per-item fair-market-value limit, and that figure can change from year to year — so confirm the current cost rules in the game manual and track your spending from day one.

10. Skipping prototyping

Rookies often go straight from an idea to a finished, machined mechanism — and discover too late that the geometry was wrong, the wheels were the wrong durometer, or the whole concept doesn't work. Rebuilding a "final" part is far more expensive than fixing a prototype.

The fix: prototype cheaply and quickly first. As FRCDesign.org advises, build with inexpensive materials like wood and screws, and power a wheeled shooter with a hand drill before you commit to motors and metal. The goal of a prototype is to learn fast and iterate, not to be pretty. Once a prototype proves the concept, then move it into CAD and build the real version with confidence.

The pattern behind every fix

Look back at the list and one theme repeats: do the simple, reliable thing early, then test it. Scope down, read the rules, build a proven drivetrain, wire it cleanly, practice driving, scout your matches, and prove every idea before you commit. None of these require genius — just discipline. Every championship team started by getting the basics right, and so can you.

Ready to dig into the details? Start with the LearnFRC guides hub and pick the track that matches whatever part of your robot needs the most help right now.