The objection we’d expect any business case for safety reporting software to meet in finance review is that it counts released hours as cash. If you keep hours, value and cash apart, show every input and leave injury savings out of the total, the case is harder to dismiss and more useful to the safety team.
This is the method we set out in chapters 9 and 10 of The Frontline Reporting Index 2027, with the arithmetic shown.
What should a business case for safety reporting software include?
Two lanes, side by side, and a clear line between them.
Lane 1, modelled economics. In the report: “Use actual workflow volumes, time by role, labour rates, adoption and full project costs. Distinguish economic capacity value from identifiable cash savings.”
Lane 2, operational value. “Track useful detail, assistance, confidence in the account, control evidence, audit preparation and readiness for analysis. Do not automatically convert these to money.”
With the first lane, finance has a number to test. With the second, the safety team keeps the reasons it wanted the change in the first place. “A credible business case does not need to assign a price to every benefit.”
How do you work out the hours a reporting process takes?
Per workflow and per role, from actual volumes.
- Pick one named workflow. Hazard reports at one site, for example, or pre-start checks on one fleet.
- Take actual annual volumes. Separate simple and complex forms, and count a crew-level form once.
- Time a small sample by role. The worker, the supervisor, and anyone who corrects or re-enters the record. Where one person does two roles, count their time once.
- Include the rework. Clarification calls, corrections and duplicate entry are part of the task.
- Keep inspection time out. The time it takes to carry out a physical inspection is not the time it takes to record the result.
Then, in the report’s words: “estimate gross hours released as the adopted annual report volume multiplied by the change in active minutes per report, divided by 60. Add the role-level results. Where the future process takes longer, retain the negative contribution.”
The worked illustration in the report uses these inputs. They are assumptions for the example, not benchmarks or results.
| Input | Illustrative assumption |
|---|---|
| Annual comparable reports | 100,000, with 80% handled through the new workflow |
| Worker time per report | 5.0 minutes today, 2.5 minutes in the assumed future process |
| Supervisor time per report | 0.50 minutes today, 0.25 minutes in the assumed future process |
| Hourly labour value | Worker $30, supervisor $45 |
80,000 adopted reports multiplied by 2.5 minutes saved, divided by 60, gives 3,333.3 worker hours. The same arithmetic on the supervisor’s quarter of a minute gives 333.3 hours. Gross physical hours released: 3,666.7.
Why aren’t released hours the same as cash savings?
Because the people whose time is released are still employed, and their time only has value if it goes to other work. In the report: “Released capacity is not automatically cash saved. A positive capacity-based business case can still require additional cash expenditure.”
That is why we keep four outputs apart in the report: “Current process hours. Future process hours on an equivalent basis. Gross physical hours released. The share of that capacity that can realistically be redeployed, plus any separately identifiable cash savings. These are not different labels for the same number.”
In the report’s illustration you can see what happens to the value when one assumption moves. At the stated rates, 3,666.7 hours have a gross labour value of $115,000. The share of that time the business can realistically redeploy is an assumption, and the value moves with it.
| Redeployment assumption | Modelled capacity value | After first-year project cost of $36,000 |
|---|---|---|
| 40% | $46,000 | $10,000 |
| 60% | $69,000 | $33,000 |
| 80% | $92,000 | $56,000 |
Physical hours released stay at 3,666.7 in every row. Of the central case, we wrote: “It does not establish $69,000 of cash savings or cash payback. It shows a value assigned to capacity, conditional on that capacity being productively redeployed.”
What belongs on the cost side?
All of it, over the forecast period. “Include the agreed subscription, usage, support and any actual implementation, integration, training, device or in-house rollout costs. Show the forecast period and adoption ramp.”
Adoption matters on both sides. A workflow at 80% adoption has 80% of the benefit and most of the cost, and in the case you should show which month each one starts.
What should stay out of the total?
“Injury reduction, avoided fines, insurance effects and reputational value stay outside the core total unless there is a distinct, supportable basis for including them.”
They still belong in the decision. We wrote in the report that “A benefit does not have to appear in the ROI total to belong in the decision.” Put them in Lane 2, with the evidence that would show them, and leave the number alone.
How should you present it?
As something a sceptical reader can challenge. Show low, central and high scenarios with every input visible, and mark each input as measured, assumed or still to be established. In the report: “A visible estimate that a site manager can challenge is more useful than a generic multiplier that conceals where the supposed benefit comes from.”
A case built this way is easier to approve, because the finance reviewer can change an assumption and watch what happens.
How do you run the numbers for your own operation?
Start with two inputs. In our business case calculator you answer two questions about your operation and see the hours your frontline spends on safety forms today and with Tandm, with every assumption on the page.
One difference to know about if you compare it with the report: the calculator applies two further allowances to the time, while the report’s example applies a redeployment factor to the value instead. Both are planning assumptions to test in a pilot.
Download The Frontline Reporting Index 2027 for the full method and the illustration, or work through your figures with us.
Sources
- Tandm, The Frontline Reporting Index 2027: The work-to-record gap, framework edition, October 2026, chapters 9 and 10. tandm.io