Program & Plan Development
Anti-Retaliation Language for Your WVP Program
How to write anti-retaliation policy language that satisfies Texas Chapter 331, protects staff who report workplace violence, and holds up in a survey and in litigation discovery.
Anti-retaliation language is the clause that makes your reporting policy believable. Staff weigh the risk of consequences before they report, so the protection must be explicit: define retaliation broadly, name the protected activities, prohibit retaliation unambiguously, and give reporters a separate channel to raise a concern. Texas Chapter 331 requires the protection; the wording determines whether staff trust it.
Weak or missing anti-retaliation language suppresses reporting, which starves the worksite analysis of data and surfaces as a deficiency. This guide covers exactly what the language must say and the failure modes that get programs cited.
#What Chapter 331 requires
Texas Health & Safety Code Chapter 331 (SB 240, 88th Legislature, 2023) requires covered facilities to protect employees from retaliation for reporting workplace violence and for seeking assistance after an incident. The reporting requirement and the anti-retaliation requirement are paired in the statute — you cannot satisfy one and skip the other.
The hospital rule 26 TAC §133.55 (Texas Register, Oct. 11, 2024) carries this into the licensure survey; HHSC Provider Letter PL 2024-10 extends the framework to HCSSAs employing two or more RNs. A written policy is the documented proof the protection exists. For the statutory pairing of reporting and anti-retaliation, see Chapter 331 confidential reporting and anti-retaliation.
#The four components of defensible language
| Component | What it must do |
|---|---|
| Broad definition of retaliation | Cover adverse actions beyond termination — schedule changes, reassignment, exclusion, hostility |
| Named protected activities | Spell out exactly what conduct triggers protection |
| Unambiguous prohibition | State that retaliation is prohibited and will be disciplined — not "discouraged" |
| Separate escalation channel | Let a reporter raise a retaliation concern without going through the alleged retaliator |
Each component closes a gap that a vague policy leaves open. A policy that only prohibits "termination for reporting" leaves every subtler form of retaliation unaddressed — and subtle retaliation is the kind that actually chills reporting.
#Define retaliation broadly
The most common drafting error is defining retaliation too narrowly. Real retaliation rarely looks like a firing; it looks like a worse schedule, a transfer to a harder unit, exclusion from opportunities, or a sudden chill from a manager. Language that holds up:
"Retaliation includes any adverse action taken because an employee engaged in a protected activity — including but not limited to termination, demotion, reduction in hours, undesirable reassignment, denial of opportunities, negative evaluation, intimidation, exclusion, or harassment."
The "including but not limited to" framing matters: it signals the list is illustrative, not exhaustive, so a novel form of retaliation is still covered.
#Name the protected activities explicitly
Staff need to know precisely what conduct is protected. Name each activity:
- Reporting a workplace violence incident through any channel.
- Participating in an investigation or committee review of an incident.
- Seeking treatment — medical or psychological — after an incident.
- Contacting law enforcement about a workplace violence matter.
- Reporting on behalf of, or as a witness for, another employee.
Tying protection to named activities removes the argument that a given action "wasn't really reporting." It also reinforces the reporting policy's promise that internal reporting and calling 911 are both protected — the linkage covered in a reporting policy that doesn't discourage calling 911.
#Make the prohibition unambiguous — and enforceable
Soft language undermines the whole policy. "Retaliation is discouraged" invites the question of what happens when it occurs. Defensible language is categorical and tied to consequences:
"Retaliation against any employee for engaging in a protected activity is strictly prohibited. Any employee, supervisor, or manager who retaliates is subject to disciplinary action up to and including termination."
Linking the prohibition to your existing discipline and just-culture framework makes it enforceable rather than aspirational. See linking your WVP policy to HR discipline and just-culture frameworks for how that connection is built.
#Provide a separate channel to raise concerns
If the only way to report retaliation is through the chain of command — which may include the alleged retaliator — the protection is illusory. The policy must name an alternate channel: a different leader, HR, compliance, or a hotline. The reporter must be able to raise a retaliation concern without confronting the person they fear. State the channel plainly and confirm that raising a retaliation concern is itself a protected activity.
#Why this language is also a litigation safeguard
Anti-retaliation language does double duty. Beyond the survey, it is part of the documented record a plaintiff's counsel reviews after an incident. A facility that prohibited retaliation in writing, named the protected activities, and gave staff a real escalation channel has evidence of a genuine program. A facility whose policy was silent or toothless has a gap that reads, in discovery, as indifference to staff who tried to report. The same language that satisfies a surveyor strengthens the defensible record — a theme explored in documentation as your best defense in a workplace violence claim.
#Common anti-retaliation deficiencies
| Deficiency | Why it gets cited or creates risk |
|---|---|
| No written anti-retaliation policy | Chapter 331 requires retaliation protection |
| Retaliation defined only as termination | Subtler retaliation goes unaddressed and still chills reporting |
| Protected activities not named | Leaves room to argue a given act "wasn't protected" |
| "Discouraged" rather than prohibited | Unenforceable; signals the protection is not serious |
| No channel outside the chain of command | Reporter must go through the alleged retaliator |
| Policy not linked to discipline framework | Prohibition is aspirational, not enforceable |
#Protect reporters, protect the program
Anti-retaliation language is not boilerplate — it is the structural reason staff trust the reporting system enough to use it. Broad definition, named protected activities, an unambiguous and enforceable prohibition, and a real escalation channel together make the protection credible. Credible protection produces reporting; reporting produces the data that makes the worksite analysis and the whole program defensible.
VIGILO drafts anti-retaliation and reporting policies as a connected set under policy development and folds them into the workplace violence prevention programs Foundation Package. If your policy defines retaliation narrowly or offers no escalation channel, a flat-fee survey-readiness audit flags it against the Chapter 331 checklist. 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.