ModulesLone WorkWork Control
Nobody working alone goes unchecked.One session record, from the first check-in to the outcome.
For supervisors, control rooms and site safety leads with people on night rounds, remote pump stations or weekend maintenance: start a session in one tap, check in at an interval the job sets, and a missed check-in climbs a named chain until someone acknowledges it.
3 people working alone · next check-in in 18 min
- Started
- 18 Nov 2026 · 22:00
- Planned end
- 19 Nov 2026 · 02:00
- Check-ins
- 22:00 start · 22:29 · 22:58 · 23:31
- On time
- Last check-in 23:31 · next due 00:01
- Reached
- No one yet
| Level | Person | Role |
|---|---|---|
| 1 | Grace Okafor | Monitor |
| 2 | Daniel Kim | Shift supervisor |
| 3 | Sofia Rossi | Site manager on call |
This is not an alarm-receiving service. Escalation reaches people through UProcess only (board and To do).
One session, three readings. An example session; the fields are the product’s, the values illustrative.
Where it connects
Also on the handover: Shift Handover, Confined Spaces, Energy Isolation, Bypass Control and 38 more modules in one workspace.
Method note
Check in every hour, or every fifteen minutes? The job decides.
Lone-working guidance asks for contact at agreed intervals and leaves the interval to the risk.
Leandro · Founder, UProcess
One school sets one interval for the whole site, so everyone knows the rule. The other sets it per task, short for work at height or near live conductors, longer for a meter round. The first is easy to remember; the second matches the hazard. Some work should not be done alone at all.
So the company sets a default, a permit type can tighten it, and some types never allow work alone.
- Company defaultOne interval for every session, 60 minutes unless you change it.
- Set by the permit typeA type marked with check-in offers a session at its own interval when the permit starts. Shorter than the default, never longer.
- Never aloneA permit type can forbid working alone. The permit does not activate while that holds.
Where Lone Work usually breaks
Four places lone work goes wrong, and what the record does about each.
An unanswered call reads as gone home.
A mechanic left alone to finish an excavator repair stopped answering calls and texts in the early afternoon. A supervisor assumed he had gone home. He was found hours later, trapped head-down.
Source: Washington State FACE report 71-251-2024
In UProcess A missed check-in is derived from time, at the due time plus twice the grace. The monitor is reached first, then one more level of the site chain at each step, until someone acknowledges.
LW-2026-0019 · missed check-in
- 00:01
- Check-in due
- 00:06
- Check-in due, grace passed
- 00:11
- Missed · level 1 · Grace Okafor
- 00:21
- Level 2 · Daniel Kim
- 00:23
- Acknowledged by Grace Okafor · called the worker
It stops when someone acknowledges, or when the worker checks in.
The day ends and nobody counts who left.
A worker on extended unaccompanied work collapsed and could not summon help with the phone they had. The sign-out records were not checked, patrols missed them, and they were found the next working day.
Source: IMCA safety event, lone worker collapsed
In UProcess The planned end is also a due time. A session still open after its planned end and the grace is treated as a missed check-in and escalates the same way.
LW-2026-0022 · after the planned end
- Worker
- Liam O’Connor
- Activity
- Weekend filter change, pump house P-301
- Planned end
- 16:00
- Reading
- Missed · level 1 · 16:10
The planned end is a due time like any check-in.
High-risk work done alone because nobody said not to.
Guidance on lone working asks for contact at pre-agreed intervals, and says some high-risk activities need at least one other person present, such as confined space work or work near exposed live conductors.
Source: HSE, Protecting lone workers (INDG73)
In UProcess Each permit type carries a lone-work rule: never alone, allowed with check-in at its own interval, or allowed. Never alone stops the permit; with check-in offers its holder a session.
Permit types · lone-work rule
Tracking that workers switch off.
Lone-worker monitoring meets lasting concern about privacy, with workers feeling watched, and most lone workers often work outside mobile coverage.
Source: National Safety Council, Work to Zero
In UProcess Location is taken only at the start, at check-ins and at a help request, seen only by the monitor and the chain, and cleared after 30 days. Check-ins made offline queue with the device time.
Location · LW-2026-0019
Session LW-2026-0019Worker Tomasz NowakMonitor Grace Okafor
| Device time | Received | Event | By |
|---|---|---|---|
| 22:00 | 22:00 | Start · from PTW-2026-0150 | Tomasz Nowak |
| 22:29 | 22:29 | Check in | Tomasz Nowak |
| 22:58 | 22:58 | Check in | Tomasz Nowak |
| 23:31 | 23:31 | Check in | Tomasz Nowak |
| 00:11 | — | Missed · level 1 | — |
| 00:21 | — | Level 2 · Daniel Kim | — |
| 00:23 | 00:23 | Acknowledged · called the worker | Grace Okafor |
| 00:31 | 00:34 | Check in · queued offline | Tomasz Nowak |
| 00:36 | 00:36 | Outcome · worker safe | Grace Okafor |
| 01:58 | 01:58 | Check out | Tomasz Nowak |
Location cleared 19 Dec 2026 · check-ins kept
The record an auditor asks for.
What happened when someone stopped answering is part of the session, not a call log on someone’s phone.
- Every session: who, where, the activity, the monitor, the interval and the planned end.
- Every check-in with the device time and the time it was received.
- Every missed check-in and help request, who acknowledged it, what they did and the outcome.
- Location cleared after the retention period, with the fact of each check-in kept.
What’s in a session
- Session
- Worker, monitor, site, activity, where, interval and planned end up to 24 h, started in one tap or from a permit. One active session per worker.
- Check-ins
- Check in, extend, help and check out. Help is a press-and-hold that reaches the monitor and the whole chain at once.
- Escalation
- Missed at due time plus twice the grace. Monitor first, then one chain level per step, 10 minutes by default, shown on the board and in To do.
- Reach
- Escalation reaches people through UProcess only: the board and To do. The screen says plainly: This is not an alarm-receiving service.
- Outcome
- The acknowledgement records what was done; the outcome follows: worker safe, emergency started, or other with a note. Sessions are never deleted.
Questions
Is this an alarm-receiving service?
No. Escalation reaches the people on your site’s chain through UProcess only, on the board and in To do. UProcess never calls emergency services; the person who acknowledges does.
What if the worker has no signal?
Check-ins and help requests are queued on the device with its time and sent when it reconnects. A late check-in resolves the missed one, and the escalation stays in the history.
Who can see where I am?
Only your monitor and the site’s chain, and only from the start, check-ins and help requests. Coordinates are cleared after 30 days by default.
Who can start a session?
Anyone with access to Lone Work at the site can start and run their own session. Protecting yourself is never refused.