QEHSmodules
Template · OSHA recordable incidents
300 / 300A / 301-aligned incident capture, case classification guard tree, restricted-duty day counter, and an ITA submission reminder cron.
6 min read · 3 sections
What it looks like
Incident AddEdit — 34 fields across 6 workflow states
app.qehsethos.com/incidents/new
300 log export — filterable by year, site, and case type
app.qehsethos.com/reports/osha-300
Sample records (pre-seeded)
| Case # | Date | Employee | Type | Days away | State |
|---|---|---|---|---|---|
| INC-2024-0001 | 2024-11-03 | J. Ortega | Laceration — R hand | 0 | Closed |
| INC-2024-0002 | 2024-11-18 | K. Patel | Strain — L shoulder | 3 | Closed |
| INC-2025-0001 | 2025-01-22 | S. Nguyen | Exposure — solvent | 0 | Investigation |
| INC-2025-0002 | 2025-02-14 | A. Kim | Fracture — R ankle | 18 | Restricted duty |
| INC-2025-0003 | 2025-03-07 | T. Alvarez | Concussion | 5 | Closed |
Typical configuration
- Guard: severity ≥ medium auto-triggers a CAPA via the "Actions" module linkage.
- Guard: "days away > 0" forces the restricted-duty day-counter field to be populated before state transitions past Investigation.
- Cron: annual March-2 reminder to submit OSHA 300A via ITA portal; fires 30 + 7 + 1 day before.
- Permissions: Safety team owns the record; HR has read-only on injured-party fields; Site lead gets read-only org-wide.