Compare "Appendix D - Team Classifications and Student Roles": v1.1 → v2.1

One or more Students make up a Team. To participate in an official VEX V5 Robotics Competition event, a Team must first register on events.vex.com and receive a VEX V5 Robotics Competition Team number. A Team’s unique number identifies their organisation and their Team within that organisation. 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 a Secondary School Team if all members are Secondary School Students.
• A Team is classified as a Secondary School Team if any of its members are Secondary School Students, or if the Team is made up of Secondary School Students who declare themselves “playing up” as Secondary School Students by registering their Team as a Secondary School Team.
• Once a Team has competed in an event as a Secondary School Team, that Team may not change back to a Secondary School Team for the remainder of the season. If a Team mistakenly registers as a Secondary 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 groups 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.

• 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 Qualification 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.