Overview
In FIRST Tech Challenge (FTC) competitions, your engineering portfolio is more than a document—it’s your team’s voice, journey, and innovation showcase. With increasing emphasis on engineering documentation and design process, a well-crafted FTC engineering portfolio can be the difference between standing out or blending in.
Whether you’re a rookie team or a seasoned contender, this comprehensive guide will help you understand what makes a portfolio successful, how to structure it effectively, and how to meet the latest FTC guidelines. Let’s dive in!
What Is an FTC Engineering Portfolio?
H3: The Purpose Behind the Portfolio
The FTC engineering portfolio is a condensed, visual representation of your team’s engineering notebook. It’s submitted to judges and used during interviews to highlight your:
- Engineering design process
- Team structure and outreach
- Robot development and iterations
- Coding strategies and problem-solving
- Community engagement and STEM impact
It’s typically 15 pages maximum and replaces the physical notebook during judging sessions.
Why the FTC Engineering Portfolio Matters
H3: It’s the Key to Judged Awards
Your portfolio is used by judges to determine eligibility for awards such as:
- Think Award – Emphasizes the design and problem-solving process
- Inspire Award – Overall top team across all areas
- Connect Award – Community outreach and STEM connection
- Control Award – Focuses on coding and autonomous excellence
Judges read your portfolio before your interview, so it’s your first impression. A strong one can influence their questions and scoring.
Understanding FTC’s Engineering Design Process
H3: What Judges Look For
The best portfolios follow and document the Engineering Design Process (EDP):
- Identify the problem – What challenge are you solving?
- Research – What ideas exist?
- Brainstorm – Generate possible solutions
- Prototype – Build rough versions
- Test and evaluate – What works? What fails?
- Iterate – Improve based on testing
- Implement – Final version
- Reflect – Lessons learned
Your portfolio should naturally walk through this process for both hardware and software development.
FTC Engineering Portfolio vs. Engineering Notebook
| Feature | Engineering Portfolio | Engineering Notebook |
|---|---|---|
| Length | Max 15 pages | No limit |
| Purpose | Judged awards | Documentation history |
| Submitted | Yes (to judges) | Not mandatory |
| Format | Condensed, visual | Detailed, chronological |
| Focus | Highlights & summary | Daily work & full records |
Your notebook supports the portfolio, but your portfolio gets judged.
How to Structure an FTC Engineering Portfolio
H3: Suggested Format for Maximum Impact
Here’s a proven FTC engineering portfolio layout that aligns with judging criteria:
1. Cover Page (1 page)
- Team name, number, season
- Team logo and theme
- Contact info and social media
2. Table of Contents (1 page)
- Clearly list sections with page numbers
- Make it easy for judges to navigate
3. Team Introduction (1 page)
- Member roles and contributions
- Team story and identity
- Diversity, leadership, and collaboration
4. Robot Design Process (3-4 pages)
- Iterative robot designs with sketches/images
- Mechanical choices and justifications
- Design matrix (pros and cons of options)
5. Programming & Control Systems (2 pages)
- Autonomous development
- Sensor use and integration
- Strategy with TensorFlow or OpenCV
- Custom algorithms or control enhancements
6. Game Strategy (1 page)
- Scouting and gameplay analysis
- Alliance strategies and scoring goals
7. Outreach & Community Impact (2 pages)
- STEM events hosted or attended
- Mentorship, volunteering
- Connection with professionals or engineers
8. Reflection and Team Growth (1 page)
- Challenges overcome
- Lessons learned
- Future goals
9. Appendices or References (Optional)
- Diagrams, source code links, citations
Pro tip: Keep it visual, use bullet points, captioned images, and avoid dense text blocks.
Design Tips for a Judge-Friendly Portfolio
H3: Layout & Visual Style
Judges review many portfolios, so design matters! Use:
- Clear headers and subheaders
- Consistent fonts and branding
- High-quality, labeled images
- Infographics for data or code flow
- White space to reduce visual fatigue
Use color schemes that reflect your team brand but don’t compromise readability.
SEO Tip (for teams posting portfolios online)
If you’re publishing your FTC engineering portfolio online (e.g., on a blog or team site):
- Use the keyword FTC engineering portfolio naturally in headings and alt text
- Include file download links with descriptive names like
FTC_Engineering_Portfolio_Team12345.pdf - Use Schema.org markup for articles or educational content to improve search indexing
- Add metadata like author, date published, and relevant categories
Tools & Software for Portfolio Creation
H3: Recommended Tools
- Canva – Templates and drag-and-drop design
- Google Slides / Docs – Collaboration and formatting
- Adobe InDesign – Professional design control
- Lucidchart – Flowcharts, wiring diagrams
- GitHub – Link to code for Control Award
Use cloud collaboration to ensure all team members contribute.
FTC Judging: What Portfolios Should Demonstrate
H3: Based on FTC Judging Rubrics
Judges score teams based on how well the portfolio supports:
- Engineering excellence – Clear iteration, testing, and analysis
- Team collaboration – Documentation of roles and joint problem-solving
- Creativity and innovation – Unique solutions or efficient design
- Sustainability – Outreach, recruitment, community efforts
Match your content with the FTC Award Descriptions and Rubrics.
How to Submit Your FTC Engineering Portfolio
- Submit digitally as a PDF before your tournament (check local event rules)
- Have digital and printed copies during judging
- Include QR codes to videos, websites, or GitHub if helpful
FTC Engineering Portfolio Checklist
- Follows 15-page limit
- Highlights full engineering design process
- Includes team roles and strategy
- Showcases community outreach
- Visually engaging layout
- Reflects team personality and identity
- Includes robot design iterations and reasoning
- Explains programming strategies clearly
- Matches award criteria and rubrics
- Proofread and consistent formatting
Real Examples from Winning Teams
H3: What You Can Learn from Top Portfolios
Many FTC teams post their award-winning portfolios online. Search for:
- “FTC Inspire Award portfolio example”
- “FTC Team [team number] engineering portfolio PDF”
- “Winning FTC Think Award portfolio”
Analyze how they present design iterations, balance visuals with text, and structure their content. Emulate—not copy—their clarity and completeness.
Final Thoughts: Your Portfolio Is Your Legacy
A great FTC engineering portfolio is more than a checklist. It’s your story—how your team worked, learned, and grew. It’s a powerful combination of documentation, creativity, communication, and engineering insight.
With the right structure, tools, and understanding of what judges value, your portfolio can not only earn awards but inspire others.
Frequently Asked Questions (FAQs)
How long can an FTC engineering portfolio be?
Up to 15 pages, not including a cover page or table of contents. Keep it concise but comprehensive.
Is the engineering notebook still required?
Not required for judging but highly recommended for internal documentation. Judges only review the portfolio.
Should we include code in the portfolio?
Include highlights or key algorithms in visual form. You can link to full code via GitHub or QR codes.
Can we use AI tools like ChatGPT for portfolio help?
Yes! As long as the work remains your own, tools like ChatGPT can help with writing clarity, grammar, and formatting ideas.
What makes a portfolio stand out to judges?
Clarity, visuals, engineering insight, and connection to the design process. Let your unique journey and problem-solving skills shine through.
