How to Scout FRC Matches: Match Scouting, Pit Scouting and Pick Lists
Last updated 2026-11-16
Rankings tell you who won. Scouting tells you why, and whether a robot will help your alliance on Saturday afternoon.
Why scouting matters
Qualification rankings mix a robot's own play with its partners, its opponents and the luck of the schedule. A strong robot can sit at 20th after a few bad draws, and a middling one can ride good partners into the top eight. Scouting is how a team sees past that: by watching every robot in every match and writing down what it actually did.
Good scouting pays off twice. During qualifications it tells your drive team what to expect from the next partners and opponents. Before alliance selection it is the only honest basis for a pick list.
Start with the questions, not the form
Before you build a form, sit down with your strategy group after kickoff and write the questions you will need answered at an event. For most games they look like this:
- How many points does this robot score in autonomous, and how reliably?
- What does it score in teleop, and where on the field?
- Does it finish the endgame task, and how often?
- Can it play defense, and does it hold up under defense?
- Does it break down, tip, or lose connection?
Every field on your form should answer one of these. If nobody can say what a field is for, cut it. Long forms make tired scouts guess.
What to record in match scouting
Match scouting means one scout per robot, six scouts per match, recording what happened as it happens. Keep it to things a scout can see and count:
- Autonomous: whether the robot moved, what it scored, and whether the routine worked.
- Teleop: counts of each scoring action, and misses if your strategy group cares about accuracy.
- Endgame: what it attempted and whether it succeeded.
- Defense: whether it played defense, and how much it was slowed by defense against it.
- Problems: no-show, disabled, tipped, lost a mechanism, fouls that cost points.
- A short note: one sentence on anything the numbers miss.
Prefer counts and yes/no answers over ratings. "Scored 6" means the same thing from every scout; "4 out of 5 for driving" does not. Where you do use a rating, write down what each number means and train scouts on it.
Rotate scouts every few matches. Attention fades after twenty minutes of staring at one robot, and scouting is a job people should be able to enjoy, not a punishment.
Pit scouting: what to ask and what to trust
Pit scouting is the interview: a visit to each team's pit, usually on the first day, to learn what the robot is designed to do. Useful things to record are the drivetrain type, the mechanisms and what they score, the autonomous routines the team says it has, its preferred role, and a photo of the robot.
Be polite and quick. Teams are busy fixing robots, so ask whether it is a good time, keep it to a few minutes and thank them. Treat what you hear as a claim to check: a team may say it has a three-piece autonomous that it has never yet run on a real field. Match data wins when the two disagree.
Keeping the data trustworthy
Bad data is worse than none, because it looks like evidence. A few habits help:
- Train before the event. Have every scout watch the same recorded match and compare counts. Where they disagree, fix the definition, not the scout.
- Agree on edge cases. Does a piece that falls out count? What counts as "played defense"? Write it down.
- Check the totals. Compare your scouted points with the official alliance scores on The Blue Alliance. Big gaps point to a scout who needs help or a field that is confusing.
- Watch for replays and substitutions so a match is not counted twice or credited to the wrong robot.
Public data is a good second opinion. The Blue Alliance has schedules, scores and match videos, and Statbotics estimates each team's contribution to its alliance score (EPA). Those numbers come from final scores, so they cannot tell you how a robot scored or why it failed. That is what your scouts add.
Building a pick list
Before the playoffs, the top-ranked teams become alliance captains and invite other teams to join them. One rule shapes every pick list: a team that declines an invitation can't then be picked by another alliance. Pick order, timers and backup robots change from season to season, so read the alliance selection section of the current season's Game Manual (on FIRST's Game & Season page; each new manual comes out at Kickoff) with your strategy group well before the event.
Build the list the night before alliance selection, with the people who will be in the stands making the picks:
- Decide what your alliance needs. Start from your own robot. If you score well but cannot finish the endgame, a reliable endgame partner may be worth more than a second scorer.
- Sort into tiers. First-pick candidates, second-pick candidates, and teams you would not pick. Reliability belongs at the top of the criteria: a robot that scores less but never breaks often beats one that is brilliant half the time.
- Rank within each tier, using averages and consistency rather than a team's best match.
- Plan for picks being taken. Your top choices will disappear. Know your next three options at every point in the draft.
- Update on Saturday morning with the last qualification matches, then freeze the list.
If you might be picked rather than picking, the same list tells you which invitations you would be glad to accept.
Respect in the stands and in your notes
Scouting notes are about robots, not people. Never write a student's name, or a comment about a person, into your data; describe what the robot did. Keep your data within your team, and be gracious when you talk to other teams about their robots. You will be on an alliance with some of them by Saturday.
How Team 4456 does it
Getting all of our team members to scout has always been a problem, especially for matches our team isn't part of. Some students rushed through or skipped their assignments.
So we now assign scouting in AUTON. Assignments spread that hefty task evenly across all available students, and each scout gets a notification telling them who they are scouting and when. They fill in the in-app form on their phone, and mentors can see which student scouted which team and when, so every student is accountable for the matches they were asked to cover. The final data is in one Scouting Data table, and the pick board shows each team's numbers in summary when we build our list.
Paper and a spreadsheet have run plenty of winning pick lists too. Whatever you use, the habits above matter more than the tool.