Addon
Personal safety for workers who work alone.
Session-based monitoring with escalation to full incident response. Built for community nurses, inspectors, maintenance, security patrols and anyone doing solo visits.
Session-based monitoring with escalation to full incident response. Built for community nurses, inspectors, maintenance, security patrols and anyone doing solo visits.
Canon list from the module’s design brief: aged-care home-care teams, field inspectors and maintenance, security patrols, and property managers running after-hours callouts.
Community nurses, domiciliary care workers and mental-health outreach teams making solo client visits. Industries.md flags Lone Worker as “essential” for this audience — the Hide Screen feature exists specifically for hostile-individual and domestic-violence encounters during home visits.
Inspection rounds on construction sites, civil infrastructure and utility yards. Overnight maintenance runs and solo site walks gain the same timer-driven escalation path straight into the EMAction incident response.
Overnight rounds, perimeter checks and venue inspections where the patroller is the only person on site. If the session’s expected duration passes without a check-in, the timer-expiry alert fires without the patroller having to do anything.
Vacancy inspections, open-home visits and after-hours callouts. Before-visit safety notes are displayed as amber banners to both the worker and Control; Send Help is one tap from any point in the session.
Five steps, same every time — start, check in, alert or complete, Control responds, close out.
Worker starts a session — QR scan at the location or direct link. Enters client/visit name, address, expected duration, and safety notes.
Countdown timer begins. Worker taps “I’m OK” to reset the timer by 15 minutes.
Timer expires or worker taps “Send Help” — Control receives immediate alert with location and client details.
Control responds — call worker, acknowledge, call 000, or escalate to full EMAction incident with live GPS tracking.
Session completes — worker taps “Session Complete”. Full session logged for compliance.
Every escalation is a specific trigger and a specific Control Room action. Nothing happens by AI judgement.
| Level | Trigger | Action |
|---|---|---|
| Normal | Worker taps “I’m OK” | Timer resets |
| Warning | Timer approaching zero | Worker receives on-screen reminder |
| Call Me | Worker taps “Call Me” | Control prompted to call. Non-emergency |
| Alert | Timer expires OR “Send Help” | Control alerted. Card turns red. SMS sent |
| Emergency | Control acknowledges alert | Control calls 000 and/or dispatches help |
| Incident | Control taps “Escalate” | Full EMAction incident created. Worker on live GPS map. Wardens notified |
Tap 3× to reveal. Hides the interface behind a “Reconnecting…” screen. For domestic violence, hostile individuals, or threat escalation risk. The session remains fully active in the background — Control Room still sees it, the audit trail still records, and GPS still plots if the session has escalated. It is the UI that is hidden, not the session.
Real-time position plotted on the incident map. Visible to Control from the moment an alert is raised; worker movements while the alert is active are tracked to the incident timeline.
Captured from the session and sent automatically to Control. Attached to the session record with uploader and timestamp, per the base platform’s audit-trail rules.
Two-way text messaging, all logged. Keeps the worker and Control in contact even when voice calls aren’t practical — during a client visit, in transit, or when the worker needs to stay quiet.
Hazard notes displayed as amber banners on both screens. Entered when the session starts; visible to both the worker and Control throughout so a hand-off at shift change doesn’t lose the context.
Timer reaching zero fires the alert. No worker action required. Designed for the case where the worker can’t tap the phone — the trigger does not depend on a human remembering to push a button.
Every action timestamped. Every session start, I’m OK tap, Call Me, Send Help, Hide Screen toggle, Control acknowledgement, photo, message and escalation step is recorded with the actor’s identity and timestamp against the tenant’s incident timeline. Exportable under the base platform’s reporting surface.
A community nurse arrives at a residential address for a 60-minute home visit. She opens EMAction Lone Worker on her phone, taps Start, scans the QR code on her agency’s laminated visit card, and enters the client’s name and address. Expected duration: one hour. Safety notes, per agency standard: any known hazards at the address.
The countdown timer starts. Fifteen minutes in, the phone buzzes a gentle “I’m OK?” prompt. She taps I’m OK. The timer resets. Thirty minutes, another prompt — tap, reset. Towards the end of the visit she taps I’m OK one final time to cover the last quarter-hour while she tidies up and says her goodbyes.
Back in her car, she taps Session Complete. The session closes. Every check-in, safety note and timestamp is logged against her agency’s compliance records. Nothing escalated — which is the typical case. The value of the module is that it’s sitting there quietly when it’s not needed, and is already running when it is.
Lone Worker sessions run independently of any active EMAction incident. A worker doing routine visits doesn’t need the rest of the organisation in an incident state — only their own session is live, watched by Control if staffed, and otherwise sitting in the queue for timer and alert handling.
When a session escalates — timer expires, Send Help is tapped, or Control taps Escalate — a full EMAction incident is created automatically. The worker is placed on the live incident map with their current GPS position; wardens in the affected tenancy are notified per the base platform’s warden structure. From that moment, the session is being handled inside the standard EMAction incident response — live map, broadcast cards, incident timeline, stakeholder summaries.
Lone Worker is an addon. It requires the base platform to run; it extends EMAction, it does not replace any part of it. A Lone Worker deployment without the base platform would have no Control Room surface for alerts to land on, no wardens to escalate to, and no incident timeline to hand off to.
Most deployments turn Lone Worker on alongside the base platform during initial setup — it’s a tenant-level feature flag, not a separate platform to install.
Request a demo