Incident Cost Calculator
Add up an incident's cost from components you can evidence.
In short
Formula: Incident cost = Duration × Revenue lost per hour + Duration × Responders × Responder hourly cost + Other direct costs
What this calculator does
A component model in the FinOps unit-economics style. No revenue figure, labour rate or reputational cost is supplied; anything the user leaves at zero is excluded from the total and shown as zero rather than estimated.
Use it to turn Currency, Length of the incident, Revenue lost per hour of impact, People responding (optional), and the other shown inputs into a checked result you can compare, copy, or rerun with different assumptions.
The page shows the formula, a numeric worked example, and the assumptions that affect this professional & industry calculation.
Inputs and what they mean
- Currency
- — Amounts are shown in the currency you pick. No exchange rate is applied..
- Length of the incident
- — Hours from the start of impact to service being restored..
- Revenue lost per hour of impact
- — Optional component. Leave at 0 to exclude it from the result. Your own figure for revenue lost while the service was impaired. Leave at 0 to exclude it..
- People responding (optional)
- — Optional component. Leave at 0 to exclude it from the result. Number of people working the incident..
- Cost per responder hour
- — Optional component. Leave at 0 to exclude it from the result. Your own loaded hourly cost for the people responding..
- Other direct costs (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Price as of (optional)
- — The date you took these prices. It is shown with the result so the figure is never read as a current vendor price..
- Price source (optional)
- — Where the prices came from. Shown with the result..
How to use it
- Enter your own figures — the calculator never fills in a rate, price or benchmark for you.
- Press Calculate to see the result.
- Read the formula, variables, assumptions and source below the result before you rely on it.
Formula
Incident cost = Duration × Revenue lost per hour + Duration × Responders × Responder hourly cost + Other direct costs.
Inputs used: Currency, Length of the incident, Revenue lost per hour of impact, People responding (optional), Cost per responder hour, Other direct costs (optional), Price as of (optional), Price source (optional).
Edge handling: Length of the incident is required.; Length of the incident cannot be negative.; Length of the incident must be no more than 1000000000000.; Revenue lost per hour of impact is required.; Revenue lost per hour of impact cannot be negative..
Worked example
A 3.5-hour incident with six responders
- Start with Currency: USD, Length of the incident: 3.5, Revenue lost per hour of impact: 4200, People responding (optional): 6, Cost per responder hour: 95, Other direct costs (optional): 0.
- Apply the method: Incident cost = Duration × Revenue lost per hour + Duration × Responders × Responder hourly cost + Other direct costs.
- Only the components you enter are counted; nothing is estimated for you.
Reading the result
The headline figure is the main answer. Any breakdown underneath shows the parts that make it up, so you can check the working and see what changes when you adjust an input.
Limitations and assumptions
- Inputs outside the supported range are rejected rather than forced into a result.
- The result depends on the values you enter for this incident cost calculator; it does not supply missing rates, rules, prices, dates, or assumptions for you.
Reference: The Linux Foundation — Unit economics — FinOps Framework
Last reviewed:
Common questions
Where does this formula come from?
FinOps Framework capability: unit economics — cost per business unit is total cost for a period divided by the units delivered in the same period; shared cost is attributed in proportion to an agreed allocation driver. See the source link on this page.
What kind of calculation is this?
An explicit component model: each component is entered by the user and excluded when left at zero. Check the formula, example, and limitations on this page before using the result for a real professional & industry decision.
What are its limits?
Arithmetic over the figures entered — it cannot tell whether the underlying monitoring, incident records or change records are complete. A mean over a short period, or over few events, is a weak description of behaviour. The result is only as current as the rates entered; a rate taken months ago is not a current cost. Counts only the components entered; indirect effects such as churn or reputation are not modelled.
How do I use the Incident Cost Calculator?
Enter the required values for Currency, Length of the incident, Revenue lost per hour of impact, People responding (optional), Cost per responder hour, and the other fields shown. The calculator applies the formula on this page and shows the main result with any supporting breakdown so you can check the arithmetic.
What formula does the Incident Cost Calculator use?
Incident cost = Duration × Revenue lost per hour + Duration × Responders × Responder hourly cost + Other direct costs The visible formula section above lists the calculation path and the edge cases the page handles, so the result can be checked without relying on the form alone. Check the formula, example, and limitations on this page before using the result for a real professional & industry decision.
Can the Incident Cost Calculator be used for exact decisions?
Use it as a calculation aid, not as a substitute for checking the underlying rule, contract, policy, or professional advice that applies to your situation. When a result depends on local rules, personal details, prices, or dates, enter those values yourself and confirm them before acting.
Formula, source and verification
An explicit component model: each component is entered by the user and excluded when left at zero.
The question it answers: What did that incident cost, what does this service cost to run, and what does one deployment cost us?
The formula
Incident cost = Duration × Revenue lost per hour + Duration × Responders × Responder hourly cost + Other direct costs
- h — Duration
- (h). Hours from the start of impact to service being restored.
- r — Revenue lost per hour
- (currency). The user's own figure for revenue lost while impaired.
- n — Responders
- (count). People working the incident.
- w — Responder hourly cost
- (currency). The user's own loaded hourly cost.
- o — Other direct costs
- (currency). Any other cost the user can evidence.
Units: Hours, counts and the currency the user selects.
What kind of calculation this is
Business input model. The answer depends on business figures only you can supply, such as your own costs, rates or volumes. No market or benchmark values are assumed for you.
Method
A component model in the FinOps unit-economics style. No revenue figure, labour rate or reputational cost is supplied; anything the user leaves at zero is excluded from the total and shown as zero rather than estimated.
Assumptions built into the result
- Mathematical: Every rate is the user's own, in the currency they chose; no exchange rate is applied.
- Mathematical: All responders are costed at the same hourly rate for the whole incident.
Figures this calculator will never guess for you
- No target, benchmark, industry average or performance band is supplied for any figure.
- A definition is never presented as a goal: the availability formula is not an availability target, and the change failure rate formula is not an acceptable failure rate.
- No labour rate, tooling price or revenue figure is built in; every amount is entered by the user.
- No cost of downtime per hour, industry average or reputational damage figure is supplied.
Limitations
- Arithmetic over the figures entered — it cannot tell whether the underlying monitoring, incident records or change records are complete.
- A mean over a short period, or over few events, is a weak description of behaviour.
- The result is only as current as the rates entered; a rate taken months ago is not a current cost.
- Counts only the components entered; indirect effects such as churn or reputation are not modelled.
Source and version
- Standard or reference
- FinOps Framework — unit economics — FinOps Foundation (FinOps Framework capability: unit economics — cost per business unit is total cost for a period divided by the units delivered in the same period; shared cost is attributed in proportion to an agreed allocation driver.)
- Published source
- The Linux Foundation — FinOps Framework
- Formula version
- Version 1
- Verification
- Reviewed against the cited source on
- How much weight the source carries
- Standards or government
- Applies to
- Currency
- Amounts stay in the currency you choose; no exchange rate is applied.
Related tools
Work out the hourly rate to charge a client so that target margin is met after overhead and non-billable time.
Find the true hourly cost of an employee once benefits, payroll cost and overhead are included.
Size a software application from its data and transaction functions before estimating effort or cost.
Estimate development effort, schedule and average team size for a software project of a known size.
Express cloud spend as a cost per customer, per transaction or per other business unit.
Set the rate used to apply manufacturing overhead to jobs for the coming period.