An osha incident rate calculator has one job: turn a case count and an hours-worked figure into a number you can trust. Ask two safety managers to run the same year's data through two different tools, though, and it's not unusual for the results to disagree — not because the formula changed, but because nobody checked the arithmetic first. This piece runs one fixed, fully worked example — a 250-person fabrication plant with a defined set of recordable cases — through the TRIR and DART formulas by hand, line by line, so you have a known-correct answer. Use it to test any calculator, including ours.
What exactly must an OSHA incident rate calculator get right?
The formula behind every osha incident rate calculator is short and fixed. TRIR — Total Recordable Incident Rate — equals the number of OSHA recordable cases multiplied by 200,000, divided by the total hours worked by all employees. DART — the Days Away, Restricted or Transferred rate — uses the same structure, but only counts cases where someone missed work, worked restricted duty, or was transferred to a different job. The 200,000 constant represents 100 employees working 40 hours a week for 50 weeks a year, a standard baseline that lets a 30-person shop and a 3,000-person plant be compared on the same scale.
Because the formula is public and short, a calculator getting the division itself wrong is rare. What breaks trust is everything upstream of the division sign: which cases genuinely count as recordable under 1904.7, whether "hours worked" means actual hours clocked or scheduled hours, and whether DART correctly excludes the milder "other recordable case" category. A total recordable incident rate calculator that gets its inputs right but never shows its formula is asking you to trust it blind — which is exactly what we're not doing here. We'll build one scenario with a known, hand-checked answer, then use it as the test.
A worked scenario: one year at a fabrication plant
Picture a 250-employee metal fabrication plant — illustrative, not a real company — that finished its year with 500,000 total hours worked by all employees, including overtime and excluding paid leave nobody actually worked. Over the year its EHS team logged ten cases that independently met the 1904.7(b) recording criteria: not first aid, not a visit that resolved with an ice pack and observation, but injuries and illnesses a physician or licensed health care professional treated beyond first aid, or that kept someone off the job. Job13's own recordability check is built for exactly this judgement call, case by case, before any number reaches a rate calculator.
Of the ten recordable cases:
- Four involved days away from work — an employee sent home to recover, unable to return that shift.
- Two involved restricted work or job transfer — light duty on a different line while a hand injury healed.
- Four were "other recordable cases" — medical treatment beyond first aid, such as sutures or a prescription-strength anti-inflammatory, with no lost time and no restriction.
That is the whole, closed dataset for the year. No ambiguous case sitting in a "needs review" queue — this scenario is built so the arithmetic has exactly one right answer.
| Input / output | Value |
|---|---|
| Employees (illustrative) | 250 |
| Total hours worked (year) | 500,000 |
| Days-away cases | 4 |
| Restricted work / job transfer cases | 2 |
| Other recordable cases (medical treatment beyond first aid) | 4 |
| Total recordable cases (TRIR numerator base) | 10 |
| DART-eligible cases (days away + restricted/transfer) | 6 |
| TRIR calculation | (10 × 200,000) ÷ 500,000 |
| TRIR result | 4.0 |
| DART calculation | (6 × 200,000) ÷ 500,000 |
| DART result | 2.4 |
Table: the fixed worked scenario — a 250-employee fabrication plant's year of recordable cases and hours worked, with the arithmetic that produces each rate. Use these figures to test any osha incident rate calculator you're evaluating.
How is TRIR calculated from these numbers, step by step?
Start with the numerator. Multiply the total recordable case count — 10 — by the fixed constant, 200,000. That gives 2,000,000. Divide by total hours worked, 500,000. 2,000,000 ÷ 500,000 = 4.0. That's the plant's TRIR: 4.0 recordable cases per 100 full-time-equivalent employees, on the standard scale OSHA and the Bureau of Labor Statistics both use. Any trir calculator that takes 10 cases and 500,000 hours and returns anything other than 4.0 has a bug, not a rounding quirk — these numbers divide cleanly, with nothing left over.
How is DART calculated from these numbers, step by step?
DART narrows the numerator. It counts only cases involving death, days away from work, or restricted work and job transfer — not the milder "other recordable case" category, which counts toward TRIR but never toward DART. In this scenario that's the four days-away cases plus the two restricted/transfer cases: 6 cases. Multiply by 200,000: 1,200,000. Divide by the same 500,000 hours: 1,200,000 ÷ 500,000 = 2.4. That's the DART rate. It must always be lower than, or equal to, TRIR for the same period, because DART cases are a subset of recordable cases. If a dart rate calculator ever returns a DART figure higher than its own TRIR for identical inputs, something upstream is broken — most likely a case counted in the wrong bucket. Our full breakdown of the DART rate covers which case types belong in that narrower count.
Where do teams get this wrong when checking a calculator against a known answer?
Once you have a known-correct answer like the one above, testing a calculator sounds simple: type in 10 cases and 500,000 hours, check you get 4.0 and 2.4. In practice, a handful of mistakes creep in and make a correct calculator look wrong, or a broken one look fine.
- Reading a rounding difference as an error. Some tools display two decimal places, some display one, and some round to the nearest whole number for a summary view. A calculator showing 4.0 and another showing 4.00 agree completely — that's formatting, not disagreement. Only flag a mismatch when the underlying value, not the display, differs.
- Entering average headcount instead of actual hours worked. A calculator that asks for headcount and multiplies by an assumed 2,000 hours a year is estimating, not measuring. Our scenario's 250 employees at a flat 2,000 hours each would suggest 500,000 hours, which happens to match here — but real payroll data rarely lines up that neatly once overtime, part-time shifts and mid-year hires are in the mix. Always check whether a tool wants actual hours worked or is silently substituting an estimate.
- A calculator silently excluding contractor or temp-agency hours. OSHA recordkeeping counts hours for workers under an employer's day-to-day supervision, not just direct payroll. If a tool's hours-worked field only pulls from a payroll export, contractor and temp hours can go missing from the denominator, quietly inflating the rate above the true 4.0.
- Mixing "other recordable" cases into the DART count. This is the single most common source of a wrong DART figure. Our scenario has four other-recordable cases that belong only in TRIR's 10. A calculator or a spreadsheet formula that accidentally sums all ten into the DART numerator would report 4.0 for both rates instead of 4.0 and 2.4 — a real error, not a rounding one.
- Comparing rates from different reporting periods. A TRIR calculated from six months of data annualised one way won't match a TRIR calculated from a full calendar year another way. Before comparing two tools' output, confirm both are working from the same period and the same case list — the OSHA 300A summary is the usual source of record for a full year's totals.
How do EHS teams cross-check an incident rate calculator's output?
The general pattern among EHS teams that catch errors early isn't exotic: they keep a small, hand-verified reference calculation like the one above, and they run it through any new safety metrics tools before trusting that tool with real data. It costs a few minutes and it catches the two failure modes that matter most — a broken formula, and a hidden assumption about what "hours worked" means. Teams that skip this step tend to find the problem months later, when two reports for the same period don't match and nobody can say which one is right.
One EHS manager we spoke with put it this way: "We don't trust a new tool because the vendor says it's accurate. We put our own numbers through it first — cases we already know the answer for — and if it doesn't match, we stop right there." That's the discipline this worked example is meant to support: a fixed, arithmetic-checked scenario you can run through any osha recordable calculator before you rely on it for a real 300A summary or an ITA electronic submission.
It's also worth separating the rate calculation from the recordability decision feeding it. A dart rate calculator or trir calculator only ever processes the case count you give it; it has no way to judge whether a specific injury belongs on the OSHA 300 Log in the first place. That judgement happens earlier, against the 1904.7 recording criteria — our recordable criteria checklist walks through exactly what qualifies. Get that step right and the rate calculation becomes the easy, mechanical part this article has just walked through.
Run your own case count and hours-worked figure through Job13's TRIR and DART calculator and check it against the 4.0 and 2.4 worked out above — it shows the formula openly, needs no signup, and covers federal 29 CFR Part 1904. For the case-by-case determinations behind the numbers, plus the 300 Log, 300A summary and ITA export in one place, see Job13 pricing.
Frequently asked questions
What is the OSHA incident rate calculator formula?
TRIR equals the number of OSHA recordable cases multiplied by 200,000, divided by total hours worked by all employees during the period. DART uses the same structure but only counts cases involving days away from work, restricted duty or job transfer. The 200,000 constant represents 100 employees working 40 hours a week for 50 weeks, so employers of different sizes can be compared on the same scale.
Why do two incident rate calculators give different TRIR numbers for the same data?
Almost always because the inputs differ, not the maths. Common causes include one tool using scheduled or estimated hours instead of actual hours worked, one excluding contractor hours the other includes, or a mismatch in which reporting period each tool's case list covers. If both tools use exactly 10 recordable cases and exactly 500,000 hours worked, both should return 4.0 — anything else points to a genuine calculation bug.
Does a DART rate calculator use the same formula as a TRIR calculator?
The structure is identical, but the case count going in is narrower. DART only includes cases involving death, days away from work, or restricted work and job transfer — it excludes the "other recordable case" category that still counts toward TRIR. In the worked example above, that difference is what separates a DART of 2.4 from a TRIR of 4.0 using the same 500,000 hours.
Can I use average headcount instead of actual hours worked in a TRIR calculator?
No, not if you want an accurate rate. OSHA recordkeeping defines the denominator as actual hours worked by all employees, including overtime and excluding paid leave nobody worked — not scheduled hours and not headcount multiplied by an assumed annual figure. A calculator that only accepts headcount is estimating rather than measuring, and the gap grows with overtime, part-time shifts or a partial-year workforce.
How many decimal places should an OSHA recordable incident rate calculator show?
OSHA's own guidance rounds rates to one decimal place for reporting purposes, so 4.0 and 2.4 in the worked example above are the standard level of precision. A calculator showing more decimal places isn't wrong, but treat a difference only in the trailing digits as a display choice, not a genuine mismatch between two tools.
This article is for general information about OSHA recordkeeping under 29 CFR Part 1904 and is not legal advice. For authoritative guidance, see OSHA's recordkeeping resources, the full text of Part 1904, and industry data from the Bureau of Labor Statistics. Read more on the Job13 blog, or find out more about Job13.
