Skip to content
HiO Robots

AMR safety guide

AMR Safety Standards: ISO 3691-4 Site Checklist

Turn the applicable safety standard into a site-specific checklist before an AMR pilot, acceptance test or production handover.

HiO Robots editorial team9 min read

An AMR safety review is a system review, not a checkbox for the robot alone. Start with the exact machine and attachment, then prove the operating zone, traffic behavior, load handoffs, abnormal cases and people-facing procedures under the conditions where the AMR will actually work.

Start with scope

ISO 3691-4 is a system reference, not a substitute for site assessment

ISO 3691-4:2023 specifies safety requirements and means of verification for driverless industrial trucks and their systems. Its examples include automated guided vehicles and autonomous mobile robots, and it notes that the operating zone has a significant effect on safe operation. That means the buyer still needs a site-specific assessment for floors, crossings, people, loads, interfaces and foreseeable misuse.

In the United States, OSHA says there is no robotics-specific OSHA standard. Applicable workplace duties remain, while ANSI/RIA R15.08 provides industrial-mobile-robot guidance for the robot and its system/application. Use the standards as the technical basis, then document how the delivered project meets local obligations.

Diagram comparing autonomous mobile robot and guided vehicle navigation choices
Use the navigation and operating-zone choice to identify the hazards that need a site test.

Site readiness

Build the checklist around the real operating zone

Walk the complete route with operations, safety, maintenance and the integrator. Record the normal path and the places where a person, pallet, door, lift or temporary obstruction changes the risk. The same AMR can require different controls in a quiet aisle and a mixed pedestrian zone.

AMR safety site checklist
Control areaEvidence to collect before acceptance
Operating zoneFloor, edges, crossings, doors, lifts, lighting, pedestrians, emergency access and restricted areas are mapped.
Robot and attachmentPayload, dimensions, stopping performance, scanners, bumpers, top module and failure states are documented.
Traffic and peopleRight-of-way, speed, crossing behavior, exclusion zones, manual overrides and recovery roles are agreed.
Load handoffsPickup/drop-off detection, stability, dropped-load response and workstation interfaces are tested.
Controls and evidenceRisk assessment, validation tests, training records, maintenance instructions and change control are retained.

Treat the operating zone as a deliverable

Mark route boundaries, pedestrian crossings, emergency access, charging locations and recovery points on the same controlled drawing used for validation. A safety claim that cannot be tied to a location is hard to test or maintain.

Verification

Test normal, abnormal and recovery behavior

A useful acceptance plan tests more than an empty route. Include the highest intended payload, representative carriers, normal traffic, a blocked path, a missed handoff, a low battery, loss of network or interface confirmation, and a safe stop/restart sequence. Define who observes each test, what result is required and how an exception is closed.

  • 01Verify detection, stopping and restart behavior at each crossing and interaction point.
  • 02Verify load stability, pickup/drop-off confirmation and the response to a failed handoff.
  • 03Verify manual recovery, maintenance access, isolation and emergency communication.
  • 04Record software, map, speed and zone configuration versions with the test result.
HiO X300 autonomous mobile robot used as an example AMR platform
The robot model is only one part of the evidence; validate the complete platform, payload and route.

Operations

Make handover and change control part of the safety case

Before production use, hand over the approved map, zones, traffic rules, load limits, inspection points, escalation contacts and training records. Keep a clear owner for software changes, route edits, new attachments and temporary construction changes. A new rack, door or workflow can alter the risk even when the AMR hardware is unchanged.

Link the safety file to your AMR project scope and quote, and use the robot platform pages to confirm payload and configuration assumptions before requesting a proposal.

Buyer questions

FAQs

Does ISO 3691-4 apply to every AMR project?

ISO 3691-4:2023 covers driverless industrial trucks and their systems, including many AMR and AGV examples. Confirm the exact scope, local adoption and any additional requirements for your machine, attachment and site.

Is a robot safety scan enough for acceptance?

No. The scan is one control. Acceptance should also cover the operating zone, traffic rules, load and attachment, interfaces, abnormal conditions, training, maintenance and evidence that the complete workflow performs safely.

Does OSHA publish one AMR standard?

OSHA states that it does not have a robotics-specific standard. U.S. projects still need applicable workplace rules and a documented risk assessment; standards such as ANSI/RIA R15.08 can provide relevant technical guidance.

When should the safety review be repeated?

Repeat it after changes to routes, loads, top modules, software, speed limits, doors, lifts, pedestrian controls, facility layout or maintenance procedures, and after incidents or near misses.

Sources

Ready to scope a safer AMR pilot?

Share the load, route, people flow, handoffs and site constraints so the first proposal includes the evidence your team needs.

Discuss your workflow