# Incident reporting for chemical and process plants

> Report from the unit, start the investigation within 48 hours, and close every fix.

Source: https://incidentkit.ai/solutions/chemical-and-process-industries · Updated Oct 5, 2026

**Status: rolling out.** This pack is being released in stages.

**Who:** Operators, techs and contractors report. Process safety engineers lead the investigation, and plant managers own each fix and sign off.

## The problems

- **Near misses are radio calls, not records:** A weeping seal lives in a logbook. OSHA's process safety management (PSM) rule also covers near misses that could have caused a catastrophic release.
- **The 48-hour clock and the missing paper trail:** An investigation must start within 48 hours. The team needs a process-knowledgeable person and any involved contractor (1910.119(m)(2), (m)(3)). Start times are hard to reconstruct.
- **Recommendations that die in the report:** Paragraph (m)(5) requires a system to promptly resolve findings and recommendations. Resolutions must be documented. A PDF on a shared drive is not that system.
- **Incidents and changes live in separate files:** A leak traces to a change that skipped management of change (MOC), and the incident file never says so. Paragraph (l) requires written MOC procedures.

## Incident types in the pack

- Loss of primary containment
- Relief valve or rupture disk activation
- Near miss with catastrophic release potential
- Fire or explosion
- Overpressure or runaway reaction
- Safety system, alarm or interlock failure
- Mechanical integrity failure
- Change made without MOC review
- Bypassed or defeated safeguard
- Contractor incident in a covered process
- Chemical exposure or inhalation
- Injury or fatality

## Regulators and standards

- **OSHA 29 CFR 1910.119(m) (PSM incident investigation):** Investigate any incident that did or could reasonably have caused a catastrophic release. Start within 48 hours. Resolve findings, review with staff, keep the report five years.
- **OSHA 29 CFR 1910.119(l) (management of change):** Written procedures for changes to chemicals, technology, equipment and procedures, except replacements in kind. Train affected employees before startup and update process safety information.
- **OSHA 29 CFR 1910.119(a) and Appendix A (coverage):** Generally covers processes with listed chemicals at or above threshold amounts, or 10,000 pounds or more of a Category 1 flammable gas or flammable liquid below 100 degrees F flashpoint.
- **EPA 40 CFR 68.81 (risk management program):** A parallel duty for covered stationary sources, with the same 48-hour start, team, report, resolution and five-year retention. EPA adds provisions for some incidents. Check the current text.
- **Chemical Safety Board 40 CFR 1604.3 (release reporting):** A covered source must report an accidental release to air that causes a death, an inpatient hospitalization or $1,000,000 or more of property damage. The deadline is eight hours.
- **OSHA 29 CFR Part 1904 and 1904.39:** Injury recordkeeping still applies. Report a fatality within 8 hours. Report an inpatient hospitalization, amputation or loss of an eye within 24 hours.

## How it works

1. **Report: from the unit, with the equipment tag** Anyone texts what happened: unit, tag, material, quantity. Lauren asks if it was contained, whether a relief device was involved, and what recent maintenance or change came before.
2. **Investigate: built around paragraph (m)** The record has fields for the incident date, investigation start date, team (including any contract employee), description, factors and recommendations. Lauren drafts, marked 'Lauren · draft'.
3. **Correct: recommendations as tracked actions** Each recommendation becomes an action with an owner, due date and evidence. Link the MOC number or work order from your own systems. Nothing closes until verified.
4. **Prove: review, retention and repeats** Record that the report was reviewed with affected personnel and contractors, and keep it five years. Analytics show repeat events by unit, equipment and cause.

## Scenario: A seal leak that could have been worse

A transfer pump seal weeps flammable liquid onto the pad overnight, and nobody is hurt.

- **Sat 3:15 am, Field operator contains leak, texts report.** The low-level alarm sounds. A field operator shuts the pump down, isolates the area and contains the liquid, then texts a report.
- **3:22 am, Lauren asks about recent maintenance.** Lauren asks for the material, amount, ignition sources, gas reading, recent maintenance and changes. The seal was replaced two weeks earlier.
- **3:40 am, Process safety engineer flags PSM event.** The shift supervisor and on-call process safety engineer get the report, and the engineer flags it as a PSM event. The 48-hour start shows.
- **Sat 11:00 am, Team convenes, start time recorded.** The investigation starts about eight hours in, with a contract employee on the team because contractors did the seal job. Start time and team are recorded.
- **Mon 2:00 pm, Different seal spec, MOC skipped.** The lead investigator edits Lauren's draft and signs the findings: the replacement seal had a different specification, and the change skipped MOC.
- **Day 9, Recommendations become actions with owners.** Each gets an owner and a date: review seal specs on every pump in that service, add a spec check to the job plan, and add an MOC trigger for seal replacements.
- **Day 12, Report reviewed with operators and contractors.** Attendance is recorded for the operators, maintenance staff and contractor crew involved.
- **Day 40, Field verification closes the actions.** The report enters the five-year record.

## What is in the pack

**Forms:** Incident and near-miss report: unit, tag, material, amount; Loss of containment supplement; PSM investigation report and team record, with contract employees; Recommendation tracker with MOC and work order references; Injury report with OSHA 301-equivalent fields

