How this instrument works
In project scheduling, slack (also called float) measures how much breathing room a task has: how many days its start can slip without pushing back the project's overall completion date. It's one of the core outputs of the Critical Path Method (CPM), a scheduling technique developed in the 1950s that's still the backbone of modern project-management software, from simple Gantt charts to enterprise planning tools.
Every task in a CPM schedule has two computed start dates: the earliest start (EST) — the soonest it could begin, based on when its prerequisite tasks finish — and the latest start (LST) — the latest it could begin without delaying the project, worked backward from the deadline. Slack is simply the gap between them: SL = LST − EST. A task with zero slack has no scheduling cushion at all; delay it by even a day and the whole project slips with it.
Tasks with zero slack sit on what's called the critical path — the sequence of dependent tasks that together determine the shortest possible project duration, and the reason project managers watch critical-path tasks most closely. Tasks with slack, by contrast, have flexibility: a task with 7 days of slack could start up to a week late, or run a week over, without threatening the deadline, which is exactly the kind of information this calculator surfaces from two dates you likely already have from your project schedule.
- Identify the task's earliest possible start — count it as days from your project's official start date (day 0).
- Identify the task's latest possible start — the last day it could begin without delaying the project deadline, also as days from project start.
- Enter both values into the calculator.
- Read Slack (days) — the scheduling flexibility this task has before it becomes time-critical.
- A result of 0 means the task sits on the critical path; watch it closely, since any delay there delays the whole project.
Worked example — a task with a week of scheduling cushion
A task in a construction schedule could earliest start on day 5 (as soon as its prerequisite foundation work wraps up), but the overall project timeline only requires it to start by day 12 at the latest without delaying the final handover date. Slack = 12 − 5 = 7 days.
That 7-day slack tells the project manager this task isn't urgent: it can be delayed by up to a week — due to a materials shipment running late, a scheduling conflict with the crew, or simply reordering the week's work — without threatening the project's completion date. Contrast that with a task showing 0 slack: any delay there, even by a single day, pushes the entire project's finish date back by the same amount.
Questions
What's the difference between slack and float?
Nothing — they're the same concept under two names, both meaning the amount of scheduling flexibility a task has before it starts affecting the project deadline. "Float" is the more traditional Critical Path Method term found in classic project-management literature; "slack" is the more everyday term, and most scheduling software uses them interchangeably.
What does zero slack mean for a task?
Zero slack means the task sits on the critical path — the sequence of dependent tasks whose combined duration determines the shortest possible time the entire project can take. A critical-path task has no scheduling cushion: delaying it by any amount delays the project's finish date by that exact same amount, which is why project managers monitor critical-path tasks far more closely than tasks with slack to spare.
Can a task have negative slack?
Yes, and it's a warning sign — negative slack means a task's earliest possible start is already later than the latest start the project deadline allows, meaning the schedule as currently planned cannot hit its deadline without intervention (adding resources, cutting scope, or extending the deadline itself). It typically shows up after a delay upstream has already pushed a dependent task's earliest start past where it needs to be.
How do I find a task's earliest and latest start dates in the first place?
They come from working through the full project network twice: a forward pass through all tasks and their dependencies computes each task's earliest start and finish (based on when prerequisites can realistically complete), then a backward pass from the project deadline computes each task's latest allowable start and finish. Most project-management software (MS Project, Primavera, and similar tools) calculates both passes automatically once you've entered task durations and dependencies.
Is this the same as the number of days between two calendar dates?
No — slack specifically compares two computed scheduling boundaries for a single task (its earliest and latest allowable start), not the raw distance between any two calendar dates. If you just need the day count between two ordinary dates, use a general date-difference calculator instead; this one is purpose-built for the CPM earliest-start/latest-start comparison.