Total Float

Total float, also called total slack, is the amount of time a single activity in a project schedule can be delayed, from its earliest possible start, without delaying the finish date of the whole project. It comes out of the critical-path method, the scheduling technique that maps how activities depend on one another and calculates how much room each one has to move. An activity with three days of total float can start or run up to three days late and the project will still end on time; use up more than that and the whole project slips. Total float is computed from the difference between an activity's late dates and its early dates — how late it can happen versus how early it could. It measures schedule flexibility against the single most important deadline: the end of the project.

Total float matters because it tells a project manager where the schedule is tight and where it has give. Activities with generous total float can absorb delays, be resource-leveled, or wait without endangering delivery; activities with little or none are the ones to watch, protect, and expedite. The activities with zero total float form the critical path — the longest chain of dependent work, where any delay pushes the finish date straight back. Knowing each activity's total float turns a schedule from a flat list of tasks into a map of risk, showing exactly which delays are harmless and which are fatal to the deadline. That is why float is one of the first things an experienced scheduler calculates and one of the last things to erode unnoticed.

Total float and free float are both measures of schedule slack, but they protect different things. Total float is how long an activity can slip without delaying the project's finish date. Free float is how long an activity can slip without delaying the earliest start of the very next activity that depends on it. Free float is therefore the stricter, more local measure — it is the slack an activity has before it starts pushing its immediate successor, not the whole project. An activity can have plenty of total float but zero free float, meaning it can move in the grand scheme yet cannot budge without shoving the next task along. Free float is always less than or equal to total float, never more, because delaying a successor is a smaller sin than delaying the finish.

The distinction is practical, not academic. Use total float to judge risk to the deadline — which delays threaten delivery. Use free float to judge risk to the flow of work — which delays ripple into the next task even if the deadline survives. A manager smoothing resources leans on free float, because moving an activity within its free float disturbs nothing downstream. A manager fighting to hit a date leans on total float, because that is the buffer against the finish slipping. Confusing the two leads to false comfort: an activity with total float but no free float looks flexible against the deadline yet cannot move a day without disrupting its successor. Reading both together shows exactly how much and what kind of room each activity really has.

Use total float to focus attention where the schedule is most fragile. Calculate it across the network, identify the critical path where total float is zero, and give those activities the tightest management — the clearest ownership, the closest tracking, the first call on resources. Treat float on non-critical activities as a buffer to be spent deliberately, not squandered by drift, because near-critical paths with little float can become critical the moment they slip. Watch float trends over time: shrinking total float on a path is an early warning that the deadline is under threat, often before any activity is formally late. And when leveling resources or resequencing work, move activities within their float where possible so the finish date is protected. Total float, monitored, is a live gauge of schedule health rather than a one-time calculation.

The failure modes are treating float as free money and letting non-critical activities drift until their float is gone and they turn critical; ignoring near-critical paths whose thin float makes them the next threat; and confusing total float with free float, so a manager assumes an activity can move freely when shifting it disrupts the next task. It is also a mistake to calculate float once and never revisit it, since every actual delay reshapes the network. The discipline is to compute float across the whole schedule, protect the zero-float critical path, spend float on other paths consciously, and recompute as reality changes — so total float stays an accurate map of which delays the project can absorb and which will push the finish date back.

Total float — the time an activity can slip without delaying the project's finish — comes from the critical-path method and is distinct from the stricter free float.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where total float is a core concern: