# Project recovery plan example: test the option before promising the date

Build a recovery review around the cause, critical dependency, credible options, approval and verification, with a copyable recovery brief.

Canonical: https://project.responseshift.academy/project-recovery-plan/
Publisher: Response Shift
Updated: 2026-10-31

## Start from the current forecast

A recovery plan should explain how a specific action changes the forecast. “Work harder” is not a schedule model. Establish the baseline, current finish, driving dependency and unresolved evidence before selecting an option.

Preserve the actual progress record. If work was reported complete but acceptance is missing, show that distinction. A recovery plan built on overstated completion will fail even if the remaining activities look plausible.

## Worked example: one day beyond the commitment

In the fictional access rollout, configuration takes three extra days. Two days of buffer absorb part of the delay, leaving completion one day beyond the commitment. The team considers three responses.

| Option | What must be true | Trade-off |
| --- | --- | --- |
| Add an installer | A separable activity exists and a qualified person is available | Extra cost; no benefit if configuration remains the bottleneck. |
| Overlap briefing and testing | Briefing does not depend on final test results | Potential rework; do not bypass required acceptance. |
| Move opening by one day | Sponsor and operational stakeholders can accept the impact | Maintains test sequence but changes the commitment. |

## Validate capacity and dependencies

Adding people helps only if the work can be divided and the new person has the access, skills and information to contribute. Ask the activity owner for an estimate with the proposed staffing, including coordination overhead.

Overlapping tasks changes risk. Name which information may change, what rework would follow and who accepts that exposure. A recovery option is not credible merely because the bars fit inside the target date.

## Copyable recovery brief



```text
Baseline / forecast / gap:
Cause and evidence:
Driving dependency and remaining work:
Recovery options / estimated effect / owner:
Capacity and acceptance prerequisites:
Cost, quality and risk trade-offs:
Approval needed / decision date:
First verification checkpoint:
Fallback if the option fails:
```

- [Download the template (Markdown)](https://project.responseshift.academy/project-recovery-plan/project-recovery-plan-template.md)
- [Download the worked example (CSV)](https://project.responseshift.academy/project-recovery-plan/project-recovery-plan-example.csv)

## Set an early falsification point

Choose a checkpoint that will tell you whether recovery is working before all remaining buffer is consumed. For example, require a confirmed crew and completed configuration check by day 5. If the evidence is absent, switch to the agreed fallback.

Do not rebaseline simply to make reporting green. Rebaseline after the authorised decision, preserve the previous version and explain the change to the people who depend on it.

## Continue

[Project practice week](https://project.responseshift.academy/practice-week/)

- [APM: project controls background](https://www.apm.org.uk/resources/what-is-project-management/what-is-project-controls/)
