Float Analysis in Construction Schedules: What It Tells You and When to Worry

Float is one of the most information-rich signals in a construction schedule — and one of the most misunderstood. This post explains how float works, how to read float values in practice, how to track float movement across updates, and how to know when float consumption is something to act on.

What Float Actually Means

Float — also called slack — is the amount of time an activity can be delayed without delaying the project's scheduled finish date. It is a product of the CPM (Critical Path Method) calculation, not something a scheduler enters manually.

There are two types:

Total float (TF) is the amount of time an activity can be delayed without delaying the project completion date. This is the number most commonly referenced in DCMA assessments and schedule specifications.

Free float (FF) is the amount of time an activity can be delayed without delaying the early start of any of its successor activities. Free float is always less than or equal to total float. An activity can have high total float but zero free float if its immediate successors are constrained.

In Primavera P6, both are stored in hours. When reading a P6 report or comparison output, these values are typically displayed in days after conversion from hours using the activity's assigned calendar.

What Float Values Tell You

Zero or Negative Float — Critical Activities

Activities with total float of zero are on the critical path. Any delay to these activities delays the project. This is the classic critical path definition.

Activities with negative float — total float below zero — indicate that the schedule cannot be executed as currently planned within the contractual end date. The project is mathematically behind. The DCMA 14-point assessment flags any negative float as an immediate concern requiring explanation.

Negative float usually has one of three causes: a hard constraint that cannot be met given the current logic network, a deadline that has slipped relative to the actual progress, or a logic error that is propagating through the network. Understanding which one applies is the first step in addressing it.

Low Positive Float — Near-Critical Activities

Activities with a small positive total float — say, 5 to 15 days — are near-critical. They are not on the critical path today, but they do not have much cushion. One subcontractor delay, one weather event, one long-lead item arriving late, and they become critical.

Experienced schedulers track near-critical activities as carefully as critical ones. The DCMA 14-point assessment does not have a formal threshold for near-critical, but most competent schedulers maintain an informal watch list of activities approaching zero float.

High Float — A Signal Worth Investigating

Activities with very high total float — the DCMA threshold is greater than 44 working days, which is adjustable in Change Inspector — are worth questioning.

High float sometimes reflects legitimate schedule flexibility: a non-critical procurement activity with months of buffer before it is needed. But it often indicates a problem: an activity that is missing a downstream logic link, or an activity that was added to the schedule without being connected to the network.

An activity with 200 days of float and no obvious reason for that buffer has probably lost a successor relationship somewhere. That missing link means the CPM engine does not know this activity needs to finish by a certain date — so it calculates enormous float. Finding and fixing that missing link may eliminate the false float and reveal a real constraint.

Float as a Contractual Asset

Float ownership is one of the more contentious issues in construction contracting. The question is: who owns the float — the contractor or the owner?

Most modern contract language addresses this directly. Many contracts state that project float is a shared resource, meaning neither party can claim it exclusively. Others state that float belongs to the project, not to any one party. Very few contracts allow a contractor to hold float in reserve and refuse to apply it to owner-directed changes.

If your contract has float ownership language, it is worth understanding what it says before a delay event occurs. In a dispute, the analysis of who consumed the float — and when — can be central to the claim.

Tracking Float Across Updates

A single float value at a single point in time tells you less than the trend over time. An activity with 20 days of total float is concerning if it had 45 days last month. It is unremarkable if it has had 20 days for the last six months.

This is why float tracking across multiple updates matters. You want to know:

• Is total float on near-critical activities increasing, stable, or decreasing?
• Which activities are consuming float fastest?
• Are any activities approaching zero that were not near-critical three months ago?

Change Inspector's Float Consumption analysis compares float values between two loaded schedule files and shows the top activities by float consumed — the difference between baseline total float and revised total float — sorted by the most consumed. A warning flag appears for any activity that transitioned from positive float to critical between the two schedules.

This analysis is separate from the 14-point health check. It is a trend tool, not a pass/fail assessment, and it is most useful when run consistently at every update cycle.

When to Escalate a Float Problem

Not every low-float situation requires escalation. Here is a practical guide:

Escalate immediately:

• Any activity with negative float on or near the critical path
• Any contractual milestone with total float under 10 days
• Float consumption of more than 5 days per update on a near-critical activity

Monitor closely:

• Total float below 20 days on any activity in the top three WBS tiers
• Float trending downward consistently for three or more consecutive updates
• High float activities that suddenly show reduced float (may indicate a missing logic link was found and corrected, or a new constraint was added)

Investigate but do not necessarily escalate:

• High float on isolated non-critical activities (may be missing logic, may be legitimate)
• Sudden changes in float across many activities simultaneously (check if schedule options changed)

Float in Claims Context

In a delay claim analysis, float is often central to the dispute. The key questions are:

• How much float existed at the time of the delay event?
• Whose actions consumed the float?
• Did the delay consume float that belonged to the project, or did it directly delay the critical path?

A robust float tracking history — built by running schedule comparisons at every update and recording the results — provides the evidentiary basis for answering these questions. Without it, you are relying on reconstruction after the fact, which is always weaker than contemporaneous documentation.