FIRST
®
Tech Challenge Game Manual Part 1 – Remote Events | 39
Gracious Professionalism
®
- “Doing your best work while treating others with respect and kindness - It’s what makes FIRST, first.”
Team Information – The Team name, Team number, a photograph of the Robot, a photograph of the Team
school or club information, the Team City and State, Team motto. Please do not include the full name of any
student, coach, or mentor in the Engineering Portfolio.
CAD drawings, business plan information, award Information, accolades, Team size, Team goals, and other
‘content’ will be viewed as Engineering Portfolio content and is counted as a page in the portfolio.
Team Plan – Any descriptor of Team goals. This could include a strategic plan that references Student
recruitment, sponsorship, mentor recruitment, outreach efforts, fundraising goals, or Team learning goals.
9.2 Engineering Portfolio
9.2.1 Overview
This section describes the requirements for creating the Engineering Portfolio, including formatting guidelines.
9.2.2 What is an Engineering Portfolio?
An Engineering Portfolio is a short and concise summary of the Team’s engineering journey throughout their
season. The Engineering Portfolio should include sketches, discussions and Team meetings, design evolution,
processes, obstacles, goals and plans to learn new skills, and each Team member’s concise thoughts
throughout the journey for the season, the Engineering Portfolio is like the Team’s CV or resume.
One of the goals of FIRST and FIRST Tech Challenge is to recognize the engineering design process and the
journey that a Team makes. This journey encompasses the phases of the problem definition, concept design,
system-level design, detailed design, test and verification, and production of the Robot.
9.2.3 Engineering Portfolio Formats
Teams may choose to document their summary portfolio with either handwritten or electronic documents.
There is no distinction made between handwritten and electronic Engineering Portfolios during judging; each
format is equally acceptable.
a) Electronic: Teams may choose to use any electronic programs to create their Engineering Portfolio.
o For remote event judging, Teams must create a single PDF file of their Engineering Portfolio.
o For traditional events, Teams must print their Engineering Portfolio.
b) Handwritten: Teams can choose to create a handwritten version.
o For remote event judging, this is discouraged due to difficulties in scanning into a readable,
sharable, online version.
9.2.4 Engineering Portfolio Requirements
1. To be considered for judged awards, a Team must submit an Engineering Portfolio.
a) Teams who do not submit an Engineering Portfolio will not be considered for judged awards.
2. The total number of pages for an Engineering Portfolio must not exceed 15 pages, plus a cover sheet
for a total of 16 pages.
a) Cover sheet may include the Team Information and a
table of contents.
i. Allowed Team Information is limited to Team
number, Team name, Team location, Team
school or organization, Team motto and an
image of the Robot and/or the Team.
b) Cover sheet may not include other Engineering
Portfolio content.