Safety, Roles, and Competition Boundaries

Robotics becomes dangerous when people treat “I know what I am doing” as a safety control.

A competition robot can contain high current, stored mechanical energy, pinch points, spinning mechanisms, heavy assemblies, sharp edges, compressed air, and software capable of moving hardware faster than a person can react. The correct response is not fear. It is procedure.

FIRST treats safety as part of the program, and the current game rules require robots to be safe and inspectable. That means safety is not a separate poster hanging on the wall. It changes how the machine is designed, tested, repaired, and operated.

The first boundary: energized or de-energized

Before changing wiring or a mechanical assembly, determine whether the robot must be powered.

For most physical changes, the safest default is:

disable robot
→ remove active control
→ power down
→ remove or isolate energy
→ verify the mechanism cannot move
→ make the change
→ inspect
→ restore power for a controlled test

Do not move wires because “it is only one connector.” Do not put a hand into a mechanism because “the code is disabled.” A disabled robot can still contain stored energy, gravity-loaded mechanisms, springs, pneumatics, or another person about to enable it.

Roles are access controls

FRC teams divide work for a reason. Mechanical, electrical, programming, drive team, strategy, scouting, pit crew, and inspection roles are not walls between people, but they create ownership.

A useful rule is:

The person making a change should know who owns the affected system and how the change will be verified.

A programmer changing motor inversion affects a mechanical system. An electrical student moving a CAN connector affects software visibility. A strategist requesting a faster cycle can create mechanical and controls risk.

Good teams make these crossovers visible instead of discovering them in a match.

Scenario: “We only need a quick test”

The intake was rewired. Someone wants to enable the robot immediately because the next match is close.

Before enabling, inspect the chain:

Skipping these steps can save thirty seconds right up until it costs ten minutes, a damaged part, or an injury.

Competition rules are engineering constraints

Each season has a game manual. Robot construction, allowed devices, dimensions, weight, power distribution, control systems, bumpers, inspection, and match behavior are governed by that current manual.

This course teaches architecture that survives across seasons. It does not replace the current manual.

When a design decision depends on legality, write the rule source next to the decision. Do not rely on “we used this last year.” Rules change.

Build your safety boundary card

For one subsystem from Lesson 1, write a small operational card with:

1. the main hazards;
2. the conditions required before physical work;
3. who should know before a change is made;
4. the controlled test you would run afterward; and
5. the evidence that would convince you the subsystem is safe to return to service.

If you do not have hardware, use the same process on a subsystem diagram and identify the hazards that would exist on the physical robot.

Failure mode: safety by memory

A checklist is sometimes treated as something beginners need until they “know the robot.” That is backwards. Experienced technical work uses checklists because experienced people know memory gets worse under interruption and time pressure.

The boring part is often the part that keeps the robot available for the next match.

Keep the card. Unit 9 will turn it into part of your inspection and readiness dossier.