Skip to content
Kairos OneBook a demo
Menu
Advanced · 2 min read

Schedule recovery-plan playbook

Convert a missed forecast into specific, resourced, risk-tested actions with measurable recovered days and approval gates.

Working definition

A credible recovery plan explains where each day comes from. It identifies the current controlling and near-critical paths, defines specific changes to sequence, access, shifts, crews, procurement, methods, or decisions, quantifies productivity and cost implications, tests secondary paths and risk, and establishes a weekly measurement plan.

Key takeaways

  • Tie every recovered day to a named operational action.
  • Test the replacement critical path, shared resources, productivity, safety, quality, and risk.
  • Measure commitments weekly and preserve the approved recovery basis separately from the original baseline.
01

Recover execution, not only dates

Reducing remaining durations or removing logic without changing field means and methods does not recover the project. Each modeled day should correspond to an operational action, responsible party, start date, resource commitment, and evidence.

02

Watch the path that replaces the recovered path

Compression often causes another path to become controlling. Use multiple-path and risk analysis to test path convergence, shared resources, congestion, access, safety, quality, and commissioning or closeout constraints.

Develop and govern a recovery plan

Start with a validated current update and factual cause analysis.

Before you start

    1. Validate the current forecast

      Confirm status, data date, logic, calendars, constraints, paths, float, and completion milestone.

      Verify: The delay and controlling path are credible before recovery is modeled.

    2. Identify operational levers

      Workshop sequence, access, decisions, shifts, crews, equipment, procurement, subcontracting, prefabrication, and work packaging with responsible teams.

      Verify: Each candidate has an owner, feasibility basis, start date, cost, and risk.

    3. Model actions transparently

      Apply actions in an analytical copy using explicit activities, logic, calendars, resources, and durations.

      Verify: Date recovery traces to visible model changes.

    4. Challenge secondary effects

      Analyze near-critical paths, resource conflicts, congestion, productivity, safety, quality, cash flow, approvals, and commissioning.

      Verify: The plan remains achievable when parallel constraints are considered.

    5. Approve and measure

      Obtain authority for cost and operational commitments, then track each action and recovered day weekly.

      Verify: Variance from the recovery plan triggers timely escalation and reforecast.

      Field-ready control

      Recovery credibility gate

      • Current update validated
      • Controlling and near-critical paths traced
      • Actions operationally specific
      • Resources and cost committed
      • Productivity basis documented
      • Secondary paths and risk tested
      • Approval obtained
      • Weekly action and recovered-day tracking established

      Common questions

      Should the recovery plan replace the original baseline?

      Normally it should remain a separately approved current or target plan while the original contractual baseline is preserved, unless the contract authorizes a formal baseline replacement.

      Sources and scope

      Follow the reference trail.

      This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

      Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01Recommended PracticesAACE International · checked 2026-08-01