Injury Severity Rate (ISR) is a crucial performance indicator that reflects workplace safety and operational efficiency.
A high ISR can indicate underlying issues in safety protocols, leading to increased costs and potential legal liabilities.
Conversely, a low ISR signals effective risk management and a commitment to employee welfare, fostering a positive corporate culture.
Organizations that actively track and improve ISR can enhance their financial health by reducing insurance premiums and minimizing downtime.
This KPI aligns with strategic goals, ensuring that safety initiatives contribute to overall business outcomes.
By embedding ISR into management reporting, companies can drive data-driven decisions that improve workplace safety and productivity.
Injury Severity Rate sits in the ISO 18001 KPI group, the occupational health and safety set, where it ranks third among the members. That is a lead position, just behind Lost Time Injury Frequency Rate (LTIFR) and Reportable Incident Rate, and ahead of Occupational Illness Rate, Return to Work Rate, Safety Incident Investigation Closure Time, and Employee Safety Training Completion Rate. Its balanced scorecard perspective is internal process, which makes it a lagging outcome measure: it reports what the safety system already produced, the human cost of the injuries that got through, rather than predicting the next one.
The distinction from LTIFR is the reason both belong in the group. Frequency counts how often injuries happen. Severity captures how bad each one is once it happens. Neither number is complete on its own, so they have to be read together. A plant can drive LTIFR down and still carry a high or rising Injury Severity Rate if the injuries that remain are the serious ones, long absences, restricted duty, permanent limitation. Falling frequency with climbing severity is a real and dangerous pattern, and only the pair reveals it.
The sharpest tension inside the group involves Return to Work Rate. A return to work push shortens measured days lost per injury, which pulls Injury Severity Rate down. That is good for injured people and for workforce capacity, but it can also make the severity number look better without the underlying injuries being any less serious. Read Injury Severity Rate next to Return to Work Rate and LTIFR so a faster return program is not mistaken for genuinely milder injuries.
The raw data lives in OSHA logs and the incident management system: one record per injury, with dates, day counts, and a case status. The honest joins are the ones where definitions get decided, so settle the forks before you compute anything.
First fork: days lost versus days restricted. Full absence and restricted or transferred duty are not the same severity, and mixing them silently inflates or deflates the rate depending on which you fold in. Second fork: calendar days versus scheduled workdays, which changes every case that spans a weekend or a shift boundary. Third fork: capped versus uncapped severe cases. A single catastrophic injury with a very long absence can dominate the average and swamp the signal from everything else, so decide whether long cases are capped and disclose the choice. Fourth fork: which injuries are counted at all, recordable versus lost-time, since that sets the denominator.
Segment the rate, do not just report one number. Injury type, department, and severity band each tell a different story, and a blended figure hides where the harm concentrates. The instrumentation pitfalls are specific. Small denominators make the rate volatile, so a handful of injuries in a period can swing it hard and invite over-reading. Open cases are the subtler trap: an injury with an absence still running has not finished accumulating days, so the current-period rate understates true severity until those cases close. Track case status and, where possible, revisit closed periods once late-maturing cases resolve.
Many organizations overlook the importance of tracking ISR, assuming low incident rates equate to safety. This can lead to complacency and increased risks over time.
Enhancing ISR requires a multifaceted approach that prioritizes safety and employee engagement.
We have 3 relevant benchmarks in our benchmarks database.
Source: Subscribers only
Source Excerpt: Subscribers only
| Value | Unit | Type | Company Size | Time Period | Population | Industry | Geography | Sample Size |
| Subscribers only | days | median | calendar year 2023 | DAFW cases | all industries | United States | 883,372 |
Source: Subscribers only
Source Excerpt: Subscribers only
| Value | Unit | Type | Company Size | Time Period | Population | Industry | Geography | Sample Size |
| Subscribers only | days | median | private industry | 2022 | cases involving days away from work | private industry | United States |
Source: Subscribers only
Source Excerpt: Subscribers only
| Value | Unit | Type | Company Size | Time Period | Population | Industry | Geography | Sample Size |
| Subscribers only | days | median | 2021–2022 | lost time cases | cross-industry | United States |
Browse the Top Benchmarked KPIs in ISO 18001
Three tracked sources report severity-adjacent figures for the United States, and they diverge enough that a single borrowed number can mislead. OSHA reports medians for days-away-from-work cases across all industries. The U.S. Bureau of Labor Statistics reports medians for cases involving days away from work in private industry. The National Safety Council reports medians for lost time cases on a cross-industry basis. Same broad idea, different scope, and the differences matter more than they look.
Start with what counts as a lost or restricted day. Some counts use calendar days, others use scheduled workdays, and the two drift apart across weekends, shifts, and holidays. There is also the days-away versus days-of-restricted-duty split: an injury can keep someone fully away from work, or move them to lighter or transferred duty, and the DART distinction (days away, restricted, or transferred) treats those differently. A source that folds restricted duty into its measure will not line up with one that counts only full absence.
Then the case population. Recordable cases, lost-time cases, and days-away-from-work cases are three different denominators, and each source draws its line in a different place. Industry mix shifts the picture again, because all industries, private industry, and a cross-industry sample carry different injury profiles. Reference year adds one more axis: these sources report different years, and severity moves with regulation, staffing, and reporting habits over time.
One more caution. These public figures are per-case severity measures, medians for a case population, which is not the same construction as this page's formula of days lost divided by number of injuries. Treat the tracked sources, cited here by name as OSHA, the U.S. Bureau of Labor Statistics, and the National Safety Council, as reference points on definition and scope, and verify what each one actually counts before setting any target against it.
Injury Severity Rate ladders directly to the ISO 18001 group's real safety objective, elevate workplace safety by reducing injuries and incident severity. That objective already names Lost Time Injury Frequency Rate (LTIFR) and Reportable Incident Rate as key results, and it treats severity reduction as part of the mission, not a side metric.
Frame Injury Severity Rate as a key result under that objective, paired with LTIFR so frequency and severity move together rather than one masking the other. A directional framing works best: lower Injury Severity Rate while holding or lowering LTIFR, so the team is not just reducing how often injuries happen but also how damaging the remaining ones are. Set any level as an illustrative team goal for the period, and read it alongside Return to Work Rate so a faster return program is credited honestly rather than counted as milder injury. The point of the pairing is a single, defensible claim: injuries are getting both rarer and less severe at the same time.
This KPI is associated with the following categories and industries in our KPI database:
KPI Depot takes you from KPI intelligence to finished deliverable. Consultants, strategy teams, FP&A leaders, and analytics teams use it to answer the two hardest questions in performance management, what to measure and what the target should be, and then to produce the scorecard itself.
The difference is intelligence, not just data. Anyone can list metrics. Every KPI in KPI Depot carries 13 practical attributes, from formula and measurement approach to diagnostic questions, risk warnings, and Balanced Scorecard perspective, across 15 corporate functions and 153 industries. And every target you set is grounded in our database of 34,304 source-attributed benchmarks, each detailing metric value, company size, time period, industry, geography, sample size, and source. Benchmark data at this scale is otherwise the domain of research services costing thousands to hundreds of thousands of dollars per year.
When your metrics are selected, KPI Depot finishes the job: export an interactive Strategy Map, a Balanced Scorecard with formulas and tracking columns, or a CSV KPI pack, and go from research to working deliverable in hours instead of weeks.
Formerly the Flevy KPI Library, KPI Depot is trusted by teams at organizations including Accenture, EY, IBM, PepsiCo, Samsung, and Vodafone.
Got a question? Email us at [email protected].
Tracking ISR helps organizations gauge the effectiveness of their safety measures. It also identifies areas needing improvement, ensuring a safer workplace for employees.
A high ISR can lead to increased insurance costs and potential legal liabilities. By reducing ISR, companies can improve their financial health and ROI metrics.
Industries like construction and manufacturing often report higher ISRs due to the nature of their work. These sectors face more hazards, making effective safety measures crucial.
ISR should be reviewed quarterly to identify trends and areas for improvement. Frequent monitoring allows organizations to respond quickly to emerging safety issues.
Yes, technology such as safety monitoring systems can provide real-time data on workplace conditions. This information can help identify risks and improve safety protocols.
Employee training is vital for reducing ISR, as it equips workers with the knowledge to handle hazards. Regular training sessions can reinforce safety practices and reduce the likelihood of severe injuries.
Each KPI in our knowledge base includes 13 attributes.
A clear explanation of what the KPI measures
The typical business insights we expect to gain through the tracking of this KPI
An outline of the approach or process followed to measure this KPI
The standard formula organizations use to calculate this KPI
Insights into how the KPI tends to evolve over time and what trends could indicate positive or negative performance shifts
Questions to ask to better understand your current position is for the KPI and how it can improve
Practical, actionable tips for improving the KPI, which might involve operational changes, strategic shifts, or tactical actions
Recommended charts or graphs that best represent the trends and patterns around the KPI for more effective reporting and decision-making
Potential risks or warnings signs that could indicate underlying issues that require immediate attention
Suggested tools, technologies, and software that can help in tracking and analyzing the KPI more effectively
How the KPI can be integrated with other business systems and processes for holistic strategic performance management
Explanation of how changes in the KPI can impact other KPIs and what kind of changes can be expected
NEW Mapping to a Balanced Scorecard perspective (financial, customer, internal process, learning & growth)