Total float and free float
Total float is the number of working days a task can slip without moving the project's finish date, and free float is the number it can slip without moving the start of any task that follows it.
Updated .
The rule
A forward pass through the links gives each task its early start and early finish. A backward pass from the finish date gives its late start and late finish. Total float is the gap between the two: how much later the task could run and still let the finish date hold.
Free float looks only one step ahead: the working days between the task's early finish and the earliest early start of the tasks that depend on it. It can never be more than total float.
Total float belongs to a chain of tasks, not to each task alone. Use it on one task and every task after it on the same chain has that much less. Microsoft Project calls float slack (Total Slack, Free Slack).
Total float = late start - early start (= late finish - early finish). Free float = days between early finish and the earliest early start of its successors.Worked example
Five tasks, all linked finish to start. A (4 days) comes first. B (2 days) and then C (3 days) follow A on one chain; D (8 days) follows A on the other. E (2 days) needs both C and D. Days are working days counted whole: a task on days 5 to 6 starts on the morning of day 5 and finishes at the end of day 6.
| Task | Duration | Early start | Early finish | Late start | Late finish | Total float | Free float |
|---|---|---|---|---|---|---|---|
| A | 4 days | Day 1 | Day 4 | Day 1 | Day 4 | 0 | 0 |
| B (after A) | 2 days | Day 5 | Day 6 | Day 8 | Day 9 | 3 | 0 |
| C (after B) | 3 days | Day 7 | Day 9 | Day 10 | Day 12 | 3 | 3 |
| D (after A) | 8 days | Day 5 | Day 12 | Day 5 | Day 12 | 0 | 0 |
| E (after C and D) | 2 days | Day 13 | Day 14 | Day 13 | Day 14 | 0 | 0 |
A, D and E have no float: they are the critical path, and the project finishes at the end of day 14. B and C each show 3 days of total float, but it is the same 3 days. B has no free float, because C starts the day after B finishes. C has 3 days of free float, because E cannot start before day 13 anyway.
If B slips 2 days, nothing reaches the finish, but C starts on day 9 and is left with 1 day of float. If B slips 4 days, the finish moves to the end of day 15.
What goes wrong in practice
- Reading each task's total float as its own to spend, when the tasks on one chain share it.
- Tasks with no successor: their float runs all the way to the project finish, so a late task looks months safe. This is what the DCMA high float check (over 44 working days) catches.
- Negative float ignored. It means a deadline or a constraint is already behind the logic, and the plan cannot meet it as it stands.
- Float used up early on easy tasks, so the late, uncertain work has none left.
- Comparing float across calendars: a task on a 4-day-week calendar counts fewer working days than one on 5 days for the same gap.
See this in your own file
Upload an .mpp, .xml or .xer file and see whether it passes the DCMA float checks: at most 5% of open tasks with more than 44 working days of total float, and none below zero.
Check the float in your own scheduleLonger read: Total Float vs Free Float: What Each One Actually Means
Questions
Is slack the same as float?
Yes. Microsoft Project calls it slack (Total Slack and Free Slack); Primavera P6 and most textbooks call it float. The arithmetic is the same.
Can total float be negative?
Yes. When a deadline or a constraint asks for a date earlier than the links allow, the late dates fall before the early dates and total float drops below zero. The DCMA assessment allows no negative float.