Most companies answer the question "what did that accident cost us?" with a guess, or with somebody else's average multiplied by a number nobody can source. There is a slower way, and it is the only one that survives a follow-up question: how to calculate the cost of a workplace accident from records you already hold. Our accident cost calculator does the adding up; this article is about what to put in it and what to leave out.
What it counts
You enter what you can evidence, category by category: paid absence, the hours managers and safety staff spent responding, interrupted production, replacement cover, damaged equipment and cleanup, claims and professional advice. Each category has its own field and each amount is added exactly once, which is what keeps the estimate explainable and stops the same cost being counted twice under two names.
The arithmetic is deliberately plain. Absence is workdays × working hours per day × your full hourly labour cost. Response is the number of other people involved × hours each × the same hourly cost. Downtime is days × your cost per day. Replacement, damage, claims and other recorded costs go in as entered. Every component is rounded to cents or pence before the totals are added.
The multiplier we deliberately left out
Most accident-cost material starts with a ratio: direct costs times some number equals the real cost. We do not apply one, and that is the tool's main design decision.
The reason is that those ratios are not portable. They differ by industry, by how severe the event was, by the insurance arrangement and by how a company books things. The UK's HSE publishes the best-known insured-to-uninsured comparison, and we link it as context rather than importing it as a multiplier (HSE, costs to Britain of workplace injuries and new cases of work-related ill health). The same goes for OSHA's Safety Pays estimator, which is useful for awareness but is built on insurance claim data rather than your books (OSHA, Safety Pays).
So the indirect-cost field starts at zero. Enter known items in their dedicated fields first. If your organisation has an internal percentage it can defend for the additional disruption nobody itemises, apply it explicitly and say so in the write-up. If not, leave it at zero and present the known-cost total as the conservative figure — which is the harder number to argue with anyway.
Why region and currency are separate from the arithmetic
The region selector changes the official context shown next to the model, not the model. Poland, Germany, the United States and the United Kingdom run different systems and different vocabulary, and mixing them produces nonsense: a German company does not have ZUS IWA reporting, and an American one is not governed by the Polish Labour Code. Keeping context beside the arithmetic rather than inside it means a Polish safety officer and a German one can both use the same calculator without either of them getting the other's assumptions.
Currency works the same way. PLN, EUR, USD and GBP are display and accounting units. Switching them does not convert anything — if your records hold more than one currency, convert them yourself with one documented rate and one date before entering the figures, and note both in the write-up.
Where the numbers come from in practice
The categories map onto records most organisations already keep: payroll data for absence and response hours, incident logs for who was involved, invoices for damage and cleanup, production reports for downtime. That is the whole point of a bottom-up model — every line has a document behind it, so the result survives the question "where did you get that?".
If you need context for what a typical accident profile looks like in your country, our workplace accident statistics tool charts the official Polish figures and EU comparisons: the yearly trend, the split by industry and cause, and where each country sits on Eurostat's standardised rate.
Turning a cost into a prevention decision
The useful move after you have the number is the comparison, not the number itself: put the estimated cost of one event next to your annual prevention budget. That framing is one decision-makers understand immediately.
Be careful about what the ratio proves. It shows scale. It does not show that a specific training, control or VR programme would have prevented that particular event. The honest next step is to look at the hazard, at how effective the proposed control actually is, at what it costs to implement, and at the evidence behind it. For the training side of that argument, the VR training ROI calculator takes the cost-per-incident figure you just built and lets you weigh it against a training programme, and slips, trips and falls: training that actually works covers what changes behaviour for the most common accident category of all.
Who it is for
Safety officers building a case for a control that costs money, HR and finance staff who have been asked to sanity-check that case, and anyone writing the post-incident report where "this cost us roughly X" needs to be defensible. Browse the VR training catalogue when the conclusion points at training, or our free tools for the rest of the questions that follow an incident.
The result is worth exactly as much as the documents behind it, which is the point of doing it this way. A number with payroll data, invoices and a production report behind every line can be shown to a board, an insurer or an inspector. A number that came from a ratio cannot.
