Product

A focused safety workflow for people who work alone.

LoneWatch combines worker-initiated protection, meaningful device evidence and responder accountability. It is designed to assist safety procedures—not replace emergency services or site-specific controls.

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.

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.

Possible-fall experience

Confirm danger before creating unnecessary noise.

A possible-fall candidate presents a cancellation window to the worker. If they confirm they are OK, the candidate is cancelled. If not, the event can escalate through the same responder and incident workflow as other safety alerts.

Conservative by design

LoneWatch does not claim to measure an exact fall height. Its current iPhone model uses a conservative combination of low-g, impact, orientation change and post-impact stillness evidence, with field validation required before strong detection claims.

Responder experience

From alert to action without losing context.

Assigned responders can acknowledge, indicate they are responding, resolve incidents and—where a worker contact number is configured—call the worker directly from the incident card.

Incident createdOPENED
Responder acceptsACKNOWLEDGED
Responder travelling/actingRESPONDING
Incident closedRESOLVED