What should happen first when a project schedule is delayed?

Validate the status date, actual dates, physical progress, remaining durations, calendars, constraints, resources, and logic. Analysis based on unreliable status data can target the wrong activities.

Should a delayed project overwrite its schedule baseline?

No. Preserve the approved baseline for performance measurement and historical analysis. An authorized revision should retain the original version and document every approved change.

How do crashing and fast tracking differ?

Crashing shortens work by adding resources, overtime, shifts, or expenditure. Fast tracking overlaps activities previously planned in sequence. Crashing increases cost and capacity exposure, while fast tracking increases coordination, interface, rework, and quality exposure.

Why are near-critical paths important?

Near-critical paths have limited float and can become controlling after a small delay, resource conflict, or sequencing change. Reviewing them prevents recovery actions from transferring the delay elsewhere.

What does what-if analysis provide?

It allows the scheduler to test durations, logic, calendars, resources, and constraints in a scenario copy without altering the approved baseline. Options can then be compared for time, cost, feasibility, and risk.

When should schedule compression be rejected?

Reject it when the delay results from inaccurate status or logic, required resources are unavailable, safety or quality controls would weaken, or the apparent time saving does not affect the controlling path.

schedule recoverydelayed project scheduleschedule compression

When the Baseline Breaks: A Controlled Recovery Playbook for Delayed Project Schedules

A commissioning milestone forecast three weeks beyond its approved date does not, by itself, justify overtime, additional crews, or overlapping work.

guide•8/29/2026•6 min read

When the Baseline Breaks: A Controlled Recovery Playbook for Delayed Project Schedules editorial illustration

Schedule recovery starts with a reliable explanation of the delay. A commissioning milestone forecast three weeks beyond its approved date does not, by itself, justify overtime, additional crews, or overlapping work. The project controls specialist first determines whether the variance reflects actual production performance, an inaccurate status update, or a weakness in the schedule model.

For example, a construction package may show installation as nearly complete while equipment testing remains unfinished. The reported percentage may describe installed quantity, whereas the milestone depends on testing, documentation, client acceptance, and release of the operating area. Treating the percentage as a direct measure of time remaining would produce an optimistic schedule forecast.

Step 1: Establish the variance fact pattern

Use one agreed reporting cut-off for the analysis and obtain status from the people accountable for the work. Compare planned dates, actual performance, and the latest forecast at activity and milestone level. The comparison should identify not only that the finish moved, but also where the movement entered the network and whether it propagates through required successor work.

Classify the source of movement

Execution variance: Productivity, access, material availability, rework, or another field condition has caused the work to take longer than planned.
Progress-recording variance: An actual start, actual finish, or progress claim was entered incorrectly or does not match objective delivery evidence.
Forecast variance: The remaining duration no longer reflects the effort required to complete the unfinished scope.
Model variance: Relationships, constraints, calendars, or calculation settings produce dates that do not represent the intended execution strategy.

This classification matters because the remedies differ. A productivity loss may require a capacity or sequencing study. An incorrect actual date requires data correction. An invalid relationship requires schedule maintenance, not compression. A constrained finish may indicate a legitimate external commitment, but it may also conceal missing logic or an obsolete date restriction.

For each affected work package, record the evidence supporting the current status, the work still outstanding, the person confirming the estimate, and the condition that could change the forecast. A commissioning activity, for instance, should identify pending test scripts, specialist availability, punch-list closure, and acceptance authority rather than rely on a rounded completion percentage.

Separate baseline performance from the live forecast

Retain the approved schedule baseline as the reference for measuring variance. The current schedule is a forecasting instrument: it should show what the team now expects under present conditions, including realistic remaining durations and known impacts. Comparing these two views allows stakeholders to see both the original commitment and the delivery outlook without disguising the slippage.

Where earned value information is available, use it as an additional performance signal rather than a substitute for network analysis. A value-based indicator can suggest that planned work is being achieved while a contractual milestone remains exposed because the remaining work is concentrated near the project finish. The scheduler therefore reconciles progress evidence, activity logic, milestone dates, and commitments before proposing any recovery action.

Schedule recovery entry gate

Proceed to intervention analysis only when the evidence supporting the forecast is complete.

Status integrity

Status date, data date, version, and comparison baseline are recorded.

Progress evidence

Actual dates, physical progress, and remaining work are reconciled with delivery evidence.

Model integrity

Logic, calendars, constraints, resources, and out-of-sequence progress have been reviewed.

Traceability

A dated schedule copy preserves the starting position for scenario testing.

Gate decision: accept the forecast for recovery analysis only after all four controls pass.

Step 2: Confirm the critical and near-critical paths

Recalculate the network and inspect the forward pass, backward pass, total float, and free float. Trace predecessors controlling the delayed milestone through every convergence point. The critical path is the sequence with the least available flexibility under the model settings, not necessarily the most expensive or visible work.

Test whether the displayed path reflects field conditions. Missing logic, excessive constraints, incorrect calendars, stale progress, and resource assumptions can create a misleading driver. Review near-critical paths simultaneously because a small delay, resource conflict, or sequencing change can consume their float and transfer the problem.

