3.1 Proof of Readiness
Teams must submit the required proof of readiness materials outlined below for each of the domains in which they will compete and for each system which will be used during the event. These submissions will be reviewed to determine whether teams and their systems are eligible to deploy at competition.
If a system is deemed ineligible, teams will not be permitted to deploy the system at competition. Submissions will be reviewed on a rolling basis during the window defined in Competition Schedule and Timeline, with responses provided in a timely manner. Teams will receive a pass/fail, including any necessary follow-up questions. Teams who receive a fail are permitted to keep submitting attempts up until the close of the submission windows. Submission windows are as follows:
01 April 1 - 31 August 2026
Submission window for Communications Proof of Readiness.
Submission window for mandatory two (2) systems, consisting of a USV and at least one (1) other uncrewed system. If you intend to use a UAV in November, the second system MUST be your UAV.
01 April - 12 October 2026 | Submission window for teams who plan to use a third uncrewed system.
Eligibility for Travel Stipend: Registered teams must successfully pass the mandatory proof of readiness requirements to be eligible to receive a travel/shipping stipend. These stipends are not guaranteed, and will be determined at a later date.
3.1.1 Submission Requirements
The submitted video and file uploads must meet the following requirements:
The entire demonstration must be recorded from start to finish with no breaks in the video.
Videos and text must be conducted in English or include subtitles in English.
Videos must be no more than 5 minutes in length.
Videos and text must include school/organization and team name at the beginning.
Videos and text must include all required content, outlined in the sections below.
3.1.2 USV Proof of Readiness Criteria
Criteria for the required Uncrewed Surface Vehicle (USV) proof of readiness submission includes:
Autonomous Navigation Demonstration (Video Submission) - In a fully autonomous run, the USV must start 3m behind the Gate, and pass through both sets of Gates.
USV must not strike any buoys.
USV must demonstrate good autonomous control throughout the run.
Safety Systems (Photo/Video Submission)
File Upload Submission:
Drawings detailing how the kill switches are wired into the system.
Pictures of clearly marked tow points with proper tow harness.
Pictures of clearly marked lift points and lift harness.
Pictures of propeller shrouds.
Functional Block Diagram and pictures of R/C (manual control) approach demonstrating operation independent of laptop connection.
Video Submission:
Demonstrate onboard and remote kill switch operating correctly.
Demonstrate functionality of the visual feedback system (auto, manual, kill).
How to Build: USV Proof of Readiness Course
The autonomous navigation demonstration course consists of buoys arranged as shown below. The USV must successfully navigate autonomously between two pairs of red and green buoys.
If a team is unable to build a course to meet these specifications, notify RoboNation for alternative instructions to attempt proof of readiness.
Course Elements
Teams may use ANY RED and GREEN buoys to construct the course for this demonstration of autonomous navigation. Buoys should extend approximately 1m above the surface of the water so that they are easily seen in your submission.
3.1.3 UUV Proof of Readiness Criteria
Criteria for the Uncrewed Underwater Vehicle (UUV) proof of readiness submission includes:
Autonomous Demonstration (Video Submission) - In a fully autonomous run, the UUV must start 3m behind the Gate, submerge, pass through the Gate, circle around the Marker, and then pass back through the Gate.
Everything attached to the UUV must submerge with the vehicle (nothing floating on the surface).
UUV must not breach the surface.
UUV must not strike any buoys.
UUV must demonstrate good autonomous control throughout the run.
Safety Systems (Photo/Video Submission)
File Upload Submission:
Drawings detailing how the kill switches are wired into the system.
Pictures of clearly marked tow points with proper tow harness.
Pictures of clearly marked lift points and lift harness.
Pictures of propeller shrouds.
Picture of mounting area for locator beacon.
Functional Block Diagram and pictures of R/C (manual control) approach demonstrating operation independent of laptop connection.
Video Submission:
Demonstrate onboard kill switch operating correctly.
Demonstrate functionality of the visual feedback system (auto, manual, kill).
Demonstrate proof the system is positively buoyant.
How to Build: UUV Proof of Readiness Course
The autonomous demonstration course consists of a Horizontal Gate and a Vertical Marker arranged as shown below.
Horizontal Gate must be:
2m wide.
positioned 1m below the surface of the water.
made of materials of any diameter and any color the team chooses.
anchored to the floor by any means necessary (ex. using PVC elbows to create two vertical legs, with a line on each end to moor the gate to the floor, etc.).
Vertical Marker must be:
positioned 10m beyond the gate.
made of materials of any diameter and any color the team chooses.
Video must make it clear that the vehicle has maneuvered around the marker.
If a team is unable to build a course to meet these specifications, notify RoboNation for alternative instructions to attempt proof of readiness.
Alternate Course for USV/UUV Tethered Pair
For teams who will have a USV tethered to their UUV, the UUV Proof of Readiness may be completed by following the alternate specifications listed below:
In order to avoid tangling of the tether with the underwater gate and marker buoy, teams may construct an alternate course configuration:
Gate: pair of buoys placed approximately 2m apart.
Marker Buoy: must be clearly indicated and placed at least 10m beyond the gate.
Both the gate and marker buoys must extend sufficiently below the surface that it is reasonable for the UUV to perceive and navigate using these as reference points.
In order to demonstrate autonomous capability as specified for the UAV/UUV tethered pair (Section 5.3.2), the submission must comply with the following requirements, at a minimum:
The UUV must remain submerged throughout the run.
Both the UUV and USV must been seen to be operating autonomously for the full duration of the proof of readiness demonstration; we will be looking for both the visual mode indicator on the system and for hands off controllers by your team members.
The USV may autonomously follow the UUV through the course.
3.1.4 UAV and Pilot Proof of Readiness Criteria
Gaining approval for pilots and UAVs to operate at RobotX 2026 is a multi-step process. UAV Proof of Readiness submissions are intended to provide organizers with sufficient Objective Quality Evidence (OQE) to increase the likelihood of obtaining approvals for teams to operate during the event.
Criteria for the UAV proof of readiness submission include the elements listed below:
RobotX UAV Information package (electronic submission)
Teams must complete and submit the UAV and Pilot information package to the best of their ability and work with the organizing team to provide sufficient detail on their aircraft in accordance with requirements set by the Civil Aviation Authority of Singapore (CAAS).
For the purposes of this submission, teams should consider the following when describing UAV configurations:
The UAV airframe and core functional flight elements are considered one configuration.
Addition of payload handling equipment (with or without the associated payload) is considered a second configuration.
Click here to download the UAV Information Package requirements and examples.
Flight Demonstration (Video Submission)
Teams must submit a video demonstrating that the UAV is ready for on-site final evaluation of flight readiness. The video must contain at a minimum the following content:
Introduction (≈ 30 Seconds): This section must include a visual and verbal identification of the School and Team name.
Safety, Risks, and Mitigations: This section should describe the potential safety risks and the steps taken to mitigate them. It should include risks during the development process and during the mission.
Proof of Readiness for Flight: This section must show the UAV from takeoff to landing with the following characteristics:
Manual Operation
Proof the system is in manual mode.
Piloted Takeoff to Above 3m AGL
Flight pattern as shown in the UAV Flight Patterns section below.
Proof that the system remains within the published geofence even when commanded to exceed the boundary.
Proof that the system does not exceed the maximum allowable altitude, even when commanded to exceed this limit.
Piloted Landing
Autonomous Operation
Proof the system is in autonomous flight.
Autonomous Takeoff to Above 3m AGL
Flight pattern as shown in the UAV Flight Patterns section below.
Proof that the system remains within the published geofence, even when commanded to exceed the boundary.
Proof that the system does not exceed the maximum allowable altitude even when commanded to exceed this limit.
Autonomous Landing
Safety Systems (File/Photo/Video Submission)
Teams must submit the following:
File Upload Submission
Picture(s) showing the mounting area for the emergency recovery light.
Picture(s) showing clearly marked safe handling areas for recovery.
Documentation detailing the UAV behaviors in each of the following scenarios:
Loss of link with remote controller
Low battery
Task/Mission abort
Geofence boundary reached
Video Submission (These may be incorporated into the Proof of Flight video)
Video demonstrating proper operation of the following emergency conditions:
Loss of link with remote controller.
Proof of compliance with geofence boundaries.
Proof that the system is positively buoyant.
Remote Controller Compliance (File/Photo/Video Submission)
Documentation of remote controller approach demonstrating compliance with UAV requirements.
Image/video of dedicated remote controller.
UAV Flight Patterns (Manual and Autonomous)
Teams should fly the following flight patterns in their video submissions:
3.1.5 Communications Proof of Readiness Criteria
Radio Frequency Transmitters
All Radio Frequency (RF) equipment must be operated within the rules and regulations of the host country. This includes, but is not limited to frequency, transmitting power, antenna, etc. The organizing team is coordinating broad spectrum clearances with the appropriate authorities. To support these efforts teams must submit radio usage information for the equipment they plan to use on site using the provided template. This information includes the following:
Radio Function
Radio Information: Manufacturer, Model Number, Frequency Range, Center Frequency, Bandwidth, Transmit Power
Antenna Information: Manufacturer, Model Number, Type (Omni, Sector, etc.), Gain
RoboCommand Compliance
Teams must demonstrate their ability to send and receive messages in compliance with the Communications Protocol prior to arrival on site.
This is accomplished by submitting rc-test logs that show a run start sequence as detailed in Section 3.4.10. The run start sequence must be performed with at least two vehicles in the run_declaration message.
Last updated