Your First FRC Competition: What to Actually Expect

Your first FRC competition is a two- or three-day marathon where your team sets up a pit, passes robot inspection, plays a schedule of qualification matches, and — if you rank well or get picked — competes in a double-elimination playoff. Expect long days, a loud venue, a robot that breaks and gets fixed repeatedly, and far more help from strangers than you would ever guess.

Knowing the rhythm ahead of time is the single biggest thing that separates a calm rookie team from a panicked one. Here is what actually happens, in order, and what to have ready.

The shape of the weekend

Events come in two formats, and the schedule differs a little between them. District events usually run two days (often Friday–Saturday). Regional events usually run three days (often Thursday–Saturday). Either way, the flow is the same: set up, get inspected, practice, play qualifications, then alliance selection and playoffs on the final day.

Days are long. Doors frequently open around 7–8 a.m. and the venue does not clear out until early evening. Bring the whole team prepared to be there all day, not to swing by for a couple of matches.

Move-in and pit setup

The first thing you do is find your pit — your team's assigned workspace on the pit floor. A standard pit is roughly 10 feet by 10 feet, though this varies by venue, so check your event's specifics. This is where your robot lives, gets repaired, and gets staged between matches.

Set up with function in mind, not looks. You want your tools reachable, your battery charging station running immediately (batteries take time to charge, and you will never have enough), and a clear path to roll the robot in and out on its cart. Get power sorted early: bring a heavy-duty extension cord and a power strip, because the outlet may not be where you want it.

Pit setup is also when reality hits that a lot of small things travel with the robot. A folding table, a labeled parts bin, spare bumpers, and a printed pit checklist do more for you here than a fancy banner.

Robot inspection

Before you can play a real match, your robot has to pass inspection (the volunteers who run it are called Robot Inspectors, or RIs). A volunteer inspector walks through a checklist to confirm your robot is legal and safe: weight, size, frame perimeter, bumpers, wiring, and the control system.

Do not guess at the limits — they shift year to year, so the current game manual is always the source of truth. Rather than build to numbers you half-remember, work from our lesson on inspection-day failures, which lists the exact bumper, size, and weight figures rookies get bounced on. A few things that trip up first-timers at inspection:

• Bumpers. You need both a red set and a blue set, built to spec, covering the required fraction of your frame perimeter with the number visible. Bumper construction rules are strict; read them carefully in the Mechanical & Build guides and the manual.
• Wiring. Correct main breaker, proper wire gauges, a fuse/breaker on every branch, and a securely mounted battery. A large share of failed inspections and dead robots come down to electrical, so tidy it up in advance — our Electrical & Wiring guides walk through what inspectors look for.
• A single, secured battery with a legal connector, and nothing that can short.

Get inspected as early as possible on day one. If something is wrong, you want hours to fix it, not minutes.

Practice matches

On the first day (three-day Regionals especially), you usually get practice matches. These are not scored and do not affect your ranking. Their entire purpose is to let you connect to the field, drive on the real carpet, test your autonomous routine, and shake out problems before it counts.

Treat practice as gold. This is where you confirm your robot actually connects to the Field Management System (FMS) — the field takes control of your robot the moment you plug into its ethernet, and if your code, radio, or driver station has a problem you want to find it here, not in a match that counts. Drill the exact pre-match connection routine that prevents a no-show before you go.

Qualification matches

The bulk of the weekend is qualification matches ("quals"). Every team plays a schedule of them — usually somewhere between about 8 and 12 depending on the event size — and the outcomes build your ranking.

A few things about quals that surprise first-timers:

Your alliance partners are randomized and change every match. Each match pits a red alliance of three robots against a blue alliance of three robots, and you are teamed with different partners nearly every time. That means cooperation is the whole game — you win with partners you met an hour ago.

The match schedule is posted, and you are responsible for getting your robot to the queue line on time, typically a few matches ahead of yours. Miss the queue and you risk a no-show, which hurts your ranking and wastes a match. Assign someone to watch the schedule and the queue all day.

