TRIR (Total Recordable Incident Rate) is the number of OSHA-recordable injuries and illnesses per 100 full-time workers per year. The formula: recordable cases multiplied by 200,000, divided by total hours worked. The 200,000 is 100 workers times 40 hours times 50 weeks, a normalizing constant, nothing more.

TRIR is the most-quoted safety number in industry: customers ask for it, insurers price on it, corporate dashboards rank plants by it. It's also routinely misread. This guide covers the math, a worked example, the DART variant, where to find honest benchmarks, and the three ways TRIR misleads, especially in smaller plants.

What is the TRIR formula?

TRIR = (number of recordable cases × 200,000) ÷ total hours worked by all employees. Both inputs come straight from your OSHA paperwork: the case count is your Form 300 log and the hours-worked figure is the same one that goes on your 300A summary. The formula is published by the Bureau of Labor Statistics (How to Compute Your Firm's Incidence Rate) and used the same way by OSHA.

Hours worked means actual hours, no vacation, sick leave, or holidays. Include temporary and part-time workers you supervise day to day: their cases go on your log, so their hours belong in your denominator.

The TRIR formula TRIR = cases per 100 full-time workers RECORDABLE CASES(from your Form 300) × 200,000(100 workers × 40 h × 50 wk) ÷ HOURS WORKED(all employees, actual) Worked example: 4 recordables × 200,000 ÷ 310,000 hours TRIR = 2.58
Both inputs come from your OSHA recordkeeping: the 300 log supplies the cases, the 300A hours field supplies the denominator.

How do you calculate TRIR? A worked example

Take a plant with about 150 employees across two shifts.

  1. Count recordable cases for the year. The Form 300 log shows 4: two lacerations requiring sutures, one shoulder strain with restricted duty, one hand fracture with days away. (First-aid-only cases never enter the count, the line is drawn in 29 CFR 1904.)
  2. Total the hours actually worked. Payroll shows 310,000 hours for the year, overtime included, leave excluded.
  3. Multiply cases by 200,000: 4 × 200,000 = 800,000.
  4. Divide by hours worked: 800,000 ÷ 310,000 = 2.58.
  5. Read it as a sentence: if 100 people worked full-time at this plant for a year, you'd expect about 2.6 recordable injuries at the current rate.

What is DART, and how is it different?

DART (Days Away, Restricted, or Transferred) uses the identical formula but counts only the subset of recordables severe enough to involve days away from work, restricted work, or a job transfer. In the example above, 2 of the 4 cases qualify (the strain and the fracture): DART = 2 × 200,000 ÷ 310,000 = 1.29. DART is always ≤ TRIR, and the gap between them says something: a TRIR full of DART cases means your injuries are serious, not just frequent. Insurers and customer prequalification forms typically ask for both.

What's a good TRIR? Benchmarks and context

"Good" only means anything against your own industry, because baseline hazard varies enormously. The primary sources:

A plant beating its NAICS average has a defensible claim. A plant comparing itself to "industry average 3.0" it saw on a poster does not.

What does TRIR hide?

Three things, and they compound.

It's a lagging indicator

TRIR counts injuries that already happened. It says nothing about the near miss last Tuesday, the bypassed interlock, or the lockout/tagout step everyone skips on Fridays. A plant can run a beautiful TRIR right up until the day it doesn't, the precursors were never measured. Leading indicators, near-miss reports filed, job safety analyses completed and revised, toolbox talks held, corrective actions closed on time, measure the work that prevents the injury, not the injury.

Lagging vs. leading indicators LAGGING, after the injury LEADING, before the injury • TRIR / DART • Lost workdays • Workers' comp cost • Citations received • Near misses reported + closed • JSAs current for active jobs • Toolbox talks held on schedule • Corrective actions closed on time • Guard / interlock checks passed Tells you the score of a game that already ended. Tells you what next quarter's TRIR will be.
TRIR belongs on the dashboard, next to the leading indicators that actually predict it.

Small numbers make it noisy

The formula divides by hours, and small plants don't have many. A 40-person plant works roughly 80,000 hours a year. Zero recordables: TRIR 0.0. One recordable, a single stitched finger, and TRIR jumps to 2.5, worse than the national all-industry average. Two, and it's 5.0, double the average. The difference between "best in class" and "twice the national rate" is literally one incident, which makes year-over-year TRIR moves at small sites mostly statistical noise. Trend it over rolling multi-year windows, or use case counts directly, before drawing conclusions.

One incident swings a small plant's TRIR 40-person plant (~80,000 hours/yr) 0 2.5 5.0 7.5 2024 national avg: 2.3 (BLS) 0 cases 1 case 2 cases 3 cases TRIR 0.0 TRIR 2.5 TRIR 5.0 TRIR 7.5 Each bar differs by exactly one incident. At this size, TRIR is a coin-flip metric year to year.
At 80,000 hours a year, every single recordable moves TRIR by 2.5 points, one stitched finger separates “world class” from “double the national average.”

It creates underreporting incentives

When bonuses, contract prequalification, or plant rankings hang on TRIR, the cheapest way to improve the number is to not record the case: pressure the clinic toward first-aid-only treatment, reclassify restricted duty as "light tasks we'd have assigned anyway," or make reporting feel career-limiting. The number improves; the plant doesn't. The tell is an implausibly quiet log next to an empty near-miss system real floors generate signals, and a plant reporting neither injuries nor near misses isn't safe, it's silent. If you want a number people can't easily game, watch the ratio of near misses reported to recordables.

How should a plant actually use TRIR?

Report it, benchmark it against your own NAICS code, and trend it over multi-year windows, it's the language customers and insurers speak, and you need it for prequalification either way. But manage the plant on the leading side: near-miss volume and closure, JSA currency, inspection findings fixed on time. Those live or die on capture friction, which is why plants digitize them first, a near miss that takes a paper form and two signatures doesn't get reported; one that takes thirty seconds on the tablet already at the station does. That's the connected worker case in one sentence, and it's how Harmony approaches floor data generally: capture at the point of work, count what predicts, not just what already happened (see how it works).