Slack Time Calculator
Calculate the float time available in a project schedule, compare earliest and latest allowable dates, and see how much buffer remains before a deadline is at risk.
Find the schedule buffer before a task becomes late
A slack time calculator measures how long a task or project activity can be delayed without delaying a project deadline. In project management, slack time is also called float time.
Use the earliest start and latest start, or the earliest finish and latest finish, to calculate the available project buffer. If you know task duration, you can also calculate slack from the time between earliest start and latest finish.
Slack time
--
--
Equivalent hours
--
Slack days multiplied by workday hours.
Buffer remaining
--
After planned delay is used.
Schedule status
--
Based on remaining buffer.
Latest safe date
--
The latest selected start or finish date.
Slack time breakdown
Review the date difference, delay used, and remaining float.
| Metric | Result | Meaning |
|---|
Planning note: A zero-slack activity is usually treated as critical because any delay can affect the project finish date. Positive slack gives the project team scheduling flexibility.
How to use the slack time calculator
- Choose the date basis: Use start dates if you know earliest and latest start, or finish dates if you know earliest and latest finish.
- Enter the earliest date: This is the first date the task can start or finish according to the schedule.
- Enter the latest date: This is the last date the task can start or finish without pushing the deadline.
- Select calendar or business days: Use business days when weekends are not working days.
- Add planned delay if useful: The calculator subtracts that delay from the total slack to show remaining buffer.
Slack time formula
The basic slack time formula subtracts the earliest allowed timing from the latest allowed timing. Another common method subtracts task duration from the time between the earliest start and latest finish. If the result is positive, the task has schedule float. If the result is zero, the task has no buffer.
Slack time = latest start time - earliest start time
Slack time = latest finish time - earliest finish time
Slack time = latest finish - earliest start - task duration
Remaining buffer = slack time - planned delay
For example, if a task can start on July 1 but may start as late as July 8 without affecting the deadline, it has 7 calendar days of slack time.
Slack time vs free float vs total float
Project schedules often use similar words for different kinds of buffer. Knowing the difference helps you decide whether a delay affects only one handoff or the entire project deadline.
| Term | What it measures | Best use |
|---|---|---|
| Slack time | General schedule buffer between the earliest and latest allowed timing. | Quickly estimate whether a task can absorb delay. |
| Free float | Delay allowed before the next dependent activity is affected. | Protect handoffs between teams or sequential tasks. |
| Total float | Delay allowed before the overall project finish date is affected. | Prioritize critical-path and deadline risk decisions. |
Scheduling procedure reference: Carnegie Mellon University - Fundamental Scheduling Procedures.
Worked examples
Use these examples to check the formula before applying it to your own project schedule.
| Scenario | Calculation | Slack time |
|---|---|---|
| Earliest start July 1, latest start July 8 | July 8 - July 1 | 7 calendar days |
| Earliest finish Monday, latest finish Friday | Friday - Monday | 4 business days |
| Slack is 6 days and planned delay is 2 days | 6 - 2 | 4 days remaining |
How to interpret your slack time result
The number is most useful when it leads to a scheduling decision. Compare your calculated slack with the size of the remaining work, review cycles, approval time, and known project risks.
Comfortable buffer
If slack is larger than the likely delay, the activity can usually move without immediate deadline pressure. Keep it visible, because borrowed buffer can disappear quickly.
Tight buffer
If slack is only one or two working days, confirm dependencies, approvals, and resource availability before treating the schedule as safe.
Zero slack
A zero result means the task has no timing cushion. Put it on the watch list and communicate changes early.
Negative slack
Negative slack shows the current plan is later than the allowed schedule. Recovery may require resequencing, extra capacity, reduced scope, or a changed deadline.
Slack time and the critical path
Slack time is most useful when it is tied to dependencies. A task with no slack is usually on the critical path, while a task with positive slack can move without immediately changing the project finish date.
Positive slack
The task can be delayed by the calculated amount before it affects the next task or final deadline.
Zero slack
The task has no schedule buffer. Any delay needs attention because the project timeline may slip.
Negative slack
The schedule is already beyond the allowable window. The plan needs recovery, scope adjustment, or extra capacity.
Critical path reference: Microsoft Support - Show the critical path of your project.
Before you trust the slack time number
A slack calculation is only as reliable as the schedule assumptions behind it. Use this checklist before you make staffing, deadline, or escalation decisions from the result.
Check calendars and non-working days
A task can look safer in calendar days than it really is if weekends, holidays, team leave, or part-time availability are not reflected.
Confirm dependency logic
Slack changes when a predecessor, successor, approval gate, or external vendor date changes. Recalculate after dependency updates.
Separate task duration from slack
Slack is not extra work time. It is the allowable delay around the planned activity, so long tasks can still have very little buffer.
Update after scope or resource changes
Adding work, changing owners, or moving people between tasks can reduce available float even when the milestone date stays the same.
Schedule assessment reference: U.S. Government Accountability Office - Schedule Assessment Guide.
Interesting Fact
The U.S. Government Accountability Office's Schedule Assessment Guide presents 10 best practices for developing and maintaining a reliable, high-quality project schedule. That is a useful reminder that slack time is not just a quick date subtraction; it depends on solid sequencing, dependency logic, calendars, and risk review. If a project schedule cannot explain how float changes, the team may miss an early warning sign before a deadline slips. Source: U.S. GAO - Schedule Assessment Guide.
Frequently Asked Questions
What is slack time in project management?
Slack time, also called float, is the amount of time a task or activity can move in a project schedule without delaying the deadline or the next dependent handoff. It helps a project manager see where the workflow has flexibility and where the timeline is tight.
How do I calculate slack time?
Use the calculator by comparing the earliest and latest timing for the same task. For a start-based schedule, subtract the earliest start from the latest start; for a finish-based schedule, subtract the earliest finish from the latest finish. If duration is known, you can also subtract task duration from the time between the earliest start and latest finish.
Is slack time the same as float?
In many project management contexts, slack time and float mean the same thing. Both describe available schedule buffer before a task affects a dependency, milestone, or finish date. Some teams separate free float from total float, so check the schedule terms before reporting the number.
What does zero slack time mean?
Zero slack means there is no buffer for delay. A task with zero slack is often on the critical path because any slip may move the project finish date or the next major milestone. It does not always mean the activity is late; it means the timeline has no cushion.
Can slack time be negative?
Yes. Negative slack means the latest start or latest finish allowed by the schedule is earlier than the current planned timing. In practical terms, the project is behind the required deadline and may need recovery action, such as resequencing work, adding resources, removing a constraint, reducing scope, or changing the workflow.
Should I calculate slack time in calendar days or business days?
Use calendar days when work can happen every day or when the deadline is based on a fixed date. Use business days when the team does not normally work weekends. For a formal project schedule, also account for holidays, company closures, resource availability, approval windows, and vendor constraints.
How does slack time help with the critical path?
Slack time helps identify which activities have scheduling flexibility and which dependencies are driving the critical path. Work with zero float usually needs close attention because a delay can push the project finish date, while activities with positive slack may be moved to balance resources, protect milestones, or resolve conflicts.
Does slack time include the duration of the task?
No. Duration is the time needed to complete the work, while slack time is the delay allowed around that activity before another task or final deadline is affected. If you know the earliest start and latest finish, subtract the task duration from that window; a long task can still have little buffer if its start date or finish date is constrained.
Other useful calculators
Disclaimer: This slack time calculator is for planning and educational estimates only. It does not replace a full project schedule, dependency map, critical path analysis, resource plan, or professional project management judgment. Actual slack can change when dependencies, calendars, staffing, approvals, holidays, scope, or deadlines change. Before making deadline, budget, staffing, or contract decisions, verify the dates against your official schedule and confirm whether the calculation should use calendar days, business days, or a custom work calendar.
Last updated: June 28, 2026