Same Robot.
New Rules.
How ISO 10218-2:2025 Moves Compliance from the Robot to the Application
ISO 10218-2:2025 has shifted the unit of safety from the robot to the application. That shift lands differently depending on which side of the deployment you’re on.
Collision safety analysis with SafetyDesigner
With the ISO 10218-2:2025 revision, the weight of responsibility the SI must bear has changed.
The scope of assessment now extends beyond the standalone robot to encompass the workpiece, the end-effector, surrounding equipment, and operator movement paths, and the number of tasks subject to risk assessment has grown from 10 to 22.
Collaborative application is now more explicit. For PFL, Contact force and pressure must be proven numerically, and verification must be re-performed from the beginning each time a change occurs.
Don't worry. Now you know clearly how fast you can operate the robot.
This expanded responsibility can, in fact, become an opportunity with advanced technology.
So you want to run your robot application as a collaborative application — no fences, no light curtains, no safety sensors. That is exactly what a collaborative robot is built for.
But before the guarding comes down, one question has to be answered: have you actually performed the collision safety analysis? And do you hold a report that proves, in numbers, that the application is safe?
The good news: ISO 10218-2:2025 now spells this out clearly — so it is no longer a guessing game. Follow what the standard sets out, and you have your path.
A risk assessment is not a one-time gate you clear at installation. Every time the robot application changes, the assessment has to be performed again — and it must be conducted at the level of the entire robot application, not the robot alone. So whether it is the operator's task that changes or simply the motion of the gripper, the risk assessment must be carried out again, from the beginning.
