Robot safety standards: what ISO 10218 means in practice
A look at the practical obligations the industrial robot safety standard creates for manufacturers and integrators, beyond the paperwork.
When a company decides to introduce industrial robots into a production line, the safety standards documentation usually arrives as a stack of PDFs and a compliance checklist from the integrator. ISO 10218, the main international standard covering the safety of industrial robots, is revised periodically and the 2011 version - still current as of this writing - is specific enough to have real operational implications for anyone running or maintaining robotic systems.
Most of the conversation about robot safety at the business level stays at the level of "we need to comply" and "our integrator handles that." Both statements can be true while still leaving important decisions unmade at the owner level.
What the standard actually covers
ISO 10218 comes in two parts. Part 1 covers the robot itself - what the manufacturer must build in. Part 2 covers the integration of robots into a system or cell - what the person installing and commissioning the robot in a specific environment must ensure.
Part 2 is where most of the practical obligations for end-users and integrators sit. It requires a formal risk assessment for the complete robot system in its specific installation, covering all the modes in which the robot will operate including teaching, maintenance, and recovery from faults, not just normal production running.
That risk assessment is not a formality. It must identify hazards, evaluate severity and likelihood, and document what mitigations have been applied. The record must be maintained and updated when the cell changes.
The collaborative robot question
By 2014 collaborative robots - systems designed to work alongside humans without traditional hard guarding - had moved from research laboratories into real production. ISO 10218 Part 2 contains provisions for this, covering four modes of collaborative operation: safety-rated monitored stop, hand guiding, speed and separation monitoring, and power and force limiting.
Each mode has specific technical requirements, and the choice of which mode to apply depends on the risk assessment for the specific task and layout. The fact that a robot is marketed as "collaborative" does not automatically determine which mode applies or whether a given application is safe without guarding. That determination still requires the risk assessment.
This is a point where business decisions and engineering decisions overlap in a way that is worth the owner understanding directly, not just delegating.
Maintenance modes and the real incident risk
A disproportionate share of robot-related incidents happen during maintenance, fault recovery, and setup - not during normal production. This is well-documented in incident data and it is reflected in the standard's requirements to address these modes explicitly.
The operational implication is that safety procedures for maintenance access - lock-out/tag-out, safeguard suspension, speed limitations during teaching - need to be designed and trained, not improvised. An integrator who hands over a cell with a thorough risk assessment for production running but thin documentation for maintenance modes has left a significant gap.
What changes as robots become more capable
The capabilities of robotic systems are changing faster than standards revision cycles. Vision systems, more sophisticated path planning, and the ability to handle greater variability in parts and environments are all expanding what robots can do. What advanced robotics development reveals about the direction of everyday automation helps set the context for where standards will need to catch up. But the fundamental safety principle does not change: a systematic risk assessment, specific to the installation, updated when the system changes.
The standard provides a framework, not a guarantee. Two cells using the same robot model can have very different safety profiles depending on how they are laid out, what they process, and who has access to them.
A question worth asking integrators
When commissioning or reviewing a robotic installation, I find one question consistently useful: show me the risk assessment and the maintenance safety procedures as two separate documents. If the second document is thin or missing, that is a gap worth addressing before the first incident rather than after.