Lone worker safety sessions

If you work alone on site — entering a property without a colleague — you can start a lone worker safety session on TruePro. The session sends periodic check-in reminders to your device. If you miss a check-in, your dispatcher is automatically notified so they can follow up.

When to use it

Start a lone worker safety session as soon as you mark yourself en route to a job (or, at the latest, once you record your arrival), if you will be working at that property without another team member present. Starting when you set off means you're covered on the drive there too, not just once you're on site.

How to start a session

1. Open TruePro on your mobile device and open the job you are heading to (or already on site for).
2. Tap Mark en route (or Record arrival if you're already there) as normal.
3. The Lone worker safety panel now appears on the job page. Choose your check-in interval: every 15 minutes, every 30 minutes, or every 60 minutes.
4. Tap Start session.

The job page confirms the session is active and shows your next check-in time. A compact reminder also appears on your My Jobs list, linking back to the job.

You can only run one safety session at a time. If you already have one active for a different job, the panel on any other job shows a link back to that session instead of new controls — end it there first.

Responding to a check-in

When a check-in is due, a notification appears on your device. Tap I'm OK to confirm you are safe. The timer resets and the next check-in is scheduled — and if you'd previously missed one and your dispatcher was notified, checking in now clears that too. There's nothing to apologize for or explain; once you've checked in, your dispatcher knows you're safe.

What happens if you miss a check-in

If you do not respond within about 2 minutes of a check-in becoming due, TruePro notifies your dispatcher within a few minutes, along with your last known job location and the time you were last checked in. Your dispatcher will attempt to contact you.

Pausing and ending a session

• To pause the session (e.g. you are with a colleague briefly), tap Pause session.
• To end the session when you leave the site, tap End session.

Sessions only end when you tap End session yourself — marking the job complete or recording your departure does not end it automatically. This is deliberate: if something goes wrong between finishing the job and actually being safe, monitoring is still active. Always end the session yourself once you're safely away from site.

If you forget to end a session, or you're no longer able to (you've left the business, for example), your dispatcher or business owner can end it for you from their safety dashboard. They must give a reason before they can do this, and it's recorded against their account.

If you leave a session running long enough that the office completes and invoices the job in the meantime, the "View job" link on your My Jobs list won't take you back to the job anymore — it's moved into a back-office stage you don't have access to. In that situation the list shows an End session button right there instead, so you can still close it out yourself without needing the job page.

Dispatcher and owner dashboard

Business owners and dispatchers have a Lone worker safety item in their main menu. It opens a dashboard showing how many sessions are currently active, how many are overdue, and any alerts still needing attention — each links straight through to the active sessions list. Below that, a log of completed sessions shows start and end times, duration, and — if a session was ever ended by a dispatcher or owner rather than the technician themselves — who did it and why. This record can be important for insurance and health & safety compliance.

The active sessions list shows one row per technician, not one row per alert — a technician who's missed a few check-ins shows a single "Last missed check-in" summary rather than a growing list, and it disappears the moment they check in. A panic alert always stays clearly visible on the row itself, with its own one-click way to acknowledge it, since that's the one case that always needs an immediate response. Every technician also has a "Log" link through to their full alert history, and there's a combined log for the whole team as well — filterable by technician, alert type, and whether it's been acknowledged.