Joint Commission Readiness
A Joint Commission WVP Tracking & Trending System
How to build a workplace violence incident reporting, tracking, and trending system aligned to Joint Commission requirements, with leadership review that closes the loop.
The Joint Commission requires hospitals to report, track, and trend workplace violence incidents, a requirement introduced January 1, 2022 in the Environment of Care (EC) and Leadership (LD) chapters and now found at NPG.02.04.01 EP 1 (TJC National Performance Goal #2a) and NPG.11.01.01 EP 3. That shorthand has three verbs, and a surveyor checks all three. A common failure is not the absence of a log; it is data that is captured but never aggregated, analyzed, or reviewed by leadership. This guide shows how to build a system that survives a tracer.
It is a companion to our workplace violence tracer walkthrough and supports our Joint Commission survey-readiness resource.
#The three verbs, and why each gets checked
The requirement is deceptively simple in wording and easy to half-build. Each verb is a separate test:
| Verb | What it means | How a surveyor tests it |
|---|---|---|
| Report | Staff have a working channel to file an incident. | Asks a frontline nurse to describe how they would report. |
| Track | A log or registry captures every report. | Opens the incident log and pulls the last several reports. |
| Trend | Data is aggregated, analyzed, and reviewed by leadership. | Asks for the trend report and where leadership reviewed it. |
A facility can have a flawless reporting channel and a clean log, and still be cited, because the data was never trended, or was trended but never reached leadership. "How do you track and trend your workplace violence data? Who sees the trend report, and how often?" is the kind of question a surveyor asks, and "who sees it" is the part that fails.
Two parts of the current text go beyond the three-verb shorthand. NPG.11.01.01 EP 3 requires the hospital to investigate safety and security incidents, not just log them, and NPG.02.04.01 EP 1 requires reporting of workplace violence incidents to the governing body. Build both into the system: an investigation note on each significant event, and a standing governing-body agenda item for the incident report.
Accuracy note on citation. Cite this requirement as NPG.02.04.01 EP 1 under National Performance Goal #2a (the process to report incidents and analyze trends, and reporting to the governing body; formerly LD.03.01.01 EP 9), together with NPG.11.01.01 EP 3 (monitoring, internally reporting, and investigating incidents; formerly EC.04.01.01), and the January 1, 2022 effective date. The EC and LD numbering is retired for hospitals and critical access hospitals as of January 1, 2026, and the 2026 National Performance Goals chapter is a free download, so the current EP numbers can be checked and quoted directly.
#Build the reporting layer so staff actually use it
A trending system is only as good as the data flowing into it, and the most dangerous failure is underreporting: floor staff who absorb minor assaults without filing because reporting is slow, punitive, or pointless. A surveyor surfaces this in tracer interviews, and a thin incident log against a high-acuity unit reads as a culture gap, not a safe one.
To build a reporting layer staff trust:
- Make reporting fast: a channel a nurse can complete in minutes, not a form that eats a break.
- Make it confidential and protected: pair it with anti-retaliation language so reporting carries no penalty.
- Close the feedback loop: when staff see incidents drive change, reporting rises; when reports vanish into a void, it falls.
The incident report form itself should capture what trending and survey evidence need: unit, shift, type of event, antecedents, response, injury, and follow-up. For form design, see our guide to the incident report form surveyors need.
#Build the tracking layer as a single registry
Tracking means one log or registry that captures every reported event, not scattered records across units. A consolidated registry is what makes trending possible and what a surveyor opens to pull the last several reports. Each entry should be retrievable, dated, and linked to its follow-up actions, so that when a surveyor asks "show me the last three reports and what happened after," the answer is one click, not a hunt.
#Build the trending layer, and route it to leadership
This is the layer most facilities under-build. Trending turns a list of incidents into intelligence:
- Aggregate the log over a period; quarterly is a defensible cadence.
- Analyze for patterns: which units, which shifts, which types of event, which antecedents recur.
- Produce a trend report: a short, repeatable document, not a one-off.
- Route it to leadership or committee for review, report incidents to the governing body, and minute both.
- Close the loop: show at least one program change the data drove.
The fourth and fifth steps are the ones surveyors quietly check. A trend report that exists but never appears in leadership minutes fails the "who sees it" test. A trend report that leadership reviewed but that never changed anything fails the closed-loop test. The data has to go somewhere and do something.
#What surveyors review
To verify the reporting-tracking-trending requirement, a surveyor opens:
- The incident reporting policy (with confidentiality and anti-retaliation language).
- The incident log or registry and individual line-level reports.
- The aggregated trend report presented to leadership.
- Committee or leadership minutes showing the trend data was reviewed and acted on.
- Governing-body minutes showing workplace violence incidents were reported.
- Investigation notes for sampled incidents.
- Evidence the data fed corrective action: the closed loop.
For the full set of documents a surveyor opens across the WVP program, see the documents a Joint Commission surveyor reviews.
#Common deficiencies
A Joint Commission finding is documented as a Requirement for Improvement (RFI) scored on the SAFER Matrix. Against the reporting-tracking-trending requirement, the recurring findings are:
| Deficiency | Why it is scored |
|---|---|
| Incidents reported but never trended | "Track" without "trend" is incomplete. |
| Trended but never seen by leadership | The requirement includes leadership review. |
| Underreporting: floor staff don't file minor assaults | Surfaces as a culture gap in tracer interviews. |
| No closed loop: incidents never change the program | Trending must drive action, not just reporting. |
| Trend report exists but no minutes prove review | If the minutes do not show the review, a surveyor treats it as not done. |
| Incidents logged but never investigated | NPG.11.01.01 EP 3 calls for investigation, not just a log. |
| Incidents never reported to the governing body | NPG.02.04.01 EP 1 names governing-body reporting explicitly. |
Every one is a documentation-and-practice gap. The fix is rarely more software; it is routing the data to leadership and proving the loop closed. We walk through remediation in our guide on closing a Joint Commission workplace violence RFI.
#How to prepare
- Audit the reporting channel for speed, confidentiality, and anti-retaliation protection; fix anything that suppresses reporting.
- Consolidate tracking into one retrievable registry linked to follow-up actions.
- Produce a quarterly trend report on a fixed schedule, analyzed by unit, shift, and type.
- Minute leadership review of the trend report every cycle; make it a standing agenda item.
- Document one closed loop per period: a specific program change the incident data drove.
- Put the incident report on the governing body's agenda and keep the minutes.
#One program, three regimes
For Texas hospitals, the same incident system answers more than the Joint Commission. The reporting-and-data element appears in all three governing regimes: reporting, tracking, and trending (NPG.02.04.01 EP 1 and NPG.11.01.01 EP 3) for the Joint Commission; a confidential reporting policy with anti-retaliation protection under Texas Health & Safety Code Chapter 331 (SB 240, with hospitals required to comply since September 1, 2024); and recordkeeping as Component 5 of OSHA's advisory Publication 3148, where serious assault injuries are also OSHA 300-recordable and cross-checked against the WVP log. One registry, one trend report, three regimes. Our guide to Texas SB 240 and Chapter 331 compliance maps the statute, and the Chapter 331 compliance checklist lets you self-audit where your evidence lives.
#How VIGILO helps
VIGILO builds the incident reporting policy and registry, designs the quarterly trend report, and structures the leadership-review step so the closed loop is documented and survives a tracer, then runs the quarterly incident-log review and trend report on a fixed calendar through a flat-fee annual compliance subscription so the data never goes stale between surveys. This is compliance and survey-readiness assistance; it is not a guarantee of safety outcomes, and VIGILO is a compliance, training, and consulting firm, not a security service.
To benchmark whether your tracking-and-trending system would survive a data-use tracer today, start with a flat-fee Joint Commission survey-readiness review.
This article is general compliance information, not legal advice; confirm the current element text in the Joint Commission's 2026 National Performance Goals chapter. Sources: The Joint Commission National Performance Goal #2a (Preventing Workplace Violence; relocated under Accreditation 360, eff. Jan. 1, 2026) and the Environment of Care chapter (effective January 1, 2022; now National Performance Goal #2a); Texas Health & Safety Code Chapter 331 (SB 240, 2023); OSHA Publication 3148 and the OSHA 300 Log (29 CFR 1904).