B
BRAINBAY

Project Controls · Intelligence · AI

Categories
Recovery

Recovery Plan vs Mitigation Plan: What Is the Difference?

Recovery

Recovery Plan vs Mitigation Plan: What Is the Difference?

11 August 2026 — Christian Ramos

Project team comparing recovery and mitigation actions around a planning table
Recovery and mitigation decisions work best when the team reviews the evidence together. Photo by Vitaly Gariev via Unsplash.

The difference between a recovery plan vs mitigation plan is often blurred in construction correspondence. Both respond to schedule risk, but they are not the same document and they should not be requested for the same reason.

Construction team comparing a recovery plan vs mitigation plan during a project meeting

A mitigation plan is mainly intended to reduce the effect of a current or expected delay. A recovery plan is normally required when the project is already behind an accepted programme and must regain lost time to meet a contractual or management target.

That distinction affects the programme logic, resources, cost, approvals, and the language used in the covering letter.

What is a mitigation plan?

A mitigation plan explains how the contractor will limit the impact of a delay event or emerging risk. It can be prepared before the delay fully affects the completion date.

Typical mitigation measures include:

  • Resequencing activities within available access.
  • Moving crews to an alternative workfront.
  • Expediting technical submissions or material delivery.
  • Splitting large activities into smaller zones.
  • Increasing supervision or improving coordination.
  • Working around an obstruction where it is safe and approved.

Mitigation does not automatically mean the contractor accepts responsibility for the delay. A well-written submission should state the cause, reservation of rights, assumptions, and any support required from other parties.

What is a recovery plan?

A recovery plan is a time-bound programme showing how delayed work will be brought back to a required date. It normally includes measurable changes to production, sequence, working time, or resource levels.

A credible recovery plan should contain:

  1. The approved baseline or latest accepted update used for comparison.
  2. The current data date and actual progress.
  3. The amount of delay to be recovered.
  4. Revised logic and sequencing.
  5. Additional crews, shifts, equipment, or workfronts.
  6. Planned productivity and quantity targets.
  7. Required decisions, access, drawings, materials, and interfaces.
  8. Cost and commercial assumptions.
  9. A monitoring method with weekly targets.

A bar chart with shorter durations is not enough. The programme needs a delivery strategy that site teams can actually execute.

Recovery plan vs mitigation plan at a glance

ItemMitigation planRecovery plan
Main purposeReduce or prevent delay impactRegain time already lost
Typical timingBefore or during a developing delayAfter measurable slippage exists
TargetMinimize forecast movementReturn to a defined completion target
Resource impactMay use existing resourcesOften needs additional resources or shifts
Programme detailFocused on affected activities and alternativesDetailed revised programme and production plan
Cost impactMay be limited or event-specificCan involve acceleration and significant cost
MonitoringRisk actions and near-term milestonesWeekly recovery quantities and time gained

A simple construction example

Assume stone installation cannot start in one area because access has not been handed over.

The mitigation plan may move the crew to another approved zone, bring forward cutting-list preparation, and coordinate alternative deliveries. The intention is to keep resources productive and reduce the delay effect.

If access remains unavailable and the project forecast slips by 30 days, the recovery plan may add a second installation crew, introduce extended working hours, divide areas into parallel workfronts, and set weekly square-metre targets. The intention is to recover the 30 days against a stated target.

Who owns the delay?

Submitting a recovery or mitigation plan should not be treated as an automatic admission of liability. Responsibility depends on the contract, event records, instructions, access, approvals, and the actions of all parties.

The covering letter should clearly state:

  • Why the plan is being submitted.
  • Which dates and information were used.
  • Whether the measures are mitigation, recovery, or instructed acceleration.
  • What third-party actions are required.
  • Whether additional cost or time rights are reserved.

AACE International publishes vetted recommended practices on schedule and cost engineering topics. These references can help teams establish consistent terminology, although the contract remains the first document to check.

How to build a realistic recovery programme

1. Status the schedule honestly

Use verified actual dates, installed quantities, remaining durations, and current access conditions. A recovery plan built on optimistic progress will fail quickly.

2. Find the controlling path

Identify the activities that drive the required completion milestone. Adding resources to non-driving work may improve visible progress without recovering the finish date.

3. Test workable scenarios

Compare resequencing, additional crews, overtime, shift work, prefabrication, alternative logistics, and partial handover. Record the assumptions for each scenario.

4. Validate productivity

For every shortened duration, show the quantity, number of crews, working hours, and output per crew. This makes the plan measurable.

5. Confirm prerequisites

Additional labor is useless without approved drawings, materials, access, lifting support, lighting, permits, and inspections. Connect these requirements to the recovery activities.

6. Establish weekly control

Convert the programme into a two-week look-ahead with owners, quantities, and constraints. Review planned versus actual output at least weekly.

Recovery plan vs mitigation plan: common mistakes

  • Calling every revised schedule a recovery programme.
  • Compressing durations without resource calculations.
  • Removing logic to make the finish date earlier.
  • Ignoring procurement, access, or approval constraints.
  • Promising acceleration before cost and responsibility are agreed.
  • Monitoring overall percentage instead of critical quantities.
  • Failing to update the plan when assumptions change.

Final takeaway

In the recovery plan vs mitigation plan discussion, timing and purpose matter most. Mitigation limits the effect of a risk or delay. Recovery regains measurable lost time against a defined date. Both must be based on current site facts, transparent assumptions, and executable actions.

For help preparing a practical programme and narrative, learn more about my planning experience or send an enquiry.

Frequently asked questions

Is a recovery plan the same as an acceleration plan?

Not always. Recovery may use resequencing and better coordination without major acceleration. Acceleration usually involves measures intended to complete earlier than the current achievable date and may have separate contractual consequences.

Can a mitigation plan protect entitlement to an extension of time?

Mitigation can demonstrate reasonable action to reduce delay, but entitlement depends on the contract, notices, causation, records, and the specific event.

How often should a recovery plan be updated?

Track it weekly and revise it when actual productivity, access, resources, or key assumptions materially change.