A missed milestone tells you where the schedule broke. It does not tell you how to repair it. Before asking the team to work faster, establish which unfinished work controls the completion date and what is preventing it from moving.
A useful project recovery plan connects the remaining scope to named owners, realistic durations, and decisions that someone has the authority to make. Start with the current facts, even when they conflict with the last status report.
Establish what is actually finished
Review the deliverables with the people who must accept them. “Development complete” might mean the code is written while testing, approvals, training, and release preparation remain open. Those are different states, with different effects on the schedule.
For each major deliverable, record:
- What has been accepted and by whom.
- What remains, including reviews and handoffs.
- Who owns that remaining work.
- What must happen before it can start.
- The evidence supporting the expected finish date.
Use a shared record that the team can update. If two reports disagree, resolve the difference with the owner before using either date in the recovery schedule.
Find the work that controls the date
Map the dependencies between the remaining activities. A late activity matters most when other work cannot proceed until it finishes. Adding people to an unrelated task will not clear that dependency.
Suppose a system launch needs a vendor configuration, a security review, and user testing in that order. If the configuration is incomplete, booking extra user testers does not bring the launch forward. The immediate questions concern the vendor’s remaining work, review availability, and whether any safe preparation can happen in parallel.
This is an illustrative example, not a client result. Its purpose is to make the scheduling decision concrete: spend recovery effort where it can change the finish date.
Put recovery choices in front of the sponsor
A team should not quietly absorb a missed date by assuming overtime or skipping checks. Prepare the available choices and make their consequences visible. Common options include reducing the initial scope, changing the delivery sequence, adding a specific skill, or moving the date.
For each option, state the expected schedule effect, extra cost or capacity needed, quality implications, and the person who can approve it. Where the effect is uncertain, say what must be confirmed before the date becomes a commitment.
The sponsor may choose a smaller first release to protect an external deadline. That choice needs a written boundary: what will be delivered, what will follow, and who accepts the change.
Build the recovery record
Use the following fields as a starting point. Keep actions specific enough that an owner can report completion without interpreting what was meant.
| Field | What to record |
|---|---|
| Deliverable | The result that must be accepted |
| Remaining work | Activities still needed to reach acceptance |
| Owner | One person accountable for the next action |
| Dependency | Work or approval needed before the action starts |
| Decision due | The last responsible date for an approval |
| Recovery date | The revised completion date and its assumptions |
| Evidence | A review, test result, document, or acceptance record |
A recovery date is only credible while its assumptions hold. If vendor availability, scope, or a required approval changes, update the plan and explain the effect rather than carrying forward an obsolete promise.
Report changes and decisions each week
A short recovery review should answer what finished, what moved, what is blocked, and which decision needs attention. Use the same schedule and action record throughout the week so leadership and the delivery team are reading the same version.
Close completed actions. Give new risks an owner. Escalate a decision while there is still time for it to affect the outcome. Meeting frequency can increase around a critical handoff, but another meeting only helps if it resolves something the team cannot resolve alone.
Bring in help when ownership is the constraint
If everyone owns one piece and nobody owns the whole plan, the recovery effort needs an accountable project lead. ALA Consulting Group’s project recovery service covers the working plan, coordination, risk and decision tracking, and leadership reporting.
For a first conversation, bring the committed date, the latest schedule, the unfinished scope, and the decisions still waiting for an owner. Contact ALA Consulting Group to discuss where the project needs support.
Put it to work
Complete and submit the template online, or open the fillable PDF in a new tab to use at your next project conversation. No account is required.