Skip to main content
    QHSEtech
    Updated
    All glossary terms
    Content date: · No individual check logged· AI use

    TRIRTotal Recordable Incident Rate

    Definition

    Total Recordable Incident Rate — recordable cases multiplied by 200,000 and divided by hours worked, using the US incidence-rate convention.

    Editorial definition: The QHSE Standard, updated 3 October 2026 · https://qhsetech.com/glossary/trir

    Scope: Define the reporting population and period; a low rate alone does not establish control of serious hazards.

    How the rate is built, and what feeds it

    BLS gives the formula as the number of injuries and illnesses multiplied by 200,000 and divided by employee hours worked, and explains that 200,000 stands for 100 employees working 40 hours a week for 50 weeks, so the result reads as cases per 100 full-time workers per year. BLS says hours worked should exclude any non-work time, even when paid, such as vacation, sick leave and holidays, and it names OSHA Forms 300 and 300A, payroll or other time records as the sources of the counts and hours. Its worked example is 7 cases over 400,000 hours, giving 3.5.

    The numerator depends on what counts as recordable. OSHA's general recording criteria in 29 CFR 1904.7 make a work-related injury or illness recordable if it results in death, days away from work, restricted work or transfer to another job, medical treatment beyond first aid or loss of consciousness. Certain significant conditions diagnosed by a health care professional, such as cancer, a chronic irreversible disease, a fractured or cracked bone or a punctured eardrum, must also be recorded. Because the numerator is the outcome of a classification, two sites with identical events can report different rates if they classify differently.

    Other conventions exist. The IOGP user guide for its safety data series defines a total recordable injury rate as the sum of fatalities, lost work day cases, restricted work day cases and medical treatment cases per million hours worked, and it says its results are presented per million hours while OSHA's incidence rates represent injuries and illnesses per 100 full-time workers (200,000 hours). A figure quoted without its multiplier is therefore ambiguous: the same cases and hours give a number five times larger on a million-hour base. BLS also advises that, when comparing with industry rates, you consider the size of the employer and whether the comparison is for total recordable cases or for cases with days away, job transfer or restriction.

    Sources opened :

    What a TRIR record set holds in software

    • Case-level records classified against the recording criteria in force, with the decision, the date and the person who made it, so that the numerator can be rebuilt.
    • Hours worked by period, site and employer group, with the source (payroll, time system, estimate) and a flag for estimated values.
    • The population definition: employees only, or also agency workers, contractors and visitors, and the reason.
    • The formula and multiplier stored with each reported figure, with the reporting period and the date it was calculated.
    • Corrections, such as late-classified cases and revised hours, with the earlier figure kept visible.
    • Links to related measures, such as cases with days away, restriction or transfer, so that one data set feeds all of them.

    TRIR, DART and LTIFR

    TRIR counts every recordable case. DART narrows the numerator to cases with days away, restricted work or job transfer, and BLS treats it as a separate comparison measure. LTIFR counts lost-time cases, and its multiplier and day-counting rules vary between schemes. The three share the idea of hours worked as the denominator and differ in numerator and multiplier, so a table that mixes them without labels misleads. A figure called an incident rate without the word recordable is looser still, because it may include near misses or first aid cases.

    A hypothetical example: four cases, then a wider population

    This case is invented and describes no real site. A warehouse records 4 cases that meet the recording criteria in a year, and its time records show 380,000 hours worked by its own employees. The rate is 4 x 200,000 / 380,000, which is 2.11 to two decimals. One more recordable case would give 2.63, and the same four cases over 10% more hours (418,000) would give 1.91, so a single event moves the figure by about half a point at this size.

    The following year the warehouse adds agency workers to the same log and adds their hours, and the rate falls although no practice changed, because the denominator grew faster than the numerator. A reader who saw only the two figures would infer an improvement. The record that stored the population definition and the source of the hours lets the safety manager explain the change, and a note beside the second figure states that the populations differ. The site also reports cases by severity alongside the rate, because the rate counts a minor strain and a serious injury as one case each.

    Common misunderstandings about TRIR

    • A low TRIR does not show that serious hazards are controlled. It counts cases, not severity, and a site can record few cases while a high-consequence hazard goes unmanaged. OSHA's recommended practices say that both lagging and leading indicators should be used.
    • Rates move with small numbers. At a few hundred thousand hours a single case changes the figure noticeably, so a month-to-month change at one site is often noise.
    • TRIR is not a legal compliance score. The legal duties are to record and, in defined cases, report; the rate is a derived measure that organisations, customers and tenders choose to use.
    • The multiplier is not universal. A TRIR of 1.2 quoted without saying whether it uses 200,000 or 1,000,000 hours leaves the number open to a fivefold misreading.

    How TRIR relates to other glossary terms

    TRIR is one of a family of rates and sits beside the terms that say what the rate leaves out.

    • LTIFR: a rate on lost-time cases only, usually quoted on a different hours base.
    • Serious injury or fatality: a classification by severity or potential severity, which a rate on all recordable cases does not provide.
    • Near miss: events with no harm, which the rate does not count at all.
    • Management review: where rates, trends and other performance evidence are examined and acted on by top management.

    Records and evidence that usually exist for TRIR

    • The log of recordable cases and the criteria used to classify them, with decision records for borderline cases.
    • Hours worked by period and group, with source documents or the method of estimation.
    • The written definition of the rate: numerator, population, multiplier and period.
    • Calculation worksheets or system reports showing how each reported rate was derived and who checked it.
    • Records of corrections or restatements and the reason for each.
    • Companion measures, such as severity or leading indicators, reported beside the rate.

    What a software tool needs to capture for TRIR

    • Case classification that follows the recording criteria in use and stores the reasoning, so the numerator can be audited.
    • Hours imported from a time or payroll system, with the source and period stored and a way to flag estimates.
    • Population controls (employees, agency, contractors) that change the rate transparently and are shown in the report.
    • A stored multiplier and formula on each output, with 200,000 and 1,000,000 as choices and no silent default.
    • Restatement handling, so that a later reclassification updates the rate and keeps the earlier figure visible.

    Catalog profiles documenting incident recording and reporting

    A documented incident-recording capability does not establish a recordable-rate calculation. In a demonstration, ask to see the case classification, the source of the hours and the multiplier.

    Same rule for every product: tagged “Incident Management” or “Incident Reporting”, with a sourced incident reporting or management capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.

    Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered

    All 56 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.

    Related software

    Frequently asked questions

    What is a good TRIR?

    There is no universal good value. Compare with employers of similar size and work, using the same case definitions and multiplier, and read the result beside severity and leading measures.

    Are contractor hours included?

    It depends on who is on the log and what the customer or scheme asks. Record the population definition so that the rate can be explained, and ask what a customer's request expects.

    Why do two sites with similar hours report different rates?

    Different case counts can reflect real differences, but also classification, reporting culture and the population counted. Compare the definitions first.

    More safety terms

    Related guides