What is float in an EPC construction schedule, and why lenders track it

If you've sat through an EPC monthly progress review, you've heard the scheduler say some version of "that activity has two weeks of float, so we're fine." Lenders and traders who track these calls for a living know that sentence can mean two very different things: there's genuinely slack in the plan, or someone is spending float to avoid reporting a slip.
Float, plainly
Float (also called slack) is the amount of time an activity can move, start later, run longer, get delayed by a vendor, without pushing the project's finish date or a contractual milestone. It comes straight out of the critical path method calculation that sits underneath every EPC schedule, whether it's built in Primavera P6 or something homegrown.
Two flavors matter in practice. Free float is how much an activity can slip without affecting the very next activity downstream. Total float is how much it can slip before it starts eating into the overall completion date. An activity sitting on the critical path, by definition, has zero float: any slip there is a day-for-day hit to startup.
Schedule contingency is a different animal and people mix the two up constantly. Contingency is a deliberate reserve, usually a block of days or weeks the project team holds back for unknowns: weather, customs delays, a vendor data package that comes in late. Float is a mechanical byproduct of how activities are sequenced and linked.
You can have a schedule with plenty of float and zero contingency, or the reverse. Lenders ask about both, but they're asking different questions. Float tells you how tight the logic is today. Contingency tells you how much the project team thinks it needs for tomorrow.
Why lenders put float on the watch list
A drawdown schedule, a loan covenant tied to mechanical completion, a hedge book built around a startup quarter, these all assume a date. The contractor's schedule says that date is safe because of X weeks of float on the module fabrication string or the piping tie-in sequence. The problem is that float is the easiest number in the whole schedule to manipulate without technically lying.
A few months of soft logic changes, a resequenced activity here, a relationship flipped from finish-to-start to start-to-start there, and ten days of float can appear on paper without a single bolt going in any faster. Lenders who've been burned before know that float burn rate, how fast the cushion disappears month over month, is often a better leading indicator of trouble than the percent-complete number the contractor reports. A project that's eating two weeks of float every reporting period isn't on schedule anymore, it's borrowing from the schedule to look on schedule.
That's the core of EPC schedule risk from a lender's seat: the trend in the underlying mechanics (float consumption, critical path length, how many activities have migrated onto the critical path since financial close) tells you more than the headline percentage does. A schedule can report 72% complete two quarters running and still be losing a week of float every reporting cycle. That's the project to call about.
The gap between the schedule file and the site
All of this analysis depends on trusting the inputs, and the inputs come from the contractor's own scheduling team. The EPC has every incentive to report progress optimistically and float conservatively, since their own fee and reputation ride on the number. Lenders and traders who want a second opinion need something that doesn't run through the contractor's P6 file at all.
That's the gap Refinery Progress is built around: a monthly, independent read on what's physically going up at site, module placement, structural steel growth, tank shell courses, pulled from high-resolution imagery instead of a status report. It won't tell you the contractor's float number. It will tell you whether the physical progress on the ground still matches the pace that float number assumes, and that's usually the question that matters more.
If your financing or your position depends on a startup date someone else is scheduling, it's worth getting a progress read that doesn't come from their file.