LTIFR (Lost Time Injury Frequency Rate): Meaning, Formula, Examples, and How to Improve It

TL;DR

• 🔧 LTIFR (Lost Time Injury Frequency Rate) measures how many lost-time injuries occur per 1,000,000 hours worked.
• 📉 It’s a lagging safety indicator that helps operations leaders track time-lost incidents, benchmark against peers, and identify improvement opportunities.
• ⚙️ This guide covers the LTIFR formula, step-by-step calculation, worked examples, common mistakes, and practical steps to reduce your rate through better data capture, corrective action workflows, and leading indicators.
• 🔢 LTIFR counts injuries resulting in at least one full shift lost, normalized to 1,000,000 hours worked
• 📊 Formula: (Number of LTIs × 1,000,000) / Total Hours Worked
• ⚠️ It’s a lagging indicator: pair with near-miss reporting, hazard closure time, and control verification for complete risk visibility
• 🏭 Industry benchmarks vary widely: offshore energy <0.5, high-volume service 3.0-6.0 per million hours
• ✅ Reduce LTIFR by closing the hazard-to-control loop faster, improving incident classification consistency, and targeting top injury causes
• 🚀 Real-time safety data and automated KPI dashboards eliminate manual errors and enable faster intervention

Every LTIFR calculation depends on the incident data your team actually logs. Roughly 60% of operational events never reach a system of record, including near-misses called in over radio, first-aid cases handled on the shop floor, and equipment incidents reported via WhatsApp. This guide covers the formula, benchmarks, and pitfalls, and points to where the data behind your safety KPI is falling through the cracks.

What is LTIFR?

LTIFR stands for Lost Time Injury Frequency Rate. It measures the number of injuries that result in at least one full shift or workday lost, normalized to a standard exposure base: typically 1,000,000 hours worked.

The metric is standard across high-risk industries, including mining, ports, construction, rail, and logistics, where it tracks safety performance and enables benchmarking across sites and peer companies.

LTIFR is reported monthly, quarterly, or annually depending on organizational size and risk profile. Smaller teams with fewer exposure hours often use rolling 12-month windows to smooth volatility.

Lost time injury (LTI) definition: what counts and what doesn’t

A lost time injury (LTI) is an occupational injury that prevents the worker from performing their normal duties for at least one complete shift or workday following the incident.

Common inclusion rules:

• The worker was unable to return to full duties for at least one full shift after the day of injury.
• Medical treatment beyond first aid was required.
• The injury is work-related and occurred during working hours or on company premises.

Common exclusion scenarios:

• First-aid-only injuries with no time lost.
• Restricted work or light duty (worker returns same or next shift but performs modified tasks).
• Commuting incidents (unless they occur on company transport or premises).

Fatalities and permanent disabilities are often counted as LTIs, but some companies track them separately to avoid diluting trend analysis. There is no universal standard, so your organization must document its classification rules clearly.

What LTIFR measures and what it misses

LTIFR is a lagging indicator: it counts outcomes after they happen. It tells you how many injuries resulted in time off, but it does not:

• Predict future incidents (leading indicators like near-miss reporting rate or hazard closure time do that).
• Capture the severity or long-term impact of each injury.
• Reflect restricted-duty or medical-treatment-only cases that did not result in full time loss.

LTIFR is valuable for trend tracking and external benchmarking, but it should never be the only safety metric you monitor. Pair it with severity measures, recordable injury rates, and leading indicators for a complete view of risk.

LTIFR formula and why the multiplier matters

Standard LTIFR formula per 1,000,000 hours

The most common LTIFR formula is:

LTIFR = (Number of Lost Time Injuries × 1,000,000) / Total Hours Worked

The 1,000,000-hour multiplier normalizes the rate to a standard exposure base, making it easier to compare performance across different-sized workforces and time periods.

Why some organizations use 200,000 hours instead

OSHA uses 200,000 hours as the base for incidence rate calculations. According to OSHA, 200,000 represents the hours 100 employees working 40 hours per week for 50 weeks per year would work.

