A credible recovery plan preserves actual progress and then shows the logic, procurement, production, staffing, approvals, milestones, float, and cost behind the new date.

Start with the schedule that explains the current delay

Confirm the approved baseline, current update, data date, calendars, actual starts and finishes, remaining durations, logic changes, constraints, procurement, approvals, milestones, critical and near-critical paths, reported delays, and prior forecasts. The current schedule should reflect what actually occurred before the team creates a recovery scenario.

Identify the variance by activity and cause rather than starting with a desired completion date. Late design, access, permits, utilities, procurement, predecessor work, trade production, rework, change, owner decision, weather, inspection, testing, or another cause can require different action. Responsibility and contractual entitlement are separate questions for the parties and their counsel; the technical review focuses on the available schedule and project evidence.

Make every day of recovery traceable

A recovery plan may change sequence, add crews or shifts, extend work hours, split work areas, revise means and methods, overlap activities, expedite procurement, use alternate materials, accelerate review, resequence inspections, create temporary conditions, or defer nonessential scope where authorized. For each change, show the affected activities, prior and revised duration or logic, required decision date, responsible party, prerequisites, and expected time gain.

Avoid unexplained negative lag, excessive hard constraints, open ends, reduced durations without production support, or new calendars that assume work can occur when access, labor rules, permits, inspections, noise limits, tenant operations, or weather make it unrealistic. The proposed schedule should remain a functioning model of the work—not a graphic that reaches the requested date.

Support production and staffing assumptions

Where recovery depends on increased production, identify quantities, completed production history, remaining quantity, crew composition, equipment, workspace, learning curve, shift handoff, supervision, quality control, safety, material flow, inspections, and the rate required. “Add manpower” is not a complete plan when the workface, equipment, predecessor, or material constraint remains unchanged.

Compare the required rate with recent actual performance and explain what enables the difference. Overtime and multiple shifts can introduce fatigue, congestion, rework, supervision gaps, premium cost, and coordination demands. Those effects do not make acceleration impossible; they belong in the evidence and monitoring plan.

Put procurement, approvals, and turnover in the recovery logic

Long-lead equipment and materials should connect submittal, approval, fabrication, release, testing, shipment, delivery, storage, installation, startup, and acceptance. Record manufacturer or supplier evidence, required deposits, substitutions, utility or agency actions, design decisions, and the last date each step can occur without moving the milestone.

Recovery often fails at the handoffs around physical work. Design responses, change authorization, shop drawing review, mockups, inspections, energization, controls integration, testing, commissioning, owner training, certificates, and turnover documents need logic and owners. A field crew cannot recover time from an approval or equipment path that remains unresolved outside the look-ahead.

Review the critical path, near-critical paths, and float honestly

GAO’s Schedule Assessment Guide describes a reliable schedule as a logic-based model that can show major events, completion dates, and the effect of change. The review should identify the longest or driving path to each material milestone, activities with low float, converging paths, imposed constraints, and whether recovery on one path simply transfers criticality to another.

Float values depend on valid logic, calendars, status, and constraints. Large or suddenly created float can indicate missing relationships, while exhausted float can place a milestone on day-for-day movement. Report the assumptions and schedule quality limits behind the result instead of presenting software-calculated float as an independent fact.

Connect the recovery plan to cost, funding, and follow-through

Identify premium time, added staffing, extended general conditions, supervision, temporary work, expediting, redesign, alternate materials, inspection, testing, incentives, liquidated-damages exposure, tenant or operator costs, and other known or potential consequences. Show whether the cost is included, proposed, disputed, owner-funded, contractor-funded, or dependent on a pending change or contingency decision.

Once approved by the responsible parties, preserve the prior schedule and identify whether the new file is a recovery scenario, a current forecast, or an authorized rebaseline. Monitor key recovery activities at a cadence short enough to see performance: planned and actual quantities, crew, hours, releases, approvals, deliveries, constraints, milestone trend, and missed commitments. The lender needs evidence that the recovery mechanism is working, not only repeated assurance that the final date is unchanged.

Primary sources

Sources and technical references.

Source review current as of September 1, 2026.