BATTLEHILL PROJECTS / EXAMPLE DOCUMENT
Recovery plan and sponsor decisions
Turn a delivery concern into owned actions, dependencies and explicit trade-offs.
Illustrative example · Fictional scenario · Not a customer document
Illustrative recovery of an implementation whose test entry is blocked by data and environment dependencies. Relative timings are examples, not delivery promises.
| Priority | Action / decision | Owner | Dependency / completion evidence |
|---|---|---|---|
| Immediate | Reconcile supplier and customer milestones. | Programme manager | Workstream owners agree one baseline and the unresolved assumptions. |
| Before test entry | Complete data reconciliation and resolve exceptions. | Data owner | Reconciliation evidence accepted by the business process owner. |
| Sponsor decision | Choose phased scope or revised release date. | Sponsor | Options paper shows effects on cost, risk, capacity and acceptance. |
| Before release | Review readiness, defects and support capacity. | Release authority | Documented go/no-go decision against agreed acceptance criteria. |
What the reader should act on
Decision brief: describe the recommendation, alternatives, business consequence and latest decision point. Record the decision and update the baseline; do not leave an approved change in meeting notes alone.
How this is adapted for an engagement
The recovery baseline is built from the actual critical path, supplier commitments and customer constraints. This example shows the structure of control rather than an assumed recovery duration.