When you see a published LTIFR, always check the multiplier. A rate of 1.0 per 200,000 hours equals 5.0 per 1,000,000 hours (multiply by 5). Conversely, divide by 5 to convert a 1,000,000-hour rate to a 200,000-hour base.

For example, Securitas reports an LTIFR of 1.1 per 200,000 hours and 5.7 per 1,000,000 hours for the same dataset, demonstrating the conversion in practice.

How to avoid apples-to-oranges comparisons

To ensure comparability, every LTIFR report should include a reporting note that specifies:

• LTI definition: What qualifies as “lost time” (one full shift? 24 hours? specific medical threshold?).
• Multiplier used: 200,000 or 1,000,000 hours.
• Hours included: Employees only, or employees + contractors? Does it include overtime, on-call, and training hours?
• Fatalities and permanent disabilities: Included in LTI count, or tracked separately?

Without this context, cross-company and cross-site benchmarking is meaningless. When standardizing KPI calculations across multiple terminals or regions, enforce a single taxonomy and calculation logic to eliminate definition drift.

How to calculate LTIFR step-by-step

Step 1. Count LTIs consistently

The biggest operational failure mode in LTIFR reporting is inconsistent classification. Injuries get miscoded, borderline cases are handled differently by different supervisors, and late incident closures skew monthly reporting.

Best practice checklist:

• Use a single incident taxonomy with clear examples for each category (first aid, medical treatment, restricted work, lost time).
• Require supervisor and safety manager sign-off before closing an incident as LTI or non-LTI.
• Audit a random sample of closed incidents quarterly to verify correct classification.
• Track “pending classification” incidents separately so open cases don’t disappear from dashboards.

If you’re connecting HR and timekeeping systems to safety reporting, automate the flag when an employee logs zero productive hours the day after an incident: it’s a strong signal for LTI review.

Step 2. Calculate total hours worked accurately

The denominator (total hours worked) is where most LTIFR errors hide. Common undercounting issues include:

• Missing contractor hours: Many sites track employee hours via payroll but forget subcontractor exposure.
• Excluding overtime and shift swaps: If someone worked the hours, they count toward exposure.
• Including leave and non-working time: Paid time off, training off-site, and administrative leave should be excluded unless the worker was on company premises.

Hours worked checklist:

• Ordinary hours + overtime + on-call (if on-site or traveling for work).
• Employees and contractors working under your operational control.
• Exclude: vacation, sick leave, parental leave, off-site training (unless injury risk is present).
• Document your method and apply it consistently every reporting period.

Real-time status capture in the field helps ensure exposure hours are logged as shifts happen, reducing reliance on retrospective payroll corrections.

Step 3. Apply the formula and round/report correctly

Once you have clean inputs:

1. Multiply the number of LTIs by your chosen multiplier (1,000,000 or 200,000).
2. Divide by total hours worked.
3. Round to one or two decimal places (industry convention is typically one decimal for rates above 1.0, two decimals for rates below 1.0).

Recommendation: Report LTIFR with a rolling 12-month trend alongside the current-period snapshot. Rolling windows reduce month-to-month noise, especially for smaller sites where a single incident can swing the rate dramatically.

LTIFR calculation examples: worked examples you can copy

Example 1. Annual LTIFR per 1,000,000 hours

A logistics terminal records:

• Lost time injuries: 6
• Total hours worked: 2,400,000 (employees + contractors, ordinary + overtime, excluding leave)

LTIFR = (6 × 1,000,000) / 2,400,000 = 2.5

Interpretation: For every 1 million hours worked, this terminal averaged 2.5 lost-time injuries during the year. If the industry benchmark is 3.0, the terminal is performing better than average; if the benchmark is 1.5, there is room for improvement.

Example 2. Converting between 200,000-hour and 1,000,000-hour bases

You read a competitor report showing an LTIFR of 1.2 per 200,000 hours. To compare it to your 1,000,000-hour rate:

LTIFR (per 1,000,000) = 1.2 × 5 = 6.0

Conversely, if your rate is 3.0 per 1,000,000 hours and you want to express it on a 200,000-hour base:

LTIFR (per 200,000) = 3.0 / 5 = 0.6

