Example 1: ES 2, EF 7, LS 5, LF 10
Total slack = 5 − 2 = 3, and 10 − 7 = 3. The task can start three days late and still finish by its latest finish. These are the mini-calculator defaults.
The subtraction that turns earliest and latest times into slack, and the difference between total float and free float.
Slack, or total float, is how long a task can slip without delaying the project: LS minus ES, which equals LF minus EF. A task with zero slack is critical. Free float is smaller: it is the room before the next task’s earliest start, not before the project end.
Total slack = LS − ES (or LF − EF).
Slack is leftover calendar in a network, not a hint that the estimate was padded. After you have earliest and latest times, slack is a subtraction. If LS is 9 and ES is 6, slack is 3. Spend those 3 days and the project end still holds; spend 4 and it does not.
The mini-calculator above uses the same subtraction as the critical path calculator. For the four times themselves, see how to calculate ES, EF, LS and LF. Slack and float are the same total-float number.
total slack = LS − ES = LF − EF
free float = min(ES of successors) − EF (project end − EF if there is no successor)
If LS − ES and LF − EF disagree, the four times are inconsistent. Recalculate the forward and backward passes rather than averaging them.
Each example uses numbers you can load into the calculator above; the results match the tool exactly.
Total slack = 5 − 2 = 3, and 10 − 7 = 3. The task can start three days late and still finish by its latest finish. These are the mini-calculator defaults.
Task A: ES 0, EF 4, LS 2, LF 6, so total slack = 2. Its only successor has ES = 4. Free float = 4 − 4 = 0. A can slip two days against the project, but any slip immediately pushes the successor. That is how total float can exist with no free float.
Lag is a wait you planned on a link (paint drying). Slack is leftover after the schedule is built. Do not add lag and slack together as if they were the same buffer. See lag and slack.
Spend slack on the task that owns it, once. Two parallel tasks that share a successor cannot both spend the same visible float. Re-run the network after a slip; the critical path calculator will show whether a near-critical chain has become critical.
Total slack is the room a task has against the project end date. Free float is the room it has against the next task’s earliest start. A schedule buffer is extra effort you added on purpose before you built the network. Those three numbers answer different questions. If a reviewer asks “can we slip this by two days?”, the honest answer is: only if free float is at least two days, or if you are willing to eat total slack that other tasks on the same chain also see. If the answer is “we padded every estimate by 20%”, that padding is a buffer, not slack, and the network will still report zero float on the critical path. Keep the three labels separate in status reports so nobody spends the same two days twice. When you do want a named buffer after the network is built, add it as its own task or as a schedule buffer on the estimator, then recompute.
Once a week, recompute ES, EF, LS and LF with actual remaining durations, not the original ones. Tasks that still have five days of slack are not the problem. Tasks that had five and now have one are. A near-critical chain becoming critical is the usual way a “green” Gantt turns red without anyone changing the end date. Pair this check with the overseeing timeline execution routine so slack is not a one-off exam trick.
Subtract earliest start from latest start (or earliest finish from latest finish). The result is total slack, also called total float.
In ordinary usage they are the same total-float number. Free float is the stricter figure against the next task.
The task is critical. Any delay delays the project unless you crash something on the same path.
In a planning network with a fixed end date that is too tight, yes: LS falls before ES. That is a signal to change scope, dates or resources, not a number to hide.
No. Buffer is extra effort you added on purpose. Slack is leftover after you schedule the work you already have.
Build the network, not a single subtraction. Use the critical path calculator so every task gets ES, EF, LS, LF and float together.
Written by Umesh Manral. Formulas checked against the site's test suite on 11 November 2026. Last updated 10 November 2026. Formulas and tests: methodology. Report a calculation error.