Finding	Control response
Critical activity slipped	Validate remaining work and test feasible duration or logic changes.
Near-critical path has limited float	Include it in every recovery and risk scenario.
Negative float appears	Review the target date, constraints, calendars, and network logic.
Forecast moves without new progress	Audit calculation settings, resources, calendars, and status data.

Step 3: Assess remaining work and capacity

For each candidate activity, document a normal remaining duration and a realistic accelerated duration. Develop estimates with the personnel performing, inspecting, or accepting the work. Record assumptions concerning additional crews, extended shifts, material release, design information, access, and handoffs.

Then test resource feasibility. A theoretical overlap may be impossible if the required engineer, crane, testing team, or specialist subcontractor is unavailable. Review skills, availability, procurement lead times, shift rules, workspace, supervision, safety, and quality controls. Resource leveling can resolve overallocations but may extend the finish; resource smoothing uses available float without changing resource limits.

Critical-path diagnostic

Use this diagnostic before assigning extra capacity to the displayed path.

1. Trace: Start at the delayed milestone and follow controlling predecessors through every convergence point.
2. Challenge: Check missing logic, artificial constraints, incorrect calendars, stale progress, and calculation settings.
3. Stress-test: Review paths with limited float and test resource conflicts, sequencing changes, and small additional delays.
4. Decide: If the path is validated, model interventions on it while monitoring near-critical paths; otherwise correct the model and repeat the analysis.

Step 4: Evaluate compression through what-if analysis

Build alternatives in a scenario copy, leaving the approved schedule baseline unchanged. Test durations, relationships, calendars, resource assignments, and constraints. Every scenario should quantify recoverable time, incremental cost, feasibility, residual float, and new exposure.

Fast tracking

Fast tracking overlaps activities originally planned in sequence. It can reduce elapsed time without substantial additional labor, but it increases interface, coordination, rework, and quality risk. Use it only when staged design releases, partial handoffs, independent work fronts, and progressive inspections are practical. Deleting a finish-to-start relationship in software is not sufficient; the revised handoff must be executable.

Crashing

Crashing adds crews, overtime, shifts, premium procurement, or other expenditure to shorten controlling work. Compare incremental cost per unit of time saved, while considering congestion, supervision, fatigue, productivity loss, and equipment availability. Crashing a non-critical activity adds cost without improving the finish unless it removes a constraint or protects a near-critical path.

A combined intervention may be appropriate. For example, controlled design and procurement overlap could be paired with a second commissioning team after equipment availability is confirmed. The model must demonstrate that the measures affect the project finish.

Recovery scenario comparison

Compare alternatives in a scenario copy; the approved baseline remains unchanged.

Option	Time mechanism	Primary exposure	Approval evidence
Model correction	Restores a credible forecast.	May recover no time.	Validated status, logic, calendars, and constraints.
Fast tracking	Overlaps selected interfaces.	Rework and coordination.	Defined handoffs, access, safety, and inspections.
Crashing	Adds capacity to controlling work.	Cost, congestion, and fatigue.	Available resources and demonstrated duration benefit.
Combined	Uses selective overlap and capacity.	Compounded complexity.	Integrated testing of dependencies and near-critical paths.

Step 5: Apply schedule risk analysis

A deterministic accelerated finish is not necessarily a reliable finish. Apply schedule risk analysis to preferred scenarios, considering uncertainty in remaining durations, logic, resources, procurement, approvals, and external dates. Quantitative simulation can estimate the probability of meeting the proposed milestone and identify activities contributing most to date exposure.

Assign each material risk an owner, response, trigger, and residual exposure. Fast tracking may generate rework risk; crashing may increase cost, fatigue, and supervision exposure. If the proposed date depends on several unconfirmed assumptions, report it as a conditional forecast.

Step 6: Use integrated change control

Prepare a change request when the intervention affects approved scope, sequence, resources, cost, milestones, or the performance measurement baseline. Include the delay cause, validated status, affected paths, alternatives, assumptions, time and cost effects, risks, decision requirements, and recommendation.

Show the current forecast beside the proposed target. Never overwrite the schedule baseline to conceal variance. Retain the original baseline and document any authorized revision so dates, logic, budgets, and resources remain traceable.

Step 7: Communicate and monitor

Stakeholder schedule communications should reflect decision rights. Executives need milestone variance, recovery probability, cost range, and approval requirements. Delivery teams need revised logic, handoffs, resources, and immediate actions. Customers may need contractual impacts, acceptance dependencies, and confidence levels.

After approval, update only authorized changes, recalculate the network, confirm resource feasibility, issue the new schedule forecast, and monitor assumptions against defined triggers. Recovery is complete when the model is feasible, the intervention is approved, and current performance remains traceable to the baseline.

Further resources

For certification and professional reference, review the PMI Scheduling Professional certification, the PMI standards library, and the PMI project management learning library.

From approved intervention to traceable execution

Recommend
Select the risk-reviewed scenario and state its conditions.
Authorize
Route impacts and alternatives through integrated change control.
Preserve
Retain the original baseline beside any approved revision.
Monitor
Recalculate, check assumptions, and escalate triggered risks.

Resources and source links

David Rise

ITIL 4, ITSM, AI and automation content specialist at FindExams

Substack

Medium