A statistic only matters if it changes a decision. This lesson connects the spreadsheet skills and summary numbers from this department to the real calls a scouting-strategy team makes: building a pick list, prepping a match, and reading published metrics without getting fooled by them.
Build a Pick List, Not Just a Ranking
After qualifications you need an ordered pick list of teams you'd want as alliance partners. Don't sort by a single number. Build a table — one row per team, one column per metric that matters this season:
- Average game pieces scored (center)
- Standard deviation of that score (consistency)
- Average penalties drawn (risk)
- Yes/no for key abilities: can it climb? can it play defense?
Then weigh them on purpose. A high average with a huge standard deviation is a gamble; a slightly lower average with rock-steady consistency is often the safer elimination pick. The numbers inform the order — your strategy call sets it.
Quantitative and Qualitative Data Both Matter
- Quantitative data is countable: pieces scored, cycle times, climb success rate.
- Qualitative data is what a scout watches: driver skill, robot reliability, whether a mechanism looked one hard bump from failing.
The best picks come from both. A sheet can tell you a robot averages eight cycles; only a human in the stands can tell you its intake jammed twice and barely recovered. When a number and a scout's eyes disagree, don't pick one — go find out why they diverged.
Read Published Metrics Critically
The FRC community publishes derived metrics so you don't recompute everything yourself. The classic is OPR (Offensive Power Rating) on The Blue Alliance. OPR uses linear algebra across alliance scores to estimate each team's average point contribution — it's not just your average match score halved, because it factors in how strong your partners were.
Useful, but know what it assumes before you trust it:
- It assumes scoring is linear and additive — each robot's contribution simply sums.
- With non-linear scoring, defense, or robots competing for the same objective, accuracy drops. OPR rewards scoring, so a strong defender can look weak.
- Early in an event it's noise. Give it at least four or five matches before reading anything into it.
As The Blue Alliance puts it, OPR can supplement but never replace proper scouting. EPA (Expected Points Added) on Statbotics is a newer model in point units that's more predictive over a season and splits into auto, teleop, and endgame components — but it's still an estimate, calibrated to be wrong a fair share of the time. Use it as a sanity check on your own data, not a substitute for it.
A Simple Decision Workflow
- Collect clean data — one row per match, consistent columns.
- Summarize with center and spread per team.
- Cross-check against scout notes and published metrics like OPR/EPA.
- Rank into a weighted pick list, not a one-column sort.
- Decide, then revisit as new matches land.
Done right, data work doesn't hand you the pick — it makes the pick obvious.
Key takeaways
- Statistics matter only when they change a decision; build a weighted pick list rather than sorting on one number.
- Combine quantitative data (countable metrics) with qualitative scout observations; investigate gaps rather than ignoring them.
- OPR estimates a team's average point contribution but assumes linear, additive scoring and degrades when robots interfere or scoring is non-linear.
- Published metrics like OPR and EPA supplement scouting but never replace it; all metrics are noisy early in an event.
- Follow a repeatable workflow: collect, summarize, cross-check, rank, decide, and revisit as data grows.
Keep going
Take the quiz · +10 XP with an accountMore in Data Foundations: Spreadsheets and Statistics
Sources & 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 — publicly, in the corrections log.
Sources and further reading
- OPR and You – Basic FRC Strategy (The Blue Alliance Blog)blog.thebluealliance.com
- The Math Behind OPR — An Introduction (The Blue Alliance Blog)blog.thebluealliance.com
- Evaluating FRC Rating Models (Statbotics)statbotics.io
- FIRST Robotics Competition (FIRST)firstinspires.org
Read next
Articles on this, for competition day
The lesson covers how it works. These cover what to do when it breaks.
- 13 min read
FRC Alliance Selection Strategy: How Picks, Scouting, and Playoffs Work
A complete, rules-accurate guide to FRC alliance selection: how the serpentine draft works, first- vs second-pick strategy, the scouting inputs behind a pick list, and the double-elimination playoff.
Read - 20 min read
Building an FRC Scouting App: Data Model, TBA/Statbotics APIs, and Picklists
Build 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.
Read - 18 min read
The Blue Alliance (TBA): How to Use FRC's Match & Team Database
The 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.
Read
Lesson quiz
RequiredAll 3 right completes the lesson. Miss one and only that question comes back — anything you already answered correctly stays banked.
0 of 3 answered
01.What is the recommended way to build an alliance pick list?
02.Which is a key assumption behind OPR that limits its accuracy?
03.How should published metrics like OPR be used in scouting?
Answer every question to submit.
All 32 lessons in Scouting & Strategy
- Not started:Project 1: Configure a QRScout Form for REEFSCAPE
- Not started:Project 2: Compute OPR by Hand, Then in a Spreadsheet
- Not started:Project 3: Pull Live Data with the TBA and Statbotics APIs
- Not started:Project 4: Build an EPA-Component Robot Ranking Sheet
- Not started:Project 5: Assemble a One-Page Pre-Match Prep Sheet