What Is Float in a Project Schedule — And How to Stop Misreading It

Ask a room of project managers what float means and most will say "the amount of time an activity can slip before it affects the finish date." That's not wrong, but it's incomplete in ways that cause real problems. Float is calculated, interpreted, and managed differently depending on the type of float, the contract, and the schedule's underlying logic. Misreading it leads to false confidence about schedule health, missed opportunities for recovery, and sometimes serious contractual disputes.

The Two Types of Float You Need to Know

Total Float

Total float is the amount of time an activity can be delayed without delaying the project's contractual completion date (or the nearest constraining milestone). It measures the activity's relationship to the end of the project. If Activity B has 10 days of total float, you can delay that activity by up to 10 days without pushing the overall completion date — assuming everything after it stays on track.

Critical path activities have zero total float: delay them by any amount, and the project end date moves by the same amount. That's what makes them critical. Activities with positive total float have buffer before they become critical — but that buffer is shared across all activities on the same path, not a private reserve for each activity.

Free Float

Free float is the amount of time an activity can be delayed without delaying the early start of any of its immediate successors. It's a narrower measure: the delay headroom before you create a problem for the next activity in the chain, not the whole project.

An activity can have significant total float but zero free float. That means you can absorb delays at the project level, but any delay to this specific activity immediately delays the activity directly following it. If that successor is on the critical path (or near-critical), the free float available is effectively zero regardless of what total float says.

Total float tells you how much time is available before the project end date is threatened. Free float tells you how much time is available before the next activity is threatened. Both matter and neither should be read in isolation.

The High Float Problem

High total float is often treated as evidence of a healthy schedule. It isn't. Unusually high float — activities with 30, 60, or 90+ days of total float deep in a detailed schedule — almost always signals one of three problems:

• Missing logic: activities that should be logically connected are not, so float is artificially inflated by gaps in the network
• Open ends: activities with no successors accumulate float because there's nothing after them to limit the calculation
• Compression at the end: if the schedule has been artificially shortened to meet a deadline by removing float rather than refining logic, activities won't have the float that should be there

A schedule with high float but poor logic doesn't represent an easy project — it represents an incomplete analysis. The float numbers are meaningless if the network isn't faithfully modelling the work sequence.

Negative Float

Negative float means the activity (or the project) is already behind relative to its constraints. It typically appears when a constraint date is set earlier than the calculated early completion — the schedule can't accommodate the constraint without compression or logic changes. Persistent negative float on the critical path means the project cannot deliver on time as currently planned, and no amount of reporting will change that fact without recovery action.

Who Owns the Float?

In contract terms, float ownership is often disputed. Contractors frequently view float as a reserve they can draw on to manage delays without claiming extensions of time. Owners often claim that float belongs to the project and that drawing it down doesn't automatically entitle the contractor to an EOT claim. Different contracts handle this differently.

NEC contracts, for example, generally treat project float as shared. AS/NZS 4300 and some FIDIC forms are less explicit. The practical implication: understand your contract's position on float ownership before treating available float as a private schedule reserve. If a delay event occurs on a near-critical path, whether the owner or contractor "used" the float first can determine whether an EOT is payable.

How to Read Float Correctly

When reviewing a schedule, treat float as a diagnostic signal rather than a comfort measure. These are the right questions to ask:

• Does the critical path trace through the actual controlling work? If everything is critical or nothing is critical, the schedule logic is probably wrong.
• Are there activities with float values that seem unrealistically high? Investigate the logic around them — there are likely missing constraints or open ends.
• What is the near-critical path (activities with 5–15 days of total float)? These are the activities that will become critical if anything slips — they deserve as much monitoring attention as true critical activities.
• Where is free float zero on activities with significant total float? These represent sequencing constraints that don't show up in the headline numbers.

Good schedule analysis isn't about reading a single number. It's about understanding what the float distribution tells you about the quality of the logic and where the real schedule risk sits.