Texas HSC Chapter 331

What Your Chapter 331 WVP Plan Must Contain

Texas HSC Chapter 331 requires a written workplace violence prevention plan with specific elements. Here is what the plan document itself must include to survive a licensure survey.

VIGILO Compliance Editorial TeamReviewed by a Physician and Healthcare Compliance Leader (MBBS, MHA)8 min

Texas HSC Chapter 331 requires a written, facility-specific workplace violence prevention plan that the WVP committee builds, maintains, and evaluates. In substance, the plan must address how the facility protects staff from violence, how incidents are reported, how the facility responds after an incident, and how the plan is evaluated annually and reported to the governing body. A generic template adopted on paper is a predictable failure mode at survey.

This article focuses on the plan document itself: what belongs inside it, in what order, and how to keep it facility-specific. Other articles cover the committee that owns it and the obligations it triggers; this one is the contents checklist. For the full statute, see Texas SB 240 explained, and the main guide, Texas SB 240 & HSC Chapter 331 compliance.

#The plan is a document, not an understanding

Chapter 331 contemplates a written plan the committee develops and keeps current (Texas HSC Chapter 331; SB 240, 88th Leg., 2023). A surveyor does not ask whether your staff "know what to do"; they open a document and read it. That means:

  • The plan must exist as a single, dated, version-controlled file, not as a scatter of unrelated policies.
  • It must be facility-specific: tailored to your units, your risks, and your incident history.
  • It must be owned by the committee and traceable to your worksite analysis.

A plan that is real and acted on, but never written down, is as citable as no plan at all.

#What the plan must address

Section 331.004(b) lists eight things the plan must do. Build the document so a surveyor can find each one in seconds.

The statute requires the plan toWhere it lives in the document
Be based on the practice settingPurpose, scope, and facility profile: sites, units, patient population, known risks
Adopt a definition of workplace violence (an act or threat of physical force that results in, or is likely to result in, physical injury or psychological trauma, and any incident involving a firearm or other dangerous weapon)Definitions
Require workplace violence prevention training or education at least annuallyTraining
Prescribe a system for responding to and investigating violent or potentially violent incidentsIncident response and investigation
Address physical security and safetyPrevention and controls
Require the facility to solicit information from providers and employees when developing and implementing the planStaff input: how it was gathered and how it is renewed
Allow staff to report incidents through the existing occurrence reporting systemReporting
Require the facility to adjust patient care assignments, to the extent practicable, so an employee does not have to treat a patient who intentionally physically abused or threatened themPost-incident response

