01
Lone-work sessions
Workers start a protected session with task context and check-in expectations, giving supervisors a clear view of who is currently working alone.
Lone-worker safety, built for accountable teams
Protection that keeps watch when people work alone.
LoneWatch helps organisations monitor lone-work sessions, detect signs of trouble and escalate verified safety events to the right responder—without drowning supervisors in noise.
iPhone firstMicrosoft Entra IDMicrosoft Teams alerts
9:41●●●
Protected
ACTIVE LONE WORK
Pump inspection
North Plant · Started 7:20 AM
Protection healthHealthy
RESPONDER ALERT
HELP · Reece Smith
North Plant · Pump inspection
AcknowledgeCall worker
Designed around signal, not noise
Know who needs attention—and why.
LoneWatch is designed to separate routine awareness from urgent safety events, preserving high-salience channels for incidents that have not been dealt with.
02
HELP and no-response escalation
Explicit HELP requests and missed check-ins become auditable incidents with acknowledgement, responding and resolution states.
03
Possible-fall detection
A conservative Core Motion model can identify possible falls, with a worker cancellation window before escalation to reduce false positives.
04
Location-aware routing
Fresh availability, site/zone membership and last-known location can help route incidents to the nearest qualified responder when the evidence supports it.
05
App + Microsoft Teams alerts
Responders can receive iPhone push alerts and detailed Teams Adaptive Cards, with acknowledgement-driven escalation designed to reduce notification noise.
06
Protection health
LoneWatch reports explainable Healthy, Degraded, Unavailable or Unknown states instead of showing optimistic green status when evidence is missing.
How it works
A clear safety chain from worker to responder.
Each step is designed to preserve context, acknowledgement state and routing evidence so incident handling can be reviewed later.
Start protected work
A worker starts a lone-work session with task context and location evidence.
Watch meaningful signals
Check-ins, motion, possible falls, connectivity and protection health are evaluated.
Escalate only when needed
HELP, confirmed possible-fall escalation and no-response events become incidents.
Route to the right responder
Availability, site/zone and fresh location can support qualified responder selection.
Notification philosophy
Escalation should get louder only when attention is missing.
✓
Routine session activity stays low-noise.
✓
Urgent events use app push and Teams.
✓
No acknowledgement promotes the responder chain and safety channels.
✓
SMS remains available as a future high-salience escalation channel.
Example policy
Worker starts lone workApp awareness
HELP / no responseApp + Teams
Possible fall not cancelledApp + Teams
No responder acknowledgementEscalate responder
Enterprise identity
Built to fit Microsoft-first organisations.
Workers sign in with their existing Microsoft work account. LoneWatch uses tenant and object IDs as the durable identity boundary, while Entra manager data can assist—rather than silently control—safety routing.
ID
Microsoft Entra
Multi-tenant work/school sign-in, customer admin consent, manager suggestions and tenant-scoped organisation mapping.
Microsoft Teams
Detailed Adaptive Card alerts can carry worker, task, alert mode, location context and responder information into enterprise Teams workflows.
Enterprise pilot
Bring LoneWatch into a controlled safety pilot.
We are preparing LoneWatch for enterprise onboarding in Australia. Talk to us about your lone-worker workflows, responder model and Microsoft environment.
Talk to LoneWatch