Two activities, two questions#
Scouting splits into two complementary activities.
Pit scouting means visiting each team in their pit to learn what their robot is designed to do. A pit scout asks questions and takes a photo of the robot. Typical questions:
- What can you score, and where? (e.g., which locations or levels)
- What does your autonomous routine do? How many do you have?
- What is your endgame capability?
- What is your drivetrain (tank, swerve, mecanum)?
- Any known reliability issues or things you are still fixing?
Pit scouting is fast to collect (you can cover all ~30-40 teams in the first hour or two of an event) and great for early-season events where there is little match data yet. Its weakness: it captures claims and intentions, not proof. Teams are optimistic about their robots, and a robot that "can" do something may rarely pull it off in a real match.
Match scouting means watching robots during actual qualification matches and recording what they really do: pieces scored, cycle times, scoring locations, penalties, endgame, and whether they broke down. The standard approach is to run one device per robot so all six robots on the field are scouted every match (a red alliance and a blue alliance of three robots each); a common refinement is two scouts per device, so one calls out the action and one records. Match scouting is your source of truth because it measures performance under real pressure, including defense.
How they work together#
| Pit scouting | Match scouting | |
|---|---|---|
| Question answered | What can the robot do? | What did the robot do? |
| When | Start of event, between matches | Every qualification match |
| Data type | Capability, specs, photo | Performance, counts, reliability |
| Strength | Fast, available before matches | Accurate, proves consistency |
| Weakness | Optimistic, unverified | Needs many matches to stabilize |
Use pit scouting to form hypotheses ("Team 4 says they can do the high-value endgame") and match scouting to confirm or reject them ("...but they have only completed it once in eight matches"). On picklists, match data should usually outweigh pit claims.
Practical tips#
- Photograph every robot during pit scouting. A picture jogs memory during alliance selection far better than text.
- Be polite and quick. Pit crews are busy. Have a fixed, short question list.
- Assign one scout per robot in match scouting and rotate so nobody loses focus. Watching one robot for an entire match is the single most important discipline.
- Note no-shows and breakdowns. A robot that misses matches or sits disabled is a reliability red flag your point averages might hide.
Many teams also do super-scouting: an experienced scout or strategist watches whole matches for big-picture qualitative judgments (driver skill, defense quality, how a robot performs under pressure) to supplement the per-robot data.
the part worth keeping
Key takeaways
- Pit scouting captures capability and intent; match scouting captures verified, real-match performance.
- Run match scouting with one device per robot (six robots per match), ideally two scouts per device.
- Use pit data to form hypotheses and match data to confirm them; weight match data more heavily on picklists.
Scouting & StrategyScouting Fundamentalslesson 2 of 3
Keep going
Take the quiz+10 XP with an accountMore in Scouting Fundamentals
where 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
- info.firstinspires.orgFIRST Introduction to Scouting Guide
- frogforce503.orgSwamp Scouting — FRC 503 (pit scouting walkthrough)
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 readBuilding an FRC Scouting App: Data Model, TBA/Statbotics APIs, and PicklistsBuild an FRC scouting app: match and pit scouting, a simple data model, pulling schedules and EPA from the TBA and Statbotics APIs, and building a picklist./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
- 6 min readFRC Scouting Sheet Template: Printable Paper Sheet + Google Form to Sheets SetupA ready-to-print FRC scouting sheet plus a Google Form to Sheets setup that auto-averages one row per scout into per-team stats, with a 2026 REBUILT note./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 difference between pit scouting and match scouting?
02Which piece of information is best gathered through PIT scouting rather than match scouting?
03Which data is best collected through MATCH scouting rather than pit scouting?
Answer every question to submit.
All 32 lessons in Scouting & Strategyopenclose
01 / prerequisites
02 / scouting-fundamentals
03 / building-a-scouting-system
04 / data-analysis-tba-statbotics
05 / strategy-picklists-and-match-play
06 / worked-examples-and-mini-projects
- Not read yet:Project 1: Configure a QRScout Form for REEFSCAPE
- Not read yet:Project 2: Compute OPR by Hand, Then in a Spreadsheet
- Not read yet:Project 3: Pull Live Data with the TBA and Statbotics APIs
- Not read yet:Project 4: Build an EPA-Component Robot Ranking Sheet
- Not read yet:Project 5: Assemble a One-Page Pre-Match Prep Sheet
07 / common-mistakes-and-troubleshooting
08 / advanced-techniques-and-case-studies