TRIR vs LTIFR vs DART: which metric should the executive review use?

Executive reviews break when one lagging rate is asked to prove too much. TRIR answers how often recordable cases entered the log. LTIFR answers how often lost time interrupted work. DART answers whether a case displaced normal work long enough to matter operationally. None of them, by itself, tells a leader whether fatal exposure is rising or whether a critical control is healthy.

Across more than 250 cultural transformation projects, Andreza Araujo has seen the same pattern repeat. The dashboard looks tidy while the field still carries the same risk. The meeting rewards the easiest number to read, although the work demands a different question. In Luck or Capability, Andreza's point is direct: good numbers can reflect luck or underreporting, not proof of capability.

During Andreza Araujo's PepsiCo South America tenure, the accident ratio fell 50% in 6 months. That change did not come from polishing a single metric. It came from changing how leaders saw work, verified controls, and reacted to bad news. That is why the right comparison is not which metric is best in the abstract. It is which metric answers the decision in front of the executive.

Key Takeaways

• Use TRIR to test recordkeeping discipline and trend integrity, not to prove that serious risk is controlled.
• Use LTIFR when leaders need to understand how much time lost after injury is changing operations.
• Use DART when restriction, transfer, or absence patterns show how injury is disrupting normal work.
• Pair every lagging metric with field proof, because lagging rates always arrive after the exposure they describe.
• Ask which decision each number should change before it reaches the executive review pack.

Why one lagging metric is not enough

TRIR, LTIFR, and DART all answer after harm has already happened, which makes them useful but incomplete. OSHA recordkeeping rules describe what happened in the event log, while BLS fatal occupational injury tables describe the harm after the fact. Neither source was designed to tell leaders whether the next high-energy task is safer than the last one.

James Reason's work is useful here because it reminds leaders that outcomes are late clues, not the system itself. A low rate can mean control, but it can also mean silence, weak classification, or a denominator that no longer matches the work. That is why Andreza Araujo's The Illusion of Compliance keeps mattering in metric reviews. A clean file can still hide a weak field.

The practical test is simple. If the metric cannot help a leader decide whether to spend, stop, verify, or escalate, it is only part of the answer. The board may still need it, but the board should not confuse it with control health.

What TRIR tells the executive review

TRIR is best understood as a recordkeeping integrity measure. It tells leaders how many recordable cases are entering the system and whether the organization is applying the same rules at the same standard across sites, crews, and shifts. That makes it useful for comparison, especially when management wants a common language across a portfolio.

TRIR becomes dangerous when leaders read it as a seriousness measure. A site can keep TRIR low while high-energy exposures stay open, because the metric flattens different injury types into one number. It can also drift when leaders pressure the edge of classification, ask for better-looking numbers, or celebrate fewer reports without checking whether the reporting climate changed.

Andreza Araujo's rule of thumb is blunt: good numbers do not prove capability if the route to the number is weak. That is why TRIR should sit beside a question about whether the site can prove its controls, not beside a trophy. If TRIR is the only number that looks good, the review may be more polished than truthful.

What LTIFR tells the executive review

LTIFR is a better lens for work disruption. It shows how much time is lost after injury and how injury is affecting operational continuity, staffing pressure, and return-to-work patterns. For plant managers and HR leaders, that information can be useful because the impact of one case may spread into overtime, backfill, contractor use, or reduced crew stability.

The blind spot is that time lost is not the same thing as exposure severity. Different return-to-work practices, medical restrictions, and local case handling can change the number without changing the underlying risk. A site can manage a return well and appear to worsen the rate, or manage a return badly and appear to improve it. The number alone does not tell you which is happening.

That is why LTIFR should be read with the work design question attached. What changed in the task, the role, or the supervision pattern before the injury? If leaders only ask how long the person was away, they miss the more valuable question, which is why the event was able to interrupt work in the first place.

What DART tells the executive review

DART is most useful when leaders need to see whether injury is creating disability, restriction, or transfer, because that makes the operational burden visible in a way that TRIR does not. It is often more practical than a simple count of recordables when the organization wants to understand how much normal work had to be reshaped after the case.

Even so, DART still lives after harm. It blends three different outcomes into one category, and each of those outcomes can be influenced by medical management, job redesign, and case handling discipline. That makes it a strong operational lens, but not a direct measure of exposure quality.

For leaders, the value of DART is that it exposes friction. A stable plant with a rising DART rate is telling you that injury is no longer just a report entry. It is changing labor, supervision, and job continuity. The mistake is to stop there and assume the number alone explains the control problem.

Comparison matrix

The table below keeps the decision clear. Each metric can help, but each one answers a different question, and each one fails in a different way when the organization gives it too much authority.

Which metric belongs in which meeting

If the meeting is about recordkeeping, TRIR belongs there. If the meeting is about work disruption, LTIFR or DART will usually tell the story more clearly. If the meeting is about fatal-risk governance, none of the three is enough on its own, because none of them tells leaders whether a critical control is healthy today.

That is why a serious executive pack should pair a lagging metric with a control question. The current Headline article on control health versus TRIR and SIF exposure is the right companion here, because it asks the next question the lagging metric cannot answer.

A plant manager can use the trio well if the pack is separated by decision. TRIR is for integrity. LTIFR is for operational burden. DART is for case impact. When the review collapses those three decisions into one score, the organization gets a cleaner slide and a worse conversation.

What each metric hides

TRIR hides how much severity sits behind a single case. A site can improve the number by changing what gets counted, by reducing minor cases only, or by pushing the reporting climate toward silence. LTIFR hides the way return-to-work design can move the number without moving the exposure. DART hides the fact that restriction and transfer can be driven by administrative practice as much as by injury reality.

The common trap is to treat a lagging metric as if it were a control metric. That mistake gives leaders a false sense of precision. It also creates a bad habit in the field, because supervisors learn that the meeting cares more about the color of the chart than the quality of the controls.

Across 250+ projects, Andreza Araujo has seen that behavior change only when leaders ask for proof that the work changed. Numbers matter, but only when they point back to the field. That is the dividing line between a dashboard and a decision tool.

What to put in the review pack

A better executive pack is small and specific. Start with one line for TRIR, one line for LTIFR or DART, and one line for control proof in the highest-risk task. Then add a short note on what changed in the field, who owns the next decision, and what evidence would make the team reopen the issue.

That structure keeps the meeting honest. It stops the group from celebrating a low number before asking whether the route to that number is credible. It also helps the executive team separate metric hygiene from risk governance, which is where many programs quietly blur the line.

The lesson from Andreza Araujo's PepsiCo South America experience is not that one number solved safety. It is that leadership changed when the organization stopped treating the metric as the answer and started treating it as a prompt for field action.

FAQ

Is TRIR useless for executives? No. TRIR is useful for recordkeeping integrity and cross-site comparison, but it should never be mistaken for proof that serious risk is under control.

Should LTIFR replace TRIR? No. LTIFR answers a different question about lost time and work disruption, so it is a complement rather than a replacement.

Why does DART matter? DART shows how injury changes normal work through restriction, transfer, or time away, which makes the operational cost visible.

What should leaders pair with these metrics? They should pair them with control evidence, field verification, and a direct question about the highest-risk tasks.

What is the first step if the pack is too focused on rates? Keep one lagging rate for integrity, then add a control-health or field-proof line for the top fatal-risk exposure.

The safest next step is to stop asking one lagging metric to do the work of three. Use TRIR, LTIFR, and DART for the questions they can answer, then add the control proof the board actually needs. That is the difference between a tidy review and a decision that changes the work.

Follow Headline Podcast for more safety leadership and metrics conversations.