Last Updated: October 23, 2026
Quick Summary
Calculating ROI on project recovery means comparing future returns against future recovery costs only, using the formula (Recovered Value − Recovery Costs) ÷ Recovery Costs × 100. Sunk costs already spent are excluded, because only new money committed to stabilise and complete the project should shape the decision.
- Sunk costs are money already spent that no future decision can recover, so strip them out before calculating.
- A worked example shows $18 million in recovery costs against $26 million recovered value producing a 44% recovery ROI.
- Expected benefit equals the sum of each benefit amount multiplied by its probability of realisation.
- Model base, upside and downside scenarios, then weight each by probability for a risk-adjusted return.
- Recalculate recovery ROI quarterly and report actual recovery spend against forecast every month.
Table of Contents
- Why Standard ROI Fails on a Project Recovery Decision
- The Project Recovery ROI Formula
- Quantifying Project Stabilization Benefits
- Cost of Project Delay Analysis
- Modelling Recovery Scenarios and Risk-Adjusted Returns
- Construction Project Turnaround Best Practices for Tracking Realised Value
- Frequently Asked Questions
Why Standard ROI Fails on a Project Recovery Decision
Standard ROI assumes a clean choice: spend money, get a return. Calculating ROI on project recovery breaks that assumption, because the money is already gone.
Most business cases ignore this. They lump sunk costs into the denominator and make every distressed project look hopeless. That single error kills viable turnarounds.
At CDI Experts, we see this play out constantly on large capital works.
The fix is to split the decision in two. Money already spent is irrelevant to what you do next.
Sunk Costs Versus Recovery Costs
Sunk costs are money already spent that no future decision can recover. (Sunk Cost) They belong in the project’s history, not in the recovery case.
Recovery costs are different. They are the new money you must commit to stabilise the project and finish it. That includes:
- Remediation and rework of defective work
- Additional supervision and recovery management
- Acceleration payments to trades
Here is the mental model we use. Ask one question: if we cancelled today, what would we still have to spend? Any cost that survives cancellation is not a recovery cost. Any cost that only exists because you continue is.
The most common mistake is letting accountants roll sunk costs into the recovery ROI. It makes good projects look bad and bad projects look acceptable. Strip them out before you calculate anything.
The Project Recovery ROI Formula
The project recovery ROI formula compares future returns against future recovery costs only:
Recovery ROI = (Recovered Value − Recovery Costs) ÷ Recovery Costs × 100
Each input has a strict definition:
| Input | What It Includes | What It Excludes |
|---|---|---|
| Recovered value | Final contract value, variations, claims, retained asset value | Money already received |
| Recovery costs | Future spend to stabilise and complete | Sunk costs to date |
| Time horizon | Months from decision to final account | Historic project duration |
The output is a percentage return on the new money you commit. A positive figure means the recovery adds value. A negative figure means cancellation may be the cheaper path.
This is the same logic behind a standard cost-benefit analysis, just applied to the forward-looking part of the ledger. The Australian Government guidance on cost-benefit analysis sets out why incremental costs and benefits should drive public project decisions.
Worked Example: A Distressed Infrastructure Project
Picture a road upgrade stalled at 60% complete. The project is $40 million over its original budget.
The naive calculation includes the full $40 million overrun and shows a heavy loss. That tells you nothing about the decision ahead.
The recovery case looks different:
- Recovery costs: $18 million to remediate, accelerate and complete
- Recovered value: $26 million in final contract value plus approved variations
- Recovery ROI: ($26M − $18M) ÷ $18M × 100 = 44%
A 44% return on new money is a strong result. The project is still over budget overall, but continuing is clearly the better forward decision.
Quantifying Project Stabilization Benefits
Quantifying project stabilization benefits means putting a defensible number on what recovery actually saves you, not just the final contract value. Most teams count the contract sum and stop, which understates the case and leaves finance unconvinced.
We break stabilisation benefits into five buckets, each with its own measurement method:
- Cost avoidance: rework, defect rectification and liquidated-damages exposure you prevent. Measure against the current defect register and the contract’s damages rate per week.
- Schedule recovery: earlier completion and the revenue, availability or tolling income that unlocks. Measure as the difference between the recovery completion date and the do-nothing completion date, multiplied by the daily value of the asset.
- Claims recovery: entitlements you can substantiate with contemporaneous records. Measure only what the evidence supports, not what the contract theoretically allows.
The asset-value bucket matters most and gets counted least. It is also the one finance teams challenge hardest, so anchor it to an independent valuation or a comparable operating asset rather than an internal estimate.
Sizing benefits without double-counting
A common mistake is counting the same dollar twice. If you claim an extension of time, you cannot also book the delay cost as avoided.
A practical discipline is to build a benefit register with four columns for every line: the benefit, the measurement basis, the evidence source, and the owner. If a line cannot name its evidence source, it does not go in the base case.
Probability-weighting the benefits
Projected benefits are not guaranteed. Recovery benefits in particular depend on claims outcomes, trade availability and client behaviour, all of which can move against you. Rather than treat each benefit as certain, assign a probability to each material line and compute an expected value:
Expected benefit = Σ (benefit amount × probability of realisation)
For example, a claims recovery line with a $6 million gross value and a 50% chance of being substantiated contributes $3 million to the expected case, not $6 million. Run the same exercise on the downside: if a benefit line has a realistic chance of falling to zero, the expected value captures that risk in a way a single-point forecast never does.
Build your benefit register before recovery starts, not after. Benefits claimed retrospectively are the ones finance teams discount hardest, and the ones most likely to be struck out in a dispute.
This is also where nonfinancial outcomes earn a line. Service continuity, compliance obligations, customer trust and employee retention rarely appear in a spreadsheet, but they shape whether the recovery was worth it. Where you can, translate them into a financial proxy, the cost of losing a key client, the penalty for a compliance breach, the recruitment cost of replacing a demoralised team, so they sit alongside the hard numbers rather than being waved through. Quantifying the human element requires a similar rigor, as assessing testing ROI provides a clearer view of how individual alignment impacts the long-term stability of a project team.
Cost of Project Delay Analysis
Cost of project delay analysis puts a dollar figure on every month the project runs late. It is the number that most often flips a recovery decision from marginal to compelling, because delay costs accrue whether or not the project is recovered, and they are the costs a cancellation case usually understates.
Delay costs fall into two groups. Time-related site costs, supervision, plant, site overheads, temporary services and insurance, accrue every week the site stays open. Consequential losses, lost revenue, extended financing costs, escalation and missed market windows, accrue alongside them and are usually larger.
The method is straightforward, but the discipline is in the records:
- Identify the delay events and their causes. Separate employer-risk events, neutral events and contractor-caused delay, because only some of them are recoverable.
- Build the as-planned versus as-built programme. The gap between the two is the delay you can evidence.
- Apply the time-related cost rate to each period. A weekly site overhead rate is the workhorse here; derive it from actual cost records, not a tender allowance.
- Add financing and revenue impacts. Financing cost is the cost of capital applied to the additional spend; revenue impact is the daily value of the asset multiplied by the delay period.
- Test the total against the recovery case. Delay cost avoided is a benefit of recovery; delay cost incurred is a cost of the do-nothing or cancellation path.
A worked illustration
Take a project with a weekly site overhead rate of $180,000 and a delay of 26 weeks. Time-related site cost alone is $4.68 million. Add financing cost on the additional spend and the daily revenue value of the asset, and the total delay cost commonly runs to several times the site overhead figure.
The Australasian procurement guidance on managing contract time and cost reinforces why delay events need contemporaneous records. Without them, delay costs stay theoretical and finance teams won’t bank them.
Why recovery cases fail here
This is where most recovery cases fall apart. The delay happened, but nobody kept the daily records to prove the cost. Recovery ROI then gets built on estimates that nobody trusts, and the board discounts the whole case.
The fix is to treat delay records as a recovery asset. Site diaries, progress photographs, delivery dockets, correspondence and programme updates should be collated and indexed before the recovery case is built, not after.
Do not let the delay cost sit only in the cancellation case. If delay cost avoided is a genuine benefit of recovery, it must appear on both sides of the comparison, otherwise the recovery case is understated and the cancellation case is overstated.
Modelling Recovery Scenarios and Risk-Adjusted Returns
Single-point ROI hides risk. Recovery is uncertain, so model at least three scenarios and weight them.

