Two of the highest-leverage paths to qualifying — and the ones most teams leave completely untapped. This guide covers both from first principles to competition strategy.
In qualification rounds, teams are ranked by Win Points (WP). A normal match win gives 2 WP. An AWP gives 1 additional WP, bringing a win to 3 WP. That one extra point compounds across every match you earn it.
Assume a team wins 7 matches and loses 1 in qualifications. Compare two scenarios:
Same win-loss record. The team earning AWPs consistently has 50% more win points — which means a dramatically better seeding position for alliance selection.
When the new season launches, your first autonomous design meeting should answer: what exactly are the AWP conditions this year, and can we reliably meet them in 15 seconds? That question should be answered before any other autonomous design decision.
Teams sometimes over-engineer their AWP routine by trying to score high and earn the AWP in the same 15 seconds. This is the wrong approach when you are learning. A simple, 90% reliable AWP routine is worth more expected win points than a complex 50% reliable one that also scores higher.
Your Skills rank at an event uses: best Programming Skills score + best Driver Skills score from the same event. These must be from the same event — you cannot combine your best programming score from one event with your best driver score from another.
Teams that struggle in qualification matches — because of a difficult schedule, getting paired with weak alliance partners, or early mechanical issues — can still earn a State or Worlds bid through Skills. This is a real backup path that teams should pursue actively, not as an afterthought.
| Factor | Match Autonomous (15 sec) | Skills Autonomous (60 sec) |
|---|---|---|
| Duration | 15 seconds | 60 seconds — 4x longer |
| Field access | Half field — opponent present | Full field — no opponent |
| Goal | Score bonus + AWP tasks | Maximize total score |
| Positioning | Alliance-specific (red/blue) | Same start each attempt |
| Odometry value | Helpful for accuracy | Essential — long routes drift without it |
| Route complexity | Short, 2–4 movements | Long, multi-zone, 10+ movements |
Top Skills autonomous runs follow a predictable structure. Build your route in this order — each phase can be developed and tested independently.
In a 15-second match autonomous, small heading errors do not compound much. In a 60-second Skills run crossing the entire field, a 2-degree heading error accumulates into a 6-inch position error by the time you reach the far zone. Without odometry correction, long-range Skills runs drift unpredictably between attempts.
If your team has not built odometry yet, see the Odometry guide and Odom Pod Build. Odometry returns more competitive value in Skills than anywhere else.
Teams that approach Driver Skills as "drive around and score whatever you can" leave significant points on the table. The top Driver Skills scores come from teams that have a pre-planned route, practice it until it is muscle memory, and execute it consistently under the added pressure of an official run.
In a qualification match, you share the field with a partner and two opponents — your robot covers roughly one quarter to one half of the field. In Driver Skills, you have the whole field. Most teams do not take full advantage of this. The design question is not "where do I score?" but "in what order do I visit every zone to maximize points per second?"
Unlike a qualification match where there is no coaching allowed from the field, in Driver Skills the coach can stand at the field boundary and call out time and targets. Establish a system before the event:
| Date | Event / Practice | Score | Phase Reached | Notes |
|---|
| Date | Event / Practice | Score | Route Phase | Notes |
|---|