Safety & Workforce worked example

OSHA 300 Log Rate with recordable cases on the osha 300 log of 3 cases: a worked example

Suppose recordable cases on the osha 300 log falls to 3 cases. This page works the full calculation at that level so you can see exactly which result moves and by how much. Calculate OSHA 300 log rate for Safety & Workforce from logged cases and total hours worked, using the OSHA 200,000-hour basis.

The inputs for this scenario

  • Recordable cases on the OSHA 300 log: 3 cases (the input this scenario stresses; the baseline uses 6)
  • 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: OSHA 300 log rate = logged cases × 200,000 ÷ total hours worked.
  • OSHA 300 rate works out to 1.2 per 100 workers at these inputs, and this is the headline figure for the scenario.
  • Cases works out to 3 cases 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 recordable cases on the osha 300 log sits at 6 cases and the headline result is 2.4 per 100 workers, this scenario comes in 50% below the baseline at 1.2 per 100 workers.
  • It computes the OSHA incident rate as recordable cases multiplied by 200,000 and divided by total employee hours worked, expressed per 100 full-time-equivalent workers. When the numbers land here, the stressed input is the lever to work; the walkthrough above shows exactly how much each output recovers as it climbs back toward the baseline.

Results at a glance

  • OSHA 300 rate: 1.2 per 100 workers (headline result)
  • Cases: 3 cases
  • 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 OSHA 300 Log Rate calculator, set recordable cases on the osha 300 log to your actual value, and adjust the remaining inputs to match your operation.

Last reviewed 2026-05-12.