A precise, no-fluff tool to calculate total recordable incident rate (TRIR) per 100 full-time employees. Instantly quantify safety performance so you can compare sites, track trends, and report OSHA metrics without manual math.
Introduction
The calculator uses recordable incidents and total hours worked to compute TRIR. It applies the standard 200,000-hour normalization (equivalent to 100 FTE working 40 hours/week for 50 weeks). Built for EHS teams, plant managers, and operations leaders who need clean, defensible safety KPIs.
How to Use the TRIR Calculator
A step-by-step guide to compute TRIR per 100 FTE accurately.
Enter the inputs
- Recordable incidents: OSHA-recordable cases for the period.
- Total hours worked: All employee hours for the same period (include temps/contractors if that’s your policy). Turn on Show decimals if you need more precision.
Review your results
- TRIR (per 100 FTE): (Recordables × 200,000) ÷ Hours worked
- Recordables: Echo of your input for quick validation - Hours worked: Echo of your input with formatting
Interpret the output
- Lower TRIR = fewer incidents per 100 FTE.
- Use consistent periods when comparing business units. - Track month-to-month, quarter-to-quarter, and year-to-date to spot trends.
Frequently Asked Questions
What is TRIR?
Total Recordable Incident Rate (TRIR) is the standard safety metric showing how many OSHA-recordable cases occur per 100 full-time employees over a given period.
How do you calculate TRIR?
TRIR = (Recordable incidents × 200,000) ÷ Total hours worked. The 200,000 factor normalizes results to 100 FTE (40 hours/week, 50 weeks/year).
What counts as a “recordable” incident?
Any OSHA-recordable case such as medical treatment beyond first aid, restricted work, job transfer, days away from work, or fatality. First-aid only cases are not recordable.
Why 200,000 hours?
It represents 100 employees working 40 hours per week for 50 weeks. Using this constant allows apples-to-apples comparisons across teams of different sizes.
Should contractor hours be included?
Include them only if you also include their recordable incidents. Be consistent with your inclusion policy across periods and sites.
What time period should I use?
Any period is fine (month, quarter, year) as long as the incidents and hours cover the same window.
What is a “good” TRIR?
Lower is better. Benchmark against your industry average and your own historical trend; large swings often signal data errors or operational changes.
TRIR vs DART — what’s the difference?
TRIR counts all recordables. DART counts the subset that cause Days Away, Restricted, or Transfer. DART is usually lower than TRIR.
Why does my TRIR look very high?
Common causes: tiny hours denominator, incidents/hours from different periods, or a missed zero in the hours entry (e.g., 20,000 vs 200,000).
Can I show decimals?
Yes. Enable decimals for precision. Many reports round to one decimal (e.g., 1.3), but keep full precision in internal logs.
Example calculation?
3 recordables and 500,000 hours → TRIR = (3 × 200,000) ÷ 500,000 = 1.2.