Signature Event Standards and Requirements

This article outlines the event standards and requirements Event Partners must meet to be approved to host a Signature Event, including Event Partner experience, team count minimums, Levels, registration limits, required event structure, judging requirements, and event listing requirements. It is written for Event Partners applying to host, or currently hosting, a Signature Event.

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 Qualifying Criteria, in addition to the specific requirements below. To be approved as a Signature Event 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 in managing event logistics, volunteers, field operations, judging, team communications, and delivering high-quality events. Additional consideration may be given to the 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:

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 ensure the event remains on track to meet the required number of competing teams.

Levels

A Signature Event must be single Level only, not blended.

Registration Limits

Each organization may register a maximum of six teams. The organization limit may be lifted eight weeks before the event if space remains available. Any adjustment to the organization limit should be communicated clearly to teams and reflected in the event's registration information.

Waitlisted teams should be reviewed in a fair and consistent manner based on the event's published registration and waitlist policies.

Regional Capacities

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.

Robot Skills Challenge

Robot Skills Challenge matches must be available to teams for a minimum of 2 days.

Teams must be provided with sufficient opportunities to complete Driving Skills and Autonomous Coding Skills attempts without interfering with Qualification Matches, judging, or other required event activities.

Robot Skills fields should be open during clearly published hours, and teams should be informed in advance of when the Robot Skills Challenge will close. The event schedule should include enough field capacity, staff, and operating time to ensure all teams have a reasonable opportunity to complete their permitted Robot Skills attempts.

Required Event Structure

Each Signature Event must include the following meetings and ceremonies:

• An Event Meeting, where the Head Referee and Event Partner review event logistics with participants, including how to queue for matches, the game rules, judging information, safety requirements, and a brief question-and-answer session.
• An Opening Ceremony that welcomes teams, coaches, spectators, volunteers, and invited guests. The Opening Ceremony should include important event announcements, recognition of sponsors or partners, safety reminders, and any other information teams need before competition begins.
• An Award Ceremony that closes the event, recognizing award recipients, volunteers, sponsors, and event staff.

All competition, Robot Skills, and practice fields must be closed during the Event Meeting and ceremonies.

Judging Requirements

Every team must have the opportunity to be judged, following the standard Global Robotics judging process described in the Judges Certification Course. 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 requirements for official awards without prior approval.

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 stating whether registration fees are refundable and under what circumstances, including what happens if the Event Partner cancels the event and what happens if a team registers and then chooses not to attend. The policy must include any applicable deadlines, administrative fees, and the procedure teams follow to request a refund.

Payment Deadline and Waitlist Policy

The event must publish a clear Payment Deadline. Teams that do not complete payment by that deadline move to the waitlist. The event listing must also explain how waitlisted teams are selected and when teams can expect registration decisions.