Safety & Workforce worked example

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

What does the result look like when reported near-miss events reaches 45 events? The full calculation is worked below with real intermediate numbers. Use it to track leading-indicator safety reporting in Safety & Workforce.

The inputs for this scenario

  • Reported near-miss events: 45 events (raised for this scenario; the documented default is 18)
  • Total employee hours worked: 500,000 hr (unchanged)

Working through the calculation

  • Applying the documented formula (Near-miss rate = near misses × 200,000 ÷ total hours worked) to the inputs above produces each figure below.
  • At this operating point the engine returns 18 per 100 workers for near-miss rate, the number this scenario is built around.
  • At this operating point the engine returns 45 events for near misses.
  • At this operating point the engine returns 500,000 hr for hours worked.
  • At this operating point the engine returns 250 FTE for full-time equivalents.

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 150% above the baseline at 18 per 100 workers.
  • A figure at this level is achievable when reported near-miss events is genuinely sustained, not just peaked for a shift. 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: 18 per 100 workers (headline result)
  • Near misses: 45 events
  • Hours worked: 500,000 hr
  • Full-time equivalents: 250 FTE

Run it with your numbers

  • Every input above is editable in the live Near Miss Rate calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.