RTLS the safety team can defend in an audit.
Mustering, lone-worker and zone control scored as risk controls — not another IT dashboard. Designed for drills, regulators and the 02:00 escalation tree.
What “good” looks like for safety
Regulators and insurers care about time-to-verified headcount, drilled escalation paths, and immutable zone logs — not map cosmetics. A locating programme earns its keep when marshals can clear a muster in minutes and lone-worker duress reaches a human who knows what to do.
That means roster sync (including contractors), coverage honesty in basements and Faraday zones, and hardware rated for the hazard (ATEX/IECEx where required).
The failure modes we design out
Clipboard musters, optional man-down sensitivity that cries wolf, and geofences that ignore live permits. Those create false confidence — worse than no system.
We also separate mustering, zone access and lone-worker as related but distinct jobs so you do not buy one product and expect three outcomes. See mustering, lone-worker safety and zone access.
Evidence packs, not screenshots
Design the audit export on day one: who was where, when, under which permit, and how long to verified muster. If it only lives in a vendor GUI, you will lose the audit argument.
Composite worked examples in mining, energy and utilities show the measurement pattern — then we baseline your sites.
How we engage with EHS
Start with the duty of care and the drill calendar. RF and vendor choice come second. Independence matters here: we do not earn margin on the hardware that will sit in a hazardous zone.
Related reading.
Drill calendar before radio choice
Start from the duty of care and the drill calendar: time-to-verified headcount, escalation tree at 02:00, contractor induction sync, and immutable zone logs. Radios and vendors come second. Hardware in hazardous areas needs certification where mandated — brochure UWB without it is not a safety architecture.
We separate mustering, zone access and lone-worker as related but distinct jobs so you do not buy one product and expect three outcomes.
Vendor-neutral, gate-driven, no reseller margin. Worked examples on this site are composite patterns — we baseline your operation before we quote outcomes.
Buying criteria for EHS locating and mustering
EHS leaders buy faster accountability and audit evidence — not another badge novelty. Criteria for lone-worker, mustering and zone programmes:
- Use-case clarity — SOS/man-down, restricted-zone alerts, automated mustering, contractor control — each with mandated response times.
- Drill-proven performance — worst-zone detection, false-alarm rates and muster latency measured in live drills.
- Integration to EHS and access — escalation into the systems you already run; PPE/training checks at geofences where required.
- Hazardous-area and offline behaviour — certifications and failover that match the site, not the brochure.
- Privacy-aware design — purpose limitation agreed with the DPO before continuous staff location is enabled.
Safety vendors sell wearables; RTLS vendors sell coverage; SIs sell install. EHS should buy evidence packs that survive an auditor and a night drill.
Safety programme failure modes
- Mustering that works in a tabletop and fails when contractors and shift changes are present.
- Man-down sensitivity tuned in an office, flooding the control room with false alarms on the floor.
- No works-council or employee notice path where staff location is identifiable.
- Battery and charging rituals that leave tags dead at the worst moment.
- Alerts without closed-loop response ownership and timestamps.
Questions EHS should ask locating vendors
- Show muster verification time and missing-person detection from a real drill at similar headcount.
- What are false-positive rates for man-down under our motion profiles?
- How do alerts escalate into our EHS/incident platform — and what if the network is degraded?
- Retention, access and purpose limitation: defaults that match our DPIA, not product marketing.
- Hazardous-area certifications for every wearable and gateway in scope.
How TRACIO differs for EHS
We design locating for safety outcomes and audit evidence first — vendor-neutral on UWB, BLE, RFID or hybrid. No hardware margin means we will not upsell badges you do not need. Drill criteria and privacy constraints are written before radios are ordered.
How vendors and SIs pitch safety locating — and what to discount
Lone-worker and mustering vendors emphasise wearables, man-down sensors and dashboards. RTLS vendors emphasise sub-metre location. SIs emphasise coverage maps and install speed. Safety leaders should discount any pitch that cannot show drill evidence: muster verification time, missing-person detection, false-alarm rates and escalation latency under realistic headcount — including contractors and night shift.
Regulatory pressure (process safety, lone-worker rules, evacuation accountability) makes audit trails as important as live maps. A system that cannot produce time-stamped response evidence will not survive the next investigation. Pair that with privacy: continuous staff location for safety needs a documented purpose and DPIA path, especially in EU works-council jurisdictions.
Hazardous-area certification, battery life under continuous monitoring, and offline or degraded-network behaviour belong in the shortlist matrix — not as footnotes after award.
Locating-led safety outcomes EHS can own
Prioritise outcomes EHS can defend: automated mustering that shrinks verification from tens of minutes toward minutes; lone-worker SOS with known location; restricted-zone alerts tied to training or PPE state; and incident replay for learning. Choose RFID chokepoints where presence is enough; choose UWB/BLE where room-level or sub-metre response matters. TRACIO remains vendor-neutral so the radio follows the hazard profile — not a catalogue push.
Buying criteria for EHS locating and mustering
EHS leaders buy faster accountability and audit evidence — not another badge novelty. Criteria for lone-worker, mustering and zone programmes:
- Use-case clarity — SOS/man-down, restricted-zone alerts, automated mustering, contractor control — each with mandated response times.
- Drill-proven performance — worst-zone detection, false-alarm rates and muster latency measured in live drills.
- Integration to EHS and access — escalation into the systems you already run; PPE/training checks at geofences where required.
- Hazardous-area and offline behaviour — certifications and failover that match the site, not the brochure.
- Privacy-aware design — purpose limitation agreed with the DPO before continuous staff location is enabled.
Safety vendors sell wearables; RTLS vendors sell coverage; SIs sell install. EHS should buy evidence packs that survive an auditor and a night drill.
Safety programme failure modes
- Mustering that works in a tabletop and fails when contractors and shift changes are present.
- Man-down sensitivity tuned in an office, flooding the control room with false alarms on the floor.
- No works-council or employee notice path where staff location is identifiable.
- Battery and charging rituals that leave tags dead at the worst moment.
- Alerts without closed-loop response ownership and timestamps.
Questions EHS should ask locating vendors
- Show muster verification time and missing-person detection from a real drill at similar headcount.
- What are false-positive rates for man-down under our motion profiles?
- How do alerts escalate into our EHS/incident platform — and what if the network is degraded?
- Retention, access and purpose limitation: defaults that match our DPIA, not product marketing.
- Hazardous-area certifications for every wearable and gateway in scope.
How TRACIO differs for EHS
We design locating for safety outcomes and audit evidence first — vendor-neutral on UWB, BLE, RFID or hybrid. No hardware margin means we will not upsell badges you do not need. Drill criteria and privacy constraints are written before radios are ordered.
How vendors and SIs pitch safety locating — and what to discount
Lone-worker and mustering vendors emphasise wearables, man-down sensors and dashboards. RTLS vendors emphasise sub-metre location. SIs emphasise coverage maps and install speed. Safety leaders should discount any pitch that cannot show drill evidence: muster verification time, missing-person detection, false-alarm rates and escalation latency under realistic headcount — including contractors and night shift.
Regulatory pressure (process safety, lone-worker rules, evacuation accountability) makes audit trails as important as live maps. A system that cannot produce time-stamped response evidence will not survive the next investigation. Pair that with privacy: continuous staff location for safety needs a documented purpose and DPIA path, especially in EU works-council jurisdictions.
Hazardous-area certification, battery life under continuous monitoring, and offline or degraded-network behaviour belong in the shortlist matrix — not as footnotes after award.
Locating-led safety outcomes EHS can own
Prioritise outcomes EHS can defend: automated mustering that shrinks verification from tens of minutes toward minutes; lone-worker SOS with known location; restricted-zone alerts tied to training or PPE state; and incident replay for learning. Choose RFID chokepoints where presence is enough; choose UWB/BLE where room-level or sub-metre response matters. TRACIO remains vendor-neutral so the radio follows the hazard profile — not a catalogue push.
Frequently asked questions
Will this replace our existing EHS platform?
No. We feed muster, duress and zone events into the systems you already use for incidents and permits — or we say clearly when a new client is justified.
How do you handle false alarms?
Tune on real tasks, publish the escalation tree, and review near-misses weekly. Untuned man-down is how programmes get muted.
What about contractors and visitors?
If they are not in the roster source, “all clear” is fiction. We design induction and visitor sync or fail closed.
ATEX / hazardous areas?
We specify certified hardware where mandated and document the zoning. Brochure UWB without certification is not a safety architecture.
Last updated: 13 September 2026