How an FRC Match Is Structured

Two alliances, one clock

An FRC match is one timed contest between two three-robot alliances, the red alliance and the blue alliance, named only by which side of the field you start on. Whoever scores more points before the buzzer wins. FIRST releases a new game every season (the field, the game pieces, and the scoring all change), but the shape of a match stays the same year to year: a short autonomous opening, a longer driver-controlled middle, and a high-stakes endgame. Learn that shape once and you can walk into any season knowing how the time will flow.

The three phases

1. Autonomous ("auto"). The match opens with no human input allowed. Robots run pre-written code, routines the programming team built and the drive team helped tune on the practice field. Auto rewards reliable code and a consistent starting position. In recent games it runs about 15 seconds.
2. Teleoperated ("teleop"). Drivers and operators take control and play the bulk of the match. This is the longest phase, recently around 2 minutes 15 seconds.
3. Endgame. The closing stretch of teleop (often the last ~20–30 seconds) where the game offers a high-value action, climbing, docking, or parking in a zone. These points are usually large enough to swing a match, so timing matters.

Durations are set fresh each season, so confirm the current numbers in that year's Game Manual instead of trusting a memorized value.

What this means at the controls

The phases change what your job is, second by second:

• During auto, you stand off the sticks. Watch what your robot and your alliance partners actually do so you can adjust the moment teleop starts.
• At the teleop buzzer, take control instantly. Every second of hesitation is lost scoring time.
• As endgame approaches, decide when to break off scoring to go for the endgame task. Leave too early and you waste cycles; leave too late and you miss the climb.

Who controls the clock

Your robot doesn't run on a stopwatch, it runs on the field. The Field Management System (FMS) starts auto, enables teleop, and ends the match. Your controller inputs travel from the Driver Station laptop over the field network to the robot's roboRIO, which runs your team's code and commands the motors. That's why every robot "wakes up" at the same instant: you're synced to the FMS.

This is also why good auto code matters, and why drivers should be able to talk to programmers in their terms. Robots are coded in Java, C++, Python, or LabVIEW on top of WPILib, the standard library that provides motor controllers, sensors, and timers. "The arm raised about half a second late in auto" is feedback a programmer can act on; "auto looked weird" is not.

The takeaway

Every match is the same rhythm: a few seconds of robot autonomy, a couple of minutes of driving, then a sprint to the endgame. Know the current timings, respect the buzzer, and plan your endgame break in advance.