Between matches you are on a tight turnaround loop: play, roll back to the pit, swap to a freshly charged battery, diagnose anything that broke, fix it, and queue again. Rookie robots break. That is normal. The teams that do well are the ones who repair fast and calmly.

Alliance selection and playoffs

On the final day, ranking closes and alliance selection happens — a live serpentine draft in which the top eight ranked teams become alliance captains and take turns picking the rest of the field into eight playoff alliances of (usually) three robots each, sometimes with an optional backup.

This is why scouting matters. Captains pick based on data about who plays well and who complements their robot, not on vibes. Even as a rookie, keep a scout or two watching matches and recording notes — being a team others want to pick is a real goal, and good Scouting & Strategy habits are how you get noticed. Getting picked in your rookie year is a genuine win.

Playoffs run as a double-elimination bracket among the eight alliances, so a single loss does not end your day — you drop to the lower bracket and can fight back. The bracket culminates in the finals, and the winning alliance advances (at Regionals directly toward the Championship; in the district system, points accumulate toward a District Championship).

What a match actually feels like

A match runs just a couple of minutes and moves fast. It opens with a short autonomous period — your robot on pre-written code with no driver input — then transitions into the longer driver-controlled teleop period, usually with a scramble of endgame scoring at the very end. If the rhythm of a match is new to your drive team, walk through it before you arrive; check the current manual for the year's exact timings and scoring.

Your drive team stands at the alliance station behind the field wall — typically a driver, an operator, a coach, and often a human player and a technician, each with a defined role and spot. You get a short, fixed window to plug in and set up your driver station before the match starts, so practice that routine until it is automatic. The field is loud, the referees are watching, and the whole thing is over before you catch your breath. It is genuinely thrilling — and completely survivable.

What to bring to an FRC event

Pack like the venue has nothing, because it mostly does not. The essentials:

• Safety glasses for everyone — ANSI Z87-rated eye protection is required any time you are in the pits or at the field, no exceptions. Bring spares; people forget theirs.
• Closed-toe shoes are required on the pit floor. No open shoes get in.
• Your full tool kit — the tools you used to build the robot, plus zip ties, tape, wire, crimpers, a multimeter, and hardware in the sizes your robot uses.
• Spare parts — anything you can imagine breaking: a spare battery or three, extra motors and controllers if you have them, spare bumper fasteners, wheels, chain/belt, and fuses.
• A battery charger (ideally more than one) and a way to log which battery is charged and rested.
• A programming laptop with WPILib and your current robot code, plus your driver station, an ethernet cable, and any radio configuration tools. Keep a known-good version of your code you can re-deploy.
• Power and workspace — extension cord, power strip, a small folding table, and a robot cart.
• Scouting materials — printed sheets, tablets, or whatever your system uses, and people assigned to run it.
• Human fuel — water, snacks, and lunch plans. Venues get hot and food lines get long.

A printed pit checklist taped to your table, and a whiteboard for the match schedule and battery status, keep a rookie team from losing track of the chaos.

Rookie mindset that actually helps

The biggest surprise for most first-year teams is how generous the community is. FIRST calls it Coopertition — you compete hard while helping the people around you. If you blow a motor and do not have a spare, ask a neighboring team; someone almost always has one. Veteran teams will lend parts, lend hands, and answer questions all weekend. Ask early and ask often.

Set the right goal. Your first event is not about winning — it is about getting your robot inspected, connecting to the field, playing every match you are scheduled for, and going home with a team that wants to come back. If you do that, you had a great rookie competition.

Spend the weeks before the event getting your people ready, not just your robot. Make sure your drive team has practiced, your pit crew knows the repair routine, and your electrical is clean enough to survive a full day of matches. If you are still getting your bearings, start with our Getting Started guide, and if a term at the event leaves you lost, our glossary has the FRC vocabulary you will hear announcers and volunteers throwing around all weekend.

Show up, stay calm when the robot breaks, help the teams around you, and soak it in. Your first competition is loud, exhausting, and one of the best things you will do all season.