Who owns float on a construction schedule decides who pays when something slips. One clause answers it, and on most projects that clause either says nothing or says something the owner has not read.
What float is
Float is the amount of time an activity can slip without delaying the completion date. An activity with fourteen days of float can start two weeks late and the project still finishes on time.
It exists because activities run in parallel. While the critical path is proceeding, other work has room. That room is float, it is real, and it has a value, because whoever gets to consume it avoids paying for a delay.
Total float is the slack against the completion date. Free float is the slack before the next activity is affected. The distinction matters in a claim and rarely matters in a negotiation, where the argument is almost always about total float.
The practical question is not what float is. It is who is entitled to use it. If the owner takes four weeks to approve a submittal on an activity with five weeks of float, has the owner caused a delay? If the contractor then slips on a different activity and the completion date moves, who pays?
The answer is written in one clause, and on many contracts that clause does not exist.
The three positions a contract can take
Float belongs to the project. The most common modern position and the most balanced. Either party may consume float, and a delay is compensable only once the float is exhausted and the completion date actually moves. It rewards whoever gets there first, which in practice is usually the contractor, since the contractor controls the sequence.
Float belongs to the contractor. Any owner caused delay to an activity is treated as compensable even where float exists. This is a strong position for the contractor and it appears more often in contractor drafted schedules than in contractor drafted contracts, because it is easier to build into a schedule than to negotiate into a clause.
Float belongs to the owner. Rare, and usually resisted, because it means the contractor carries the risk of its own sequence having no room in it.
Where the contract is silent, the argument is decided by the schedule and by whatever the parties can show about intent. That is an expensive way to settle a question that one sentence would have settled at signature.
How float gets consumed before anybody notices
Float is not mainly lost to delays. It is absorbed by ordinary process.
Submittal review is the largest consumer. A contract allowing fourteen days for review, on a job with several hundred submittals, consumes a great deal of the room in the early sequence. Where review takes twenty days instead of fourteen, the difference comes straight out of float and nobody logs it.
Owner decisions are the second. Every selection, every approval and every value engineering exercise sits on an activity, and most of them sit on activities with float, which is precisely why they feel unhurried.
Procurement is the third. A package awarded three weeks late does not show as a delay if the activity had four weeks of float, and the float is gone.
By the time a genuine problem arrives, often in the enclosure or fit out sequence, the room that would have absorbed it has been used by a hundred small things. The project then moves from comfortable to critical in a single month, which is how a schedule that reported on track in April reports a claim in June. Whether the date was ever real is the subject of testing whether the completion date is real.
Who owns float on a construction schedule is also a drafting question
The clause is half the answer. The other half is how the schedule was built, and four things are worth checking.
Where the float sits. A schedule showing large float on owner dependent activities and none on contractor activities has made a choice about who absorbs a problem. That choice was made by the party that built it.
Whether constraints are hiding it. Date constraints on activities suppress the calculated float and make a sequence look tighter than it is. A schedule with many hard constraints is not a network, it is a wish list with arrows.
Whether durations are padded. Float distributed inside activity durations rather than shown at the end of the network is float the contractor controls and nobody can see. This is common, it is not improper, and it is worth knowing about.
Whether the critical path makes physical sense. A critical path that runs through an unusual set of activities frequently indicates a logic error rather than a genuine constraint, and logic errors move float around.
A worked example
Illustrative figures. Not taken from any client project and not a quotation.
A twenty two month project. At award the facade package shows thirty one days of total float. The contract is silent on float ownership.
Months three to nine: submittal reviews on facade components average nineteen days against a contractual fourteen. Six submittals, thirty days consumed. The owner defers a glazing color decision twice, consuming a further eleven days on the same path.
Month ten: the facade package now shows negative ten days of float. Nothing was reported as a delay at any point, because at each step the activity still had room.
Month twelve: the subcontractor loses three weeks to a fabrication problem of its own making and issues a claim for twenty one days of extension, arguing that the path was only critical because of owner consumed float.
Both positions are arguable and neither is dishonest. The entire dispute exists because one sentence about float ownership was not in the contract, and because nobody was tracking float consumption monthly, when it was still free to correct.
What to do before you sign
- Find the float ownership clause. If it does not exist, that absence is the finding.
- Agree the position in writing, and understand that float belonging to the project is the normal answer.
- Check the submittal review periods against the number of submittals the job will generate.
- Identify every owner decision on the critical path and every one with less than thirty days of float.
- Count the date constraints in the schedule and ask what each one is for.
- Require float consumption to be reported monthly by path, not just the completion date.
- Require schedule updates to preserve the original logic, so the baseline stays comparable.
Item six is the one that prevents the example above. Float reported monthly turns a slow disappearance into a visible trend, and a trend can be acted on while the room still exists.
Item four is the one owners underestimate. A decision sitting on a path with four weeks of float feels unhurried, and it is, right up to the point where three other things have also consumed that float. Listing those decisions at signature, with the float against each, converts an abstract obligation into a short calendar somebody can be responsible for. It is usually a list of six to ten items on a job of any size, and half of them belong to one person. The scoping options for that reading are in the review packages.
What we do
We read the schedule logic and the float ownership clause together, because neither answers the question alone. The output names every path with thin float, every owner decision sitting on one, and every constraint that is suppressing the calculation, with the contract language that governs each. It is a commercial reading rather than a planning exercise and we do not rebuild the schedule. The work sits in the schedule and procurement risk review.
Questions people ask
If the contract is silent on float, who owns it?
It becomes an argument decided by the schedule and by evidence of intent, which is an expensive way to settle a point one sentence would have covered. Entitlement is a question for your counsel. What is consistent is that the party controlling the sequence is usually better placed in that argument.
Can an owner cause a delay on an activity that has float?
It depends entirely on the float ownership position in the contract. Where float belongs to the project, consuming it is not a compensable delay until the completion date actually moves. Where it belongs to the contractor, the same act can be treated as compensable immediately.
Why does float disappear without anybody reporting a delay?
Because it is consumed in small amounts by ordinary process: submittal reviews running long, decisions deferred, packages awarded late. Each event is individually too small to report and none of them moves the completion date. The cumulative effect only becomes visible when the room has gone.
This is general information about construction contracts and is not legal advice.