How FTC awards actually work

Two families of award

Performance awards come from the field: winning alliance, finalist alliance, and the top qualifying seed. You influence these by building a good robot and being picked.

Judged awards come from a panel of volunteers who read your portfolio, visit your pit, and talk to your students. These are decided on evidence, not on scores, and a team that has never won a match can win one.

The second family is where most teams leave points on the table, because the evidence has to be gathered across the whole season and cannot be produced on the day.

What each judged award rewards

• Think: the engineering journey itself. What problem you identified, what you tried, what failed, and why you chose what you chose. This is the portfolio award.
• Connect: reaching outward to the engineering community, professionals, mentors and sponsors, plus a real plan for growing the team.
• Innovate: a creative or ingenious solution, a mechanism or approach nobody else on the field is running.
• Design: industrial design done well. A robot that is sturdy, serviceable and deliberately built rather than assembled.
• Motivate: team spirit and spreading FIRST. Outreach, recruiting, and how the team works together.
• Control: sensors and software advancing the machine. Autonomous, telemetry, tuning and control systems.
• Inspire: the whole package, with strong evidence in every other category at once. It ranks first for advancement.
• Regions also run additional awards: rookie-specific ones, judges' discretionary picks, and individual awards for students and mentors. The event's award list is published; read it.

Inspire is an aggregate, not a separate competition

There is no Inspire submission. It goes to the team that is credible across every other category simultaneously: decent robot, real engineering process, documented outreach, working software, a team that presents well.

This is why it advances furthest, and why chasing it directly does not work. The route to Inspire is to be genuinely in contention for three or four of the others.

How judging actually happens

Judges read submitted materials before or early in the day, then visit pits in pairs on a schedule you do not control. You get a short interview, often five to ten minutes, and possibly a follow-up visit if you are in contention. Deliberation happens between the panels, from notes.

Three consequences follow. Your portfolio is read by people who have not met you, so it has to stand alone. Your pit interview has to work when it interrupts a repair. And the students, not the mentor, have to be able to answer. Judges notice immediately when an adult takes the question.

What a rookie team can realistically win

The awards that reward effort rather than accumulated capability are the ones to aim at in year one.

Motivate is the most winnable: it rewards team spirit, recruiting and outreach, none of which require a competitive robot. Connect is next, because a team that genuinely built relationships with local engineers and sponsors can show it in the first season. Think is winnable by any team that documented honestly during the season, and honest documentation of a robot that mostly failed is often more compelling than a polished account of one that worked. Many regions also run rookie-specific awards worth checking for.

Design, Innovate and Control generally need a robot that is further along. That is a reason to write them off this year, not a reason to write off judging.

Awards are how young teams advance

Advancement from an event is a fixed, small number of slots, filled from both routes: the winning alliance and the award list, with Inspire ranking first. For a team that is unlikely to be the strongest robot in the room, the judged route is not the backup plan; it is the plan.

You can see who has won what, at which events, across every season in the award records, including the teams in your own region, which is a fast way to see what a winning entry in your area looks like.

What to do about this in September

• Read this season's judging rubric, not a summary of it. The criteria are published and they are specific.
• Pick two awards to genuinely target, and check every month whether you have evidence for them.
• Start the portfolio in week one; writing it during the season is the whole difference.
• Record outreach as outcomes with numbers and dates as it happens, not as a list in April. See outreach that wins Connect and Inspire.
• Practise the pit interview with someone outside the team, twice, before the first event.
• Tag documentation entries with the award they support so the gaps are visible while there is still season left. The documentation workspace does this.