Recovering a date is valuable only when the benefit of time regained exceeds the cost, risk and disruption created by the recovery.
When a project falls behind, leadership pressure concentrates quickly. Add resources. Work weekends. Start construction before design is finished. Remove non-essential activities. Find a way to recover the date.
Urgency can be appropriate. Delay may threaten revenue, public commitments, shutdown windows, contractual obligations or dependent programs. But acceleration is not a purely technical response. It changes cost, quality exposure, resource allocation and sometimes the solution itself.
The question is not “How do we return to baseline?” It is “Which response now creates the greatest enterprise value?”
The Strategic Context
Schedule compression usually takes two recognised forms, consistent with established project-scheduling practice.
Crashing adds or changes resources, methods or working arrangements to reduce duration, normally at additional direct cost.
Fast-tracking overlaps work that was previously sequential, normally increasing coordination, rework or execution risk.
Projects may also resequence work, change scope, use modularisation, revise procurement, change technical solutions or accept a later date. Each option creates a different distribution of value and risk.
Compression should begin with a current, credible schedule. Acting on a historical critical path can spend money on activities that no longer control completion.
What Leaders Commonly Misread
The first misreading is that all delay must be recovered. Some dates are valuable; others are inherited targets with little remaining economic significance. Recovery can cost more than lateness.
The second is that more resources always create speed. Work may be physically indivisible, specialist-constrained or coordination-intensive. Additional people can reduce productivity or create rework.
The third is that only critical activities matter. Compressing non-critical work normally does not improve the finish date, but near-critical paths and shared resources can change after each intervention. Recovery must be recalculated iteratively.
The fourth is that fast-tracking simply saves time. Overlap transfers work downstream before upstream uncertainty is resolved. The schedule shortens by accepting a greater probability that completed work must be revised.
Reframing the Issue
Recovery is an investment choice among alternative futures:
- spend more to preserve the date;
- accept more execution risk to preserve the date;
- reduce scope to protect the most valuable outcome;
- move the date and protect quality or cost;
- change the delivery model; or
- stop when the remaining value no longer justifies commitment.
The choice should be based on incremental consequences from today, not the sunk cost or embarrassment of missing the original plan.
Related article: The Critical Path Is a Forecast, Not a Promise
Diagnose Before Accelerating
Schedule variance is a symptom. Recovery depends on cause.
Common causes include:
- incomplete scope or late requirements;
- unrealistic duration estimates;
- missing dependencies;
- unavailable resources or materials;
- slow decisions and approvals;
- design quality problems;
- supplier underperformance;
- excessive work in progress;
- technical failure; and
- ungoverned change.
Adding labour to a delayed decision will not help. Fast-tracking work based on unstable requirements may amplify the underlying problem. Recovery should address the constraint that is producing delay, not merely increase activity around it.
Crashing Requires Marginal Analysis
Crashing should compare the incremental cost of reducing an activity’s duration. If Activity A can be shortened by two weeks for $100,000 and Activity B by one week for $20,000, B appears attractive—but only if it is on a path controlling completion.
The analysis must be repeated after each change because critical paths can shift. A project with two parallel paths may require both to be shortened before the final date moves.
Cost also extends beyond overtime or contractor rates. Leaders should consider:
- supervision and coordination;
- productivity loss from congestion;
- quality and safety exposure;
- onboarding time;
- disruption to other projects; and
- downstream operating cost.
The cheapest project-level crash may be expensive at portfolio level if it consumes a specialist needed elsewhere.
Fast-Tracking Purchases Time with Uncertainty
Fast-tracking overlaps activities that would normally be sequential. Examples include beginning procurement before design is fully complete or commencing installation in one area while design continues elsewhere.
The method is rational when interfaces are understood, portions of work are stable and the value of time exceeds expected rework. It is reckless when unresolved decisions affect the work being released.
Before overlapping, teams should define:
- what information is stable;
- what remains uncertain;
- which downstream work could be invalidated;
- the cost and time of credible rework;
- hold points for irreversible commitment; and
- who can stop the overlap when assumptions fail.
Fast-tracking should be governed as a risk decision, not celebrated as urgency.
Scope Reduction Can Be the Stronger Recovery
Teams frequently protect every feature while compressing time and quality. A better response may be to protect the highest-value outcome and defer lower-value scope.
This requires modularity and clear acceptance boundaries. Leaders need to know which components produce standalone value, which are mandatory for safety or compliance and which can be delivered later without expensive rework.
Scope reduction is not automatically failure. It can be disciplined portfolio optimisation when the remaining package produces a stronger return than the original commitment under changed conditions.
Related article: Scope Is an Investment Boundary, Not a Requirements List
Decision Framework
| Option | Primary advantage | Primary exposure |
|---|---|---|
| Crash | Reduces duration without deliberately changing sequence | Additional cost, congestion and resource displacement |
| Fast-track | Gains time through overlap | Rework, interface failure and quality risk |
| Resequence | Uses available workfronts differently | May create inefficient flow or new dependencies |
| Reduce or stage scope | Protects highest-value outcome | Deferred benefits and integration consequences |
| Move the date | Protects cost, quality or safety | Delayed benefit, contractual or reputational impact |
| Stop or redesign | Prevents further low-value expenditure | Transition cost and recognition of loss |
For each alternative, leaders should compare time gained, incremental cost, confidence, risk, resource demand, benefit timing and reversibility.
From Strategy to Execution
Immediate action: Establish the current forecast and constraint. Quantify the value of the threatened date and generate at least three recovery alternatives, including accepting delay.
Medium-term capability: Build recovery playbooks covering commercial options, modularisation, alternative resources, decision escalation and rapid schedule-risk analysis.
Long-term positioning: Govern scarce recovery capacity at portfolio level. Framework contractors, specialist teams and executive decision bandwidth should be directed to the initiatives where recovered time creates the most value.
Signals to Monitor
- Overtime begins before the cause of delay is agreed.
- Recovery actions do not change the forecast completion date.
- The project accelerates work based on unapproved design.
- Quality defects and rework rise after overlap begins.
- Specialists are moved without assessing portfolio consequences.
- The baseline date is defended without quantifying its remaining value.
- Each recovery produces a new critical path that was not considered.
Questions for the Leadership Team
- What is the current constraint producing delay?
- What measurable value is preserved by each week recovered?
- Which option has the best risk-adjusted time gain?
- What downstream work becomes vulnerable if we fast-track?
- Which scope can be staged without destroying the outcome?
- What other initiative pays the price for the resources we redirect?
- At what point should we stop recovering and redesign the commitment?
Closing Perspective
Project recovery is an exercise in judgement under pressure. The original date matters only to the extent that it still protects value, obligation or strategic position.
Leaders demonstrate control when they compare credible choices, confront trade-offs and direct scarce capacity deliberately. Returning to baseline is not the objective. Preserving the best achievable enterprise outcome is.
About the author
Kevin Jogin is Founder & Principal Advisor at EraNorth. Meet the Founder.