This article outlines the event standards and requirements Event Partners must meet to be approved to host official VEX Robotics Competitions during the 2026-2027 season, including team count minimums, registration limits, required event structure, and judging requirements.
Definitions of the terms used here are maintained in the central glossary.
For registration limits on teams per organization, see the Team and Organization Registration Policy. For notebook guidance referenced in judging, see Engineering Notebook Rubrics.
All events covered by this article must follow the requirements outlined in the Event Qualification Guide, in addition to the specific requirements below. To be approved for the 2026-2027 season, Event Partners must meet and agree to the following.
Event Standards
Event Partner Experience
The Event Partner must have successfully hosted official VEX Robotics Competitions during each of the previous two competition seasons.
The Event Partner should demonstrate experience managing event logistics, volunteers, field operations, judging, and team communications, and should show a track record of delivering high-quality events. Additional consideration may be given to an Event Partner's history of meeting event requirements, submitting results on time, and providing a positive experience for teams and participants.
Minimum Team Counts
Events must meet the following minimum number of registered and competing teams:
| Program | Minimum Teams |
|---|---|
| VEX U | 12 teams |
| VEX V5 High School | 64 teams |
| VEX V5 Middle School | 50 teams |
| VEX IQ | 50 teams |
Events that do not meet the minimum team count may be required to adjust their event structure, combine divisions where permitted, or submit an alternative plan for approval .
Registered teams should be monitored throughout the registration period to help ensure the event stays on track to meet the required number of competing teams.
Level Structure
Events must be limited to a single grade level. Blended divisions or events that combine multiple grade levels are not permitted. Middle school and high school teams must compete in separate events or divisions, as applicable.
Registration Limits
No more than 50% of the registered teams at an event may come from a single region . This requirement helps ensure broad geographic representation and gives teams from multiple regions reasonable access to the event.
Each organization may register a maximum of six teams . The organization limit may be lifted eight weeks before the event if space remains available .
Waitlisted teams should be reviewed in a fair and consistent manner based on the event's published registration and waitlist policies.
Robot Skills Challenge
The Robot Skills Challenge must be available for at least two days of the event . Teams must be given sufficient opportunities to complete Driver Skills and Autonomous Coding Skills attempts without interfering with qualification matches, judging, or other required event activities.
Skills fields should be open during clearly published hours, and teams should be told in advance when the Robot Skills Challenge will close. The event schedule should include enough field capacity, staff, and operating time to give all teams a reasonable opportunity to complete their permitted skills attempts.
Event Listing Requirements
The event listing on events.vex.com must include complete and accurate information for teams before registration opens. At a minimum, the listing must include the following.
Refund Policy
The event must publish a clear refund policy explaining whether registration fees are refundable and under what circumstances.
The policy should include any applicable deadlines, administrative fees, cancellation conditions, and procedures teams must follow to request a refund.
Payment Deadline and Waitlist Policy
The event must publish a registration payment deadline.
Teams that do not complete payment by the published deadline may be moved to the waitlist or removed from the event, provided this process is clearly stated in advance.
The event listing must also explain how waitlisted teams will be selected and when teams can expect to receive registration decisions.
Required Event Structure
The event must include the following scheduled activities.
Event Meeting
An Event Meeting must be held before competition begins. The meeting should review important rules, event logistics, field procedures, queueing expectations, judging information, and safety requirements, and give teams the chance to ask questions.
Competition, practice, and Robot Skills fields must remain closed during the Event Meeting so all teams and key event staff can attend.
Opening Ceremony
The event must include an Opening Ceremony that officially welcomes teams, coaches, volunteers, spectators, and invited guests. The ceremony should include important event announcements, recognition of sponsors or partners, safety reminders, and any other information teams need before competition begins.
Award Ceremony
The event must conclude with an official Award Ceremony that recognizes award recipients, volunteers, sponsors, and event staff, and provides a professional and celebratory conclusion to the event.
All awards must be presented in accordance with the official Competition Judge Guide and the published award criteria.
Judging Requirements
All teams must be judged using the official Global Robotics and Science Foundation Competition Judge Guide. Judging must be conducted consistently and fairly across all divisions, using the official award criteria, interview process, deliberation procedures, and Engineering Notebook guidance .
Event Partners may not create alternative judging criteria or modify the requirements for official awards without prior approval.