Metrics & Leadership
Build a Workplace Violence Dashboard for Leadership
How to build a workplace violence incident dashboard for hospital leadership — the views, the data sources, and the trending that Chapter 331 and the Joint Commission expect.
A workplace violence incident dashboard turns your raw incident log into a repeatable, trended view leadership can read at a glance — incidents by type, unit, and severity over time, paired with program activity like training completion and corrective-action closure. It is the operational layer beneath the statutory annual board report, and it is how you prove incident data is actually used.
This article shows how to build the dashboard referenced in our pillar, reporting workplace violence to your board. It is written for the safety director, risk manager, or compliance officer who owns the data between annual reviews.
#Why a dashboard, beyond the annual report
Texas Health & Safety Code Chapter 331 requires an annual plan evaluation reported to the governing body (SB 240, 88th Leg., 2023). But a once-a-year snapshot is not how a program stays healthy. The Joint Commission's workplace violence requirements (effective January 1, 2022 for hospitals; TJC R3 Report Issue 45) require reporting, tracking, and trending of incident data — and a surveyor's test is not whether you have data, but whether you use it. A dashboard is the artifact that demonstrates use: it trends incidents over time and shows the action each trend prompted.
The dashboard also feeds the annual report. The board scorecard in the metrics every hospital board should see is, in practice, a once-a-year freeze of the same data the dashboard tracks continuously.
#Start with the data sources
A dashboard is only as trustworthy as the inputs feeding it. Map each view to a source first:
| Source | Feeds | Note |
|---|---|---|
| Incident report form | Incidents by type, unit, severity | The foundation; must be consistent and structured |
| Training rosters | Training completion (full census) | Include agency, per-diem, contracted |
| Worksite-analysis findings log | Findings open/closed | From your annual risk assessment |
| Committee minutes | Meetings held vs. scheduled | Evidence the committee functions |
| Corrective-action tracker | Actions open/closed, aging | The metric surveyors quietly check |
| OSHA 300 log | Injuries, days away from work | Where recordable |
The single most important input is a consistent incident report form. If two units capture incidents differently, no dashboard built on top can be trusted. Standardize capture before you build views.
#The four views a leadership dashboard needs
#View 1 — Incident trend
Incidents over time (monthly or quarterly), broken out by type (the four standard categories), unit, and severity. Always show a denominator — per 1,000 patient-days or per FTE — so the trend reflects exposure, not just census changes. Read rising reports carefully: better reporting and more violence look identical on a raw count.
#View 2 — High-risk-unit focus
A drill-down on the emergency department, behavioral health, and other concentration points. This view earns its place because surveyors run individual tracers on exactly these units, and because that is where controls pay off. It pairs naturally with the unit-specific exposures covered for hospitals.
#View 3 — Program activity (leading indicators)
Training completion, worksite-analysis findings closed, committee cadence, and corrective-action closure with aging. This is the leading-indicator half of the dashboard — the forward signal that the program is working. See leading vs. lagging indicators for why this view matters as much as the trend.
#View 4 — Action loop
A short log of what changed because of the data — a control added, a policy revised, a training module updated, with the date and the trigger. This view is small but decisive: it is the visible proof that data drives change, and it directly answers the surveyor's question, show me where an incident changed your program.
#Keep it honest, keep it light
A dashboard fails when it becomes either dishonest or unreadable:
- Attribute every figure with a denominator and a year — the same discipline as the board report.
- Trend, do not snapshot. A single period in isolation misleads; show direction.
- Resist vanity charts. A board and an executive team need four clear views, not forty.
- No tool is required to start. A disciplined spreadsheet beats an expensive platform fed by an inconsistent form. The structure matters more than the software.
- Mind underreporting. Treat a low count as a question, not an achievement.
#From dashboard to board report
The dashboard runs monthly or quarterly for the committee and executive team; the annual report freezes it for the governing body. The two are the same data at different cadences — which is exactly the structure that satisfies Chapter 331's annual obligation while keeping the program alive between reviews. We connect the two in reporting workplace violence to your board.
#How VIGILO helps
VIGILO helps standardize the incident report form, define the dashboard views, and wire the data sources into a repeatable leadership view that rolls up cleanly into the annual governing-body report. This is compliance, documentation, and consulting assistance, not a guarantee of any safety outcome, and VIGILO operates strictly as a compliance, training, and consulting firm — never as a security-staffing provider.
To stand up incident tracking and trending that a surveyor accepts, start with a flat-fee survey-readiness audit, or maintain the dashboard through an annual program review.
Sources: Texas Health & Safety Code Chapter 331 (SB 240, 88th Leg., 2023); The Joint Commission Workplace Violence Prevention requirements (effective Jan. 1, 2022 for hospitals; R3 Report Issue 45); OSHA General Duty Clause §5(a)(1) and Publication 3148. This article is general compliance information, not legal advice.