Guides

Workplace violence

Maintain the written prevention plan with its annual review, log workplace-violence events by type and severity, record the post-incident debrief within two days, and correct serious ones with a CAPA.

This module covers the two halves of a workplace-violence prevention program, kept under OSHA's General Duty Clause and structured after published program requirements such as Cal/OSHA §3342 (SB-553) and the Joint Commission workplace-violence standards: a written prevention plan that gets reviewed at least annually, and the violent-incident log. The log captures threats, physical assault and harassment by type (the four published types: criminal intent, service recipient, worker-on-worker, personal relationship) and severity, with a prompt post-incident debrief.

Maintain the prevention plan

  1. Under Prevention plans, pick a site and click Create plan — Cal/OSHA §3342-style programs require an effective written plan to be established and maintained, per site.
  2. Each plan shows its last-reviewed date and next-due date (annual); an overdue plan flags with an overdue badge.
  3. Click Mark reviewed when you complete the annual review to reset the clock. The review is recorded under your name.

Log an incident

  1. Go to Workplace violence and use the Log a workplace-violence incident form.
  2. Choose the Site, the date it occurred, the location, and the department.
  3. Pick the type and severity (near miss → verbal threat → physical, no injury → physical with injury → fatality), and describe the event.
  4. Record the aggressor category or role only (no personal identifiers), employees affected, and the flags — weapon involved, law enforcement notified, and whether it resulted in an OSHA-recordable injury.
  5. Click Log incident. It gets a log number.

Record the debrief

The Debrief… button on a row records the post-incident response:

  1. Click Debrief…, type the debrief outcome / support offered, and click Save debrief.
  2. The row's response badge flips to debriefed (green). Until then it shows pending, or overdue (red) once the due date passes.

Correct a serious event

Use the CAPA button on a row to raise a corrective action, for example to add controls after a serious incident — you can name an owner and due date right there. The row then links to the CAPA so you can track it to closure.

Open the recordkeeping case for an injury

If the event resulted in an injury, click 300-log case… on the row and pick the injured employee — that opens a linked case in Incidents where the safety team completes the recordability determination. The injured person is named only on the case; this log stays de-identified by design.

Export the log

Click Export log CSV to download the violent-incident log (the record Cal/OSHA §3342-style programs must produce on request). It carries the aggressor category, never a personal identifier.

What happens automatically

  • A prevention plan whose annual review is overdue escalates by notification to the recorded reviewer (or the Safety Team when nobody has reviewed it yet).
  • The debrief is due 2 days after the event occurred. Once past due, the row flags overdue and the escalation sweep notifies the Safety Team — the open debrief doesn't just sit as a number.
  • Serious events — a weapon involved, or physical-with-injury / fatality severity — highlight red in the list and escalate immediately, without waiting out the debrief window.
  • The dashboard counts events logged, events awaiting response, serious events, and prevention-plan reviews overdue.

Tip: record the aggressor category or role rather than a name — the log is designed to avoid personal identifiers.

Want to see this working?

Open a sandbox with your industry's data already in it — no signup, nothing to install.