Why ROI in OHS is calculated differently than in production
In production, return on investment comes from line efficiency. In occupational safety, most benefits are costs that never happen: an accident that did not occur, a shutdown that did not follow, a penalty that was not imposed. Such an item does not appear in the books, so a plant director often hears from finance that the project “has no return”. The mistake lies in the method, not in the project.
A sound calculation separates two kinds of benefit. The first is hard, directly measurable savings: minutes saved on the permit cycle, less double data entry, shorter waiting time for contractor admission. The second is risk reduction, which is valued through the probability and cost of an event rather than as a certain sum. These two blocks must be shown separately, because they carry different credibility with the board.
Costs that enter the calculation
The cost side is simpler, because the vendor puts it in the offer. For a digital work permit and OHS training system, the structure from 2025–2026 deployments looks as follows (indicative ranges from 2025–2026 deployments; individual quotation):
- One-off implementation: in the order of PLN 10,000–20,000 net, usually in five items (server and accounts, training module, permits and especially dangerous work, QR control in the field, workplaces and company register), paid in two instalments of 50%.
- Licences: a flexible model of about PLN 80 net per active user per month (minimum 10), or a fixed package that becomes cheaper at around 30 active users.
- Maintenance: from about PLN 2,000 to 4,000 net per month, depending on the number of workstations and options; this amount covers the server, backups, updates and support.
- On the client side: administrators' time for workshops, employee training hours and, where the plant requires an on-premise installation, its own server.
What to check in the offer so costs do not grow
Ask the vendor about four items that can wreck the budget after the contract is signed: hosting, new software versions, service requests and access for external contractors. A good offer lists them as included in the monthly rate or states a price. If external companies are not counted as users, the cost does not rise with the number of subcontractors.
Cost and saving after 12 months (worked example)
Savings you can measure
Include in the calculation only those savings for which you have a baseline measurement from before implementation. Most often there are four quantities: the time to prepare and close a permit, the time a contractor waits for admission to work, the number of jobs cancelled or suspended because of formal gaps, and the time spent on reports and on preparing documentation for an audit.
The formula is simple: monthly saving equals the number of permits per month, multiplied by the minutes saved per permit, divided by 60 and multiplied by the hourly cost of the people involved. Take the hourly value from the employer's cost, not from the gross rate alone. Remember that saved time turns into cash only when it frees up overtime or cover, or lets people take on additional tasks; otherwise it is an organisational benefit, which is worth marking separately in the calculation.
Worked example step by step
Take a mid-sized plant that issues 200 work permits per month. The assumptions of the worked example: a saving of 15 minutes per permit, a labour cost of PLN 95 per hour, implementation of about PLN 13,000 net, and maintenance of PLN 2,000 net per month for the first ten users.
The monthly saving is 200 times 15 minutes, that is 50 hours, times PLN 95, that is PLN 4,750. After deducting maintenance, PLN 2,750 per month remains. Implementation therefore pays back after about 4.7 months (13,000 divided by 2,750). After 12 months the total cost is about PLN 37,000 (13,000 for implementation and 24,000 for maintenance), and the saving is PLN 57,000, giving a positive balance in the order of PLN 20,000.
The same formula shows the profitability limit of time savings alone: at 100 permits per month the net saving falls to about PLN 375 and the payback period grows to nearly three years. At 400 permits it shortens to under two months. That is why the number of permits is the variable to measure first.
Implementation payback period by number of permits
The risk side: how to value an avoided loss
Do not add the second block to the first in one column. Record it as a scenario: the cost of an event times its yearly frequency, before and after implementation. An example with an explicit assumption: if one unplanned shutdown lasts 4 hours and an hour of downtime costs the plant PLN 15,000, a single event is PLN 60,000. Avoiding one such shutdown in a year exceeds the cost of the whole first year in the previous example. This is an illustrative assumption: only you know the value of an hour of downtime, so substitute your own.
In sectors covered by the NIS2 directive there is one more element. For essential entities, Article 34 of the directive allows fines of up to EUR 10 million or 2% of annual turnover, whichever is higher. A system that provides audit evidence (a register of permits, training and contractor qualifications) supports meeting the requirement and shortens preparation for an inspection, but it does not guarantee compliance, so do not enter the fine as a saving. Enter it as a justification for the board.
How to build the calculation in five steps
The sequence below works regardless of vendor and industry. Each step ends with a number that can be checked after the pilot.
- Measure the baseline: permits per month, average cycle time, number of cancelled jobs, number of people in the process.
- Choose one activity to shorten and define a success threshold, for example minus 15 minutes per permit.
- Gather the full first-year cost: implementation, maintenance, licences, your own time, any server.
- Calculate the payback period and balance in three scenarios: conservative, base and optimistic.
- After the pilot, replace the assumptions with measured values and update the decision.
Worked example: payback of a work permit system
| Parameter | Value |
|---|---|
| Work permits | 200 pcs/month |
| Time saved per permit | 15 min |
| Labour cost per hour | 95 PLN/h |
| Implementation (indicative) | 13 000 PLN net |
| Maintenance | 2 000 PLN net/month |
Result: Saving PLN 4,750/month, net PLN 2,750/month, payback after about 4.7 months, balance after 12 months about +PLN 20,000.
Note: Worked example. Indicative ranges from 2025–2026 deployments; individual quotation. The result depends on the measured number of permits and time.
Video
Frequently asked questions
Is permit time alone enough to justify the investment?
With several hundred permits per month, usually yes. At about 100 per month the payback from time alone exceeds two years, so add a risk scenario and the need for audit evidence.
How do I value an avoided shutdown?
Multiply the downtime by the hourly cost of stoppage on the given line, and the result by the realistic yearly frequency of such events. Record it as a scenario with an explicit assumption, not as a certain saving.
Do external companies increase the licence cost?
In the model discussed, the licence covers people acting in the system on the plant side and company coordinators; contractors' employees and guests are not counted. Always confirm this in the offer.
When should I check the result?
After 3 months of the pilot, replace the assumptions with measured values, and after 12 months do a full settlement against the baseline measurement.
Sources
Calculate the return on your plant's data
Book a conversation with InnerWeb: together we will measure the baseline and prepare a calculation for your plant, with explicit assumptions.
Let's talk