Overview#
A utility technician enters a confined space alone at 06:00. At 06:32, the expected check-in does not arrive. Within seconds, supervisors receive an overdue alert showing the worker's last known GPS position. The Lone Worker domain makes that chain of events automatic: it manages check-in sessions, escalates missed check-ins, and surfaces SOS and man-down emergencies at the top of the safety dashboard.
Key Features#
- Lone worker session lifecycle management: active, overdue, SOS, man-down, and ended
- Configurable check-in intervals with a default of 30 minutes
- Five check-in types: manual, automatic, SOS, man-down, and supervisor check
- Missed check-in counting with configurable alert thresholds
- GPS location tracking on check-ins with last known position updates
- Vitals data capture: heart rate, motion, and battery level
- Overdue session detection for supervisor alerting
- Session statistics dashboard: active, overdue, SOS, man-down, and total
- Priority-ordered session display for safety dashboards, with SOS first
- Optional work order linking for field assignment context
Use Cases#
Relevant sectors include critical infrastructure, law enforcement, and defence field operations.
- Monitoring field worker safety with configurable check-in schedules
- Detecting overdue check-ins and escalating to supervisors for follow-up
- Responding to SOS and man-down alerts with location-aware dispatching
- Tracking worker safety statistics across the organisation
Integration#
The Lone Worker domain integrates with Work Orders for session-to-assignment linking and National Telemetry for aggregated worker safety data.
Open Standards#
- BS 8484 (UK Lone Worker Device Service): The domain's session lifecycle (active, overdue, SOS, man-down, ended), configurable check-in intervals, missed-check-in counting, and supervisor escalation directly implement the duty-of-care monitoring requirements codified in this British Standard for lone worker protection services.
- GraphQL (June 2018 specification): All session management, check-in recording, supervisor dashboard, and escalation operations are exposed as a typed GraphQL API, enabling clients to query and mutate lone worker state over a single endpoint.
- JSON Web Token (RFC 7519) with RS256: Every GraphQL operation on the lone worker domain is gated by an RS256-signed JWT verified against a JWKS endpoint, ensuring only authenticated and authorised principals can start sessions or trigger welfare checks.
- WGS 84 (EPSG:4326): Worker location is stored and transmitted as decimal-degree latitude and longitude on the WGS 84 geodetic datum, the coordinate reference system used by GPS and all major mapping services.
- ISO 8601: All temporal data, session start and end times, check-in timestamps, and next-check-in-due windows, are represented as ISO 8601 UTC datetime values.
- RFC 4122 (UUID): Every session, check-in record, itinerary leg, and partner assignment is identified by a version-4 UUID, ensuring globally unique, non-colliding keys across tenants and organisations.
Last Reviewed: 2026-02-24 Last Updated: 2026-04-14