Compare "Appendix E - Team Classifications and Student Roles": v2.0 → v2.1

−Removed: Version 2.0 (Old)

Three or more Students make up a Team. To participate in an official VEX IQ Robotics Competition event, a Team must first register on events.vex.com and receive a VEX IQ Robotics Competition Team number. A Team’s unique number identifies their organization and their Team within that organization. Each Team must design and build their own Robot, create their own code, develop their own strategies to play the game, and maintain their own engineering notebook if they choose to use one.

• A Team is classified as an Elementary School Team if all members are Elementary School Students.
• A Team is classified as a Middle School Team if any member is a Middle School Student, or if the Team is made up of Elementary School Students who declare themselves as “playing up” as Middle School Students by registering their Team as a Middle School Team.
• Once a Team has competed in an event as a Middle School Team, that Team may not change to an Elementary School Team for the remainder of the season. If a Team mistakenly registers as an Elementary School Team but is ineligible for that age group, their registration may be revised mid-season with the assistance of VEX Robotics; all prior qualifications for the season will be lost.
• Teams may be associated with schools, community/youth organizations, or a group of neighborhood Students.

In the context of this Game Manual, Student Team members fill multiple roles related to Robot design, build, coding, strategy, and documentation. See G2, G4, G5 for more information. Adults may not fulfill any of these roles.

+Added: Version 2.1 (New)

To participate in an official VEX IQ Robotics Competition event, a Team must first register on events.vex.com and receive a VEX IQ Robotics Competition Team number. A Team’s unique number identifies their organization and their Team within that organization. Each Team must design and build their own Robot, create their own code, develop their own strategies to play the game, and maintain their own engineering notebook if they choose to use one.

All rules concerning the eligibility of both individual Students and their Teams are set forth in the Student Eligibility Policy, such as Student age restrictions, Team size requirements, and more.

In the context of this Game Manual, Student Team members fill multiple roles related to Robot design, build, coding, strategy, and documentation. Adults may not fulfill any of these roles. See G2 and G4 for more information.

• Designer - Any Student Team member who helps design the Robot to be built for competition. Adults are permitted to teach Designers associated concepts, but should never work on the design of the Robot.
• Builder - Any Student Team member who helps build the Robot. Adults are permitted to teach Builders associated concepts, but should never work on the Robot.
• Coder - Any Student Team member who contributes to the computer code that is downloaded onto the Robot. Adults are permitted to teach Coders associated concepts, but should never work on the code that goes on the Robot.
• Strategist - Any Student Team member who contributes to the Match strategies used to score points during a Teamwork Match or Robot Skills Match, including assessing the impact of other Teams’ performance and strategies on the Team’s strategy (e.g., scouting). Adults are permitted to teach Strategists associated concepts, but should never create or dictate a Team’s Match strategy.
• Notebooker - Any Student Team member who contributes to the Team’s engineering notebook or associated documentation. Adults are permitted to teach Notebookers associated concepts, but should never work on the engineering notebook or other documentation.