Threat Assessment
Communicating a Credible Threat Across Shifts
A credible threat known only to one shift is a gap surveyors and litigators find. Learn how to hand off threat information across shifts and departments — defensibly and within privacy rules.
A credible threat that lives in one nurse's head, on one shift, in one department is a failure of communication waiting to become an incident — and, in survey or litigation, evidence that the facility held knowledge of a foreseeable risk and failed to move it to the people who needed it. Communicating a credible threat across shifts and departments is the discipline of getting the right minimum-necessary safety information to the right staff, through defined channels, documented along the way, and within privacy rules.
This is one of the least glamorous and most consequential capabilities in a workplace violence program. The threat assessment was done; the management plan exists; and then the day shift goes home and the night shift inherits a patient with no idea a credible threat was made eight hours earlier. This article covers how to close that gap defensibly.
#Why the handoff is where knowledge dies
Hospitals run on shift changes, transfers, and department-to-department movement. Each transition is a point where information can drop. A patient assessed as a concern in the emergency department is admitted to a floor; a visitor who made a threat on days returns on nights; a concern raised in one building is unknown in another. Every one of those seams is where a credible threat can vanish.
The compliance stakes are direct. The Joint Commission's workplace violence requirements (effective Jan. 1, 2022 for hospitals) expect incident reporting, tracking, trending, and follow-up — and follow-up that does not travel across shifts is follow-up in name only. A facility-specific plan under Texas HSC Chapter 331 requires a functioning reporting and response mechanism, which presupposes the information reaches responders. In litigation, the inference is unforgiving: if the facility's own records show a threat was known, an incident on a shift that never received it reads as a self-inflicted gap.
#Three channels, three jobs
Effective cross-shift threat communication is not one tool but three working together. Each does a job the others cannot.
| Channel | What it does | When it carries the threat |
|---|---|---|
| Behavioral alert flag | Standing, documented marker in the record | Persists across encounters until cleared by policy |
| Shift handoff / report | Active verbal transfer between outgoing and incoming staff | Every shift change while the concern is active |
| Threat assessment escalation | Routes the concern to the team for management | When the concern is more than in-the-moment |
The behavioral alert flag is the persistence layer — it survives the shift change and the transfer. The handoff is the real-time layer — it makes sure incoming staff actually know, not just that the information exists somewhere. The threat assessment escalation is the management layer — it routes the concern into the structured process so a named owner is accountable across all the shifts the concern spans.
#The minimum-necessary principle
The single discipline that keeps cross-shift threat communication rail-safe and HIPAA-defensible is minimum necessary: communicate the safety information staff need to stay safe and respond, and no more. The driver is conduct and safety — what was said or done, what the management plan requires, who to call — not diagnosis, history, or speculation.
In practice that means a handoff sounds like "Mr. ___ made a specific threat toward staff on discharge; behavioral alert is flagged; two-staff rule in effect; threat assessment team is managing, owner is the charge nurse; call security if he returns to the unit" — concrete, actionable, conduct-based. It does not editorialize about the person, and it does not broadcast clinical detail unrelated to safety. The exact content and channel should be coordinated with your privacy and legal functions so the practice is defensible under HIPAA's safety and minimum-necessary provisions and your own policy.
#Communicating across departments, not just shifts
People move. A concern raised in triage follows the patient to a unit; a discharged visitor under a behavioral flag may reappear anywhere on the campus. Cross-department communication needs a defined broadcast path:
- Define the perimeter. Which areas might the person enter? The unit, the ED, registration, the affected clinician's department, lobby and access points.
- Use the alert layer. The behavioral flag travels with the record so any department that opens it sees the concern.
- Notify the human nodes. The departments and roles a person is likely to encounter receive an active, minimum-necessary notice — not a campus-wide announcement.
- Route to one owner. The threat assessment team owns the case so the cross-department picture is held in one place, not fragmented.
#Documenting that the information actually moved
The handoff only protects the facility if it can be shown to have happened. Build documentation into the channels:
- The behavioral flag is, by nature, a dated record of the standing concern.
- The threat assessment record notes that the communication plan was set and to whom it was directed.
- Handoff tools and shift reports that reference the active concern leave a trail that the information was transferred shift to shift.
This is the evidence that converts "we told the night shift" from a contested verbal claim into a documented fact — the difference, in discovery, between a defensible handoff and a he-said-she-said.
#How VIGILO helps
VIGILO helps facilities design cross-shift and cross-department threat communication into the written WVP plan and policies and the threat assessment program — defining the channels, the minimum-necessary content, the broadcast perimeter, and the documentation that proves information moved — coordinated with your privacy and legal functions. The handoff discipline is trained through staff education and audited in an annual program review. For Texas facilities it aligns with HSC Chapter 331. To find the seams where your threat information currently drops, start with the Chapter 331 compliance checklist.
VIGILO provides compliance, training, and consulting assistance and supports survey-readiness and preparedness; it does not provide legal advice, does not guarantee safety outcomes, and does not provide security guard, patrol, or investigative services. Communicate only minimum-necessary safety information; coordinate channels and content with your privacy and legal functions. Sources: The Joint Commission Workplace Violence Prevention requirements (incident reporting, tracking, trending, follow-up; effective Jan. 1, 2022 for hospitals); Texas Health & Safety Code Chapter 331 (SB 240, 88th Leg., 2023) and 26 TAC §133.55; OSHA General Duty Clause §5(a)(1) and Publication 3148; HIPAA Privacy Rule minimum-necessary and safety provisions.