What Makes a Project Recovery Plan Credible?
Written by Andrew McDonald, Founder & Principal at Carpadium· Published 24 September 2026
When a project misses major milestones or delivery confidence deteriorates, the natural response is often to create a revised plan.
But changing dates, adding resources or increasing governance does not by itself create a credible recovery plan.
A credible recovery plan starts with an evidence-based understanding of why the previous position became unachievable, what constraints now exist and what must change to restore confidence in delivery.
Executive guide | Project Recovery
Executive question
“Given what we know now, why should we believe the revised plan is more achievable than the one it replaces?”
RECOVERY IS NOT REPLANNING
A new plan does not necessarily mean the project has recovered.
A revised schedule can create the appearance of control without resolving the conditions that caused delivery confidence to deteriorate.
Before approving a recovery plan, executives should understand:
- what caused the previous plan to become unachievable
- which assumptions were incorrect
- which constraints remain
- what has materially changed
- what decisions are required
- why the new plan should now be achievable
“Recovery starts with evidence, not a new date.”
ESTABLISH THE REAL POSITION
A credible recovery plan begins with the current reality.
Recovery should begin by establishing an evidence-based baseline rather than automatically modifying the existing plan.
SCOPE
What is actually committed and what can realistically be delivered?
SCHEDULE
What work remains and which dependencies genuinely determine completion?
COST
What has been spent, what remains and what will recovery require?
RESOURCES
Does the project have the capability and capacity required?
TECHNOLOGY & DATA
What technical constraints, defects, integration or migration issues remain?
TESTING & QUALITY
What evidence exists about solution quality and remaining effort?
VENDORS
Which external commitments and dependencies are genuinely achievable?
BUSINESS READINESS
Can the organisation absorb and implement the proposed change?
GOVERNANCE
Are decisions being made at the speed recovery requires?
UNDERSTAND THE CAUSES
Do not carry the same assumptions into the recovery plan.
Recovery planning should distinguish symptoms from underlying causes.
A missed milestone may reflect unrealistic sequencing.
Repeated forecast increases may indicate incomplete scope understanding.
Testing delays may originate in environment, data or build quality problems.
Vendor delay may expose an unmanaged dependency rather than simply poor supplier performance.
Implementation pressure may reflect business-readiness constraints rather than technology delivery alone.
“If the causes remain unchanged, moving the dates may simply move the problem.”
The objective is to understand conditions and causes, not to assign blame to individuals or teams.
WHAT HAS ACTUALLY CHANGED?
The recovery plan must be based on different conditions.
SCOPE
Has scope been reduced, prioritised or clarified?
TIME
Has sequencing or the implementation approach changed?
FUNDING
Has sufficient funding been committed to the revised approach?
RESOURCES
Has capacity or capability materially changed?
DELIVERY MODEL
Have responsibilities, dependencies or ways of working changed?
GOVERNANCE
Can required decisions now be made more effectively?
If the underlying delivery conditions remain materially unchanged, executives should challenge why the revised outcome is expected to be different.
TEST THE NEW PLAN
Seven tests of a credible recovery plan.
REALISTIC BASELINE
Is the plan based on the actual current position rather than the position the project was expected to have reached?
CLEAR SCOPE
Is there agreement on what will and will not be delivered?
ACHIEVABLE SCHEDULE
Are estimates, dependencies, sequencing and contingency supported by evidence?
CREDIBLE COST
Does the forecast reflect the work, resources and risk remaining?
RESOLVED CONSTRAINTS
Have the issues that undermined the previous plan been addressed?
EXECUTIVE DECISIONS
Are required decisions explicit, owned and capable of being made in time?
IMPLEMENTATION REALITY
Does the plan reflect technology, operational and organisational readiness?
“A recovery plan should be something executives can believe and delivery teams can execute.”
RECOVERY REQUIRES DECISIONS
Some recovery problems cannot be solved inside the project team.
Credible recovery may require executive decisions about:
“Recovery becomes credible when the plan reflects the decisions the organisation is actually prepared to make.”
MORE GOVERNANCE IS NOT ALWAYS THE ANSWER
Control comes from better decisions, not simply more meetings.
When confidence deteriorates, organisations sometimes respond by adding reporting, meetings and governance layers. Additional oversight may be appropriate, but it does not automatically address the delivery problem.
Recovery governance should create clarity around:
WHAT IS TRUE?
Establish the verified delivery position from available evidence.
WHAT MATTERS MOST?
Separate the issues that materially affect recovery from normal project noise.
WHAT MUST CHANGE?
Identify the conditions and decisions required for credible delivery.
WHO MUST DECIDE?
Clarify the decisions executives and governance are accountable for.
WHAT HAPPENS NEXT?
Agree the immediate actions, owners and the evidence that will confirm progress.
LEADING INDICATORS OF RECOVERY
Do not wait for the final milestone to know whether recovery is working.
Executives should look for evidence such as:
Not every project uses the same recovery indicators. The measures should reflect the specific causes and objectives of the recovery.
WHEN INDEPENDENT REVIEW MAY HELP
Recovery plans benefit from independent challenge.
The team developing a recovery plan often has the deepest knowledge of the project. Independent review provides a different function: testing whether the evidence, assumptions and proposed changes collectively support the revised delivery position.
It can be particularly useful where:
Previous replans have not restored confidence
Executive and delivery views differ
Significant additional investment is required
Major scope or implementation decisions are required
Vendor commitments are central to recovery
The organisation needs greater confidence before approving a revised plan
External assurance is not mandatory. Where existing governance can provide sufficient confidence, that may be adequate.
HEALTH CHECK OR PROJECT RECOVERY?
Establish the position, or establish what must change.
PROJECT HEALTH CHECK
Use when executives need to establish the real delivery position before deciding what intervention is required.
Primary question
“What is the real delivery position?”
EXPLORE PROJECT HEALTH CHECKPROJECT RECOVERY
Use when delivery confidence has materially deteriorated and the organisation needs to establish a credible path forward.
Primary question
“What must change to restore credible delivery?”
EXPLORE PROJECT RECOVERYA Health Check can establish the position. Recovery focuses on what must change next.
EXECUTIVE CHECKLIST
Before approving a recovery plan, ask these questions.
If these questions cannot be answered confidently, the recovery plan may require further challenge before becoming the new delivery baseline.
CONCLUSION
Credibility comes from changed conditions, not changed dates.
A credible project recovery plan explains why the previous position became unachievable, establishes the real current position and demonstrates what will materially change.
It connects scope, schedule, cost, resources, dependencies, technology, vendors, readiness and governance into an achievable delivery position.
Most importantly, it makes the decisions and assumptions supporting recovery visible to the executives accountable for the outcome.
“Recovery is not simply replanning. It is resetting the conditions required for credible delivery.”
RELATED INSIGHTS
Continue exploring project recovery and delivery confidence
WRITTEN BY
Andrew McDonald
Founder & Principal, Carpadium
Andrew leads and delivers Carpadium’s independent project and program assurance, health check and recovery engagements, working directly with executives, sponsors and governance forums across the Australian market.
RESTORE DELIVERY CONFIDENCE
If the current plan is no longer credible, establish what needs to change.
Carpadium provides independent Project Recovery support for complex projects and transformations where delivery confidence has materially deteriorated.