Float (Slack) in Project Management
How Float Works
Float is the schedule flexibility available on a non critical path task. It is calculated as the difference between the latest allowable start time and the earliest possible start time for a task: Float = LS minus ES (or equivalently LF minus EF). Tasks on the critical path have zero float. Any delay to a zero float task delays the project. Tasks off the critical path have positive float and can slip by that amount without affecting the end date.
Float is a byproduct of the critical path method’s forward and backward pass calculations. It is not something a project manager creates. It emerges from the dependency network. A task with 5 days of float has 5 days of flexibility because its successors do not need its output until 5 days after it could be finished at its earliest.
Total Float vs Free Float
Total float is the amount a task can be delayed without delaying the project end date. Free float is the amount a task can be delayed without delaying the start of any immediate successor. Free float is always less than or equal to total float. A task can have total float but zero free float, meaning it can slip without affecting the end date but will delay its direct successor.
The distinction matters for resource management. If a task has 10 days of total float, the project manager might choose to delay it to level resource workload. But if that task has zero free float, delaying it will push its successor later (even though the project end date is still safe). The successor’s owner needs to know about the shift.
When to Use Float Information
Float information drives three scheduling decisions. Resource leveling: when the team is overallocated, shift tasks with positive float to less busy periods. Priority management: tasks with zero or near zero float get priority for resources and management attention. Schedule recovery: when the critical path slips, look for parallel tasks with float that can absorb additional scope or resource reallocation.
Near critical tasks (float of 1 to 3 days on a multi month project) deserve almost as much attention as critical path tasks. A small unexpected delay converts them to the critical path, and the project manager loses a safety margin they were counting on.
When Float Is Misleading
Float calculations assume task durations are deterministic. In reality, a task with 5 days of float and high duration uncertainty may effectively have zero usable float because the task might overrun by 5 or more days. Combining float analysis with PERT standard deviations or Monte Carlo criticality indices gives a more realistic picture of schedule risk.
Commonly Confused With
| Term | Key Difference |
|---|---|
| Buffer | A buffer is time intentionally added to the schedule as contingency. Float is schedule flexibility that emerges naturally from the dependency network. Buffers are planned. Float is calculated. |
| Lag | Lag is a deliberate delay between dependent tasks (e.g., wait 2 days for concrete to cure before framing). Float is unintentional flexibility. Lag is a constraint. Float is an opportunity. |
| Critical Path | The critical path is defined by tasks with zero total float. Float is the measure that identifies which tasks are on the critical path (zero float) and which are not (positive float). |