Rollback Time Budget Calculator

Work out rollback time budget instantly with clear inputs, formula shown and shareable results.

About Rollback Time Budget Calculator

Rollback time has three parts and the human decision step is usually the largest. Automated rollback triggered by SLO burn removes that latency entirely, which is why progressive delivery tooling ties rollback to metric thresholds rather than to a human noticing a dashboard. Pricing the delay in revenue per minute is what usually justifies building that automation.

Formula

Rollback budget

total = detect + decide + execute; exposure = total x revenue per minute

Worked example

With the default values below, Rollback Time Budget Calculator returns Total time to roll back of 18.0. Change any input above and every figure here is recalculated in your browser.

Inputs used

Time to detect the problemminimum 0 min: 4 min
Time to decide to roll backminimum 0 min: 6 min
Time to execute the rollbackminimum 0 min: 8 min
Revenue at risk per minuteminimum 0: 900

Results

Total time to roll back: 18.0 min
Revenue exposed during the rollback: $16,200.00
Share of time spent deciding: 33.3%
Assessment: Acceptable but decision latency is worth attacking

Step by step

1Values used
2Rollback budget
3Total time to roll back= 18.0 min
4Revenue exposed during the rollback= 16,200.00
5Share of time spent deciding= 33.3
6Assessment= Acceptable but decision latency is worth attacking

Assumptions and limits

The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

Should rollback be automatic?

For clear signals such as error-rate spikes, yes. Automated rollback with a manual override is faster and more reliable than paging a human to make an obvious call.

Is rolling forward ever better?

When the change cannot be reverted cleanly — an irreversible migration or a third-party state change. That is an argument for designing changes to be reversible rather than for slow rollbacks.