What Does an FTC Engineering Portfolio Actually Need to Contain to Win Inspire?
Winning the FIRST Tech Challenge Inspire Award requires moving past polished retrospectives. Judges look for documented, messy iteration—including failures—captured in a disciplined weekly cadence.
To win the Inspire Award—the highest peer-reviewed honour in the FIRST Tech Challenge (FTC)—your team must master the art of technical storytelling. Many South African teams assume that the Inspire Award goes to the team with the most polished, glossy portfolio or the highest-scoring robot. This is a fundamental misunderstanding of how judges actually score.
On forums like r/FTC, the single most recurring complaint from competitors is the apparent opacity of the judging process. Teams often receive their feedback forms with generic ticks and zero written comments, leaving them wondering why a team with a simpler robot won the top subjective prize. The reality is that judges are looking for a highly specific, evidence-backed narrative of engineering discipline, not a marketing brochure.
To win Inspire, your engineering documentation must prove that your robot is the logical result of a structured, iterative process, rather than a series of happy accidents.
Portfolio vs. Notebook: Knowing the Rules
Before writing a single line, you must understand the distinction between the Engineering Notebook and the Engineering Portfolio. Under current FTC rules, teams submit a 15-page Engineering Portfolio for the judges to evaluate. However, the full Engineering Notebook remains your team's internal archive. A winning portfolio is not a summary written from memory in the week before the South African National Championship; it is a highly curated distillation of a detailed, daily notebook. If the judges interview your team and suspect your 15-page document was fabricated at the last minute, they will ask to see your full notebook to verify your engineering habits.
What Judges Look For vs. What Teams Assume
The mismatch between team assumptions and judge realities comes down to the polish trap.
| What Teams Think Judges Want | What Judges Actually Reward |
|---|---|
| A clean, linear story where everything worked perfectly on the first try. | Documented failures, snapped components, and the exact reasons why a design failed. |
| High-end, professionally rendered CAD models of the final robot. | A progression of CAD models alongside physical prototypes showing evolution. |
| Vague statements like "We chose a Mecanum drive because it is agile." | Mathematical and physical justifications: "We calculated our torque requirements based on a 15kg load-shedding-proof steel chassis..." |
The Anatomy of a Winning Page
Every page of your portfolio must earn its place. A winning engineering entry should follow a strict structural hierarchy:
- The Problem Statement: Clearly define the specific challenge (e.g., "The intake mechanism is jamming when picking up pixels at an angle of greater than 15 degrees").
- The Constraints: Document your real-world limitations. In South Africa, this often includes budget constraints, local material availability, or limited workshop hours due to load-shedding schedules.
- The Iteration Cycle: Show at least three distinct stages of the design. Include photos of the rough cardboard prototype, the intermediate 3D-printed version that warped, and the final CNC-routed polycarbonate plate.
- The Data: Use tables and graphs. Show the motor RPM, the gear ratios considered, and the test results (e.g., "Design B reduced jam rates by 42% over 50 trial runs").
The judges do not care if your first design worked. They care about how you figured out why it did not, and what scientific steps you took to fix it.
The Weekly Cadence: A Habit, Not a Project
You cannot fake an engineering journey. The most successful teams treat documentation as a core engineering role, equal in importance to CAD design or programming.
At the end of every single workshop session, the documentation lead must capture three things: what was tested, what the quantitative result was, and what the next step is. If you wait until week 10 to write your portfolio, you will lose the raw, authentic details of your early failures. Judges easily spot retrospectives because they lack the specific, messy data of real-time problem-solving.
For South African teams looking to build these structured engineering habits, Sheen Robotics provides targeted mentoring and resources at /ftc to help teams align their weekly workflows with international judging standards.
Acknowledge Your Real Constraints
Do not try to emulate international teams with massive corporate sponsorships and school machine shops. South African judges are highly receptive to resourcefulness. If your team had to hand-file an aluminium bracket because your school's 3D printer was offline during Stage 6 load-shedding, document that. Explain how you adapted your design to accommodate simpler manufacturing methods without sacrificing structural integrity. This level of engineering maturity and adaptability is precisely what defines an Inspire-worthy team.
