Safety & Workforce worked example

Near Miss Rate with reported near-miss events of 9 events: a worked example

Here is what the math looks like when conditions slip. We hold every other input steady and drop reported near-miss events to 9 events, then walk the calculation through step by step. Calculate the near-miss reporting rate for Safety & Workforce on the OSHA 200,000-hour basis.

The inputs for this scenario

  • Reported near-miss events: 9 events (the input this scenario stresses; the baseline uses 18)
  • Total employee hours worked: 500,000 hr (held at the documented default)

Working through the calculation

  • The calculation starts from the formula this tool documents: Near-miss rate = near misses × 200,000 ÷ total hours worked.
  • Near-miss rate works out to 3.6 per 100 workers at these inputs, and this is the headline figure for the scenario.
  • Near misses works out to 9 events at these inputs.
  • Hours worked works out to 500,000 hr at these inputs.
  • Full-time equivalents works out to 250 FTE at these inputs.

How this compares with the baseline

  • Against the tool's baseline example, where reported near-miss events sits at 18 events and the headline result is 7.2 per 100 workers, this scenario comes in 50% below the baseline at 3.6 per 100 workers.
  • The practical read: the gap between this scenario and the baseline is entirely attributable to reported near-miss events, so recovering it is worth quantifying in dollars before considering equipment or staffing changes. A low rate can mean either a genuinely safe operation or a broken reporting culture where people don't bother logging close calls — read it with context, not in isolation.

Results at a glance

  • Near-miss rate: 3.6 per 100 workers (headline result)
  • Near misses: 9 events
  • Hours worked: 500,000 hr
  • Full-time equivalents: 250 FTE

Run it with your numbers

  • To rerun this with your own numbers, open the live Near Miss Rate calculator, set reported near-miss events to your actual value, and adjust the remaining inputs to match your operation.

Last reviewed 2026-05-12.