How to Calculate Safety Software ROI: 5 Key Inputs
You already know the question that gets budget approved. It’s not “Can we afford this software?” It’s “Can we afford to keep operating the way we are today?”
So what numbers do you bring into the meeting where these questions get asked?
Coming in unprepared is where most safety software business cases stall. In Novara’s recent business case building workshop, sales manager Scott Blankenship put it simply: evaluations fall apart when the problem never gets tied to a number. “We have too many incidents” might be true. It still isn’t something a CFO can approve.
Consider this post the math behind a defensible ROI case. It uses the same five inputs Novara works from when we sit down with a safety team, and you can run them with any tool, or with a spreadsheet and your OSHA 300 log.
Five Inputs.
One Defensible Business Case.
Gather these before your CFO conversation. Each one comes straight from your own records.
and Payroll
EHS Spend
Mod Rate
Costs
and Insurance
Input 1
Headcount and Payroll
Start with two numbers your CFO already knows: total employees and average annual salary.
Headcount sets your total hours worked, which you’ll need for TRIR in a minute. Payroll drives your cost per employee and shows what time savings are worth. When your team stops chasing paper forms and rebuilding spreadsheets, those hours go back to real work. Payroll puts a dollar figure on that.
Mark Hasson, Novara’s VP of New Sales, calls headcount one of the three inputs that carry the most weight in an ROI case. So pull it from HR or payroll, not from memory.
Here’s why it matters:
This is the number your CFO can check in seconds. Get it exactly right, and the rest of your case borrows that credibility.
Input 2
Current EHS Spend
Next, total what you already pay for EHS tools and services. That might be an SDS manager, a separate audit platform, a training LMS, or outside consultants.
Don’t overthink this one. For a lot of safety teams, the honest answer is $0 or close to it. Paper, binders, and spreadsheets don’t show up as a software line item. That’s normal, and it won’t skew your case. As Mark put it, this input matters less than the others.
Here’s why it matters:
Any tools a new system would replace offset its cost. That’s an easy win to hand your CFO.
Input 3
Your Safety Profile
Your safety profile tells the CFO how much risk the business carries today. The best measure is your experience modification rate (eMOD, or mod rate), the number your workers’ comp carrier uses to price your premium. If you know it, use it.
If you don’t, use your Total Recordable Incident Rate (TRIR). You can calculate it from your OSHA 300 log in about two minutes. In fact, Novara has a free TRIR calculator that will do the math for you.
So what’s a good number? A TRIR under 1.0 is excellent. Once you climb over 4.0, the cost starts showing up on the bottom line.
For eMOD, the benchmark is 1.0 — the industry average. Anything below 1.0 lowers your premium, and anything above it raises your premium. An eMOD of 0.8, for example, cuts your workers’ comp premium by 20% (Insureon).
Here’s why it matters:
eMOD and TRIR are widely recognized and industry standard safety metrics. They translate your incident log into a number your executives can understand.
Input 4
Incident Severity and Direct and Indirect Costs
A count of incidents isn’t a cost. Ten minor incidents and one serious injury tell very different stories, so sort the last 12 months by severity.
The business case Scott and Mark walked through uses five severity levels. At one end, a minor incident runs about $20,000 in direct and indirect costs. At the other, a catastrophic injury runs about $160,000.
Costs Climb Fast
With Every Step in Severity.
-
$20KMinorLaceration, contusion, puncture, hearing loss
-
$32KLow-ModerateSprain or strain, carpal tunnel, heat stress
-
$50KModerateFracture, concussion, burn, respiratory
-
$100KSevereCrushing, amputation, vision loss
-
$160KCatastrophicElectric shock, asphyxiation, cancer
Average total cost per incident, direct plus indirect. Source: Novara Business Case Workshop.
Why so high for a “minor” incident? Blame indirect costs. Direct costs are the bills your insurance pays, like medical treatment. Indirect costs land on the company, and they run about 2 times the direct cost:
- Lost productivity while work stops
- Overtime to backfill the shift
- Hiring or retraining a replacement
- Hours of investigation and paperwork
That 2.1 figure sits within the range OSHA uses in its $afety Pays estimator, which applies indirect-cost multipliers from 1.1 to 4.5. The less serious the injury, the higher the multiplier (OSHA $afety Pays).
The Claim Report Shows
the Tip of the Iceberg.
Medical treatment and workers’ comp claims.
Insurance pays these, so they’re the costs leadership sees.
Uninsured, so your company absorbs it.
- Lost productivity while work stops
- Overtime to backfill the shift
- Hiring or retraining a replacement
- Investigation and paperwork hours
Here’s why it matters to you:
Indirect costs never show up on a claim report, so leadership rarely sees them. They’re usually the bigger share of what an incident really costs.
Input 5
Labor Rate and Insurance Premium Impact
The last input pulls in two things. The first is your hourly labor rate. It turns lost time (from incidents, downtime, and manual paperwork) into dollars. Mark ranks it with headcount and recordables as one of the three inputs that move the number most.
The second is your workers’ comp premium. It’s set by three things: your payroll, your industry’s loss cost rate, and your mod rate. You can’t change the first two much. You can change your mod rate.
Fewer and less severe incidents bring your mod rate down over time, and your premium follows. That’s a return that keeps paying year after year, on top of the incident costs you avoid. Mark has seen companies cut premiums by tens of thousands of dollars a year, not a thousand here and there.
Here’s why it matters:
Your CFO already watches the premium line closely. Showing how your program moves it speaks their language directly.
Putting it together
A Conservative Estimate
Now let’s build a real number. Take a company with:
- 500 employees
- An average annual salary of $60,000
- A TRIR of 2.5
- A $25,000 annual cost for safety software
Scott builds these cases with modest numbers on purpose, so leadership can see what even a small improvement is worth. We’ll do the same here. Assume a 15% cut in incidents in year one and 30% in year two. Then price every recordable as a minor incident at $20,000, the lowest severity tier.
| Year 1 | Year 2 | |
|---|---|---|
| Recordables (TRIR 2.5 on 1,000,000 hours) | 12.5 | 12.5 |
| Incident exposure at $20,000 each | $250,000 | $250,000 |
| Projected Reduction | 15% = 37,500 | 30% – $75,000 |
| Less software cost | -$25,000 | -$25,000 |
| Net Return | $12,500 | $50,000 |
That’s the floor. Even if every incident were minor, the software pays for itself in year one and returns $62,500 over two years.
Even the Floor Case
Pays for Itself in Year One.
- 500 employees, $60K average salary
- TRIR of 2.5 (12.5 recordables a year)
- Every incident priced as minor: $20K
- $25K a year for safety software
Not included: more serious incidents, lower premiums, time saved, retired tools. Each one raises the return.
Now look at what we left out:
- Any incident more serious than minor
- Lower workers’ comp premiums as your mod rate drops
- Hours your team gets back from paperwork and spreadsheets
- Tools you’d retire
Every one of those pushes the number up. And that brings up something Mark flagged in the workshop: when you add them back in, the real number can look high, even to you. That’s normal. Don’t defend a methodology. Walk your CFO through the inputs, one at a time. If you know where every number came from, the follow-up questions get easy.
Here’s why it matters:
A case that pays off when every incident is minor is hard for a CFO to argue with.
Ready to build a business case that gets to “yes”?
Work one-on-one with a Novara specialist to turn your numbers into a case your CFO can approve.
Want to see one built live first?
Watch the Business Case Building Workshop and follow along as Scott and Mark build a real case on screen.
