Program & Plan Development
WVP Reporting Policy That Doesn't Discourage 911
How to write a confidential workplace violence reporting policy that encourages staff to report and still preserves the right to call law enforcement — aligned to Texas Chapter 331.
A workplace violence reporting policy has two jobs that can pull against each other: get staff to report every incident, and never give the impression that an internal report replaces calling 911. A defensible policy resolves the tension by stating both plainly — clear, confidential internal channels and an explicit preserved right to contact law enforcement at any time. Reporting internally is never a substitute for emergency response.
Underreporting is the quiet failure that undermines an entire program: a worksite analysis built on incomplete data understates risk, and a surveyor reads the gap. This guide covers how to write the reporting policy so staff actually use it and the law-enforcement door stays open.
#What Chapter 331 requires of the reporting process
Texas Health & Safety Code Chapter 331 (SB 240, 88th Legislature, 2023) requires covered facilities to provide a process for employees to report workplace violence and to protect employees from retaliation for reporting. The statutory floor is a reporting mechanism plus anti-retaliation protection. A policy that survives a survey builds on that floor with the operational detail surveyors and staff both need.
The hospital rule 26 TAC §133.55 (Texas Register, Oct. 11, 2024) wires this into the licensure survey; HHSC Provider Letter PL 2024-10 applies the framework to HCSSAs employing two or more RNs. For the statutory requirements specifically, see Chapter 331 confidential reporting and anti-retaliation.
#The five elements of a usable reporting policy
| Element | What it does |
|---|---|
| Clear channels | Tells staff exactly how to report — form, hotline, supervisor, online — with no ambiguity |
| Confidentiality standard | States how the reporter's identity is protected and who sees the report |
| Anonymous option | Offers a no-name path for staff who fear exposure even with confidentiality |
| Preserved 911 right | Expressly states that internal reporting never waives the right to call law enforcement |
| What happens next | Describes the response, follow-up, and that the reporter will not be retaliated against |
Each element raises reporting rates by removing a reason not to report. A policy that names a channel staff trust, protects them, gives an anonymous fallback, keeps the emergency door open, and tells them what to expect is a policy people actually use.
#Writing the "you can always call 911" provision
This is the clause that separates a defensible policy from a risky one. The language should be unambiguous and prominent:
"Nothing in this policy limits any employee's right to contact law enforcement at any time. Internal reporting is in addition to, not a substitute for, calling 911 in an emergency. An employee who calls law enforcement is protected from retaliation to the same extent as one who reports internally."
Why this matters beyond compliance: a policy that channels everything through an internal form can be read — by staff, by a surveyor, or later by plaintiff's counsel — as discouraging emergency response. That reading is a liability and a survey risk. The explicit preservation clause removes it. For where law-enforcement involvement is a program decision rather than an individual choice, see when to involve law enforcement in a healthcare threat.
#Confidential vs. anonymous: offer both
These are different protections and staff value each differently:
- Confidential reporting shields the reporter's identity from unnecessary disclosure but allows the committee or program leader to follow up. Most reports run this way.
- Anonymous reporting removes identity entirely. It lowers the barrier for staff who fear exposure even with a confidentiality promise — often the staff closest to the most serious patterns.
Offering both, and saying so in the policy, maximizes the data you capture. That data is what a defensible worksite analysis is built on — a worksite analysis that understates risk because half the incidents never got reported is the gap a surveyor and a plaintiff's expert both exploit.
#Connect the policy to the incident report form
A reporting policy is only as good as the form it points to. The two must be built together: the policy names the channel, the form captures what surveyors and trend analysis need. If the form is hard to find or asks the wrong questions, the policy's promise of "easy reporting" is hollow. See building a WVP incident report form that captures what surveyors need for the capture fields, and ensure the policy directs staff straight to it.
#The anti-retaliation half of the policy
Encouraging reports and protecting reporters are inseparable — staff will not report if they fear consequences. The reporting policy must carry, or sit beside, clear anti-retaliation language: what retaliation is, that it is prohibited, and how a reporter raises a retaliation concern. The drafting of that language is detailed enough to warrant its own treatment in anti-retaliation policy language for your WVP program. Keep the two policies cross-referenced so neither stands alone.
#Common reporting-policy deficiencies
| Deficiency | Why it gets cited or creates risk |
|---|---|
| No documented reporting process | Chapter 331 requires a reporting mechanism |
| Policy implies internal reporting replaces calling 911 | Reads as discouraging emergency response — survey and liability risk |
| Only a named-report channel; no confidential or anonymous option | Suppresses reporting and understates risk in the worksite analysis |
| Policy exists but staff cannot describe how to report | A policy staff can't use is functionally absent |
| No description of what happens after a report | Staff distrust a black-box process and stop reporting |
| Reporting policy with no linked anti-retaliation protection | Chapter 331 pairs reporting with anti-retaliation |
#Make reporting the easy choice
The goal of a reporting policy is volume: the more incidents reach the system, the more accurate the worksite analysis, the stronger the trends, and the more defensible the program. A policy that offers clear channels, real confidentiality, an anonymous fallback, an open 911 door, and a transparent follow-up — backed by genuine anti-retaliation protection — makes reporting the path of least resistance. That is the entire design goal.
VIGILO drafts the reporting and anti-retaliation policies together under policy development and integrates them into the workplace violence prevention programs Foundation Package. If your policy channels everything through one internal form, a flat-fee survey-readiness audit flags the gap. For the underlying statute, see the HSC Chapter 331 requirements page.
This article is compliance-assistance guidance, not legal advice. Primary sources: Texas Health & Safety Code Chapter 331 (SB 240, 2023); 26 TAC §133.55 (Texas Register, Oct. 11, 2024); HHSC Provider Letter PL 2024-10.