BLS reports 2.5 million private-industry injury and illness cases for 2024
The January 2026 release shows a lower total-recordable rate, but the change is driven partly by illness trends and cannot serve as a universal safety-performance benchmark.
Editorial figure by Safety Operations Standard. Source context: U.S. Bureau of Labor Statistics.
The headline rate does not explain one company's performance
The Survey of Occupational Injuries and Illnesses is a national statistical program with defined populations and methods. A company metric can differ in establishment mix, geography, contractor inclusion, exposure hours, recordkeeping practice, and case definitions. Those differences must be visible before comparison.
The drop in illness cases also matters. A lower combined recordable rate is not automatically evidence that every injury hazard improved. Analysts should separate injuries from illnesses and examine detailed industry and case-type tables rather than treating the total as a single causal signal.
What an EHS analytics product should preserve
A credible benchmark view should retain the BLS series, year, industry classification, rate definition, denominator, statistical error where provided, and the customer's own inclusion logic. It should prevent a user from comparing unlike measures without a warning.
Buyers should ask whether definitions are versioned, historical calculations are reproducible, acquisitions and workforce changes are handled, and narrative interpretation can be separated from the underlying data.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Safety Operations Standard will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.