Long-Term Care & Home Health

Multi-Branch HCSSA: A WVP Program of Record

How a multi-branch Texas home health or hospice agency builds one survey-defensible workplace violence program of record across all locations under Chapter 331 and PL 2024-10.

VIGILO Compliance Editorial Team9 min

A multi-branch home health or hospice HCSSA faces a compliance problem a single-site agency never sees: it must run one coherent workplace violence program of record across many locations, each with its own service area, workforce, and risk profile — while keeping every branch facility-specific under Texas Chapter 331 and HHSC Provider Letter PL 2024-10. The answer is a shared program framework, tailored at the branch level, maintained as a living source of truth rather than rebuilt under each survey's deadline.

For a home health or hospice HCSSA operating several offices, the two failure modes are mirror images. One generic corporate plan stamped onto every branch fails the facility-specific test. A pile of disconnected branch plans with no central governance fails the consistency and oversight test. This article covers the architecture that satisfies both.

#The multi-branch tension: consistent yet specific

Chapter 331 requires a facility-specific plan built on a worksite analysis, with training, a confidential reporting pathway, post-incident response, and an annual plan evaluation reported to the governing body. PL 2024-10 applies all of this to HCSSAs employing two or more RNs. None of that changes with scale — but at scale, "facility-specific" and "consistent program" pull against each other.

Resolve the tension with a two-layer structure:

  • A shared program framework owned centrally: the policy architecture, the plan template, the reporting system, the training curriculum, the documentation standards, and the governance cadence. This is what makes the program consistent and lets a surveyor see one coherent program rather than improvisation.
  • A branch-specific layer that tailors the framework to each location: that branch's service-area conditions, its worksite-analysis findings, its incident history, and its staffing model. This is what makes each branch specific and survives the facility-specific test.

The framework is the backbone; the branch layer is the proof that the backbone was applied to real, local conditions. The single-site version of this build — committee, plan, reporting, training, post-incident response, annual evaluation — is laid out step by step in our HCSSA PL 2024-10 program guide; the multi-branch program layers governance on top of it.

Primary source: Texas Health & Safety Code Chapter 331 (SB 240, 2023); HHSC Provider Letter PL 2024-10 (Revised), applying Ch. 331 to home health and hospice HCSSAs that employ two or more RNs; OSHA Publication 3148.

#Governance: one committee, branch-level inputs

Chapter 331 specifies committee composition for covered facilities. A multi-branch agency typically satisfies this with a central workplace violence committee that carries the required roles and holds program-level oversight, fed by branch-level champions who supply local data. The champions are not a second bureaucracy — they are the conduit that keeps the central committee connected to ground truth at each location.

A workable governance model:

  1. A central committee with the Chapter 331-required composition meets on a defined cadence, owns the framework, and reports the annual evaluation to the governing body.
  2. Branch champions conduct or coordinate the local worksite analysis, surface branch incident trends, and confirm local training completion.
  3. Standardized reporting flows upward so branch incident data aggregates into one program-level picture the committee can act on.
  4. The annual plan evaluation rolls branch findings into a single governing-body report that shows the program working across the whole footprint.

The governing body's oversight is program-wide, but the evidence it reviews must show each covered branch was assessed, not just headquarters.

#One worksite analysis method, many service areas

The worksite analysis is where multi-branch specificity is won or lost. The agency uses one method — the same hazard categories, the same screening criteria, the same scoring — applied separately to each branch's reality. A branch covering a dense urban service area faces different travel-time-to-backup, neighborhood, and after-hours conditions than a rural branch with hour-long drives between visits.

Each branch's analysis should produce its own findings and its own corrective-action log, even though the method is shared. When a surveyor at the rural branch asks to see the worksite analysis, the answer is a local document that names local conditions — not a corporate PDF that could describe any office in the state. The pre-visit screening and check-in/check-out controls that the analysis drives are detailed in our guide to pre-visit risk screening for field staff, applied per branch.