Always verify that the LTI definition matches before converting: if one company includes restricted work and the other does not, the rates are not comparable even after base conversion.

Example 3. Rolling 12-month LTIFR for small teams/sites

A rail yard employs 80 workers and logged:

• LTIs in past 12 months: 2
• Hours worked (12 months): 160,000

LTIFR = (2 × 1,000,000) / 160,000 = 12.5

This rate is high, but the sample size is small: two incidents. If one of those injuries had been prevented, the rate would drop to 6.25. For small sites, use multi-year rolling windows (24 or 36 months) to get statistically meaningful comparisons, and always report absolute counts alongside the rate.

LTIFR vs TRIR/TRIFR/DART/IFR: which KPI should you use?

LTIFR vs TRIR: recordables vs lost time only

TRIR (Total Recordable Incident Rate) includes all OSHA-recordable injuries: lost time, restricted work, medical treatment, and certain first-aid cases. LTIFR counts only injuries that resulted in at least one full shift lost.

LTIFR is narrower. It can be “gamed” by offering light duty or restricted work to avoid lost time, which makes the rate look better even though the injury occurred. TRIR provides broader coverage and is harder to manipulate.

If your goal is benchmarking with U.S. peers or reporting to regulators, use TRIR. If you operate in regions where LTIFR is the industry standard (common in offshore energy, mining, and international operations), report both and explain the difference.

LTIFR vs TRIFR: including restricted work?

TRIFR (Total Recordable Injury Frequency Rate) is similar to TRIR but uses the 1,000,000-hour base common outside the U.S. Some organizations define TRIFR to include restricted-work cases, others use it interchangeably with LTIFR.

Always check the published definition before comparing. If a peer company’s “TRIFR” includes restricted duty and yours does not, their rate will be higher even if actual safety performance is similar.

Leading indicators to pair with LTIFR

LTIFR alone is a lagging outcome. To drive improvement, complement it with a KPI stack that includes:

• Near-miss reporting rate: Incidents per 1,000 or 10,000 hours worked; higher is often better (shows active hazard identification).
• Corrective action closure rate: Percentage of actions closed on time; tracks whether you close the loop after incidents or audits.
• Critical control verification: Percentage of planned control checks completed (e.g., pre-start inspections, permit audits, lockout/tagout compliance).
• Average time to close incidents: Days from report to investigation closure; faster closure improves data quality and learning velocity.
• Hazard observation frequency: Number of hazards reported per worker per month; reflects frontline engagement.

OSHA recommends using multiple variables including both leading and lagging indicators.

For high-risk physical operations like mining, ports, rail, and logistics, combine LTIFR with severity (days lost per LTI), equipment-specific incident rates, and shift-level safety observations to get a complete picture.

How to benchmark LTIFR and what a ‘good’ LTIFR looks like

Use industry bodies and peer groups: same definition + same base

Credible LTIFR benchmarks come from industry associations that enforce consistent reporting definitions. When comparing your rate to published benchmarks:

• Verify the multiplier (200,000 or 1,000,000 hours).
• Confirm the LTI definition matches yours (especially treatment of restricted work and fatalities).
• Check whether contractor hours are included.
• Note the time period (calendar year, rolling 12 months, or multi-year average).

Never benchmark against a generic “industry average” without knowing how it was calculated.

Examples of published LTIFR values with citation

IMCA (International Marine Contractors Association) reports the following 2024 safety statistics:

• Total 2024 LTIFR: 0.3 (per 1,000,000 hours)
• Offshore 2024 LTIFR: 0.35
• Contributing companies: 198
• Total man-hours: 1,015,506,567
• Top LTI cause: Line of fire / caught between / struck against

Securitas published 2024 social sustainability data showing:

• Total hours worked: 648,222,198
• Lost-time injuries: 3,669
• LTIFR: 1.1 per 200,000 hours; 5.7 per 1,000,000 hours

These examples illustrate the wide range of LTIFR values across industries. Offshore energy (IMCA) operates with extensive safety controls and reports rates well below 1.0, while high-volume service industries with dispersed workforces report higher rates.

