Can a task have total slack but no free slack?

Yes. B in the example can delay without changing the project finish, but it immediately shifts D's earliest start.

Is slack measured in money?

In this scheduling context, it is measured in time.

Does shortening a noncritical task always shorten the project?

No. Another path may still determine completion.

AI Glossary / Graphs and symbolic AI / Intermediate

Slack

Definition

In scheduling, slack is the amount of timing flexibility available to an activity under the schedule's assumptions. In the critical-path context used here, total slack equals latest start minus earliest start, or equivalently latest finish minus earliest finish. It indicates how much an activity can be delayed without delaying the specified project completion.

What it means

A schedule contains dependencies: some activities cannot begin until others finish. Those dependencies create different paths to completion. An activity on a shorter path may have timing flexibility because another path determines the overall finish.
Slack belongs to a calculated schedule, not permanently to the activity. It can change when durations, dependencies, deadlines, calendars, or resource constraints change. This entry follows the supplied glossary's planning meaning. It is separate from a slack variable in optimization and from the communication product named Slack. The same everyday word therefore needs its context stated clearly.

How it works

For a simple finish-to-start dependency network, calculate earliest times in a forward pass. An activity's earliest start is the latest earliest-finish time among its predecessors. Its earliest finish adds its duration.
Then work backward from the required project finish. An activity's latest finish is the earliest latest-start time among its successors, and its latest start subtracts its duration. Total slack is the difference between latest and earliest timing. Free slack is narrower: it measures delay that does not postpone a successor's earliest start. The distinction matters because an activity can use shared path flexibility while shifting its successor.

Three practical examples

A project coordinator can identify tasks whose delays would immediately affect the modeled completion date.
An AI scheduling assistant can flag activities with little remaining flexibility for human review.
A training exercise can show why delaying two tasks on the same path may consume the same shared slack twice.

Think of it this way

Think of two groups traveling to a meeting where everyone must arrive before it begins. The faster group's journey has some timing flexibility because the slower group determines the meeting's earliest start. The analogy is limited because real schedules may involve many merging paths, resource conflicts, working calendars, and uncertain durations.

Worked example

Consider an original project starting at time 0. Task A takes 4 days and precedes C, which takes 3 days. In parallel, task B takes 2 days and precedes D, which takes 2 days. Final task E takes 1 day and requires both C and D to finish. Assume fixed durations, finish-to-start dependencies, and enough resources for parallel work.
The forward pass gives A: 0-4, C: 4-7, B: 0-2, D: 2-4, and E: 7-8. The earliest project finish is day 8. Path A - C - E takes 8 days; B - D - E takes 5.
Working backward from day 8 gives E: latest 7-8; C: latest 4-7; A: latest 0-4; D: latest 5-7; and B: latest 3-5. Total slack is zero for A, C, and E, and 3 days for both B and D.
Those two 3-day values are not independent buffers that can simply be added. If B starts 3 days late, it finishes at day 5 and pushes D to days 5-7, consuming the shorter path's flexibility. Delaying D another 3 days would push E and the project finish later.
B's free slack is 0 because its earliest finish, day 2, equals D's earliest start. D's free slack is 3 because it can finish as late as day 7 without shifting E's earliest start. Thus B has positive total slack but zero free slack.

Illustrative case study

In a fictional case, Hazel Launch uses a dependency schedule for preparing a small website release. A dashboard highlights two activities with three days of total slack each. Their owners initially interpret this as six spare days.
The coordinator reviews the shared path and shows how a delay in the first activity shifts the second. The team updates its handoff dates and recalculates the schedule after changes. The example illustrates interpretation of shared flexibility, not a claim that any real launch met its deadline.

Common misconceptions and mistakes

Slack is not an automatic allowance to delay work, and it is not a probability that a deadline will be met. A deterministic schedule can show positive slack while uncertain durations still create substantial risk.
Total slack and free slack are different. Slack values along one path should not generally be added as independent reserves. Zero-slack activities are critical in the simple unconstrained critical-path model used here, but scheduling software can have additional conventions. Negative slack can indicate that a required finish conflicts with the currently modeled timing.

Business use

For business planning, use slack to identify where timing changes may matter most and to support coordinated resource decisions. Before moving work, check whether the apparent flexibility is shared with dependent tasks or constrained by a specific person, supplier, or calendar.
An AI-generated explanation should name the schedule version, calculation assumptions, and affected successors. Recalculate after material changes rather than repeating an old slack value. Human review remains useful when the dependency model omits informal commitments or when task duration estimates are weak.

Check your understanding

If B starts on day 3 and D follows immediately, when does D finish?

Answer: Day 7. That uses the shorter path's three days of flexibility while allowing E to remain on days 7-8.

Related terms

Critical path
Scheduling
Resource constraint
total float
free float
earliest start
latest start
dependency graph
resource constraints

Learn next

Increase D's duration from 2 to 5 days. The B - D - E path now lasts 8 days, matching A - C - E. Under the same assumptions, both paths are critical and the previous three days of slack disappear.

Sources

Sources: AIMA original glossary context, slack as latest start minus earliest start: https://raw.githubusercontent.com/aimacode/aima-glossary/master/sentences.txt . Hendrickson, Project Management for Construction, fundamental scheduling procedures and activity float: https://www.cmu.edu/cee/projects/PMbook/10_Fundamental_Scheduling_Procedures.html . Microsoft Project documentation, TotalSlack: https://learn.microsoft.com/en-us/office-project/xml-data-interchange/totalslack-element?view=project-client-2016 .

Previous: Skyline operator Next: Slice