#Training and reconciliation across the footprint

Training is the area where multi-branch scale most often produces a deficiency, because the roster-to-census reconciliation has to hold across every location and every employment category at once. The agency must prove that each branch's full active census — full-time, part-time, PRN, per-diem, and contracted clinicians — completed the required training for the period.

A defensible multi-branch training discipline:

  • Uses a shared curriculum mapped to field hazards so content is consistent agency-wide.
  • Reconciles each branch roster against its own census and rolls the result into a program-level completion view.
  • Tracks new hires into orientation and separations out at every location.
  • Treats contracted personnel as the highest-risk gap, branch by branch, because surveyors check them first and agencies often assume a vendor handled it.

The full delivery-and-reconciliation playbook for a scattered field team is covered in our guide to workplace violence training for a distributed home health workforce. At multi-branch scale, the program-level completion view is what lets leadership and the committee see gaps before a surveyor does.

#Why a program of record beats a survey scramble

The phrase program of record is the point of the whole exercise. A multi-branch agency that rebuilds its workplace violence evidence under deadline pressure before each branch survey is perpetually exposed — and at multi-branch scale, surveys are never all on the same day. A program of record is the single, maintained source of truth that stays current between surveys:

Program-of-record elementWhat it holdsMaintained how
Current plan (framework + branch layers)The facility-specific plan per branchReviewed on cadence, version-controlled
Committee recordsMembership, minutes, decisionsPer central-committee meeting
Worksite analysesOne per branch, currentAnnual + on material change
Training rostersCensus-reconciled per branchContinuous, rolled up program-wide
Incident logs + trendsBranch and aggregatePer incident, trended for the committee
Annual plan evaluationGoverning-body reportAnnually, footprint-wide

Kept current, this is what lets any branch survey on any day without a scramble — and what demonstrates a living, governed program across the organization.

#The bottom line

Chapter 331 carries no fine schedule, but for a multi-branch HCSSA the exposure compounds with the footprint: every branch is a separate HHSC licensure-survey surface, and a gap at any one becomes a deficiency and a discovery problem in post-incident litigation. The agencies that stay survey-ready run one governed program of record — a shared framework, tailored and proven at each branch, maintained between surveys rather than reconstructed under pressure.

A flat-fee survey-readiness audit scores your program across branches against the full requirement set, and our Chapter 331 compliance checklist lets you self-assess first. For ongoing maintenance across locations, VIGILO offers subscription-based annual compliance support built to keep a multi-branch program current year after year.


VIGILO is a healthcare compliance, training, and consulting firm. It builds survey-defensible programs and documentation; it is not a security-guard, patrol, or investigations company, and it does not guarantee safety outcomes. Every compliance claim traces to a named primary source.

From this article

Frequently asked questions

Does each branch of a multi-location HCSSA need its own workplace violence plan?

Under Chapter 331 and PL 2024-10 the plan must be facility-specific, which for a multi-branch HCSSA means a shared program framework that is tailored to each branch's service area, workforce, and worksite-analysis findings. One generic corporate plan applied unchanged to every location fails the facility-specific test; a single plan that ignores branch differences is the most-cited deficiency pattern.

Can a multi-branch home health agency run one workplace violence committee?

A multi-branch agency can operate a central program with governance oversight, but the Chapter 331 committee-composition and annual-evaluation obligations must be satisfied in a way that reflects each covered branch. Many agencies use a central committee plus branch-level champions who feed local worksite-analysis data and incident trends upward into one program of record.

What is a WVP program of record for an HCSSA?

A program of record is the single, maintained source of truth for an agency's workplace violence program — the current plan, committee records, worksite analyses, training rosters, incident logs, and annual evaluations — kept current between surveys rather than rebuilt under deadline pressure. For a multi-branch HCSSA, it is what lets one program stay consistent and survey-ready across every location, year after year.

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