The Engineering Portfolio Path
The single most important document your team will produce this season. It must be finished before the first qualifying tournament — and building it right requires the whole team.
Of every Right Brain skill on this team, the Engineering Portfolio has the highest leverage. It is required reading for every judged award in FTC — Think, Innovate, Control, Design, Connect, and Motivate — and it is the deciding document for the Inspire Award, the single award that advances a team in the AeroCoast League to the State Championship, and from State to the FIRST Championship.
Robots break. Drivers have rough days. Autonomous scripts crash. What gets your team to advance is a portfolio that proves how your team thinks. Judges read it before they ever meet you, and they pass it between each other during deliberation. Get this document right and you have won half the battle before the first match of the season.
The Reality Check
This Is a Season-Long Project, Not a Writing Assignment
A winning portfolio documents dozens of outreach events, every significant engineering decision, every failed prototype, every sponsor conversation, every community partnership, and the full arc of the robot’s development from kickoff to competition. The photos, the meeting notes, the CAD progression, the build journal — none of that exists unless someone was capturing it in real time, all season long. The “writing” at the end is really just assembly. The work is the documentation that happens every single week from September onward.
Plan accordingly. There is no shortcut version of this document that wins anything.
The Hard Deadline
This Document Must Be Competition-Ready Before Your First Qualifying Tournament
AeroCoast League Timeline
The AeroCoast League runs four regular meets before the qualifying tournament. Those meets are practice — for the robot and for the portfolio. The season kicks off in September. That means your portfolio needs to be in a competitive, judge-ready state no later than mid-December to early January at the absolute latest. If you are still drafting sections the week before the qualifier, you have already lost ground to teams that finished in November.
Build your timeline backward from the qualifier date, not forward from kickoff.
| When | Portfolio Milestone |
|---|---|
| September — Kickoff | Start the engineering notebook immediately. Every meeting documented from day one. |
| September–October | Read 3–5 winning portfolios. Build your 15-page outline. Assign page owners. |
| Meet 1 & 2 (Oct–Nov) | First rough draft complete. Outreach events documented. Photos being captured continuously. |
| Meet 3 & 4 (Nov–Dec) | Full draft with all sections. Photos placed and captioned. Design process pages drafted. |
| 🔴 Mid-December / Jan | HARD DEADLINE — Portfolio must be competition-ready. Final polish and PDF export. |
| Qualifying Tournament | Submit. Present. Win. |
The Most Important Thing Nobody Tells You
You Cannot Write This Document Without the Left Brain Team
Right Brain and Left Brain Are One Team
The portfolio’s most heavily judged section — the Engineering Design Process — is entirely about what the Left Brain team built, designed, tested, and iterated on. You do not need to understand every line of code or every mechanical calculation. But you absolutely must know what problems came up, how the team decided between competing solutions, what failed and why, what was rebuilt, and what the final design rationale was.
That knowledge does not come from reading notes after the fact. It comes from being present. The Right Brain portfolio leads must attend build sessions regularly, ask questions, take photos, and keep running notes on decisions as they happen. If you are not in the room when the intake gets redesigned for the third time, you will not be able to write about it compellingly — and judges will notice.
The portfolio team and the build team are not separate. They are one team doing two different jobs that depend on each other completely.
Team Structure
It Takes a Strong Lead and a Real Support Group
One student cannot write a 15-page competition portfolio alone. This is not a solo assignment — it is a team project with a clear lead and defined roles. The Portfolio Lead owns the document, drives the timeline, and is responsible for the final product. But they need writers for specific sections, photographers at every build session and outreach event, a CAD liaison who can get clean screenshots from the Left Brain team, and at least one editor who reads every page aloud before submission.
The Portfolio Lead must be someone with strong organizational and writing skills who is also willing to show up to build sessions and ask questions. They need the authority to set internal deadlines and hold teammates to them. This is one of the most demanding leadership roles on the entire team — Right Brain or Left Brain.
Before You Start — Required Reading
Two Pages on This Site You Must Read First
Read these before you draft a single page of your own:
📄 The Most Important Document — what the portfolio is, why it controls every judged award, and what FTC requires page by page → 🏆 Award-Winning Portfolios — a curated gallery of real portfolios from teams that have won at State and Worlds → ⚖️ Judges, Awards & Scoring — exactly how the Inspire Award is scored, and why it outweighs winning the field → 📚 Hivemind FTC Portfolio Library — the largest public collection of award-winning FTC portfolios, multiple seasons →The Five-Stage Journey
How to Actually Build This Document
Read 3–5 Winning Portfolios — Before You Write Anything
You cannot write what you have never seen. Open the Hivemind FTC Portfolio Library and the Award-Winning Portfolios page on this site. Pick three to five portfolios from teams that won the awards you are targeting — Inspire, Think, Rookie All-Star. Read each one cover to cover. No skimming.
Note how they open, how they structure the design process section, how they balance technical and non-technical pages, how photos are captioned, and how they close. Make a running list of what works — layouts, voice, diagram styles, page structures you want to borrow.
Build Your 15-Page Outline — and Assign Every Page an Owner
FTC allows a maximum of 15 pages plus a title page. Every page must earn its place. Before anyone writes a sentence, build a complete page-by-page outline: section names, subheadings, target content, which photos go where, and which Left Brain liaisons you need information from.
The split between technical (Left Brain) pages and non-technical (Right Brain) pages should be roughly even. A portfolio that is 12 pages of CAD and 3 pages of outreach will not win Inspire — and neither will the reverse. Assign a named student to own each section. No orphaned pages.
Draft the Engineering Design Process Section — The Heart of the Document
Judges spend more time on this section than any other. You are walking them through one complete design cycle: identify the problem → brainstorm → prototype → test → iterate → final solution. Show the journey, not just the destination. This is where the Right Brain team’s presence at build sessions pays off — you need real dates, real decisions, real failures, and real explanations of why the team changed direction.
Pick one robot subsystem — intake, drivetrain, scoring mechanism — and walk through its full design history. Include at least one failure and what the team learned from it. Reference specific build journal entries by date. Use short paragraphs, captioned photos, and labeled CAD screenshots from the Left Brain team.
The single most common mistake: writing about the robot instead of writing about the engineering process. Judges already see the robot. What they cannot see — what only the portfolio can show them — is how the team thinks.
Integrate All Visual Assets — Photos, CAD, and Outreach Documentation
A captioned photo is worth a thousand bullet points. In this stage you transform the draft into a visual document. Every photo cropped tight — no empty workshop floor, no random clutter. Every CAD view labeled with dimensions where relevant. Every caption written to explain what it shows and why it matters, not just what it is.
This is also where your season of continuous photography pays off — or where you discover you don’t have the photos you needed. Teams that had someone photographing every build session and every outreach event have a rich library to draw from. Teams that didn’t are now scrambling. Keep one consistent layout pattern across the document. Judges feel the polish even when they can’t name it.
Final Layout, Polish, and the Tablet Test
This is where good portfolios become winning portfolios. Consistent fonts, page numbers on every page, color accents that match your team identity, and a non-engineer proofreader on every page. If someone who was not in the build room all season cannot follow what you wrote, the sentence needs to be rewritten.
Export to PDF and read the entire document on a tablet. That is how judges actually read it — not on a desktop monitor, not printed out. Check that every photo is sharp, every caption is visible, and every page number is present. Count the pages. Count them again. Anything beyond page 15 is not reviewed by judges — and the judges will not tell you they stopped reading.
Have Questions? Reach Out.
Your mentors and student team leaders have worked through these materials and can help you get unstuck — on the portfolio, on documentation strategy, or on how to coordinate with the Left Brain team.
✉ Email the Coach Read: The Most Important Document →Winning teams aren’t louder. They aren’t richer. They aren’t smarter. They’re the teams that started documenting in September, stayed connected to their Left Brain teammates all season, finished the portfolio before December was over, and walked into the judges’ room ready — because the document in that judge’s hand told the whole story.