PART 1: OVERVIEW AND IMPORTANCE

1.1. What Is an Engineering Portfolio?

In the modern FTC competition system, the Engineering Portfolio is likened to the team's "CV" (Curriculum Vitae) or "Resume."

It is the most concise summary, distilling the very best highlights from the team's entire season journey.

It is the only mandatory document that must be submitted to the judges at competitions.

It acts as a "gateway" leading judges to explore the team more deeply. If the Portfolio is impressive enough, judges will then request to view the Engineering Notebook (an optional, more detailed document).

1.2. Why Is the Portfolio Important?

The Portfolio is the key to unlocking Awards. In the FTC judging system, the Portfolio directly impacts the evaluation for the most prestigious awards:

Major awards requiring a strong Portfolio:

Inspire Award: The highest honor, requiring a well-rounded, strong Portfolio (Engineering + Outreach + Teamwork).

Think Award: An award recognizing the engineering design process (evaluated solely based on the Engineering Section in the Portfolio).

Connect & Motivate Awards: Evaluated through the Outreach and Business Plan sections in the Portfolio.

Control Award: Evaluated through the Software/Programming section (requires submitting the Control Award Submission Form alongside it, though the content itself must be included in the Portfolio).

PART 2: TECHNICAL RULES AND CRITERIA

To avoid having your portfolio disqualified right at the "door," teams must strictly comply with the rules in Game Manual Part 1:

2.1. Limits and Formatting

Page Count: Maximum of 15 content pages.

IMPORTANT NOTE: The Cover Sheet does not count toward these 15 pages. If you submit 16 content pages, the judges will tear off the final page and will not score it.

Paper Size: Standard A4 or Letter (8.5 x 11 inches).

Font: There are no strict rules, though a minimum size of 10pt is recommended. Photo captions may be smaller, provided they remain legible to the naked eye. Layout: Flexible. You can use a Landscape orientation to optimize space for timelines and horizontal photos, or Portrait orientation.

2.2. Other Rules

Team Number: Must appear clearly right on the cover sheet. It is recommended to place the Team Number in the Header/Footer of every page to prevent misplacement.

External Links: Using QR codes or links leading to videos/websites is discouraged. Judges have very limited time (about 5–10 minutes to read) and are generally not permitted to use electronic devices to access unfamiliar links. All evidence must be on paper.

Submission Format: For Offline competitions: Submit a printed Hard Copy. For Online competitions (if applicable): Submit a PDF file.

PART 3: DETAILED CONTENT STRUCTURE

Below is the recommended structure to optimize your 15 pages and ensure full coverage of all judging criteria.

3.1. Cover Sheet - Does not count toward the 15 pages

Required Information: Team Number.

Recommended Information: Team Name, Logo, Season, and the most impressive featured photo of the Robot or the entire team.

Purpose: Immediate brand recognition.

3.2. Team Info & Culture - Approximately 1–2 pages

This section targets the Connect and Motivate awards, as well as the "Team Attribute" criteria for the Inspire Award.

Team Bio: A brief introduction to the team's history and philosophy/Motto.

Team Roster:

• List of members accompanied by photos.
• Clearly state Roles: Who is the Hardware Lead, Software Lead, Driver, Human Player, Media, etc.
• Diversity and standout personal stories, if applicable.

Sustainability Plan:

• How will the team sustain operations after 12th-grade members graduate? (Recruitment Plan).
• Internal Mentoring activities: How veteran members train newcomers.

3.3. Engineering Design Process - Approximately 6–8 pages

This is the most critical section (the core focus of the Think Award, Design Award, and Innovate Award). Do not just tell "what you did"—explain "how you did it" and "why."

Strategy & Goals:

• Game Analysis: Which strategy did the team choose? (e.g., focusing on high-scoring tasks or focusing on defense?).
• Design Requirements: Based on that strategy, what characteristics does the robot need (speed, strength, or precision?).

Iterative Process: This is the golden keyword. Present your work following this cycle:

• Brainstorming & Sketching: Rough hand-drawn sketches.
• CAD: 3D design visuals (using Onshape, Fusion 360, etc.).
• Prototyping: Test prototypes built from cardboard, wood, or rough 3D prints.
• Testing & Failure: Failed test runs and iterations.
• Refining: Improvements leading to the Final version.

Concrete Evidence:

• Use real photos comparing "Version 1 vs. Version 2."
• Data tables: For example, a table comparing the shooting speeds of 3 different wheel types to select the best one.
• Math/Physics formulas: Proving gear ratios, center-of-gravity calculations, or projectile trajectories.

3.4. Software & Control - Approximately 2–3 pages

The core focus of the Control Award. Do not paste entire pages of raw code (judges will not be able to read them).

Autonomous:

• Describe your autonomous strategy.
• Use Flowcharts to illustrate your logic.
• Sensors utilized: Gyro, Encoder, Color Sensor, Distance Sensor, Camera (Computer Vision/AprilTag).

