What is a schedule recovery plan, and when does an EPC have to file one?

Aerial view of a construction site with steel structural framework and tower cranes under an overcast sky.

What triggers the filing

Most EPC contracts for a refinery turnaround or an LNG train don't leave "recovery schedule" as a vague obligation. The trigger sits in the schedule article, usually tied to float erosion on the critical path. Fall more than a set number of days behind the baseline, often 30, 60, or 90 depending on the contract, and the contractor owes the owner a formal recovery plan within a fixed window after notice. Some contracts tie the trigger to a missed interim milestone instead of raw float on the overall completion date. A contractor can blow a steel-erection milestone by three weeks and still owe a recovery schedule, even if the completion float on the master schedule shows 45 days of cushion on paper.

The recovery schedule itself is a new logic network, not a compressed copy of the baseline with dates moved up. It has to show how the contractor gets back to the planned startup date: added crews, extended shifts, work fronts split and resequenced, procurement accelerated on whatever long-lead item is running behind. A one-page memo saying "we expect to recover in Q3" doesn't meet the bar in a well-drafted contract. Lenders' technical advisors and owner's engineers expect activity-level detail they can trace against the as-built progress curve.

Why the trigger date matters more than the plan's content

Filing a recovery schedule and triggering liquidated damages are two different clocks, and people conflate them. The LD trigger usually keys off mechanical completion or a specific contractual milestone date, separate from the schedule-recovery obligation. Submitting a recovery schedule is a notice requirement. It doesn't stop the LD clock, and it doesn't admit fault, but it is often the first formal document from the contractor that says the baseline is blown, sometimes months before the monthly progress report's headline percentage moves.

That gap is the problem for anyone outside the contract. A trader pricing a feedstock position against a startup date, or a lender holding a completion guarantee, needs to know the real state of the site before the contractor's home office decides how to characterize it in next month's report. Module placement, piping isometrics walked down, structural steel erected: those are things you can check from outside the fence without depending on anyone's S-curve.

Reading the plan against conditions on the ground

A recovery schedule that claims a 15% productivity gain from "enhanced coordination" is a different animal from one that shows a second crane mobilized and a work front physically split in two. The filed document is a commitment the owner can hold the contractor to later, in a claim or a backcharge. Whether it's achievable is a separate question, and it's the one that matters for drawdowns, hedge timing, and offtake scheduling.

That's where an independent progress read earns its place in the file. Comparing monthly imagery of the site against the milestones named in a filed recovery schedule, module by module, pad by pad, gives a lender or a desk a second data point that never passes through the contractor's own reporting chain. Refinery Progress tracks module placement and structure growth from satellite imagery against a project's planned dates, independent of what shows up in the monthly contractor report.

If a contractor says the recovery schedule has the project back on track, the module count and the structural footprint on the ground will say so, or won't, within a month or two. No narrative changes what's actually been bolted down.

Worth checking the physical progress against the next recovery schedule before you take the headline percentage at face value.

Start a project

← Back to the blog