Float Ownership

1. Why Float Ownership Matters

Float ownership is one of the most heavily litigated and most frequently misunderstood topics in construction scheduling. It sits at the intersection of two CCM domains – Time Management and Contract Administration – because the question who owns the float? determines who absorbs the cost and schedule consequences of delays that do not immediately push the completion date. On a project with a 30-day float path, an owner-caused 20-day delay on that path may cost the owner nothing if float is shared, or may trigger a compensable time extension claim if the contractor is deemed to own the float. The Construction Manager (CM) must understand the concept because the CM typically reviews the baseline schedule, approves updates, evaluates time extension requests, and advises the owner on how the contract allocates schedule risk. Expect the CCM exam to test this topic through scenario-based questions involving delays, time impact analyses, early-completion schedules, and contract clauses.

2. What Float Is

In the Critical Path Method (CPM), float (also called slack) is the amount of time an activity can be delayed without delaying either a successor activity or the project completion date.

• Total Float (TF) = Late Start – Early Start (or Late Finish – Early Finish). It is the amount of time an activity can slip without delaying the project completion date. Activities on the critical path have zero (or the lowest) total float.
• Free Float (FF) = Early Start of the earliest successor – Early Finish of the activity. It is the amount of time an activity can slip without delaying the early start of any successor.
• Project Float (sometimes called terminal float or contract float) = the difference between the contractor's planned early completion and the contractually required completion date.
• Negative Float occurs when the schedule cannot meet a constrained date; it signals that the project is behind and recovery is needed.

Key point for the exam: total float is a path attribute shared by all activities on that path, not a private reserve attached to a single activity. When one activity consumes float, every other activity on that path loses it too. This shared nature is exactly why ownership becomes contentious.

3. What Float Ownership Means

Float ownership refers to the question of which party – owner, contractor, or neither – has the right to consume the float in a CPM schedule without liability to the other party. There are three principal positions:

(a) The Contractor Owns the Float. The contractor argues that float is a product of its means, methods, sequencing, and planning. The contractor built the schedule, created the float by efficient logic, and should be able to use it to manage its own resources, absorb its own inefficiencies, and protect its planned completion. Under this view, when the owner consumes float (e.g., through late submittal reviews or change orders on non-critical paths), the contractor may claim compensation for lost flexibility even if the completion date did not move.

(b) The Owner Owns the Float. The owner argues that it pays for the project, bears the ultimate risk, and is entitled to the time within the contract duration. Float is a contingency within the contract period that the owner may use to make changes or resolve design issues without incurring delay damages. Few contracts adopt this view explicitly, but some owners attempt to reserve it.

(c) The Project Owns the Float (Shared Float / First-Come, First-Served). This is the prevailing industry position and the one most commonly reflected in standard specifications, federal contracting practice, AACE International Recommended Practices, and CMAA guidance. Float is a shared resource that belongs to the project and is available to whichever party needs it first, on a non-discriminatory basis. A delay is compensable (or excusable) only when it consumes all available float and extends the critical path, thereby delaying the contract completion date. Neither party may sequester or hide float for its exclusive use.

4. How Float Ownership Works in Practice

Contract Language Controls. The single most important rule: float ownership is determined by the contract. Many specifications (e.g., federal agency scheduling specs, state DOT specs, ConsensusDocs and many owner-drafted specs) contain a clause such as: 'Float is not for the exclusive use or benefit of either the Owner or the Contractor, but is an expiring resource available to both parties as needed to meet contract milestones and the contract completion date.' If the contract is silent, courts and boards generally default to the shared/project-owned position, and a time extension is granted only when the delay affects the critical path.

Delays and Float Consumption. Under the shared-float approach, a delay is analyzed as follows:
• If a delay consumes only float and the completion date is unaffected, there is generally no time extension and no delay damages.
• If a delay exceeds available float and extends the critical path, the responsible party bears the consequences: an owner-caused critical delay produces an excusable and compensable extension; a contractor-caused critical delay produces liquidated damages or acceleration obligations; a third-party or force majeure critical delay produces an excusable but non-compensable extension.
• Float is an expiring resource: it changes with each schedule update as logic, durations, and actual progress change. Ownership is evaluated at the time the delay occurs (contemporaneous analysis), not at baseline.

Early Completion Schedules. A contractor may submit a baseline schedule showing completion ahead of the contract date. The difference is project float. If the contract does not prohibit early-completion schedules and the schedule is reasonable and achievable, owner-caused delays that push the contractor's planned early finish may be compensable even if the contract completion date is still met – because the contractor's project float was consumed. Many owners counter this by specifying that the schedule must show completion on the contract date, or by stating that project float belongs to the project.

