Metrics & Leadership
Measuring WVP Underreporting: The Capture-Rate Method
Underreporting distorts every workplace violence metric. Here is how to estimate your capture rate, close the reporting gap, and report a defensible trend to your board.
Workplace violence is one of the most underreported hazards in healthcare, which means a raw incident count is an unreliable number on its own. To measure underreporting you estimate a capture rate — the share of events that actually occurred that were formally reported — by comparing your incident log against independent records that captured the same events. The gap is the story your board needs.
This article supports our pillar, the metrics every hospital board should see. It is written for the risk manager, quality lead, and compliance officer who already know their incident count is too low and need a defensible way to say so — and to fix it.
#Why underreporting breaks every other metric
Every downstream metric — your trend line, your benchmark against peers, your incident rate per 1,000 patient-days — is built on the incidents you captured. If capture is incomplete, the analysis sits on sand. Two failure modes follow directly:
- A low count looks like safety. A unit that reports almost nothing may have a strong culture of brushing off assault as "part of the job," not a low-risk environment. The quietest log is sometimes the most dangerous unit.
- A rising count looks like deterioration. When a program first improves reporting, counts climb because staff finally surface events that were always happening. A board reading the count without context may conclude the program is failing at the exact moment it is working.
The sector backdrop makes the stakes concrete: the healthcare workplace-violence injury rate ran roughly 5x the private-sector average in 2018 (BLS, 2018, via NIOSH/CDC). When official counts run that high despite well-documented underreporting, the true burden is higher still — and your facility's count almost certainly understates it.
#What "capture rate" means
Capture rate is the proportion of events that occurred that were formally reported through your incident system:
Capture rate ≈ formally reported events ÷ estimated total events that occurred
You cannot know the true denominator exactly — that is the nature of an underreported hazard. But you can triangulate it from independent records that each captured some events your incident log may have missed. The goal is not a precise percentage; it is a defensible estimate and a direction of travel you can trend year over year.
#Four independent sources to triangulate against
No single source captures every event, but each catches a slice your incident log can miss. Cross-referencing them is the core of the method, and it is the same reconciliation a surveyor or inspector respects.
| Source | What it independently captures | What the gap reveals |
|---|---|---|
| OSHA 300 Log | Recordable assault injuries under 29 CFR 1904 | An injury on the 300 Log with no matching incident report = a missed report |
| Security / behavioral-response activations | Calls for help, response-team activations, restraint events | Activations without a paired incident report = events that "got handled" but never logged |
| ED encounter and triage notes | Staff-assault documentation, agitated-patient encounters | Clinical mentions of staff aggression with no incident report |
| Anonymous staff survey | Events staff experienced but chose not to report | The honest gap between "experienced" and "reported" |
The first three are record-to-record reconciliations you can run quarterly. The fourth — a short, periodic, genuinely anonymous survey asking how many violent events a respondent experienced versus reported in a defined window — gives you the human-scale multiplier the logs cannot. For the underlying data-integrity practices these reconciliations depend on, see incident data quality and completeness.
#The drivers you are actually measuring
Underreporting is not random. It clusters around four known causes, and naming them turns a number into an action plan:
- Normalization. Staff who believe assault is part of the job will not report it.
- Fear of retaliation. Staff who fear being blamed or penalized stay silent. Texas Health & Safety Code Chapter 331's confidential reporting and anti-retaliation requirements target this driver directly — which is why your reporting policy is also a data-quality control. See confidential reporting and anti-retaliation under Chapter 331.
- Friction. A reporting tool that takes fifteen minutes mid-shift will not be used. The fix is operational, not cultural.
- Definitional uncertainty. Staff who are unsure whether a verbal threat "counts" will not report it. A written, communicated definition of a reportable event removes the doubt.
#Turning the capture rate into a trend
A single capture-rate estimate is a snapshot; the governance value is in the direction. Re-run the triangulation on the same schedule each year and report the movement, paired with the leading indicators that explain it:
- Reporting volume, read explicitly as a culture signal rather than only a risk signal.
- The reconciliation gap between the incident log and the OSHA 300 Log, trended toward zero.
- Survey-reported "experienced but did not report" rate, trended down.
- Training completion and reporting-policy awareness across the full census.
Reported alongside the count, these are what let you tell a board: reported incidents rose 22% this year; over the same period the log-to-300 gap closed, survey-reported silence fell, and reporting awareness reached 94% of staff — so the rise reflects better capture, not a more dangerous environment. That is the narrative a governing body can govern by. For how this fits the wider trend analysis, see trending incident data the way Joint Commission expects.
#What surveyors and plaintiff's counsel see
This matters beyond the boardroom. A surveyor who finds OSHA 300 Log injuries with no matching incident reports sees a recordkeeping and credibility gap. And in litigation, an incident log that mysteriously shows few events on a unit the ED notes describe as routinely violent can read as a facility that looked away. Demonstrating that you measure your own capture rate — and act to improve it — is itself evidence of a living, good-faith program rather than a paper one.
#Common mistakes
- Reporting the count with no capture context — the single most common way a board is misled.
- Treating a low count as a win — the quietest log can be the highest-risk unit.
- Skipping the log-to-300 reconciliation — the easiest underreporting check to run and the one inspectors run too.
- Running a "anonymous" survey that staff don't trust — if anonymity is not credible, the survey understates the gap.
#How VIGILO helps
VIGILO builds capture-rate estimation into the annual program review — reconciling your incident log against the OSHA 300 Log, response activations, and a confidential staff survey, then folding the result into a board narrative that reads the trend correctly. This is compliance and survey-readiness assistance, not a guarantee of any safety outcome, and VIGILO operates strictly as a compliance, training, and consulting firm.
To measure your capture rate and close the reporting gap, start with a flat-fee survey-readiness audit, or maintain it through an annual program review. To see who relies on these numbers, visit who we serve.
Sources: Texas Health & Safety Code Chapter 331 (SB 240, 88th Leg., 2023); OSHA General Duty Clause §5(a)(1), Publication 3148, and recordkeeping rule 29 CFR 1904; The Joint Commission Workplace Violence Prevention requirements (effective Jan. 1, 2022 for hospitals); BLS 2018 incidence data via NIOSH/CDC. This article is general compliance information, not legal advice.