# Know about the near miss before it becomes the injury

> Near misses, injuries and fixes in one record, tied to work orders.

Source: https://incidentkit.ai/solutions/plant-managers · Updated Oct 5, 2026

**Who:** Operators and supervisors report; the EHS lead investigates. You own the site's results and often certify the OSHA 300A.

## The problems

- **A report competes with the schedule:** A report that takes a supervisor off the floor loses to the production plan. So near misses stay unreported until one becomes an injury.
- **Four owners, four records:** Safety has the injury, maintenance the work order, quality the nonconformance and HR the claim. Each tells a different story.
- **Fixes wait for downtime:** The right fix needs the line down, and downtime needs approval. Weeks pass. Nobody checks if the fix worked.
- **You sign for the plant:** You may be the top official on site, who can certify the 300A. Where process safety management applies, an investigation must start within 48 hours.

## Incident types in the pack

- Near misses: pinch points, forklift and pedestrian conflicts, dropped loads
- Injuries that need a recordable decision
- Lockout/tagout events and bypassed interlocks
- Machine guarding incidents and unexpected startups
- Chemical releases and near-miss releases
- Fires and smoke events
- Contractor injuries on site
- Forklift and powered industrial truck incidents
- Equipment failures that stopped the line
- Slips, trips and falls
- Workplace violence and threats
- Corrective actions waiting on downtime or a work order

## Regulators and standards

- **OSHA recordkeeping, 29 CFR 1904:** Keep a separate 300 Log for each establishment and enter recordable cases within seven calendar days. A company executive certifies the 300A. Post it February 1 through April 30.
- **Severe injury reporting, 29 CFR 1904.39:** Report a fatality within 8 hours and an inpatient hospitalization, amputation or loss of an eye within 24 hours.
- **Lockout/tagout, 29 CFR 1910.147:** Inspect each energy control procedure at least annually to make sure the procedure and the standard are being followed.
- **Process safety management, 29 CFR 1910.119(m):** Where covered, investigate any incident that did or could have caused a catastrophic release of a highly hazardous chemical. Start within 48 hours, document findings and keep reports five years.
- **NIOSH hierarchy of controls:** Elimination, substitution, engineering controls, administrative controls, then personal protective equipment, from most to least effective.
- **BLS incidence rates:** Rate equals cases times 200,000 divided by employee hours worked. The DART rate counts days away, restricted or transferred cases.

## How it works

