Start from the current forecast
A recovery programme should explain how the team intends to regain time. Begin with a reviewed update, then identify the path that drives completion and the constraints that limit available options. Nexora provides recovery planning within the project-controls workspace.
A target finish date is a goal, not evidence that a scenario is feasible. Review quantities, work fronts, crew availability, safety, inspections and procurement before accepting a compressed programme.
Crashing and fast-tracking change different assumptions
| Option | What changes | Review before acceptance |
|---|---|---|
| Crashing | More capacity or a changed method reduces an activity duration | Achievable output, resource availability, added cost and site congestion |
| Fast-tracking | Work overlaps where the construction sequence allows it | Released work fronts, interface logic, rework risk and approvals |
Use these as engineering options, not automatic rules to apply to every activity. Shortening a non-driving activity may have no effect on project completion.
Worked example: three options for a twelve-day chain
Illustrative example: A takes four days, B five days, and C three days. All three form one critical chain with no other constraints.
- Current forecast: A → B → C, finish-to-start, takes 12 working days.
- Crash B: reducing B from five to four days gives 11 working days, if the extra capacity is achievable.
- Overlap A and B: allowing B to start two days before A finishes gives 10 working days, if the released work front and method justify the overlap.
These are separate illustrative scenarios. Neither is an automatic recommendation. A different path can become critical, and a resource limit can remove the apparent benefit.
Make the recommendation reviewable
- Keep the current updated programme as the scenario reference.
- Document every changed duration, dependency, calendar and resource assumption.
- Compare forecast completion, critical paths and resource peaks.
- Record cost, access, approval and execution risks with the relevant team.
- Obtain project approval before issuing the selected recovery programme.
Use schedule updates to establish the reference forecast. If a delay event also needs assessment, keep the delay analysis and the proposed mitigation clearly documented.
Common questions
Will adding more labour always recover time?
No. Available work fronts, equipment, interfaces and non-labour constraints can limit output. Test the changed duration and resource assumptions.
Is recovery scheduling the same as delay analysis?
No. Recovery compares corrective execution options. Delay analysis assesses the effect of events using a defined programme and method.
Does a compressed schedule guarantee the target date?
No. Review feasibility, resources, approvals and any new critical path before committing to a target.
Explore the workflow in Nexora
Bring a representative work package and review the assumptions with your project team.