How to write an FTC engineering portfolio

What judges are actually reading for

Not the robot. Judges see the robot separately. What the portfolio has to prove is that a process produced it: that the team considered options, chose between them for stated reasons, tested the result and changed it when the test went badly.

That means the most valuable content in your portfolio is the thing teams instinctively leave out — the design that did not work, and why you abandoned it.

Structure it so it can be skimmed

A judge may have twenty minutes and a stack of portfolios. Structure is not decoration; it is what makes your evidence findable. The notebook outline has the full section list, but the shape is:

1. Who the team is and how it is organised
2. How you read the game and what strategy followed
3. The robot, one section per subsystem, each showing concept → iterations → final with reasoning
4. Software and autonomous, including what you tried and dropped
5. Testing, with numbers
6. Business, budget and sustainability
7. Outreach, measured by what resulted rather than what was attended
8. Reflection

What a credible entry looks like

An entry that convinces a judge has four things: a date, a decision, an alternative that lost, and a measurement.

• Dated, and spread across the season. Entries clustered in the final fortnight say the notebook was reconstructed.
• A named trade-off. "We chose the two-stage lift because it cleared the barrier, accepting the extra 400g" beats any amount of description.
• A number. Cycle time, mass, success rate over ten attempts. One measurement is worth a page of adjectives.
• A failure. A notebook where everything worked reads as a team that never tested.
• Captions that say what changed. Two photos of a mechanism prove nothing unless the caption names the difference.

Outreach that counts

Every team lists outreach; most list attendance. "We ran a workshop for 30 fourth-graders" is an activity. "Four of them joined the middle-school team we helped start, which is now in its second season" is an outcome. Judges are looking for the second, and they are looking for evidence it will continue without you.

Sustainability is a real section, not filler

Sustainability means the team exists next year: funding that is not one sponsor deep, students being trained to replace the seniors, and documentation good enough that knowledge survives graduation. Write what you actually do — the recruiting, the mentor pipeline, the budget — rather than an aspiration.

Write it during the season

Everything above is easy if entries are written the week the work happens and impossible if they are not. Fifteen minutes at the end of a build session, with a photo and a paragraph, produces a better portfolio than a full weekend in February.

Whatever you use — paper log, shared doc, or the notebook in the toolkit — the requirement is the same: writing an entry has to be easier than not writing one.

Before you submit

• Hand it to someone who was not on the team and ask them to explain your intake from it.
• Check every subsystem section actually shows a rejected option.
• Check the dates are spread across the season.
• Check every photo has a caption that says what it demonstrates.
• Read the current season's judging rubric and confirm each criterion has evidence somewhere findable.