1. **Operators report from the floor** Scan a QR code on the machine or text Lauren from a phone, including where signal is poor. See [mobile and offline](https://incidentkit.ai/product/mobile-and-offline). Voice reporting is rolling out.
2. **Lauren asks what the investigator would ask** Equipment, task, lockout step, guard status, shift and who restarted. The supervisor reviews, edits and signs, and drafted fields stay marked 'Lauren · draft' until approved.
3. **Investigations start inside the clock** Routing alerts you and the EHS lead by severity and equipment. An investigation records the team, the date it began, the description, contributing factors and recommendations, which are the elements a PSM report requires.
4. **Actions carry a work order and a check** Each action has an owner, a due date, evidence and an effectiveness check. Record your CMMS work order number on the action. Deeper CMMS integration is rolling out.

## Scenario: A conveyor near miss on third shift

The line restarts while an operator clears a jam, nobody is hurt, and the report still matters.

- **02:10, Supervisor scans QR and texts Lauren.** The operator's hand is clear when the conveyor restarts. The supervisor scans the QR code on the conveyor and texts Lauren.
- **02:12, Lauren asks about the lockout step.** Lauren asks for the equipment ID, task, lockout step, who restarted the line and whether a guard was in place. The draft is marked 'Lauren · draft'.
- **02:30, Signed report routes to EHS lead.** The supervisor edits and signs. Routing sends it to the EHS lead and plant manager because it is a near miss involving energy control.
- **07:00, EHS lead starts the investigation.** At shift handoff the plant manager opens the report. The EHS lead starts an investigation with the team lead and a maintenance technician.
- **Day 2, Investigation finds no lockout point.** The cluster view shows a similar near miss on the sister line five weeks earlier. The jam-clearing procedure had no lockout point on this line.
- **Day 5, Engineering and procedure actions created.** An engineering action adds a lockout point and interlocked door on both lines. An administrative action revises the procedure. Maintenance adds the work order number to each action.
- **Day 40, Effectiveness check closes both actions.** The check finds no jam-clearing events with energy exposure on either line. The EHS lead verifies the evidence and the actions close.
- **Annual lockout/tagout inspection, Annual inspection uses the record.** The periodic inspection under 29 CFR 1910.147(c)(6) uses the record: the near miss, the finding, the fix and the check.

## What is in the pack

**Forms:** Near miss and hazard report, with QR quick report on equipment; Injury and illness report with recordability questions; Equipment and process incident report; Contractor incident form; Corrective action plan with work order and effectiveness check

**Routing:** Alerts to EHS and plant manager by severity and equipment; Instant alert for hospitalization, amputation, eye loss or fatality; Maintenance notice when an action needs a work order; Overdue-action reminders to the owner, then the plant manager

**Exports:** OSHA 300, 300A and 301 (rolling out); Analytics by equipment, shift, location and cause; Investigation report: team, contributing factors, recommendations; Read API and signed webhooks

**Roles:** Plant manager: reads across the site, certifies the record; EHS lead: classifies, investigates and signs; Supervisors: first-line review; Maintenance, quality and operations: close actions with evidence

## Outcomes

- **Near misses that get reported:** A text or QR code takes less time than a form, so reports compete less with the schedule. See [near-miss reporting](https://incidentkit.ai/use-cases/near-miss-reporting).
- **One record, not four:** The report, investigation, actions and work order reference sit together, so the shift meeting starts with the same facts.
- **Fixes that prove themselves:** An action closes only after evidence and an effectiveness check are verified, so a failed fix stays open. See [close corrective actions](https://incidentkit.ai/use-cases/close-corrective-actions).
- **Patterns across lines and sites:** Clusters by equipment, shift, location and cause show where the same event happens twice, even across plants.

## Frequently asked questions

### Is the plant pack available today?

Industry packs beyond healthcare are rolling out, and healthcare packs are available now. OSHA 300, 300A and 301 exports are also rolling out. [Contact us](https://incidentkit.ai/contact) to see what is ready for your site.

### Does IncidentKit replace our CMMS?

No. It runs alongside your CMMS, EHR and HRIS. You can record a work order number on an action today. Deeper CMMS integrations are rolling out; the platform offers signed webhooks and a read API.

### Does it support PSM incident investigations?

Yes. It gives an investigation the structure PSM asks for: a team, description, contributing factors, recommendations, documented resolutions and an audit trail. Whether process safety management covers your process depends on the chemicals and quantities, so check 29 CFR 1910.119. See [process safety incident investigation](https://incidentkit.ai/compliance/osha/process-safety-incident-investigation).

### Who certifies the OSHA 300A at a plant?

A company executive: an officer of the corporation, the highest-ranking company official at the establishment, or that official's immediate supervisor. At many plants that is the plant manager. Post the summary from February 1 through April 30. See [OSHA 300A](https://incidentkit.ai/compliance/osha/osha-300a-summary).

### How do contractor injuries work?

Whoever supervises the worker day to day records the injury: the contractor if it does, you if you do (29 CFR 1904.31). The same test applies to temporary and leased workers. Contractor and visitor incidents have their own form and routing. See [contractor and visitor incidents](https://incidentkit.ai/use-cases/contractor-and-visitor-incidents).

## Sources

- [29 CFR 1910.119(m), Incident investigation (eCFR)](https://www.ecfr.gov/current/title-29/part-1910/section-1910.119)
- [29 CFR 1910.147(c)(6), Periodic inspection (eCFR)](https://www.ecfr.gov/current/title-29/part-1910/section-1910.147)
- [29 CFR 1904.30, Multiple business establishments (eCFR)](https://www.ecfr.gov/current/title-29/part-1904/section-1904.30)
- [29 CFR 1904.31, Covered employees (eCFR)](https://www.ecfr.gov/current/title-29/part-1904/section-1904.31)
- [29 CFR 1904.32, Annual summary (eCFR)](https://www.ecfr.gov/current/title-29/part-1904/section-1904.32)
- [29 CFR 1904.39, Reporting fatalities, hospitalizations, amputations and loss of an eye (eCFR)](https://www.ecfr.gov/current/title-29/part-1904/section-1904.39)
- [BLS, How to compute your firm's incidence rate](https://www.bls.gov/iif/overview/compute-nonfatal-incidence-rates.htm)
- [CDC NIOSH, Hierarchy of controls](https://www.cdc.gov/niosh/hierarchy-of-controls/about/index.html)

## Related

- [Manufacturing incident reporting and OSHA 300 software](https://incidentkit.ai/solutions/manufacturing)
- [Near-Miss Reporting: How to Build a Program That Works](https://incidentkit.ai/use-cases/near-miss-reporting)
- [Root Cause Analysis: How to Run One That Leads to Action](https://incidentkit.ai/use-cases/root-cause-analysis)
- [Corrective Actions: How to Close Them With Proof](https://incidentkit.ai/use-cases/close-corrective-actions)
- [Contractor and Visitor Incidents: Who Reports What](https://incidentkit.ai/use-cases/contractor-and-visitor-incidents)
- [Mobile incident reporting that works offline](https://incidentkit.ai/product/mobile-and-offline)
- [Incident reporting API, webhooks and integrations](https://incidentkit.ai/product/integrations-and-api)
- [Hierarchy of controls: definition and meaning](https://incidentkit.ai/glossary/hierarchy-of-controls)
- [Lockout/tagout 29 CFR 1910.147: program and event data](https://incidentkit.ai/compliance/osha/lockout-tagout)
- [PSM incident investigation: 29 CFR 1910.119(m) explained](https://incidentkit.ai/compliance/osha/process-safety-incident-investigation)
- [OSHA recordkeeping requirements: 29 CFR 1904 explained](https://incidentkit.ai/compliance/osha/recordkeeping-overview)
- [OSHA severe injury reporting: 8-hour and 24-hour rules](https://incidentkit.ai/compliance/osha/severe-injury-reporting)
- [OSHA 300A summary: who signs, when to post, how long](https://incidentkit.ai/compliance/osha/osha-300a-summary)
- [TRIR and DART rates: formula, example and BLS 2024 rates](https://incidentkit.ai/compliance/osha/trir-and-dart-rates)