TeleOp:

• Driver enhancements. For example: Pressing a single button to automatically return an intake/claw to its home position (Automation/Macros).
• Safety features in the code.
• Intelligent Control: Mention advanced algorithms if used (PID Controller, Odometry, Motion Profiling, etc.).

3.5. Outreach & Connect - Approximately 2–3 pages

Connect:

• List of Mentors and professional engineers the team has met.
• Lessons learned from them (not just meeting to take photos, but gaining actual technical or professional insights).

Motivate/Outreach:

• Robot demo events at schools and science fairs.
• Charity and fundraising activities.
• Assisting other FTC teams.
• Impact Metrics: How many people were reached? How much money was raised?

3.6. Business Plan / Finance - Approximately 1 page

Budget: Pie charts showing Income (Sponsorships, Grants, Self-funding) and Expenses (Robot parts, Registration fees, Travel, Marketing).

SWOT Analysis: Strengths – Weaknesses – Opportunities – Threats.

PART 4: WORKFLOW

To produce 15 high-quality pages, the team needs a structured workflow from the very start of the season.

4.1. The "Team Historian" Role

Assign 1–2 members specifically dedicated to Documentation.

Responsibilities: Take photos at every meeting, record videos of robot test runs, keep rough sketches (do not throw them away!), and take screenshots of buggy code alongside the fixed code.

Use cloud storage (Google Drive, OneDrive, etc.) with structured folders (technical, outreach, business, notebook) for easy retrieval when compiling the portfolio.

4.2. Meeting Logs

Even though you do not submit all your Meeting Logs, they serve as the database for writing your Portfolio.

Log Structure: Date & Time -> Attendees -> Meeting Goals -> Tasks Completed -> Results/Failures -> Next Meeting Plan.

4.3. Recommended Tools

Storage: Google Drive/OneDrive. Organize into clear folders: 01. CAD, 02. Code, 03. Photos (sorted by date), 04. Outreach.

Design:

• Canva: Easy to use, plenty of great templates, strong team collaboration features.
• Adobe InDesign/Illustrator: More professional, offering superior print control.
• Google Slides/PowerPoint: Simple and easy for quick edits.

Important Note: Start with the goals the team set at the beginning of the season and cross-reference them against each award's requirements. Start writing early, revise multiple times, ask for feedback from mentors, and avoid rushing at the last minute, as quality will suffer.

PART 5: VISUAL AND DESIGN STRATEGY

Competition judges often get fatigued from reading dozens of Portfolios. Make your document "Easy to Read – Easy to Understand – Easy to Remember."

5.1. The "Show, Don't Just Tell" Principle

Instead of writing: "We tested several types of grippers and chose the best one." (Unconvincing)

Present it as: Photo of Gripper A (Failed due to slipping) -> Photo of Gripper B (Failed due to weight) -> Photo of Gripper C (Succeeded), accompanied by a grip-strength data table. (Convincing).

5.2. Layout Techniques

White Space: Do not cram text from edge to edge. Leave breathing room so the eyes can rest.

Highlight Keywords: Bold or color-code technical keywords (e.g., PID Control, Iterative, CAD). Judges often skim to look for keywords.

Use Bullet Points: Avoid long paragraphs (Walls of text). Use bullet points to summarize ideas.

Consistency: Use a unified color palette and 1–2 fonts consistently from page 1 to page 15. This creates a professional brand identity (Branding).

PART 6: INTERACTING WITH JUDGES (JUDGING)

The Portfolio is not just a document you hand in; it is the script for your interview.

6.1. In the Interview Room (Formal Interview - 10 minutes)

The team has 5 minutes to present. Ensure that what you say matches what is written in the Portfolio.

When answering questions, cite the Portfolio: "As you can see on page 7, we encountered this issue and resolved it by..."

Bring spare copies of the Portfolio to hand to the judges during the presentation (in case visual aids are needed).

6.2. In the Pit Area (Pit Interview)

Note: After the main interview round, judges will visit the technical area (Pits) to ask follow-up questions.

Pit Copy: Always keep a nicely printed color copy of your Portfolio ready at your Pit table. When visitors or judges stop by, open it up and walk them through it.

Use the Portfolio to back up your statements. If a judge asks about Code, immediately flip to the Software page to explain.

PART 7: COMMON MISTAKES.

MISTAKES TO AVOID:

• Too wordy: Judges do not have time to read a novel. Use infographics instead.
• No Captions: Every photo and diagram needs a caption.
• Showing only successes: A Portfolio lacking "Lessons Learned" from failures is a Portfolio lacking depth of thought (Think).
• Spelling and terminology errors: Misspelling award names or misusing technical terms (e.g., calling a "Motor" an "Engine") will cost you impression points.
• Forgetting the Team Number on the cover sheet: A basic mistake that many teams still make, causing difficulties in document management.