Benchmarking pitfalls: definitions, exposure hours, contractor mix

Even within the same industry, cross-company benchmarking is difficult because:

• Definitions vary: One company’s “lost time” is another’s “restricted work.”
• Contractor mix differs: A site where contractors make up the majority of hours may under-report if contractor hours are excluded.
• Exposure intensity varies: High-overtime periods, seasonal peaks, and night shifts carry different risk profiles.
• Reporting culture: Some organizations encourage reporting every near-miss and minor injury; others discourage it (“safety bonus” programs tied to zero incidents).

Use benchmarks as a directional guide, not absolute truth. Focus more on your own trend over time and year-over-year improvement than on beating a peer’s published number.

For port terminal safety benchmarks, compare against terminals with similar equipment, throughput, and labor mix: a container terminal and a bulk terminal have very different risk profiles.

Common LTIFR mistakes and how to fix them

Misclassifying LTIs and inconsistent medical thresholds

The most common error is inconsistent application of the LTI definition. One supervisor codes a knee strain as “restricted work” (not an LTI) because the worker returned on light duty the next day. Another supervisor codes an identical injury as LTI because the worker took one full day off before returning to light duty.

Fix: Implement a single taxonomy with written examples, and require dual sign-off (supervisor + safety manager) before closing any recordable incident. Use AI-driven data capture to flag classification inconsistencies by scanning incident narratives for keywords like “off work,” “lost shift,” or “modified duty.”

Run quarterly audits on a random sample of closed incidents to verify correct coding.

Under-counting exposure hours: contractors, overtime, shift swaps

Many organizations pull hours worked from payroll and miss:

• Contractors (especially short-term or project-based).
• Overtime and shift-swap hours not reflected in standard schedules.
• Workers on loan from other sites or business units.

Fix: Establish a single source of truth for hours worked. If you use multiple systems (payroll for employees, vendor invoices for contractors, field logs for casual labor), reconcile them monthly. Integrate HR and timekeeping data into your KPI reporting platform to automate the rollup and flag missing sources.

Document which hours are included and excluded, and apply the same rule every period.

Over-focusing on one lagging KPI

LTIFR measures outcomes after they happen. If it’s your only metric, you’re flying blind on risk. A site with zero LTIs this quarter might have dozens of unreported near-misses, overdue maintenance, or ignored hazard observations.

Fix: Build a balanced KPI stack with leading and lagging indicators. Track near-miss reporting rate, corrective action closure time, control verification completion, and hazard observation frequency alongside LTIFR. Investigate any site where LTIFR is low but leading indicators are also low: it’s a red flag for under-reporting culture.

How to reduce LTIFR in physical operations: practical playbook

Improve hazard identification and close the loop faster

Most lost-time injuries are preventable if the hazard was identified and controlled earlier. The data exists. The gap is between identifying a risk and getting it fixed.

Execution steps:

• Set response SLAs for hazard categories: critical hazards must be controlled or isolated within 24 hours; high-priority within 7 days; medium within 30 days.
• Trigger formal investigations at defined thresholds (e.g., any LTI, any high-potential near-miss, or three similar incidents in 90 days).
• Link investigation findings to corrective actions with named owners and due dates. Track closure rate as a KPI.
• Use incident-to-corrective-action workflows to enforce accountability and escalate overdue actions automatically.

The faster you close the loop from hazard to control, the fewer LTIs you’ll record.

Make safety data real-time, not end-of-month

Waiting until month-end to review LTIFR means you’re always reacting to last month’s injuries. Real-time dashboards let you intervene when patterns emerge: three slips in the same yard zone, two hand injuries on the same piece of equipment, or rising near-miss counts during night shifts.

Execution steps:

• Deploy real-time operational visibility tools that surface incidents, near-misses, and exposure hours daily.
• Set up alerts when LTIFR crosses a threshold (e.g., rolling 30-day rate exceeds site target).
• Hold weekly safety stand-downs with shift leads to review the past week’s incidents and corrective action status.
• Make safety data visible on the same dashboard as throughput, equipment uptime, and labor hours so operational trade-offs are transparent.

