TRIR, LTIFR and the Denominator That Trips Everyone Up

Three recordable incidents in six months. The operations director circled them in red on the board report. What nobody had written down was that the site was running 600 people across four shifts, racking up nearly a million hours of exposure. Context lives in the denominator.

TRIR and LTIFR both exist to provide that context. They normalise your incident count against hours worked so you can compare a 50-person site with a 500-person one, or your own performance against an industry figure. The trouble starts when people use the wrong denominator and then compare the result to a benchmark built on a different one.

Why the Base Figure Matters

Two standards are in common use, and they are not interchangeable.

• OSHA (US standard): 200,000 hours. That represents 100 employees working 40 hours a week for 50 weeks.
• UK/EU (HSE standard): 1,000,000 hours. Five times larger.

Run the same incident count through both bases and you get two numbers that look completely different. A UK manufacturer with an LTIFR of 2.3 sounds very different from a US site quoting 0.46, yet they may be reporting exactly the same underlying performance. Always note which standard you are using, and check which one any benchmark you are comparing against was built on.

How to Calculate TRIR

TRIR (Total Recordable Incident Rate) captures every recordable incident: fatalities, lost-time injuries, restricted-duty cases, and treatments that go beyond basic first aid.

Formula (OSHA, 200,000-hour base):

TRIR = (Recordable incidents × 200,000) ÷ Hours worked

Worked example:

A site employs 450 people. Over the year, each person averaged 1,920 hours (48 weeks at 40 hours). Total hours worked: 864,000.

Six recordable incidents occurred.

TRIR = (6 × 200,000) ÷ 864,000 = 1.39

To express that on the UK/EU 1M-hour basis, multiply by five: 6.94 per million hours. That is broadly in line with the HSE’s published manufacturing average, which sits between 5 and 8 depending on sub-sector.

How to Calculate LTIFR

LTIFR (Lost Time Injury Frequency Rate) counts only incidents where the person lost at least one scheduled working day.

Formula (UK/EU, 1,000,000-hour base):

LTIFR = (Lost time injuries × 1,000,000) ÷ Hours worked

Worked example (same site):

Two of those six incidents resulted in lost time.

LTIFR = (2 × 1,000,000) ÷ 864,000 = 2.31

Using the OSHA 200,000-hour base instead: (2 × 200,000) ÷ 864,000 = 0.46. Same site, same incidents, very different-looking number. Neither calculation is wrong, but they only mean something once you know which standard was applied.

What Good Looks Like

There is no single threshold that defines a safe site, but some reference points help with orientation.

• UK manufacturing LTIFR (1M-hour base): typically 3 to 5, varying by sub-sector.
• World-class manufacturers often achieve LTIFR below 1.0.
• TRIR (OSHA 200k base) below 1.0 is considered strong in most manufacturing sectors; below 0.5 is exceptional.

Treat very low rates at small sites with caution. One incident at a 30-person facility can shift the LTIFR by eight or ten points. The rate is only statistically meaningful once you have accumulated something close to 500,000 hours. If your site is smaller than that, report the raw counts alongside the rate.

Common Mistakes

Mixing the bases. Someone looks up an HSE benchmark (1M hours) and puts their OSHA calculation (200k hours) next to it. The result looks five times better than the industry average. It is not.

Excluding contractor hours. If contractors are working on your site, their hours and their incidents belong in your figures. Leaving them out makes the rate look cleaner than it is and conceals real exposure.

Misclassifying incidents. A first-aid case becomes recordable the moment it involves prescription medication, stitches, or restricted duties. Under-recording flatters the KPI and creates problems during audits.

Counting calendar days instead of working days. A Friday injury that keeps someone off until Tuesday is two lost days, not four. Count scheduled shifts, not the calendar.

Not annualising partial-year data. A rate based on three months of data is volatile and misleading in isolation. Either annualise it (multiply by four) or label it clearly as a partial figure in any report.

Keeping the Numbers Clean

The calculations are not complicated, but maintaining them across a live site is. Cells get overwritten, formulas break, and the number in the board report stops matching the source data somewhere around the third quarterly update.

SafetyDeskStudio’s offline HSE KPI Dashboard, available on Etsy at etsy.com/listing/4552096963, handles LTIFR and TRIR automatically. It runs in Excel with no cloud connection required, is built to UK reporting standards, and produces output the HSE would recognise. If you are spending more time maintaining your tracking tool than acting on what it shows, it is a practical shortcut.

Rates Are Lag Indicators

A low LTIFR is a good sign, not a guarantee. These figures tell you what has already happened. A site with no lost-time injuries in 18 months can still be accumulating the conditions for a serious event.

If you want to understand where losses are building before they show up in an incident log, the losses analysis tool is a useful starting point. And if the wider operational picture needs attention, the 5S self-assessment will surface where the gaps actually are.