Capability
Recovery Scheduling
Recast remaining logic when the current path is no longer credible — options with time consequences, not a new slide date.
C02 — The problem
The technical problem
When a programme is late, the usual response is a new target date without a new sequence. Remaining work is compressed with lags and constraints until the bar lands on the old milestone.
Recovery Scheduling starts from remaining scope and remaining logic, then tests alternative sequences, resources, or work fronts that could change completion. Each option has time consequences that cost and commercial teams can price. It is not a claim for acceleration (that is a Claims assignment) and not a routine look-ahead (Short-Term Planning).
C03 — Engagement
When this capability is needed
-
01
Forecast breach
Completion or a contractual milestone is no longer achievable on the current path.
-
02
Instruction to recover
The employer or contractor requires a recovered programme.
-
03
After major change
Remaining works need a new sequence, not a painted date.
-
04
Before commercial negotiation
Parties need options, not a single unexplained crash.
C04 — Scope / method
How the work is approached
Options for remaining work: re-sequence, alternative work fronts, overtime or additional resources as scenarios — each with time effect. Commercial entitlement to acceleration or prolongation is out of scope unless separately instructed under Claims.
-
01
Freeze remaining scope
What is left to do, on current evidence.
-
02
Explain why the current path fails
Driving work, constraints, and interfaces.
-
03
Build recovery options
Sequence and resource scenarios, not slogan dates.
-
04
Compare time consequences
Effect on completion and intermediate milestones.
-
05
Recommend an implementable path
What would have to be instructed for the option to be real.
C05 — Outputs
Typical deliverables
| Output | What it contains |
|---|---|
| Recovery programme options | Alternative remaining-work files or fragments. |
| Comparison of time consequences | Dates and driving logic per option. |
| Implementation notes | Instructions, interfaces, and assumptions each option needs. |
| Narrative | Why the current path fails and what each option changes. |
C06 — Decision value
What this work is used to decide
Which recovery option to instruct, reject, or take into commercial discussion. Selecting an option does not guarantee the date it shows.
C08 — Project environments
Relevant project environments
C09 — Who we support
Who commonly needs this capability
C10 — Boundaries
Important distinctions
Recovery scheduling is planning, not an acceleration claim and not legal advice on who pays for the recovery.
C11 — Next step
Discuss your project
If this is the technical problem you are facing, talk to Value Construction about the work, the records required, and what you would receive. Outcomes are not guaranteed.