Can you get the right help to the room — and prove it?
A threatened worker experiences one question: can I get the right help here, now? This is a focused 10-question read across the response chain — activation, location, acknowledgment, dispatch, verification, and the record. It surfaces where your chain can and can’t yet prove it worked; it is not a score and not a design. Yes = in place, integrated, and provable; Partial = it exists but coverage or the record is inconsistent; No = not in place; N/A = not applicable. Count only Yes; each Partial names the gap. The band thresholds are our design decision, not a regulation’s.
This self-assessment runs entirely in your browser. Nothing you enter is sent to us or stored. No email required.
Activation & coverage
Can staff activate help from the places where they actually work — inside patient rooms, corridors, and parking — not just the nurse station?
Fixed points only, or coverage gaps where staff actually are.
Is duress something staff carry — wearable or mobile — and can they trigger it discreetly?
Fixed only, or wearables issued but not used in practice.
Location & routing
Does the alert identify the caller’s current location accurately enough for a responder to go straight there?
Zone-level only, or the location is often wrong.
Does the alert route to the right responders automatically — not depend on someone being in earshot or line of sight?
It routes, but still depends on someone hearing or seeing it.
Acknowledgment & escalation
Does someone have to acknowledge the alert — and does it escalate if no one does?
Acknowledgment exists but there’s no escalation path.
After the fact, can you tell a response failure apart from a reporting failure?
Not reliably — the two look the same in the record.
Dispatch & verification
Can whoever responds immediately see the relevant camera and the fastest route?
Video exists but isn’t tied to the alert.
Is the alert record time-synchronized with video and access control?
The systems aren’t time-synced; stitching is manual.
The record — the question nobody asks until they have to
Does testing cover the entire chain, activation through record — or only individual devices?
Devices are tested; the end-to-end response isn’t.
Can one authorized person retrieve the full physical-evidence package after an event — activation, location, acknowledgment, response, access, and video — without stitching systems together by hand?
Only by manually pulling from separate systems.
Your chain looks whole — verify the record
Activation, location, routing, response, and the record look integrated. The value now is confirming the Partials you flagged are truly closed — especially that one person can retrieve the full event record without stitching systems by hand.
The chain has gaps that show up under pressure
The pieces exist, but the seams — location accuracy, acknowledgment and escalation, or the retrievable record — would surface exactly when an incident or an after-action review tests them. The Partial notes point to where to look first.
Help may not reach the room, and you may not be able to prove what happened
There are real breaks between a worker in trouble and the right help arriving — and between an event and the record of it. Start here, with security, nursing, and facilities together.
There are real breaks between a worker in trouble and the right help arriving — and between an event and the record of it. Start here, with security, nursing, and facilities together.
This self-assessment surfaces where a staff-safety response chain can and can’t yet prove it worked; it points to gaps, it is not a security design and not a compliance determination. Technology is one part of a workplace-violence program, not the whole. The band thresholds are a declared design decision, not drawn from any regulation. Current as of Accreditation 360 (eff. Jan 1 2026).
This surfaces where a program can’t yet prove it functions; it is not a compliance score and not a survey. Count only Yes. Each Partial is a named gap — the note identifies the specific condition that prevents a full Yes. N/A does not penalize. Responses stay in your browser and are not transmitted.