By elimination time, the team with the best process for turning data into a plan wins more than the team with the fastest robot. This project gives the drive coach a one-page brief template and a workflow to fill it before every match.
The template. One landscape page with three zones:
- Alliance plan (top). For each of the three robots on your alliance, write its primary job: who farms FUEL, who is the dedicated TOWER climber, who plays support/defense. Anchor each role in data — e.g., "7492 is our climber (endgame EPA 24, climbed Level 3 in 9/11 quals)."
- Opponent threats (middle). List the opposing alliance's single biggest scorer and its biggest reliability liability. Decide one thing: do we play defense, and on whom? The classic rule is to put defense on the opponent's best scorer — and your scouting tells you which robot that is.
- Pre-match checklist (bottom). Battery swapped and labeled, bumpers correct color, robot powers on, dashboard connected, controllers zeroed, gyro reset position confirmed. Mirror the WPILib operator-console guidance: laptop on a high-performance power plan, sleep set to never, Wi-Fi off, FRC Driver Station in focus.
The workflow (do this for every match):
- T-15 min: scouting lead pulls the six teams' rows (your averages + OPR/EPA) and fills zones 1 and 2.
- T-8 min: drive coach and drivers huddle at a whiteboard, draw starting positions and the first 20 seconds of auto, and agree on one defensive decision.
- T-3 min: run the bottom checklist out loud; the last person to touch the robot confirms each item.
Defense, done legally. If the plan calls for defense, brief the driver on the rules so a smart play doesn't become a match-losing foul. You may use contact to slow an opponent, but in 2026 REBUILT you cannot PIN them for more than 3 seconds before backing off (a violation is a MINOR FOUL worth 5 points to the opponent, escalating to a 15-point MAJOR FOUL for every additional 3 seconds uncorrected), and you cannot tip, entangle, or reach inside their frame. Verify these numbers in the current 2026 REBUILT Game Manual Section 7 (Game Rules) and the latest Team Updates before every event — foul values can be adjusted mid-season.
Why one page. A driver can't absorb a paragraph 30 seconds before a match. The discipline of fitting the whole plan on one page forces you to decide what actually matters: roles, the one defensive call, and the checklist. Run this for an entire event and you'll feel the difference in elims, when matches are decided by who executed the plan they walked in with.
the part worth keeping
Key takeaways
- A pre-match brief has exactly three zones: alliance roles (data-backed), opponent threats + one defense decision, and a pre-match checklist.
- Default defensive target is the opponent's best scorer per your scouting; brief drivers that pinning past 3 seconds draws a foul.
- Always confirm foul values and the pin limit in the current 2026 REBUILT manual Section 7 and Team Updates - they can change mid-season.
Drive TeamWorked Examples & Mini-Projectslesson 5 of 5
Keep going
Take the quiz+10 XP with an accountwhere this came from
Sources and corrections
This lesson 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, in public, in the corrections log.
sources and further reading
- firstinspires.orgFIRST: Team Management Resources (worksheets)
- firstfrc.blob.core.windows.net2026 REBUILT Game Manual (PDF)
clipped to this lesson
Articles that go further on this
The lesson gets you through the topic. These go wider on it, and they read in one sitting.
- 20 min readPlaying Defense in FRC: Legal Defense, Positioning, and Picklist ValuePlaying defense in FRC done right: when it pays off, legal vs. illegal defense and pinning rules, driving technique, counter-defense, and picklist value./blogread it
- 8 min readFRC Build Season Timeline: A Week-by-Week Plan from Kickoff to CompetitionA practical week-by-week FRC build season timeline, from Kickoff and game analysis through prototyping, CAD, fabrication, wiring, programming, and driver practice./blogread it
- 18 min readThe Blue Alliance (TBA): How to Use FRC's Match & Team DatabaseThe Blue Alliance (TBA) is FRC's free match and team database. Navigate team, event, and match pages, set up myTBA notifications, and use its read API./blogread it
answer sheet
Lesson quiz
All 3 right completes the lesson. Miss one and only that question comes back, anything you already answered correctly stays banked.
0 of 3 answered
01What is the core purpose of a one-page pre-match strategy brief?
02How should an alliance decide which opposing robot to play defense on?
03To be usable by the drive team in the minutes before a match, the strategy brief should be:
Answer every question to submit.
All 34 lessons in Drive Teamopenclose
01 / prerequisites
02 / the-drive-team-and-its-roles
03 / driver-station-and-controls
04 / driver-practice-and-match-performance
05 / the-pit-and-match-turnaround
06 / worked-examples-mini-projects
- Not read yet:Project 1: A Production-Ready Driver Control Scheme
- Not read yet:Project 2: A Drivetrain That Survives a Whole Match
- Not read yet:Project 3: Build a Paper + Spreadsheet Scouting System
- Not read yet:Project 4: Pull Live OPR & EPA Data with Python
- Not read yet:Project 5: The One-Page Pre-Match Strategy Brief
07 / common-mistakes-troubleshooting
08 / advanced-strategy-case-studies