Sequestering Float. Contractors sometimes manipulate schedules to hide float – using preferential logic, artificially long durations, excessive constraints, or lags – so that nearly everything appears critical. This practice, called sequestering float, converts almost any owner delay into a critical delay. The CM's schedule review should identify and reject such tactics: check for unrealistic durations, excessive date constraints, hidden lags, out-of-sequence logic, and a suspiciously high percentage of critical activities.

Concurrent Delay. When both parties cause delays in the same period, float analysis is essential. If one party's delay consumes float while the other's is on the critical path, only the critical delay drives completion. True concurrent critical delays typically result in time but no money (excusable, non-compensable) for the contractor and no liquidated damages for the owner.

Time Impact Analysis (TIA). To determine whether a delay affected the critical path, the CM uses a forward-looking TIA: insert a fragnet representing the delay event into the schedule update current at the time of the event, recalculate, and compare the completion date before and after. If completion does not move, the delay only consumed float; if it moves, the net change is the entitlement.

5. The Construction Manager's Role

• Recommend and enforce a scheduling specification that clearly states float ownership (preferably shared/project-owned).
• Review the baseline for sequestered float, unreasonable constraints, and early-completion claims before acceptance.
• Maintain contemporaneous monthly updates so float availability can be documented at the moment each delay occurs.
• Evaluate time extension requests using critical-path analysis, not merely on whether an owner delay occurred.
• Advise the owner on the risk of consuming float early in the project, since float used early is not available later when owner changes may be needed.
• Document everything: float ownership disputes are resolved on the strength of schedule records.

6. Exam Tips: Answering Questions on Float Ownership

Tip 1 – Default to 'the project owns the float.' Unless the question stem provides specific contract language stating otherwise, the CCM-expected answer is that float is a shared, expiring resource available to whichever party needs it first. Answer choices saying the contractor or owner exclusively owns float are usually distractors.

Tip 2 – Look for the words 'contract' or 'specification.' If a question asks how float ownership should be established or resolved, the best answer almost always points to the contract documents or scheduling specification. The CM's recommended practice is to define float ownership in the contract before the baseline is submitted.

Tip 3 – Tie entitlement to the critical path. When a scenario describes an owner-caused delay, ask yourself: did it consume only float, or did it extend the completion date? No critical path impact = no time extension and no compensation (under shared float). Critical path impact = excusable extension, compensable if owner-caused.

Tip 4 – Know the float definitions cold. Expect direct questions distinguishing total float, free float, and project float, and calculation questions (TF = LS – ES or LF – EF; FF = ES of successor – EF of activity). Remember that critical activities have the least total float, usually zero, and that negative float means the schedule misses a constraint.

Tip 5 – Recognize sequestering float. If a scenario describes a schedule where almost every activity is critical, durations are padded, or many constraints are used, the exam wants you to identify this as hidden or sequestered float and the correct CM action is to reject or require revision of the schedule.

Tip 6 – Early completion = project float. If the question involves a contractor planning to finish early, recognize that the gap is project float, that owner-caused delays to an achievable early-completion plan may be compensable, and that the CM should review the contract to see whether early-completion schedules are permitted or limited.

Tip 7 – Use contemporaneous analysis. When asked how to evaluate whether a delay consumed float, the preferred method is a time impact analysis using the schedule update in effect when the delay occurred, not the original baseline and not an after-the-fact as-built comparison alone.

Tip 8 – Remember 'expiring resource.' Float available early is not guaranteed later. Questions about the owner wanting to 'save' float for future changes should be answered by noting that float cannot be reserved; it belongs to whoever needs it first, and the CM should advise the owner of the risk.

Tip 9 – Eliminate absolutes. Answer choices that say float 'always' belongs to one party, or that any owner delay 'always' entitles the contractor to compensation, are generally wrong. The nuanced answer – ownership depends on the contract, default is shared, entitlement depends on critical path impact – is usually correct.

7. Quick Reference Summary

• Float = schedule flexibility; total float protects completion, free float protects successors, project float is the gap between planned and required completion.
• Three ownership theories: contractor, owner, project (shared). Industry and CCM default: project/shared, first-come first-served.
• Contract language governs; the CM should ensure the spec defines ownership.
• Delay consequences depend on critical path impact, not merely on who caused the delay.
• Watch for sequestered float, early-completion schedules, and concurrent delay.
• Analyze with contemporaneous time impact analysis and document float at the time of each event.

Mastering these principles will prepare you for both the direct-definition questions and the scenario-based judgment questions the CCM exam uses to test float ownership.