Float (Slack)

Float, also called slack, is the breathing room a task has in a project schedule — the amount of time it can start late or run long without pushing back the project's finish date. Every task in a scheduled project sits inside a web of dependencies. Some things cannot begin until others end, and float measures how much a given task can slip before it starts delaying whatever comes after it and, eventually, the whole project. A task with several days of float can wobble within that window harmlessly. A task with zero float has no room at all, so any delay to it delays the project. Float is calculated from the schedule's network by comparing the earliest a task could happen with the latest it could happen without causing harm; the gap between those is its float.

Float is central to how project managers see risk and priority. Tasks with lots of float are flexible. They can absorb a hiccup, be rescheduled to free up people, or wait behind more urgent work. Tasks with little or no float are fragile, and they demand attention because a slip there ripples straight to the deadline. Knowing each task's float lets a manager tell the difference between a delay that matters and one that does not — a late task with a week of float is a shrug, while the same delay on a zero-float task is a fire. This is why float is not just an accounting figure but a management tool. It points attention at the tasks where timing actually controls the outcome and relaxes it where the schedule can bend.

Float and the critical path are two views of the same schedule, tightly linked. The critical path is the longest chain of dependent tasks running through a project, the sequence that determines the shortest possible finish. Its defining feature is that every task on it has zero float, so none of them can slip without extending the whole project. The critical path is therefore exactly the set of tasks with no slack, and float is what separates the critical tasks from the rest. Tasks off the critical path have positive float, so they finish with time to spare relative to when they are actually needed. Put simply, the critical path is where float runs out, which is why identifying float across the schedule is how you find the critical path in the first place.

The distinction guides where effort goes. Compressing the schedule means shortening the critical path, because speeding up a task with float does nothing for the finish date — you are shaving time off something that already had slack. Only accelerating zero-float, critical-path tasks pulls the deadline in. Likewise, protecting the deadline means protecting the critical path, where any slip costs a day for a day. There are also two flavors of float worth separating. Total float is how long a task can slip without delaying the project finish; free float is how long it can slip without delaying even the very next task. A task can have total float but no free float, meaning it can move relative to the project end but not without disturbing its immediate successor. Confusing the two leads to schedules that look flexible but are not.

Using float well means reading the whole schedule through it, not just tracking dates. Watch the zero-float, critical-path tasks most closely, because they govern the finish, and manage tasks with float more loosely, using their slack to level workloads, cover for scarce people, or buffer against risk. When a task with float starts consuming it, treat that as an early warning, because slack disappearing is how a non-critical task quietly becomes critical. Recalculate float as the project changes, since dependencies shift, tasks finish early or late, and today's comfortable float can vanish tomorrow. And distinguish total from free float when you make moves, so that using one task's slack does not unexpectedly delay its successor. Float, watched actively, is a live gauge of where the schedule is tight and where it can give.

The failures come from ignoring float or misreading it. Treating every task as equally urgent wastes attention on tasks that have slack while under-guarding the ones that do not. Assuming float is permanent is dangerous, because it erodes as tasks slip, and a project can drift into trouble as more and more tasks reach zero float and the critical path lengthens. Confusing total float with free float leads to rescheduling that delays successors unexpectedly. And letting float sit unused until it is gone forfeits its value as a buffer, since the point of slack is to absorb surprises, so spending it deliberately beats losing it accidentally. The discipline is to know each task's float, protect the tasks that have none, and treat shrinking float anywhere as a signal that the schedule is tightening.

Float and slack both borrow everyday images of looseness — something floating free, or a rope with slack — applied in mid-twentieth-century critical-path scheduling to spare time in a plan.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where float (slack) is a core concern: