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

    Lagging Indicator

    Definition

    A measure of outcomes that have already occurred, such as injuries, illnesses or days lost, used to judge whether past results met the goals set.

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

    Scope: Use it with measures of control performance and reporting quality.

    Sources checked: . Examples are editorial illustrations.

    How OSHA, BLS and HSE use measures of past outcomes

    OSHA describes lagging indicators as measures of the occurrence and frequency of events that happened in the past, such as counts or rates of injuries, illnesses and deaths. They can alert an employer to a failure in part of its programme or to a hazard. OSHA's point is that leading measures are the ones that show whether current activities are effective at preventing incidents, which is why it says to track both kinds. In its programme evaluation guidance the examples are how many injuries and illnesses occurred and how severe they were, results of worker exposure monitoring that show hazardous exposures, and workers' compensation data such as claim counts, rates and cost.

    A common lagging measure is the incidence rate. BLS's formula multiplies the number of cases by 200,000 and divides by employee hours worked, with the base equal to 100 full-time employees over a year. It says such rates help determine problem areas and progress, and that they mean more when compared with similar employers. Because the counts come from recording decisions, the rate inherits the rules behind them, a point developed on the TRIR and DART pages.

    HSE asks boards to give proper weight to preventive information as well as to incident data, for instance accident rates and sickness absence. Three limits follow from what a lagging measure counts. It reports only after events occur. A small organisation may have few or no events in a period, so one case moves the rate. And what is counted depends on how events are defined and reported. OSHA's reporting rule in 29 CFR 1904.35 makes a point of reporting procedures that do not deter accurate reporting, so a fall in recorded injuries cannot be read as safer work without checking. This page is general information.

    Sources opened :

    What a lagging indicator record holds in software

    • The measure's definition: what is counted, the criteria applied, the denominator, any multiplier and the period.
    • The event records behind each count, so a figure can be traced to its cases.
    • The population covered, such as employees only or also contractors and agency staff.
    • Severity breakdown beside the total, since one count mixes minor and serious events.
    • Any restatement, with the earlier figure kept and the reason for the change.
    • The comparison used, such as prior years or an industry rate, with its source and date.
    • The leading measures reported next to it.
    • The reporting period and the date the data was extracted, since late-classified cases can change an earlier period.

    Lagging indicator, outcome measure and incident rate

    Lagging is a role a measure plays and not a fixed list. Injury counts are lagging, and some other counts can play either role depending on how they are used. Terms such as outcome measure and reactive measure overlap with it, so check how a report defines them. A rate is a ratio of a count to exposure and not a score of how safe a site is. A figure called an incident rate with no stated numerator, hours base and period cannot be compared with another.

    A hypothetical example: a rate that falls on one case

    The depot in this account is invented, with made-up figures, and it describes no real operation. A distribution depot records 3 injury cases over 150,000 hours worked in one year. Using the BLS formula, that is 3 x 200,000 / 150,000, a rate of 4.0. The next year there are 2 cases over 160,000 hours, a rate of 2.5. The fall looks large but rests on a difference of one case, and the second year's hours are only a little higher. The safety manager also checks that both years use the same definition of a recorded case, and notes that the hours include agency staff in both.

    The safety manager reports the counts, the hours and the severity of each case, not just the rate. She also reports the leading measures, such as inspection actions closed on time, and notes that one event with serious potential was recorded as a near miss and so appears in no injury count. The management review decides on actions for the serious-potential event instead of congratulating the team on the rate. The next year's report states the same definition so the three figures can be read in sequence.

    Common misunderstandings about lagging indicators

    • A lagging measure describes the past and not the present state of controls. OSHA says it can show a failure after the fact, while leading measures show whether activities are working.
    • Zero events does not prove control. In a small workforce a quiet period is common, and OSHA pairs lagging with leading measures.
    • A better rate is not automatically better safety. The count depends on what was reported and how it was classified, and 1904.35 requires that reporting not be deterred.
    • Comparison needs like-for-like data. BLS says comparisons mean more against similar employers, so industry, size, definition, base and period must all match.
    • A lagging measure does not give causes. It points to where to look, and an investigation has to establish why.

    How lagging indicators relate to other glossary terms

    They sit beside the rates built from them and the leading measures that complement them.

    • Leading indicator: the preventive measures OSHA pairs with outcome measures.
    • TRIR: the rate on all recordable cases, one common lagging measure.
    • LTIFR: a lost-time rate, quoted on a different base in many schemes.
    • Serious injury or fatality: a severity-based view that a count of all cases does not provide.

    Records and evidence that usually exist for lagging indicators

    • The written definition and formula for each measure.
    • The event records or logs that feed the counts.
    • Hours or other exposure records, with their source.
    • Calculation worksheets or system reports, and who checked them.
    • A log of restatements and the reasons.
    • Management review minutes that show the figures were considered and acted on.
    • Comparison data with its source and the date it was retrieved.

    What a software tool needs to capture for lagging indicators

    • A figure that traces back to the event records that make it up.
    • The formula, multiplier, population and period stored with every output.
    • Hours imported with their source, and a flag for estimates.
    • Severity and potential-severity fields beside the count.
    • Restatement history that keeps the earlier figure visible.
    • Raw counts shown next to every rate, so small numbers are obvious.
    • Prompts for periods with very few events, as a reminder that one case moves the rate.
    • A side-by-side view with the leading measures, and an export.

    Catalog profiles documenting incident recording and reporting

    Incident recording in a profile does not establish a rate calculation. Ask where the hours come from, which cases are counted and what multiplier is applied.

    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

    Are injury rates always lagging indicators?

    OSHA gives counts or rates of injuries, illnesses and fatalities as its examples of lagging measures, because they count events that have already happened.

    Why keep lagging measures if leading ones are preventive?

    OSHA says lagging indicators measure whether the effort worked, while leading ones drive change. Outcomes remain the check on whether controls and activities achieved what they were meant to.

    How do we compare our rate with others?

    BLS says rates mean more when compared with similar employers, so match the industry, size, definition, hours base and period. This page gives no benchmark values.

    More safety terms

    Related guides