Three companion duties sit beside the plan and belong in the same binder: the written policy (§331.003: significant consideration of the committee's plan, confidential information to the committee, and protection from retaliation), the committee's annual review and report to the governing body (§331.004(d)), and the duty to make the plan available on request to any provider or employee (§331.004(e)). A worksite analysis is not in the statute by name, but it is the most defensible way to show the plan is based on the practice setting, and the Joint Commission requires one of accredited hospitals.

Each row is a discrete, survey-checkable requirement. Two carry specific statutory language worth getting exactly right: confidential reporting and anti-retaliation, and post-incident response, including acute treatment and patient care assignment adjustment.

#Facility-specific is the whole game

The most predictable deficiency on the plan itself is a generic template that does not reflect the facility. A plan downloaded, lightly branded, and adopted will name hazards the facility does not have, omit the ones it does, and read identically to a hundred other plans a surveyor has seen.

To make the plan demonstrably yours:

  1. Drive it from your own worksite analysis. The prevention-and-controls section should respond to the specific hazards your risk assessment found (boarding in the ED, an exposed triage window, a parking structure, lone home-health visits), not a stock list.
  2. Name your units. A plan that references your actual emergency department, behavioral-health unit, or home-health branches reads as real.
  3. Reflect your incident history. If your data shows a pattern, the plan should show you responded to it. A plan that ignores your own trend line is the gap plaintiff's counsel and surveyors both look for.
  4. Match floor practice. The plan must describe what staff actually do, not an aspirational process no one follows. The "policy-to-practice gap" is precisely what tracer methodology is built to expose.

#Version control makes the plan provable

Because the plan is evaluated at least annually, it is a living document, and a living document needs a paper trail. A surveyor wants to see that the current plan is the current plan:

  • A version number and date on the plan itself.
  • A revision history showing when it was adopted and last updated.
  • Committee minutes approving the plan and any revisions.
  • Evidence the plan was last evaluated within the trailing twelve months and reported to the governing body.

Without version control, a facility cannot prove which document governs, or that the annual evaluation actually touched it. Two undated drafts in a shared drive is not a plan of record.

#What a surveyor reviews

A Texas HHSC licensing surveyor verifies the plan by reading it and tracing it:

  1. The written plan document, dated and version-controlled.
  2. Whether it addresses each required element: a plan based on the practice setting, a definition of workplace violence, at-least-annual training, a system for responding to and investigating incidents, physical security and safety, soliciting information from providers and employees, reporting through the existing occurrence reporting system, and patient care assignment adjustment, along with the committee's annual evaluation.
  3. Whether it is facility-specific and tied to the facility's worksite analysis and incident data.
  4. Committee minutes showing adoption, annual evaluation, and any revisions.

The signature findings are a generic, non-facility-specific plan, a missing required element (post-incident response and confidential reporting are common omissions), and a plan that does not match practice when surveyors trace it to the floor.

#How to build a defensible plan

  1. Run the worksite analysis first so the plan responds to real hazards.
  2. Draft each required section and confirm every Chapter 331 obligation has a home in the document.
  3. Tailor it to your units, risks, and incident history; strip every generic line.
  4. Version-control it and route it through the committee for documented adoption.
  5. Calendar the annual evaluation so the plan is reviewed and re-dated every twelve months.

Facilities that want this written for them use our policy and plan development service, which drafts a facility-specific Chapter 331 plan with every required element in place, or the full workplace violence prevention program, which builds the plan from your worksite analysis and assembles the survey-readiness binder around it. To self-check first, the Chapter 331 compliance checklist maps each required element to "where the evidence lives," and a survey-readiness audit scores whether your plan would survive a trace.

A Chapter 331 plan is not hard to write, but it is easy to write generically, and a generic plan is the one that gets cited. Build it from your own risk assessment, give every required element a section, and keep it version-controlled, and the plan becomes the spine of a program that holds up at survey and after an incident.


Sources: Texas Health & Safety Code Chapter 331 (SB 240, 88th Leg., 2023); 26 TAC §505.55; HHSC Provider Letter PL 2024-10. This article is general compliance information, not legal advice.

From this article

Frequently asked questions

What must a Texas Chapter 331 workplace violence plan include?

Section 331.004 requires a written plan, developed by the WVP committee, that is based on the practice setting; adopts a definition of workplace violence; requires training at least annually; prescribes a system for responding to and investigating incidents; addresses physical security and safety; requires the facility to solicit information from providers and employees; allows reporting through the existing occurrence reporting system; and requires patient care assignments to be adjusted, to the extent practicable, after a patient intentionally physically abuses or threatens staff. The committee reviews the plan at least annually and reports the results to the governing body.

Does the Chapter 331 plan have to be in writing?

Yes. Chapter 331 contemplates a written plan that the committee develops, maintains, and evaluates. A surveyor opens the plan document itself, so an unwritten understanding or scattered policies do not satisfy the requirement. The plan should be a single, dated, version-controlled document the committee owns.

Can we use a template for our Chapter 331 plan?

A template can be a starting structure, but the plan must be facility-specific. The most predictable deficiency is a generic plan that does not reflect the facility's own worksite analysis, units, and incident history. Surveyors look for evidence the plan was tailored to your facility and is acted on, not just adopted on paper.

Turn this guidance into a survey-ready program

VIGILO builds, documents, and maintains the workplace violence prevention program of record (committee, written plan, training, and binder), aligned to Chapter 331, the Joint Commission, and OSHA.

CallRequest an Audit