A session, not an app somebody forgot to open
A lone worker session starts with the visit and runs alongside the work order. The technician confirms they are safe at intervals; if a check-in is missed the system warns, then escalates to the nominated contacts. The monitoring runs on the server, so it keeps working when the phone is in a pocket and the browser is closed.
Only real proof of life counts
The rule that matters is what resets the clock. Only a genuine check-in from the worker does. Activity by a colleague, a page loading, or a job being updated elsewhere does not, because a board that shows someone as safe when they are hours overdue is worse than no board at all.
This is the kind of detail that only comes from operating the thing. The rule exists because the alternative failed somewhere, once.
Journeys and overdue returns
Travel to and from remote sites is covered as well as time on site, with overdue journeys raised the same way as missed check-ins. Supervisors see live sessions, warnings and escalations on one board, and can stand a session down or terminate it with a reason recorded.
Common questions
Does the technician need to keep the app open?
No. Monitoring is server-side, so a missed check-in escalates whether or not the app is in the foreground.
Who gets escalated to?
Nominated contacts, configured per organisation and site, in order, until somebody responds.
Related
See it running on your own asset types
Thirty minutes, no slides. We set up your site structure and show you the product doing the job you actually need it to do. Most teams are live within weeks.
Book a demo