Skip to main content
    QHSEtech
    Updated
    Free tools

    QHSE Calculators

    Free calculators for common QHSE numbers: the cost of an incident, a software ROI scenario, a compliance fine scenario from your own amounts, incident rates, ISO 45001 self-assessment and a selected-source emissions subtotal. Each tool page states its inputs and assumptions; the results are estimates, not audited figures.

    Which tool answers which question

    The tools split into three kinds: rates and footprints computed from your records, cost scenarios built from your assumptions, and a self-rating against a standard. The kind decides what to gather first and how far to trust the result.

    Choosing a calculatorThree questions sort a need into one of six tools: injury rates, emissions subtotal, incident cost, compliance fine scenario, software ROI or ISO 45001 readiness.A rate or total fromrecordsA cost or budgetscenarioHow ready a systemisInjury ratesFuel and electricityEvents that happenedA penaltyA software purchaseQ1What do youwant to workout?Q2Injuries andillness, oremissions?Outcome 1TRIR, LTIFRand DARTCases and hoursworked.Outcome 2EmissionssubtotalQuantities andyour factors.Q3Which cost isthe question?Outcome 3Incident costYour direct andadditional costs.Outcome 4Compliancefine scenarioYour own amountsonly.Outcome 5Software ROILabour, costs androllout delay.Outcome 6ISO 45001readinessA self-rating,not anassessment.
    Follow the branch that matches your question. Each tool is also listed with a link under the figure.
    Text version of this decision tree
    1. Q1. What do you want to work out?
      • A rate or total from records: go to Q2 (Injuries and illness, or emissions?).
      • A cost or budget scenario: go to Q3 (Which cost is the question?).
      • How ready a system is: go to Outcome 6 (ISO 45001 readiness).
    2. Q2. Injuries and illness, or emissions?
      • Injury rates: go to Outcome 1 (TRIR, LTIFR and DART).
      • Fuel and electricity: go to Outcome 2 (Emissions subtotal).
    3. Outcome 1. TRIR, LTIFR and DART. Cases and hours worked.
    4. Outcome 2. Emissions subtotal. Quantities and your factors.
    5. Q3. Which cost is the question?
      • Events that happened: go to Outcome 3 (Incident cost).
      • A penalty: go to Outcome 4 (Compliance fine scenario).
      • A software purchase: go to Outcome 5 (Software ROI).
    6. Outcome 3. Incident cost. Your direct and additional costs.
    7. Outcome 4. Compliance fine scenario. Your own amounts only.
    8. Outcome 5. Software ROI. Labour, costs and rollout delay.
    9. Outcome 6. ISO 45001 readiness. A self-rating, not an assessment.

    What each formula does

    Each tool page sets out its steps, a worked example with invented figures and its limits. In one line each:

    • Incident cost. The incident count is multiplied by the direct cost plus the additional cost per incident. Nothing else is added.
    • Compliance fine scenario. The item count is multiplied by your amount per item, and one lump sum of additional costs is added once. No penalty schedule is built in.
    • Software ROI. Released hours are multiplied by an hourly cost and by the share you expect to turn into cash, then set against subscription, operating and one-off costs, with benefits starting after a rollout delay.
    • TRIR, LTIFR and DART. Each rate is 200,000 times a case count, over the hours worked. TRIR counts recordable cases, LTIFR days-away cases, and DART days-away plus restricted-only cases.
    • Scope 1 and 2 subtotal. Each quantity you enter is multiplied by the emission factor you enter, divided by 1,000 to give tonnes, and the selected sources are added.
    • ISO 45001 readiness. You score each of 25 editorial questions from 0 to 4, so the maximum is 100 points. Points are totalled out of 100 and shown as an overall percentage, with percentages by clause group beside it. It is a self-rating and does not assess conformity.

    Before you enter any number

    • Fix the period and the scope first, such as one calendar year and one site, and keep every input to that period and scope.
    • Take hours, counts and costs from payroll, incident registers or finance records, and write down the source and date of each.
    • Decide in advance how you classify borderline cases, such as first aid against medical treatment, so that the count is repeatable.
    • Enter each cost once. If two figures might overlap, remove the overlap before entering either.
    • Use one currency throughout and enter each quantity in the unit its field shows. The cost tools convert no currency.
    • Keep the inputs with the result. A total without its inputs cannot be checked or repeated.

    Mistakes when reading a result

    Reading a scenario as a forecast

    The cost, fine and ROI tools add what you enter. A total shows the consequence of your assumptions, not a prediction of what will happen.

    Comparing with a benchmark that does not match

    A published rate covers a defined population and year. Check that your industry, size, country and period are comparable before reading a gap as good or bad.

    Trusting a rate built on few hours

    With a small workforce a single case moves a rate by a large step. Look at several years, or at the counts alongside the rate.

    Entering a factor you cannot cite

    An emissions subtotal is only as sound as its factors. Record the source, year and geography of each, and leave a quantity at zero only for a source you have deliberately left out.

    Citing the result without its assumptions

    If you quote a figure in a report or presentation, state the inputs and the tool's limits next to it, so a reader can see what it rests on.

    Using a self-rating as an audit finding

    A readiness assessment shows how you rated yourself. It is not an independent assessment and does not predict a certification outcome.

    Reference tools

    Need a tool that isn't here? Tell Dimitris Mitsios (editor).

    Embed a calculator on your website

    The incident-rate, software ROI and ISO 45001 readiness tools are also available as embeddable widgets, with copy-ready code and attribution guidance.

    View embeddable widgets

    Need software that fits your numbers?

    Take the Get Matched quiz: three questions, up to five profiles matched on your priority, industry and team-size tags.

    Get Matched

    Frequently Asked Questions

    Are these calculators free?
    Yes. The calculators run in your browser and show results without signup. Where a tool offers a PDF report, it asks for an email address to send it.
    Where do the benchmarks come from?
    Each tool page names the sources and assumptions it uses. Where you have your own figures, such as hours worked, case counts, costs or fuel and electricity use, enter them instead; the compliance fine calculator uses only the amounts you provide.
    Can I get a report I can share?
    The incident-cost, TRIR/LTIFR/DART, carbon footprint and ISO 45001 tools can email a PDF of your results. The ROI calculator exports its scenario as CSV.
    Which calculator should I start with?
    Start from the question. A rate or footprint from your own records needs the incident-rate or emissions tool; a cost question needs the incident cost, fine scenario or ROI tool; a readiness self-rating needs the ISO 45001 assessment. The decision tree above follows that order.
    Do any of the tools predict a result?
    No. The cost, fine and ROI tools add or multiply the numbers you enter, the rate tool applies a published formula to your counts, and the readiness tool totals your self-ratings. None forecasts incidents, penalties, savings or an audit outcome.
    Why do the cost tools start with no preset figures?
    Published averages come from a different population, period and method from your own. Entering your own costs, with a source and a date, makes the result checkable, and a preset figure would not be.
    Can I cite a result?
    Yes. The tools are free to use and to cite. If you use a result in a report, article or presentation, credit The QHSE Standard with a link, and state the inputs and assumptions behind it.