Skip to content
Drive Team·Lesson 31 of 34

Building Pick Lists That Survive Reality

Construct robust, scenario-based pick lists that account for your seed, robot archetypes, and reliability.

Sign in to track progress, earn XP, and save lessons.

A pick list is not a power ranking — it's a decision tool for the few high-pressure minutes of alliance selection. The classic FRC mistake is building one ranked list and freezing when reality diverges from it. Top teams build scenario-based lists.

Make multiple lists, because your role isn't fixed. Standard practice is to prepare separate lists for the situations you might land in: one for if you're an alliance captain (you pick the best complement to your robot), and one for if you're being picked / picking later (the strong robots are gone, so you optimize among what remains). The right first pick for a top FUEL-scoring captain is different from the right first pick for a captain whose strength is defense and endgame.

Rank by complementary fit, not raw score. If your robot is an elite FUEL farmer, your highest-value partner may be a reliable TOWER climber and HUB defender — not the second-best farmer. Use the EPA component breakdown to find complements: pair your strong teleop-EPA with a partner who has strong endgame-EPA, and you cover two ranking-point thresholds at once. Build the list around what your alliance needs to clear ENERGIZED + SUPERCHARGED + TRAVERSAL, not around who has the prettiest highlight reel.

Weight reliability heavily. A robot that averages high but died in 2 of 11 quals is a coin flip in elims, where one disable can end your tournament. Annotate every candidate with a reliability flag from your own scouting (the public OPR/EPA can't see a robot that broke). Many strong teams will deliberately rank a slightly-lower-scoring but bulletproof robot above a flashier, fragile one.

Tier, don't just rank. Group candidates into tiers (A: pick immediately; B: good; C: situational; DNP: do-not-pick for reliability/behavior reasons). Tiers survive the chaos of selection better than a brittle 1-through-N list, because when your top choice is taken you just grab the next name in the tier instead of re-deriving everything live.

Pre-decision the hard calls. Decide in advance: do you prioritize a second strong scorer or a dedicated defender for your second pick? Do you ever pick a robot that can only play defense? Walking into the selection table with these answers already made is what separates calm captains from teams that burn their pick on whoever the crowd is cheering. The list is the artifact; the pre-made decisions are the real value.

Key takeaways

  • Build separate scenario lists (as captain vs. as a later picker) - the optimal pick depends on your role and who's left.
  • Rank by complementary fit using EPA components (pair your strength with a partner who covers a different ranking-point threshold), not raw score.
  • Tier candidates (A/B/C/DNP) and weight reliability heavily, since public analytics can't see a robot that died in quals.

Lesson quiz

Required

Answer all 3 questions correctly to complete this lesson.

1.When building a pick list, why is robot reliability/consistency weighted heavily alongside peak scoring?

2.Statbotics' EPA (Expected Points Added) is useful for pick lists largely because it is designed to do what?

3.What does it mean for a pick list to 'survive reality' on selection day?

Answer every question to submit.