Incidents

The Incidents module is the front door for anything that went wrong or nearly did. It captures the OSHA 301 narrative, determines recordability under the site's regime (OSHA 29 CFR 1904 or MSHA Part 50), and drives the investigation and corrective actions from one case.

Report an incident

Go to Incidents and click Report incident.
Fill in the site, date, and employee — pick from the roster or type a name — plus where it occurred and the OSHA 301 narrative: what the employee was doing, what happened, the injury/illness, the object or substance involved.
Tick the criteria that apply (work-related, days away, restricted work, medical treatment beyond first aid, …). For a needlestick or cut from a contaminated sharp, tick Needlestick / contaminated-sharps injury (1904.8) — 29 CFR 1904.8 makes it recordable even when no other criterion applies, and it should also be a privacy-concern case so the name is withheld from the 300 log. For a standard threshold shift at a 25 dB level, tick Recordable hearing loss — STS at ≥25 dB (1904.10) (usually the hearing module opens this case for you).
If the case is a fatality or a severe injury, tick the matching report to OSHA box — see the reporting section below.
Click Save incident. A case opens with a human-readable case number and an automatic recordability determination.

Prefer plain words? The Intake assistant (top of the Incidents list) lets you paste — or speak — what happened and returns a suggested classification, recordability hint, and draft action with cited rule text. Advisory only; the safety team confirms.

Sign the recordability determination

The case shows the determination — recordable or not, the OSHA 300 column classification, the rationale, and the cited rule text. A human must sign it off: click Confirm, or Dispute with a required note. Analyze with AI gives an advisory second opinion with citations; the suggestion is recorded to the audit trail, but it never decides — a person always signs.

Report a severe injury to OSHA (1904.39)

Reporting a severe injury to OSHA is a separate duty from recording it on the 300 log. Under 29 CFR 1904.39 you must call OSHA — a work-related fatality within 8 hours, and an in-patient hospitalization, amputation, or loss of an eye within 24 hours — by phone at 1-800-321-OSHA or online at osha.gov/report.

On the report form, each of these outcomes is its own checkbox labeled with its window. The in-patient-hospitalization help text is a reminder that it means a formal admission to the in-patient service — not emergency-room treatment or observation only.
The moment a qualifying case is saved, the case shows a prominent red banner with the reason(s), the computed deadline (UTC), and the phone number and osha.gov/report link. That banner is the primary alert by design: the 12-hour escalation sweep can't meet an 8-hour deadline, so it's only a backstop — act on the banner, not on a notification.
Once you've called or filed, use Mark reported to OSHA (choose By phone or Online form); who reported it, when, and by which method are captured in the audit trail, and the banner turns green.
Mine cases are excluded — their analog is the MSHA 30 CFR 50.10 immediate notification, tracked separately.

FMCSA accident register (49 CFR 390.15)

A motor carrier keeps a 3-year register of DOT-recordable crashes — a duty distinct from the OSHA 300 log and from the 1904.39 severe-injury report. A crash is DOT-recordable (49 CFR 390.5) when it involved a commercial motor vehicle AND resulted in a fatality, an injury treated away from the scene, or a vehicle towed from the scene by disabling damage. Crucially, this is not gated on work-relatedness — the same crash can be DOT-recordable without being OSHA-recordable, and vice versa.

On the report form, tick Commercial motor vehicle crash (DOT) plus the outcome(s) that apply — the injury-treated-away-from-the-scene and the tow-away/disabling-damage checkboxes. A fatality reuses the existing Fatality checkbox.
A qualifying case shows a DOT-recordable badge with the reason(s), and a Mark logged in accident register button — bookkeeping only (register membership is derived from the crash facts, so a case that qualifies is already in the register; the button just records that you entered it).
The register table and CSV live on the recordkeeping page — Export register CSV downloads /api/recordkeeping/fmcsa/accident-register.csv, and a dashboard info tile shows the count. This is a retention/production duty with no deadline or escalation — keep each accident 3 years and produce the register on request.
See fleet & DVIR for the vehicle side of carrier compliance.

Investigate, correct, close

Start investigation opens a root cause analysis linked to the case.
CAPAs raised against the case or from confirmed root causes are listed on it — see CAPA.
Close case is blocked for a recordable case until its investigation is verified effective. Closed cases can be reopened.
If the worker returns on restrictions, open a return-to-work case and link it back.

What happens automatically

Recordability is determined at save, with the governing regime and rule citations.
Some cases arrive on their own: a needlestick or sharps exposure recorded in bloodborne pathogens opens its 300-log privacy case here automatically (29 CFR 1904.8); a work-related recordable annual audiogram in hearing conservation opens its hearing-loss case (29 CFR 1904.10); and an injury-flagged workplace-violence event opens a linked case when the safety team names the injured employee. All link back to their source.
Hazard type, energy source, and body part are auto-coded from the narrative (deterministic); validated high-energy SIF precursors are flagged on the list and the case. The coder recognizes logistics vehicle-dynamics events — jackknife, rollover/overturn, tip-over, trailer creep and backing (→ vehicle/mobile-equipment), a load shift (→ struck-by), and a dock fall (→ fall from height) — all flagged as high-energy SIF precursors.
The case's audit trail is tamper-evident — the page verifies the chain and shows the result.

Capture more near misses

Generate a site's public no-login link (the Public field-capture links page) and put it on a QR poster — any worker or contractor can submit a near miss in minutes, online or offline.

Bring in history

Load an existing OSHA 300 log via spreadsheet import — target Incidents; the site column accepts site names. Recordable cases feed the OSHA 300/300A logs — see recordkeeping.

Recordkeeping & MSHA — OSHA 300/301 and MSHA Part 50 from the case
Root cause analysis — Structured root-cause investigation of the incident
CAPA (corrective & preventive actions) — Corrective actions raised to fix causes
Return-to-work cases — Track the injured worker's restricted-duty return
Observations (BBS) — Near-miss capture feeding incident reporting