Total float, and the question of who owns it

Float is the most valuable thing on a construction schedule that nobody paid for directly. It is also, on most projects, the asset least likely to be addressed clearly in the contract, which is why the argument about who consumed it tends to arrive at the same time as the argument about who pays for the overrun.

Two kinds of float

Total float is how long an activity can slip before it delays the project completion date. Free float is how long it can slip before it delays its own immediate successor. Free float is always less than or equal to total float, and the gap between them is where a lot of confusion lives.

An activity with twenty days of total float and zero free float can be delayed by twenty days without moving the end date, but it will push every activity behind it the moment it slips by one. That matters enormously to the subcontractor sitting downstream of it, and not at all to the completion date, until the twenty days are gone.

When people argue about float ownership they almost always mean total float. It is the resource that gets spent.

Three positions on ownership

Contracts take one of three positions, sometimes without realizing they have taken one at all.

1. The project owns the float. Float is a shared resource, available to whichever party needs it first, on a first come first served basis. This is the most common default where the contract is silent, and it is the position most US courts have gravitated toward.
2. The owner owns the float. The contractor may not use float to absorb its own delays without permission, and the owner may consume it through changes without granting time. Owners like this clause. It is aggressive, and it tends to encourage contractors to hide float rather than schedule honestly.
3. The contractor owns the float. Float was created by the contractor's own sequencing and means and methods, so it belongs to the contractor, and any owner-caused consumption is compensable. Rare, but it appears.

The first come first served problem

Shared float sounds equitable and creates a perverse incentive. If float belongs to whoever gets there first, then the rational move for both parties is to consume it early, before the other side does. Contractors pad durations to bank it privately. Owners issue changes without time extensions while the cushion still exists.

Both behaviors are individually rational and jointly destructive, because they burn the buffer the project needs later, on the risks nobody forecast. By the time an unforeseen condition shows up in month eighteen, the float that would have absorbed it was spent in month four on things that were entirely foreseeable.

Negative float, and what it really means

When a constrained completion date sits earlier than the calculated finish, the backward pass produces negative float. Minus thirty days on the critical path means the project is calculated to finish thirty days after the date it is contractually required to.

Two things follow. The first is that negative float is a symptom, not a schedule status. It does not mean the contractor is thirty days behind. It means the network, as currently modeled and constrained, does not reach the required date. The second is that a hard constraint applied to force a date will manufacture negative float across an entire path and obscure which activities are genuinely driving. Constraints should be used sparingly and disclosed every time.

What a workable clause looks like

The clauses that survive contact with a real project tend to share four features.

• They define the terms. Total float and free float are stated explicitly, along with the method of calculation and the software the calculation will be performed in.
• They forbid float suppression. No hard constraints, no artificially extended durations, no preferential logic used to conceal available float. Schedules are checked for this on submission rather than argued about later.
• They set a disclosure duty. Any change to logic, calendars or constraints between updates is identified and explained in the narrative. This single requirement prevents more disputes than any other.
• They tie float to the extension of time provision. The clause states what happens to an owner-caused delay that consumes float without moving the completion date, because that is the exact scenario that generates the argument.

The practical position

Whatever the contract says, treat float as a project asset that is being spent whether or not anybody is tracking it. Report float erosion every period alongside progress, because a project that has burned sixty days of float on the near-critical path while remaining nominally on schedule is a project about to have a bad quarter, and the schedule will have said so for months before anyone acted on it.