On this page
A recovery schedule should explain how remaining work becomes achievable sooner. Shorter durations are outputs of a changed plan: another crew, another work front, a different sequence or an earlier release. Without that explanation, the new finish date is only a target.
First preserve the current forecast. Then create a separately identified recovery scenario so the team can distinguish actual status from proposed intervention.
- 01Inspect the fileDates, logic, calendars
- 02Read the contractEdition, clause, exceptions
- 03Check the fieldSequence, access, resources
- 04Record the decisionOwner, evidence, next action
Diagnose the controlling work
Trace the path to the milestone being recovered. Check nearby paths as well: improving one sequence can expose another as the new limit. Confirm calendars, constraints, actual progress and remaining durations before comparing options.
For a fictional project, electrical installation needs ten days while a parallel controls path needs nine. Reducing electrical installation to seven days does not necessarily recover three days at the shared finish. If both paths start together and drive the same finish, the nine-day controls path now governs, producing only one day of improvement under these assumptions.
Compare options the field can execute
| Option | Evidence needed | Common dependency |
|---|---|---|
| Add a crew | Available people, supervision and production basis | Separate work fronts |
| Add shifts or weekends | Approved working pattern and support coverage | Inspections, access and deliveries |
| Resequence areas | Defined handoffs and temporary conditions | Safety and coordination review |
| Expedite procurement | Supplier commitment and release requirements | Design decisions and shipping |
| Change installation method | Technical review and production assumptions | Equipment and approval availability |
Treat these as options to evaluate, not recommendations that every project should adopt. More workers do not automatically create proportional output in a congested space.
Record the assumptions behind the benefit
For each scenario retain the baseline forecast, modified inputs, recalculation settings, resulting milestone dates, implementation owner and unresolved conditions. State units when reporting recovered time. Keep cost and feasibility evaluation alongside the date comparison.
Mark an option proposed until the necessary parties have committed. A six-day calendar should not appear as the operating plan while Saturday access is still undecided.
Review implementation after the decision
At the next update, compare planned recovery measures with what actually occurred. Did the extra crew mobilize? Was the work front available? Did the expedited equipment arrive? Retain the evidence and update remaining work from observed progress.
Recovery, acceleration and entitlement are different questions. Document the instruction and applicable contract process when changes to working methods or compensation are at issue. The SCL Delay and Disruption Protocol offers further discussion of mitigation and acceleration; project-specific obligations need their own review.
Continue with calendar changes, float and the Schedule Forensics resource library.
Share this article