The FRC game manual is the season's official rulebook. Here's how to read the FRC manual without getting lost: structure, rule prefixes, scoring, and Team Updates.
to read
words
sections
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.
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.
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.
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.
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:
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.
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.
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 ROBOT 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.
Here's the sequence I'd give any new team on Kickoff day:
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.
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.
A few rule categories cause the most rookie pain, mostly because they're easy to overlook until inspection day:
None of these are hard. They just have to be right, and the manual tells you exactly what "right" is.
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.
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.
This article is AI-assisted: drafted from primary sources, then reviewed and edited by hand. Errors still get through. When one is reported we fix it and write down what changed — publicly, in the corrections log.
Keep going
You came here for one answer. These lessons teach the same subject properly, in the order a team actually learns it. All 28 are free and none of them need an account to read.
Go deeper
LearnFRC has 394 free FRC lessons across every department. Create a free account to save your place, track your progress, and earn a certificate.
Create a free accountKeep reading
Structured lessons and quizzes across every department. Create a free account to save your progress, track your team, and earn a certificate.