In brief
- Recovery starts when someone with the authority to change the plan accepts that the current one no longer describes the programme.
- The first six weeks decide the outcome: establish the true position, stabilise, reset governance, then build a recovery plan on evidence.
- A new baseline is credible only when it is derived from the diagnosis and owned by the people who must deliver it.
- Some programmes should be stopped. A good recovery includes the discipline to say so early, while that decision is still cheap.
What is programme recovery?
Programme recovery is the deliberate reset of a programme that can no longer meet its commitments: an independent diagnosis, a new baseline built on evidence, and delivery to that baseline under governance that can hold it. Project rescue is the same discipline applied to a single project.
Recovery differs from ordinary course correction in one respect. The plan, the forecast and the reporting have lost the confidence of the people funding the work, so adjusting them is not enough; they have to be rebuilt. Until that happens, every decision the steering committee makes rests on information it no longer trusts.
Government assurance frameworks describe the same point in their own terms. Under the Commonwealth process, a Red delivery confidence assessment means successful delivery appears unachievable and the programme may need re-baselining, and one Red, or two Amber ratings in a row, triggers Enhanced Notification to the accountable authority.
What are the signs a programme needs recovery?
A programme needs recovery when the gap between its reporting and its reality can no longer be closed by the team inside it. The signs are consistent across sectors, and two or three together are enough to act on.
- The finish date holds while everything before it moves. Interim milestones slip and the end date stays, compressing untested work into a window nobody believes in.
- Contingency is drawn faster than milestones are met. The money describes the programme more accurately than the status report does.
- The plan has been reset before, without a diagnosis. The new dates were chosen rather than derived, and they are already slipping.
- Decisions return to the steering committee unresolved. The people holding them lack the authority or the information to close them.
- The supplier owns the narrative. The best account of progress comes from the vendor, and the client team has no way to test it.
- Experienced people are leaving. Knowledge of the systems and the history walks out with them, and the remaining team carries more risk each month.
If an independent health check has already returned an amber or red rating, the question is no longer whether to act. It is how quickly.
Precision perspective
What happens in the first six weeks of a recovery?
The first six weeks establish the true position, stabilise the programme and produce a recovery plan the board can decide on. Most of the value lies in the sequence: diagnose before promising anything, and stabilise before re-planning.
- Weeks one and two: establish the true position. Read the documents and the delivery data, interview the people doing the work in confidence, and test the forecast against the evidence. The output is a candid statement of where the programme actually stands.
- Weeks two and three: stabilise. Pause the work that is creating risk faster than value, freeze uncontrolled change, and protect the critical path and the people who carry it.
- Weeks three and four: reset governance. Confirm who decides what, rebuild the steering committee around decisions rather than updates, and agree the reporting the sponsor will rely on from here.
- Weeks four to six: build the recovery plan. Derive scope, schedule, cost and risk from the diagnosis, test them with the people who must deliver them, and take the options to the board.
Six weeks is a ceiling, set by the size of the programme. A smaller project can reach its decision sooner, and nothing in the sequence should wait for the next reporting cycle.
The stage that is most often skipped is the first. A sponsor under pressure wants a new date, and a new date announced before the diagnosis is the surest way to need a second recovery.
How do you re-baseline a programme credibly?
Derive the new baseline from the diagnosis, have it owned by the people who will deliver it, and size contingency to the risks the diagnosis found. A baseline announced before it is derived will fail the way the last one did.
- Plan from the productivity the programme has actually achieved, measured over recent months.
- Re-scope before re-scheduling: decide what the programme must deliver, and what can move to a later release.
- Price the risks the diagnosis named, and hold contingency where each risk sits.
- Agree in advance how progress will be measured, so the next amber is visible within weeks.
- Take the baseline to the board as a decision, with the options and the cost of each.
A new baseline should also say what has changed in how the programme is run. If the governance, the reporting and the team are all unchanged, the board is being asked to believe the same plan with later dates.
Should a failing programme be recovered or stopped?
Recover it when the outcome still matters, a credible path exists and the organisation can fund and staff that path. Otherwise stop it, or re-scope it to what can still be delivered, and decide before more money is committed.
The test looks forward. Money already spent is gone whichever way the decision goes, so it should carry no weight. What matters is the cost to complete, the value of the outcome at the end, and whether the organisation has the capability and the appetite to see it through.
Stopping is a legitimate result of a recovery. A programme closed deliberately, with its useful work preserved and its lessons recorded, serves the organisation better than one that continues on hope. Part of a recovery adviser's job is to say which path the evidence supports.
How long does programme recovery take?
The diagnosis and recovery plan typically take four to six weeks. The recovery itself runs for the life of the new baseline, which depends on the size of the programme and how far it has drifted.
Assurance frameworks set the clock for the response. The NSW infrastructure framework gives a project rated Stressed or Low up to 12 weeks to address its critical recommendations, and the Commonwealth process requires an action plan once a programme reaches the second level of Enhanced Notification. A recovery should be planned to meet those deadlines with evidence in hand.
Who should lead a programme recovery?
A recovery needs one accountable lead who has run programmes of comparable scale, holds the sponsor's authority to change the plan, and has no stake in defending the old one. That is usually someone from outside the programme, working with the existing team.
The existing team usually holds most of what a recovery needs: knowledge of the systems, the stakeholders and the history. What it lacks is distance from the decisions that led here, and the standing to reopen them. A recovery lead supplies both, transfers what the team needs to sustain the reset, and steps back once the programme is delivering to its new baseline.
Independence still matters after the reset. A firm that leads a recovery should not then assure the same programme, so the board keeps an independent view of whether the recovery is holding.
Sources and further reading
Statements about government frameworks were checked against these sources on 26 September 2026. Frameworks are revised, so read the current guidance for your jurisdiction.