**Routing:** Reports go to the shift supervisor and process safety engineer; Possible catastrophic releases show the 48-hour deadline; Contractor events copy the contractor's safety contact; Severe injuries alert EHS; covered sources also get a CSB report prompt

**Exports:** PSM investigation report as a PDF; Open recommendations report for reviews and audits; OSHA 300 log, 300A summary and 301 report (rolling out); Incident register by unit, equipment and cause; Audit trail

**Roles:** Reporter: any operator, tech or contractor; Shift supervisor: reviews and routes; Investigator: process safety engineer or team lead; Process safety manager: approves and closes; Executive: certifies the 300A; Read-only: insurer, corporate or auditor

## Outcomes

- **Near misses captured at the source:** A weeping seal or lifted relief valve takes a minute to report, so it is on record before shift handover.
- **The 48 hours stay visible:** The deadline, team, contract employee and start time are recorded as they happen, not rebuilt for an audit.
- **Recommendations that reach closure:** Each recommendation has an owner, due date and evidence, and links to the MOC or work order in your own systems.
- **Repeats show up by equipment:** Leaks, alarms and bypasses clustered by unit and equipment show a repeating failure before it becomes a bigger event.

## Frequently asked questions

### What does OSHA PSM require after a near miss?

It requires an investigation. Paragraph (m) of 29 CFR 1910.119 covers each incident that resulted in, or could reasonably have resulted in, a catastrophic release. It must start within 48 hours and use a process-knowledgeable team. Findings are resolved and documented. The report is reviewed with affected personnel and kept five years.

### Does IncidentKit manage our whole PSM program?

No. It tracks incidents, investigations and recommendations. It links to the MOC, PHA and mechanical integrity records you keep elsewhere. It works beside your maintenance and document systems.

### How does EPA's 40 CFR 68.81 compare with the PSM rule?

It reads much like paragraph (m): investigate any incident that did or could reasonably have caused a catastrophic release, start within 48 hours, form a team, write a report, resolve findings and keep it five years. EPA adds provisions for some incidents, so check the current text.

### Do we need to tell the Chemical Safety Board about a release?

Possibly. The CSB's rule at 40 CFR 1604.3 covers accidental releases to air from stationary sources that cause a fatality, a serious injury or $1,000,000 or more of property damage. Report within eight hours, or send the NRC number within 30 minutes of an NRC report. A person decides, and IncidentKit flags the possibility.

### Can contractors report, and what does it cost?

Yes. A contractor reports by QR code or text like any employee, and a contract employee can sit on the investigation team. Non-patient incident reporting is free on the Open plan, with no seats, modules or setup fee. A per-site Regulated plan adds compliance packets and setup.

## Sources

- [eCFR: 29 CFR 1910.119, process safety management of highly hazardous chemicals](https://www.ecfr.gov/current/title-29/section-1910.119)
- [eCFR: 40 CFR 68.81, incident investigation](https://www.ecfr.gov/current/title-40/section-68.81)
- [eCFR: 40 CFR 1604.2, definitions (Chemical Safety Board)](https://www.ecfr.gov/current/title-40/section-1604.2)
- [eCFR: 40 CFR 1604.3, reporting an accidental release](https://www.ecfr.gov/current/title-40/section-1604.3)
- [eCFR: 29 CFR 1904.39, reporting fatalities, hospitalizations, amputations and loss of an eye](https://www.ecfr.gov/current/title-29/section-1904.39)
- [OSHA: Process safety management](https://www.osha.gov/process-safety-management)
- [OSHA: Incident investigation](https://www.osha.gov/incident-investigation)

## Related

- [Incident investigations and root cause analysis](https://incidentkit.ai/product/investigations)
- [Corrective and preventive actions (CAPA) tracking](https://incidentkit.ai/product/corrective-actions)
- [Incident audit trail: every change, who and when](https://incidentkit.ai/product/audit-trail)
- [Root Cause Analysis: How to Run One That Leads to Action](https://incidentkit.ai/use-cases/root-cause-analysis)
- [Near-Miss Reporting: How to Build a Program That Works](https://incidentkit.ai/use-cases/near-miss-reporting)
- [Contractor and Visitor Incidents: Who Reports What](https://incidentkit.ai/use-cases/contractor-and-visitor-incidents)
- [Root cause analysis and CAPA: methods and strong actions](https://incidentkit.ai/guides/root-cause-analysis-and-capa-guide)
- [PSM incident investigation: 29 CFR 1910.119(m) explained](https://incidentkit.ai/compliance/osha/process-safety-incident-investigation)
- [Hazard communication 29 CFR 1910.1200: SDS, labels, training](https://incidentkit.ai/compliance/osha/hazard-communication)
- [OSHA severe injury reporting: 8-hour and 24-hour rules](https://incidentkit.ai/compliance/osha/severe-injury-reporting)
- [OSHA recordkeeping requirements: 29 CFR 1904 explained](https://incidentkit.ai/compliance/osha/recordkeeping-overview)
- [Lockout/tagout 29 CFR 1910.147: program and event data](https://incidentkit.ai/compliance/osha/lockout-tagout)