Learning Center
What Total Float Actually Tells You About Risk
It’s easy to treat total float as a piece of scheduling arithmetic -- a number the software calculates and moves on from. It’s actually one of the more direct risk signals a schedule produces: it says how much room a given path has before something going wrong actually reaches the project finish date. Low float means little room. Float that’s dropping across updates means the room is shrinking. And float that’s unusually high can mean there’s no real room being measured at all.
Low Float Means Low Room for Error
Total float is how many days an activity can slip -- start late, run long, whatever the cause -- before that slip starts eating into the project finish date. An activity with a large float balance can absorb a real hit and the finish date never moves. An activity with a small float balance can’t: even an ordinary, unremarkable delay is enough to push the finish date out by the difference.
Take two fictional activities on the same project, each hit by the same 5-day slip:
| Code | Activity | Total Float | 5-Day Slip | Result |
|---|---|---|---|---|
| X | Elevator installation | 2 d | 5 d | Finish date pushed 3 days |
| Y | Exterior signage | 25 d | 5 d | 20 days of cushion still in reserve |
Elevator installation started with only 2 days of float. The identical 5-day slip that Exterior signage absorbed without any consequence pushes Elevator installation’s path 3 days past what its 2 days of cushion could cover -- and that 3-day overrun goes straight to the project finish date. Exterior signage, with 25 days of float going in, comes out of the same slip with 20 days still in reserve. Same slip, same duration, completely different outcome -- the only difference was how much float each path started with.
Watch the Trend, Not Just the Snapshot
A single update showing healthy, positive float doesn’t tell you whether that float is stable or being steadily consumed. A path can still be technically fine -- float still positive -- while trending downward update after update in a way that will cross zero in a predictable number of months if nothing changes. That downward trend is itself a warning sign worth acting on, well before any activity actually goes negative. For the mechanics of tracking that trend across updates, see the deeper technical dive on float erosion and negative float.
When High Float Is the Red Flag
It’s tempting to read a very large float balance as extra-safe -- lots of room, nothing to worry about. Often it means the opposite: an activity that isn’t genuinely tied to the rest of the network by realistic logic will show enormous float that doesn’t reflect any real slack in the actual work, simply because nothing downstream depends on it the way it should. This is exactly what DCMA 14-point Check 6 looks for -- activities with float well above a commonly used 44-calendar-day threshold, flagged not because a large cushion is inherently bad, but because it’s a common symptom of missing or incomplete logic. Unusually high float is a prompt to check the activity’s relationships, not a reason to relax.
Same Slip, Different Exposure
The diagram below carries the same two fictional activities from the comparison above. Each bar shows the float cushion available; the arrow shows the identical 5-day slip landing on both.
Claims Digger surfaces total float for every activity across every schedule update you upload, making it straightforward to see at a glance which parts of a project currently carry the least room for error -- without cross-referencing float values by hand, activity by activity, update by update. See how it works.
Frequently Asked Questions
- Is total float the same thing as a safety margin the project team planned on purpose?
- Sometimes -- but not always. Float is simply a byproduct of the network logic and durations: how much an activity's start or finish can slip before it affects the project finish date. It can reflect genuine slack the team built in, or it can be an artifact of missing logic that makes an activity look freer than the real work actually allows.
- How much total float counts as "low"?
- There's no single universal number -- it depends on the activity's duration, how far out the finish date is, and how much uncertainty remains in the remaining work. As a rough gut check, float that's smaller than the likely size of an ordinary slip on that activity (a permitting delay, a weather day, a late delivery) is worth watching closely.
- If an activity has zero float, does that mean the project is already late?
- No. Zero float just means that activity is on the critical path -- any slip at all will push the project finish date by the same amount, with no cushion to absorb it. That's different from negative float, which means the network's own logic already shows the project finishing later than a required date.
- Why would a scheduler want a path to have low float?
- Usually they wouldn't choose it directly -- low float is typically a consequence of how tightly activities are sequenced or how close the finish date is being pushed, not a deliberate target. What matters is knowing which paths have little room to spare so they get closer attention as work proceeds.
Part of the Claims Digger Learning Center. Related reading: Float erosion and negative float · The complete DCMA 14-point assessment · Total Float (glossary)