When safety and performance data live together, safety stops being an afterthought.

Target the top causes with focused controls

Generic safety programs (“be careful, wear PPE”) don’t move the LTIFR needle. Prioritize the hazards that are actually causing injuries at your site.

Execution steps:

• Analyze LTIs by cause theme (struck by, caught between, slip/trip/fall, line of fire, ergonomic strain, etc.). IMCA data shows “line of fire / caught between / struck against” as the top cause in offshore operations; adapt the analysis to your own incident log.
• For each top-3 cause, identify the critical control (e.g., lockout/tagout for caught-between, barricades and exclusion zones for line of fire, surface treatment and lighting for slips).
• Verify control effectiveness in the field weekly: walk the site, observe work, check that controls are in place and being used.
• Use AI for maintenance safety to scan technician notes and flag recurring equipment or task risks before they result in an LTI.

Pre-start risk checks, near-miss capture workflows, and control verification routines are the operational habits that prevent injuries: LTIFR is just the scorecard.

LTIFR reporting template: what to include in a dashboard

Minimum fields for incident and exposure data

An effective LTIFR dashboard includes:

Numerator (incidents):

• Lost time injuries (count)
• Fatalities (count, reported separately)
• Permanent disabilities (count, reported separately)
• LTI severity proxy (total days lost, or average days lost per LTI)

Denominator (exposure):

• Total hours worked (employees)
• Total hours worked (contractors)
• Total hours worked (combined)

Calculated metrics:

• LTIFR (current period)
• LTIFR (rolling 12 months)
• Period-over-period change (percentage and absolute)

Supporting context:

• Top 3 incident causes (by count)
• Top 3 incident locations (terminal, yard, shift)
• Corrective action closure rate (percentage)
• Open incidents > 30 days (count)

Recommended visuals: trend, rolling 12 months, by site/shift/task

Use these chart types:

• Line chart: Monthly LTIFR (current period) and rolling 12-month LTIFR on the same axis to show trend smoothing.
• Column chart: LTI count by site, shift, or equipment type to identify hotspots.
• Stacked area or bar: Hours worked by source (employees vs contractors) to verify denominator completeness.
• Table: Top causes with counts, percentage of total, and year-over-year comparison.

Slice LTIFR by operational unit (terminal, yard, shift, task type) to find high-risk pockets that get averaged out in company-wide totals.

Executive summary format

For leadership reporting, use a one-page summary:

• Headline number: LTIFR (rolling 12 months) with trend arrow (up/down/flat) and percentage change vs prior year.
• Context: Total LTIs, total hours, and multiplier used.
• Top 3 causes with corrective action status.
• Data quality indicator: Percentage of sites with complete hours data; number of open incidents older than 30 days.
• Action summary: What’s being done to address the top causes; due dates and owners.

Include a reporting note at the bottom that states: LTI definition, multiplier (200k or 1M hours), hours included (employees + contractors, ordinary + OT, excluding leave), and whether fatalities are included.

Automated KPI dashboards eliminate manual spreadsheet errors and keep definitions consistent across sites, ensuring every executive summary is based on the same calculation logic.

Conclusion

LTIFR is a powerful lagging indicator for tracking lost-time injuries, but it’s only as good as the data and definitions behind it. Calculate it correctly by counting LTIs consistently, capturing total hours worked accurately, and using the right multiplier (200,000 or 1,000,000). Always disclose your LTI definition and base when publishing or benchmarking LTIFR.

To reduce LTIFR in physical operations, pair it with leading indicators, close the loop from hazard to control faster, and target the specific causes driving injuries at your sites. Real-time safety data, structured workflows, and credible benchmarks turn LTIFR from a compliance checkbox into a tool for operational improvement.

Opsima is the AI-native software factory for industrial operations, built to fix the root problem: off-system safety events that skip the record, leaving your LTIFR count lower than what actually happened on the floor.

Ready to close the safety data gap in your LTIFR? Opsima overlays on your existing EHS, CMMS, or EAM stack, or builds the replacement from scratch. Working software in weeks; you pay when you see the value. Book a working session.