Safety controllers for mobile robots are the independently rated hardware modules that execute emergency stop, protective stop and speed limiting without relying on the navigation software, and under PUWER 1998 the duty to validate them on site rests with the user, not the manufacturer. That separation is the whole point: when the navigation stack fails, the safety channel still stops the truck. The risk is not theoretical. HSE recorded 24 of the 126 workers killed at work in Great Britain during 2025/26 as struck by a moving vehicle. For a Plant Director on an MHRA-regulated site, that is where automation stalls. Your qualification protocol demands documented evidence that each safety function is rated and verified on its own. The supplier offers a conformity declaration and a brochure. Your auditor wants the performance level, the SIL or category rating, the validation record, and proof the function was tested on your floor.
Why safety evidence stalls robot projects on regulated sites
Three forces collide on a regulated site, and the safety controller sits at the intersection of all three. The first is procurement framing. Mobile robots are bought as vehicles, on payload, lift height, runtime and aisle width. The safety controller is a line in an appendix, if it appears at all. By the time anyone asks which component executes the protective stop, the order is signed and the answer is whatever the manufacturer fitted.
The second is a category error about certification. A UKCA or CE mark records that the manufacturer has declared conformity against the directives applying to the machine. It says nothing about whether that machine is safe in your building, at your aisle widths, with your traffic. PUWER places the duty on the user, and it does not transfer with the invoice.
The third is qualification culture. On an MHRA-regulated site nothing enters routine use without documented evidence that it does what it is specified to do. Your team is fluent in qualifying a filling line. A driverless truck that reroutes dynamically and shares floor space with people does not fit the template, so it lands in a queue nobody owns. Navigation software also changes far more often than safety hardware, so the plant needs a component whose behaviour is fixed, rated and independently verifiable.
Safety controllers for mobile robots are the independently rated hardware modules that execute emergency stop, protective stop and speed limiting without relying on the navigation software, and under PUWER 1998 the duty to validate them on site rests with the user, not the manufacturer.
Lever 1: specify the safety controller before you specify the robot
Write the safety architecture into the tender, not the acceptance test. Three questions settle most of it. Which functions are safety-rated? At minimum: emergency stop, protective stop from the scanner, speed limiting in defined zones, and safe direction or steering monitoring. Ask for each one named individually with the rating it achieves, not a blanket claim that the truck is "safety certified".
Is the safety channel independent of navigation? A controller sharing the processor that runs the mapping stack gives you a single point of failure. A dual-channel architecture on a dedicated safety processor, in effect a safety PLC riding on the vehicle, makes the function verifiable in isolation and lets you argue the case without reference to software you cannot inspect.
Does it speak a documented interface? A controller that exposes its state over an open standard such as VDA 5050 keeps the orchestration layer, M4, and leaves you free to add a machine class later without rewriting the safety case. FlyWei's safety controllers for mobile robots range documents the ratings and interfaces for each class.
Lever 2: validate the safety functions on your own floor
A rating on a datasheet is a claim about a component, while your obligation concerns a system in a building. Close that gap with a validation run. Map the hazards first: blind corners, dock-door transitions, the pedestrian route that cuts the main aisle, the chilled airlock where condensation settles on a scanner lens. HSE guidance on workplace transport is built around exactly these interfaces between vehicles and people.
Then test each safety function against each hazard, and record it. Trigger the protective stop with a test piece at the scanner's rated detection height. Confirm the speed limit applies in the zone you drew. Force an emergency stop mid-lift and record the load's behaviour. Interrupt the network and confirm the truck holds safely rather than continuing on its last order.
Plan the validation window in, because it competes with everything else in commissioning: our guide to how long autonomous forklift commissioning takes shows where that time goes. Sign each test off with a named engineer, a date and a result. That record is what your auditor reads.
Lever 3: build the PUWER and ISO 3691-4 evidence pack
Two references carry most of the regulatory weight. PUWER 1998 (SI 1998/2306) is the duty. Work equipment must be suitable, maintained, inspected, and used only by trained people. Regulation 11 covers dangerous parts of machinery, which is where a moving mast and a powered fork sit. Where the truck lifts, LOLER 1998 applies alongside it.
ISO 3691-4, adopted in Britain as BS EN ISO 3691-4, is the specification. It covers driverless industrial trucks and their systems, and an auditor expects it referenced when you explain how the safety functions were chosen and verified. Check through BSI that you hold the edition in force, not the one quoted in an older tender.
Assemble the pack as one controlled document: the declaration and UKCA mark, each safety function with its rating, your site validation records, the layout as built, supervisor training records, and the inspection interval. Reviewed annually, it answers an inspector's questions in advance.
| Safety function | Typical datasheet claim | What your qualification pack needs | Owner |
|---|---|---|---|
| Emergency stop | "Fitted as standard" | Named category or SIL rating, plus a site test record | User |
| Protective stop (scanner) | "360 degree safety scanner" | Detection height and field geometry verified on site | User |
| Speed limiting by zone | "Configurable zones" | Each zone drawn, tested and signed against the layout | User |
| Load behaviour during stop | Rarely stated | Mid-lift stop tested at rated load, result recorded | User |
| Network loss behaviour | Rarely stated | Documented safe-hold behaviour, demonstrated | Integrator |
Lever 4: standardise one controller family across a mixed fleet
Most plants do not automate in one move. A counterbalanced truck arrives for pallet movements, a narrow-aisle machine follows for high-bay, a low-profile unit handles dock-to-stock. Left alone, each brings a different safety architecture needing its own validation, spares and training.
A common controller family across the fleet collapses that. The safety case is written once against a known architecture and extended per machine class. Supervisors learn one diagnostic behaviour, and spares consolidate to a handful of part numbers. It is the same logic that decides whether a multi-vendor robot fleet can run in one warehouse at all.
This is where an independent integrator earns its place. A single-manufacturer supply chain gives you whatever controller that manufacturer fits. Choosing across manufacturers lets the controller be the fixed point and the machine the variable, which is the right way round: the controller is what your evidence pack rests on, and the machine is what changes when the process does.
What FlyWei does here
FlyWei is an independent UK systems integrator of autonomous forklifts and AMRs. We are not a manufacturer and not a reseller, which is why the safety controller is a specification we set rather than one we inherit.
On a regulated pharmaceutical site the work runs in three stages. We start with the flow, not the machine: a 48-hour read on your highest-volume movement, usually packing through to the quarantine or bonded area, establishes whether it suits a driverless truck at all, and which class fits. That may be a FlyWei autonomous reach truck for high-bay racking, a stacker class for mid-height, or a latent-jacking lifting robot where the load is a wheeled cage.
We then specify the controller against your evidence requirement, naming and rating each safety function before anything is ordered, from the range on our controllers page. Finally we run validation on your floor with your team, producing the signed records for your qualification pack.
M4 manages the fleet and holds the traffic rules, while the robot dispatch software takes work from the systems you already run, so robots receive orders from your existing ERP and WMS rather than replacing them. Regulated operators across the East Midlands corridor, around Magna Park, DIRFT and Burton-on-Trent, meet the same qualification gate, and our solutions pages set out the approach by sector.
Frequently asked questions
What does a safety controller do for a mobile robot?
It executes emergency stop, protective stop and speed limiting independently of the navigation software. Because it is rated and verified on its own, it stays trustworthy when the navigation stack fails.
Is a safety controller the same as a safety PLC?
Close relatives. A safety PLC is a certified logic controller used across fixed plant. A mobile robot safety controller is the same idea packaged for a vehicle, with scanner inputs, zone switching and drive monitoring. Both are evidenced the same way.
What is a category 3 stop on a mobile robot?
Categories describe the structure of a safety function, not how hard the truck brakes. A category 3 architecture uses redundant channels so a single fault cannot defeat the function. Which category or SIL your stop needs comes from your risk assessment.
Does PUWER apply to driverless forklifts?
Yes. PUWER 1998 applies to work equipment provided for use at work, and makes no distinction between a truck with a driver and one without. The duty sits with you as the user.
Is a UKCA or CE mark enough for our qualification pack?
No. A conformity mark records the manufacturer's declaration about the machine, not whether it is safe at your aisle widths and pedestrian routes. The pack needs site validation records too.
What is ISO 3691-4?
The international standard covering driverless industrial trucks and their systems, adopted in Britain as BS EN ISO 3691-4. It is the reference an auditor expects when you explain how each safety function was verified. Copies come through BSI.
What performance level do the safety functions need?
There is no single answer. The required performance level, SIL or category comes out of the risk assessment for your site and layout. Ask each supplier to state the rating achieved per function.
Who signs off mobile robot safety validation on a regulated site?
The user organisation does. A named engineer runs each test and signs the record, your quality function accepts it into the qualification pack, and the integrator supplies the architecture evidence behind it.
Can one safety controller family run robots from different manufacturers?
In practice, yes, where a common controller is specified across the fleet and vehicles expose state over an open standard such as VDA 5050. The safety case then extends per machine class rather than being rebuilt per supplier.
If evidencing mobile-robot safety functions to an auditor is on your Q4 risk register, the quickest way to find out where you stand is one flow.
Get a 48-hour feasibility read on your highest-volume flow, or review the ratings and interfaces across our safety controllers for mobile robots range first.
No obligation. We reply within one business day.
