How to Read the FRC Game Manual (Without Getting Lost)

The FRC game manual is the official rulebook FIRST publishes at Kickoff every January. It defines that season's game, the field, how points are scored, and every rule your robot, drivers, and team have to follow. The way to read it without getting lost is simple: don't read it front-to-back like a novel. Skim it once for structure, read the scoring section closely, then have each sub-team deep-read only the parts that apply to them.

That's the whole strategy. The rest of this is how to actually do it.

What the game manual actually is

Every FRC season is a brand-new game, revealed at Kickoff in early January. Minutes after the reveal animation, FIRST drops the game manual, a PDF that usually runs well over 100 pages. It is the single source of truth for the season. Chief Delphi threads, YouTube breakdowns, and your mentors' opinions are all helpful, but none of them override the manual. If there is ever a disagreement about what's legal, the answer is in the text (or in the official Q&A, which we'll get to).

The manual covers four big things: the game (objective, match flow, scoring), the arena (the field you play on), the robot (what you're allowed to build), and the tournament (how events and rankings work). Almost everything a rookie needs for their first season lives somewhere in those four buckets.

Where to find it, and which version to read

The manual lives on the FIRST website's game-and-season page, alongside the field drawings, the Kit of Parts list, and the other official documents. Download the PDF and keep a copy locally. You'll be searching it constantly, and you don't want to be reloading a web page in the middle of an argument. Ctrl+F is genuinely your most-used tool all season.

One critical thing rookies miss: the manual you download at Kickoff is not final. Throughout build season, FIRST releases Team Updates that add, change, or clarify rules. A rule you memorized in week one can be different by week three. More on that below, but the short version is to always confirm you're looking at the latest version.

How the manual is organized

The manual is split into numbered sections with a consistent internal logic. You don't need to memorize the section numbers, since they shift year to year, but you do need to understand the three conventions that make the whole thing readable.

Rule prefixes: G, R, and the rest

Every rule has a short code like G401 or R501. The letter tells you what kind of rule it is, and that lets you jump straight to what you care about:

• G rules are game rules, things you can and can't do during a match. Drivers and the drive coach live here.
• R rules are robot rules, the construction and build constraints like size, weight, legal materials, and motor limits. Your mechanical, electrical, and CAD people live here.
• Other prefixes cover inspection, tournament, and event rules. The manual's own "how to read a rule" intro page lists exactly which letter means what for the current season. Read that one page and the entire document gets easier.

Getting fluent in the prefixes is the single biggest unlock. When a teammate asks "is this legal?", you should know whether the answer is an R rule or a G rule before you even open the file.

Blue boxes are the best thing in the manual

Scattered through the manual are shaded Blue Boxes. These are not rules themselves. They explain the intent behind a rule, give worked examples, or clarify edge cases the plain rule text can't cover on its own. When a rule confuses you, the Blue Box right after it usually answers the exact question you had. Rookies skip them because they look like filler. They are the opposite of filler.

Defined terms and the glossary

The manual formats specific defined terms in a consistent style (you'll notice certain words are capitalized or styled differently), and each one has a precise meaning listed in the glossary at the back. A term like FRAME PERIMETER, BUMPER ZONE, or ALLIANCE means exactly what the glossary says, not what it sounds like in everyday English. When a rule hinges on a defined term, go read that definition before you argue about the rule. Half of all "these rules contradict each other!" moments are just someone using the casual meaning of a word the manual defines narrowly.

If a term ever trips you up, our FRC glossary explains the common ones in plain language.

A reading order that actually works

Here's the sequence I'd give any new team on Kickoff day:

1. Watch the game reveal animation first. Two minutes of video gives you the mental model that makes the text readable.
2. Read the game overview and match-flow section to get the shape of a match start to finish — the autonomous period, the driver-controlled period, and endgame — and let the manual fill in that season's exact timing. If those phases are new to you, our lesson on how a match works walks through them so the manual reads faster.
3. Read the scoring section slowly and completely. This is the part your entire strategy is built on.
4. Skim the whole manual once so you know what exists and where it is. Don't try to absorb it, just build a map in your head.
5. Split the deep read by sub-team. Build and CAD read the R rules cover to cover. Drivers and strategy read the G rules. Whoever handles inspection reads the inspection and bumper rules. Nobody reads all 100-plus pages at full depth alone.

That last point is the real anti-getting-lost move. The manual is written for an entire team, not one person. Trying to be the single human who has every rule memorized is how you burn out by week two.

Read the scoring like your season depends on it

Because it does. The scoring section is where design and strategy actually come from. Before you sketch a single mechanism, your team should be able to answer: what's worth the most points, what's cheap and reliable to score, what the autonomous period rewards, and what the bonus ranking-point objectives are.

A robot that reliably does the one highest-value thing usually beats a robot that tries to do everything and does none of it well. You can only make that call if you've read the points closely. This is also where Scouting & Strategy starts, because the scoring rules define what's even worth scouting in the first place.

The parts that quietly disqualify rookies

A few rule categories cause the most rookie pain, mostly because they're easy to overlook until inspection day:

• Size and weight limits. Robots have a maximum weight and have to fit inside a starting volume, with rules about how far mechanisms may extend during a match. The exact numbers change year to year, so check the current R rules, but know these limits exist and design to them from day one, not the night before your event.
• Bumper rules. Bumpers have their own detailed rules: how they're constructed, where they sit on the frame, what colors they are, and how much of the frame perimeter they cover. Get these wrong and you fail inspection, so read them carefully before you finalize your frame.
• The control system and wiring. The legal electrical system (main breaker, correct wire gauges, a properly secured battery) is spelled out in the rules and checked at inspection. Our Electrical & Wiring guides map directly onto what the manual requires.

None of these are hard. They just have to be right, and the manual tells you exactly what "right" is.

Team Updates and the Q&A change the manual under you

Two official systems keep the manual alive after Kickoff, and ignoring them is a classic rookie mistake.

Team Updates are FIRST's official amendments to the manual, released on a schedule during build season. They can change a rule, add a new one, or correct an error. Reading them is not optional, because a Team Update can invalidate a design decision you already committed to. Assign someone to check for updates and read them out to the team every time they drop.

The official Q&A system is where teams submit questions about rules they find ambiguous, and FIRST answers on the record. Those answers are official clarifications straight from FIRST, though the manual text itself takes precedence if the two ever conflict. Before you spend an hour arguing about an edge case, search the Q&A. Odds are another team already asked and there's an official ruling. If there isn't, you can submit the question yourself.

Common mistakes when reading the manual

• Reading it front-to-back like a book. You'll lose the plot by page 30. Skim for structure, then deep-read by section.
• Trusting a Chief Delphi hot take over the actual text. The community is great for pointers, but always confirm against the manual and the Q&A.
• Ignoring the Blue Boxes. They answer the exact question the rule left open.
• Skipping the glossary. Most rule confusion is a defined term someone assumed they already understood.
• Forgetting Team Updates. The manual changes. Keep up.
• Reading a rule without its penalty. Most rules state the consequence for breaking them, whether a FOUL, a TECH FOUL, a card, or a disqualification. Knowing the cost tells you how much a rule actually matters to your strategy.

The bottom line

The FRC game manual looks intimidating because it's long and precise, but it's precise on purpose. It's the one document every team on the field has agreed to play by. Read it in layers instead of all at once: animation, overview, scoring, a full skim, then a deep read split across your sub-teams. Learn the rule prefixes, respect the Blue Boxes and the glossary, and never let a Team Update sneak past you.

If this is your first season and the manual is your first real taste of FRC, start with our Getting Started guide and let it point you to the rest as you grow. Read the manual well and you'll spend build season building, not arguing about rules.