Total Float vs Free Float: The Difference That Saves Deadlines

Float — slack, in American scheduling practice — is the amount of delay a task can absorb. There are two kinds, and every scheduling argument that ends in a missed date is somewhere downstream of treating them as one number.

The definitions, in plain terms

Worked example

A nine-task website migration, durations in working days. The critical path is A → B → C → E → H → I, and the project runs 33 days.

Why the D row is the whole lesson

Content rewrite (D) shows 3 days of total float and zero free float. A resource manager who sees only the 3 and pulls the writer away for three days has not spent D's slack — it has been spent on the D → G chain. Content load (G) now starts three days late and arrives on day 26 with zero float of its own. The next hiccup anywhere on that chain moves the launch.

• Report total float to leadership: it answers "is the date still safe?"
• Report free float to team leads: it answers "can I move this person this week without hurting anyone?"
• Track chain float, not task float — the 3 days on D and G is one pool of 3 days, not 6.
• Watch for negative total float; it means a constraint or deadline is already unachievable and the plan is fiction.

How to use float deliberately

1. 1Recalculate early and late dates after every actuals update, not monthly.
2. 2Publish a float column next to every task in your status report; a schedule without float is a picture.
3. 3Assign float ownership: the PM releases total float, team leads may spend free float.
4. 4Before crashing anything, confirm it sits on the critical path — resources added to a task with float buy nothing.
5. 5Log every float consumption; a steady drain is the earliest reliable slip signal you will get.