Run these three cases:
- Base case: current plan holds, moderate claims recovery
- Upside case: accelerated completion and strong claims outcomes
- Downside case: further scope growth, weak claims, extended delay
Then apply a probability to each. If the downside case produces a negative return and carries a real chance of occurring, the recovery is riskier than the base case suggests.
We also test the counterfactual. What does cancellation cost? Termination payments, demobilisation, dispute exposure and asset write-down all belong in that comparison.
The decision is never recovery versus a perfect project. It is recovery versus cancellation. Model both, weight both for risk, then choose.
Construction Project Turnaround Best Practices for Tracking Realised Value
Construction project turnaround best practices share one habit: they track realised value against the recovery case from day one. The model is only useful if you keep score.
What we recommend:
- Set a baseline recovery budget and benefit register at mobilisation
- Report actual recovery spend against forecast every month
- Track each benefit as it is realised, not when it is claimed
Nonfinancial outcomes deserve a line too.
CDI Experts deploys recovery teams to stabilise projects and track realised value through to final account. That discipline is how we have delivered over $3 billion in verified value.
Frequently Asked Questions
How do you calculate ROI for a failing construction project?
Start by isolating future recovery costs from money already spent, because sunk costs cannot be recovered and should not sit in the denominator. Estimate the total benefits recovery delivers: avoided termination costs, delay damages avoided, retained margin and any recoverable variations. Subtract the recovery costs from those benefits, divide by the recovery costs, and express the result as a percentage. Run the calculation across best, base and worst-case scenarios so the decision to recover or cancel rests on a range rather than a single optimistic figure.
What financial metrics matter most in project recovery analysis?
ROI tells you the percentage return on recovery spend, but pair it with net present value, internal rate of return and payback period so cash timing is visible. A recovery that returns 40% over four years is a different proposition to one returning 30% within twelve months. Cost of project delay analysis also belongs in the model, since every week of overrun carries standing costs, financing charges and lost revenue. Track these against a baseline set at the point recovery begins, not the original tender.
Is it possible to achieve a positive ROI on a distressed infrastructure project?
Yes, provided the recovery cost is smaller than the value preserved. The value preserved typically includes avoided termination and re-procurement costs, liquidated damages exposure, financing costs during a replacement tender, and the margin still available on remaining works. Quantifying project stabilization benefits carefully is what makes the calculation credible. Where recovery costs approach or exceed the value preserved, cancelling or restructuring the contract often produces the better financial outcome, and the ROI model should show that clearly.
How do you account for risk when calculating ROI on project recovery?
Assign a probability to each benefit and cost line, then multiply to get expected values rather than headline figures. A recoverable claim of $10 million at 60% likelihood contributes $6 million to the model. Weight the whole calculation across three scenarios and compare the risk-adjusted return against the counterfactual of cancelling. Construction project turnaround best practices include revisiting these probabilities monthly, because recovery risk falls sharply once scope is stabilised and the programme is back under control.
Distressed projects rarely fail because the numbers are hidden. They fail because the numbers are calculated the wrong way. If your board needs a defensible recovery case, CDI Experts can build it with you. Our recovery teams stabilise projects, our claims specialists substantiate entitlements with evidence, and our dispute resolution work protects the value you recover. Get started with CDI Experts and turn a stalled project into a decision you can defend.



