Maryland FIRST RoboticsPreparing Your Robot for Inspection at a Maryland FRC Event
A successful FIRST Robotics Competition event begins well before the robot reaches the inspection queue. Teams must demonstrate that their machine is safe, legal, identifiable and ready to operate within the current season’s rules. A careful inspection plan also reduces pit congestion and gives drive teams more time to practise before qualification matches.
For Australian teams visiting Maryland, preparation involves an extra layer of planning. Metric tools, international shipping, school-term schedules and volunteer requirements can affect the build calendar. Whether your team is based in Sydney, Melbourne, Brisbane or elsewhere, the same principle applies: treat inspection as an engineering milestone rather than a final administrative task.
Start With The Current Rules
Download the latest FIRST Robotics Competition manual, inspection checklist and event-specific updates before making final design decisions. The game manual takes precedence over advice from previous seasons, online forums or old team notebooks. Pay particular attention to robot construction, starting configuration, bumpers, electrical systems, software, pneumatics and permitted mechanisms.
Create a compliance worksheet with a page for every major inspection area. Record the relevant rule number, the person responsible and the date of the last check. When a design changes, update the worksheet immediately. This habit makes it easier to explain a feature to an inspector and helps new students understand why a component was selected.
Australian teams should plan around local school calendars and competition travel. A robot leaving Adelaide or Perth may need to be packed days before a Maryland flight, while teams from Sydney or Melbourne may be working through a different term schedule from their US counterparts. Build in time for a final inspection at home, followed by a second check after transport.
Verify Documentation And Identification
Inspectors need to connect the physical machine with the correct team and event records. Confirm that the team number is visible where required and that robot labels, battery markings, sponsor information and other identification are legible. Keep a printed and digital copy of the team roster, consent records, emergency contacts and event details in the pit.
Prepare a compact inspection folder containing the robot checklist, wiring diagram, pneumatic layout, software version, motor-controller inventory and notes about unusual mechanisms. A clear diagram is especially useful when several students share responsibility for electrical work. It can also help mentors explain troubleshooting decisions without taking control away from students.
Documentation skills matter beyond competition. Teams writing sponsorship proposals, equipment requests or volunteer materials may use editing support to improve clarity, while students should still own the technical content and verify every claim. A well-organised folder supports safer decisions and makes handovers between mentors and students much easier.
Inspect The Mechanical And Electrical Systems
Begin with the robot’s frame, fasteners and moving parts. Check that every structural component is secure, that sharp edges are covered and that mechanisms cannot unexpectedly deploy while the robot is disabled. Look for loose chain, exposed gears, cracked brackets, excessive play in shafts and fasteners that have loosened during repeated testing.
Battery security deserves special attention. Confirm that the battery is firmly restrained, its leads cannot rub against metal and the connector cannot be pulled loose during impacts. Inspect the main breaker, power distribution components, fuses, wire gauges and terminal crimps. Use strain relief wherever cables move or connect to a device, and label both ends of important cables.
A final weight and size check should use the robot’s actual competition configuration, including bumpers, battery, protective covers and any required attachments. Do not rely on a CAD estimate. Weigh the machine on a calibrated scale and measure it in the positions most likely to be examined. If your team buys replacement parts from the Australian market, allow for shipping delays from overseas suppliers and keep approved spares available.
Test Software Pneumatics And Safety
Software inspection is easier when the programming team can demonstrate a controlled startup and shutdown. Confirm that the correct season libraries and firmware are installed, the robot is identified properly and the driver controls match the physical labels. Test disabled mode, autonomous mode, teleoperated mode and emergency procedures with the robot raised safely or wheels clear of the floor.
Check that sensors are mounted securely and that commands fail safely when a sensor is disconnected. A loose encoder or damaged cable can produce unpredictable movement even when the mechanical assembly appears sound. Record a known-good software release and keep a backup on more than one approved device.
For pneumatic systems, verify legal pressure limits, tubing condition, fittings, storage tanks, relief components and compressor operation. Bleed the system during transport according to the rules and your team’s safety procedure. At the event, never energise a mechanism in a crowded pit. Establish a verbal warning, a clear test area and one person responsible for authorising movement.
Safety culture should extend to outreach and mentoring. Teams supporting underrepresented students can find useful mentorship ideas for assigning responsibilities without excluding beginners. Students should learn how to inspect a robot, ask questions and stop a test when something looks unsafe.
Rehearse The Inspection Conversation
A mock inspection should feel like a real technical review, not a quiz designed to catch students out. Ask students to explain the robot’s power path, describe how the battery is secured, identify the main breaker and show how the machine is made safe. Rotate the speaker so that knowledge does not sit with one mentor or one senior student.
Run the rehearsal in the packed competition configuration. Include bumpers, tools, spare batteries and the pit materials that will travel to Maryland. Check whether the robot can be moved through doors and placed on the inspection scale without removing essential parts. Photograph the approved configuration so the team can restore it after transport or repairs.
For teams running community events, a light game can make technical ideas approachable. A probability demonstration using a play-focused activity can support a discussion about randomness, testing and calculated risk, while the robot inspection itself teaches a more practical lesson: reliable results come from repeatable processes.
| Inspection Area | What To Verify At Home | Useful Event Evidence |
|---|---|---|
| Robot identity | Team number, labels and documentation are clear | Printed checklist and team records |
| Structure | Fasteners, edges, frame and moving mechanisms are secure | Physical demonstration |
| Power | Battery restraint, breaker, wiring and connectors are sound | Wiring diagram and visual inspection |
| Pneumatics | Tubing, pressure control, fittings and relief protection comply | Pneumatic layout and controlled test |
| Software | Correct version, modes, controls and sensor responses work | Safe demonstration and backup release |
| Configuration | Weight, dimensions, bumpers and attachments match the rules | Measured robot in competition setup |
Build A Reliable Pit Workflow
The inspection queue is easier to manage when the pit has defined roles. One student can handle documentation, another can answer mechanical questions, and another can operate the robot under mentor supervision. A fourth person should record requested changes and confirm that each issue is resolved before the team returns for reinspection.
- Perform a complete inspection rehearsal at least one week before travel.
- Measure and weigh the robot with its real bumpers, battery and attachments.
- Photograph wiring, pneumatic routing and the approved packing configuration.
- Pack metric hand tools, threadlocker, labels, cable ties and tested spare parts.
- Keep printed rules, checklists and diagrams in a waterproof document wallet.
- Assign students to speak with inspectors while mentors provide quiet support.
- Record every inspection correction so the design team can prevent repeat problems.
Australian teams should also review travel and safeguarding requirements well ahead of departure. Volunteer checks vary by jurisdiction, such as a Working With Children Check in New South Wales or a Working With Vulnerable People registration in the Australian Capital Territory. These do not replace Maryland event requirements, so mentors should confirm the host organisation’s current procedures before travelling.
A practical pit kit may include metric Allen keys, because many Australian teams build and maintain equipment in metric sizes, along with any imperial tools required by the robot’s imported components. Keep tools organised and avoid bringing untested modifications to the event. If a repair is necessary, document the change, retest the robot and reassess whether it affects inspection compliance.
Your robot is ready when students can explain its design, prove that it operates safely and restore it after transport without guesswork. Use the inspection checklist as a learning tool, complete the mock review, and arrive at the Maryland event with time reserved for questions and reinspection. That preparation gives the team more confidence in the pit and more attention for the engineering, teamwork and competition that follow.