Programme recovery assurance tests whether a recovery plan has changed the conditions that caused delivery to fail, rather than simply changing dates, actions and reporting.
Enigma provides independent client-side programme recovery assurance for technology programmes where reported progress, supplier recovery claims or revised milestones need evidence-based challenge. The purpose is to give accountable client governance a defensible view of whether delivery capability is actually being restored.
When programme recovery assurance is needed
- Milestones have moved repeatedly and the revised plan depends on assumptions that have not been demonstrated.
- A supplier has presented a recovery plan but the client lacks an independent basis for judging its credibility.
- Actions and governance activity are increasing while the programme-level critical path remains exposed.
- Defect closure, testing, migration, architecture or business availability assumptions are carrying material schedule risk.
- Individual workstreams report progress but dependencies between them remain unresolved.
- The programme board must decide whether to continue, intervene, re-scope, condition further investment or accept a revised delivery commitment.
The buyer problem
A recovery plan can create the appearance of control without restoring deliverability. More meetings, more actions and a new baseline do not by themselves demonstrate that the constraints which caused the failure have changed.
The client therefore needs to distinguish activity from risk reduction. Enigma’s Programme Health Checks and Recovery service provides the broader recovery context. Independent recovery assurance focuses specifically on whether the evidence supports the revised delivery position and the next client decision.
What Enigma examines
- Recovery hypothesis: whether the plan identifies the actual causes of delivery failure and addresses them.
- Schedule logic: whether revised dates are supported by credible sequencing, dependencies, resource assumptions and remaining work.
- Supplier commitments: whether commitments are specific, owned, measurable and supported by delivery evidence.
- Testing and defects: whether quality exposure and closure assumptions support the recovery timeline.
- Data and migration: whether migration, reconciliation and exception handling can be completed within the proposed recovery path.
- Architecture and interfaces: whether unresolved technical dependencies remain on the critical path.
- Business capacity: whether client decisions, subject-matter expertise, UAT and operational preparation are realistically available when required.
- Governance: whether decision latency, escalation and ownership are helping or obstructing recovery.
Where the dominant exposure is supplier performance, see Independent Supplier Challenge for Technology Programmes. Quality evidence is addressed through Quality and Test Assurance, while migration and deployment exposure is addressed through Data Migration and Cutover Assurance.
Recovery claims must be evidenced
Enigma applies the Evidence Sufficiency Standard to the claims on which the revised plan depends. A recovery action is not treated as effective because it has been completed. The evidence must show that the underlying constraint, exposure or dependency has changed.
The Closure Verification Standard is particularly important in recovery. Closing an action without verifying the outcome allows the programme to reproduce the same risk under a new baseline.
From recovery plan to decision conditions
Where recovery is possible but material evidence remains incomplete, the Decision Condition Framework converts uncertainty into explicit conditions. Each condition identifies what must become true, the evidence required, ownership, timing and closure authority.
This allows a programme board to distinguish between risks it can consciously accept and conditions that must be resolved before further commitment.
Typical evidence requested
- the integrated recovery plan and critical-path logic;
- dependency and assumption records;
- supplier commitments and delivery forecasts;
- test progress, coverage and defect evidence;
- migration rehearsal and reconciliation evidence;
- architecture and interface decisions;
- resource and business-availability assumptions;
- RAID, decision and change records;
- prior recovery actions and evidence of verified closure.
The Supplier Evidence Request Checklist and Programme Board Evidence Checklist provide practical starting points for assembling that evidence.
What the client receives
- an independent view of whether the recovery plan is internally coherent and evidenced;
- the material constraints that remain unresolved;
- unsupported assumptions and dependencies that could invalidate revised dates;
- an assessment of whether recovery actions are reducing risk;
- explicit decision conditions where progression remains conditional;
- a clear basis for client governance to continue, intervene, re-scope or withhold acceptance.
Independence boundary
Enigma does not take ownership of the recovery plan and then independently assure its own work. Delivery ownership remains with the programme and its suppliers. The assurance mandate, reporting route and conflict boundary are defined through the Assurance Mandate and Independence and Conflict Standard.
When to commission the review
The useful point is before the revised recovery position becomes another committed baseline. Independent challenge has greatest value while the client can still alter scope, sequencing, supplier commitments, acceptance conditions or investment decisions.
Engagement structures are described in Engagement Models. The wider assurance method is set out in How We Assure.