Float Explained: When Can an Activity Slip Without Delaying the Project?
admino
How much scheduling flexibility exists?
An activity finishes three days later than planned.
Does that mean the project is now three days late?
Not necessarily.
The activity may have enough schedule flexibility to absorb the delay without moving the project completion date.
But that does not mean nothing changed.
The project may now have less flexibility available for whatever happens next.
That creates the real PMP® reasoning question:
How much can this activity move before something else is affected?
A useful Project Reasoning Lab principle is:
Float measures schedule flexibility — not permission to ignore delay.
1. What Is Float?
Float represents scheduling flexibility created by the structure of the project network.
It exists because not every activity is on the path that currently controls the project finish date.
Consider two simplified paths:
Path A
A → B → C
Total duration: 20 days
Path B
D → E → F
Total duration: 16 days
If both paths begin together and must be completed before the project can finish, Path A currently controls completion.
Path B therefore has some flexibility relative to Path A.
The key idea is:
Float comes from the relationship between activities and paths — not from adding spare days arbitrarily.
And importantly:
Float is not a management reserve. It emerges from the schedule network itself.
2. What Is Total Float?
Total float is the amount of time an activity can generally be delayed without delaying the project completion date, subject to the schedule’s logic and constraints.
Suppose an activity has:
5 days of total float
If it slips:
- 2 days → some float may remain
- 5 days → available float may be fully consumed
- 7 days → the delay may begin to affect the project finish date
Assuming nothing else changes, a two-day delay would leave about three days of flexibility.
So:
Total float answers: “How much schedule flexibility exists before project completion is affected?”
3. What Is Free Float?
Free float asks a different question.
Free float is the amount of time an activity can generally be delayed without delaying the early start of a successor activity.
The distinction is:
Total float protects the project finish date. Free float protects the next activity’s early start.
An activity may have total float available while having little or no free float.
In that situation, a delay may shift the successor without yet shifting the overall project completion date.
4. Total Float vs. Free Float
| Question | Total Float | Free Float |
|---|---|---|
| What does it protect? | Project finish date | Successor's early start |
| Main question | How long can the activity slip before project completion is affected? | How long can it slip before the next activity is affected? |
| Perspective | Broader path/project | Immediate successor |
| Can it be consumed? | Yes | Yes |
| Can it change? | Yes | Yes |
A simple way to remember it:
Total float looks toward project completion. Free float looks toward the next activity.
5. Float May Be Shared Across a Path
Suppose several activities sit on the same non-critical path.
The path has five days of schedule flexibility.
That does not necessarily mean each activity independently has five days available to use.
If an upstream activity consumes three days, less flexibility may remain for downstream work.
So this reasoning would be wrong:
“Activity A has five days of float and Activity B has five days of float, so together they can slip ten days.”
Not necessarily.
A stronger principle is:
Float can be shared across a path. One activity’s delay can consume flexibility that another activity might otherwise have had.
6. A Delay Within Float Still Changes the Schedule
Consider:
An activity has six days of total float and slips four days.
The project finish date may remain unchanged.
But only about two days of flexibility may remain.
That matters because:
- future delays become harder to absorb,
- the path may become near-critical,
- schedule risk may increase,
- downstream options may become more constrained.
So:
No change to the finish date does not mean no change to schedule risk.
The correct reasoning is:
The delay may be absorbed, but the schedule has become less flexible.
7. Float and the Critical Path
Activities on the critical path typically have little or no usable total float.
But another path can consume its available float and become critical.
Consider:
- Path A = 30 days
- Path B = 26 days
In this simplified example, Path B has about four days of flexibility relative to Path A.
Now Path B experiences a four-day delay:
- Path A = 30 days
- Path B = 30 days
The schedule may now have:
- multiple critical paths,
- a changed critical structure,
- less resilience to further delay.
So:
Consuming float can change what controls the project finish date.
Float is dynamic.
8. Scenario: Total Float Exists, but Free Float Does Not
Consider:
An activity has four days of total float but zero free float.
The activity slips two days.
What happens?
The project finish date may remain unchanged.
But the successor’s early start may move by two days.
This gives us an important distinction:
“Does the next activity move?” and “Does the project finish late?” are different questions.
Free float helps answer the first.
Total float helps answer the second.
9. Float Can Be Fully Consumed
Suppose:
A non-critical path has three days of available float and experiences a three-day delay.
That flexibility may now be gone.
The path may become critical or near-critical.
Any additional delay could place direct pressure on project completion.
So:
Float is not a permanent property. It changes as the schedule changes.
That is why actual performance should be reflected in the schedule network.
10. Negative Float
Negative total float can indicate that the current schedule cannot satisfy a required or imposed date under the existing logic and constraints.
The useful interpretation is:
The current schedule requires recovery or adjustment to meet the applicable date or constraint.
Possible responses may include:
- schedule analysis,
- changed sequencing,
- schedule compression,
- resource adjustments,
- reconsideration of constraints through the appropriate process.
The key is not to treat negative float as “negative spare time.”
It signals that the current schedule and the required date are not aligned.
11. Float Is Not a Reserve to Spend Casually
Suppose an activity has five days of float.
Should the PM think:
“Great. We can delay it five days.”
No.
Float provides flexibility.
It does not mean delay is desirable.
Using float can:
- reduce resilience,
- increase schedule risk,
- create a near-critical path,
- affect successors,
- remove flexibility that may be needed later.
A strong Project Reasoning Lab principle is:
Float is flexibility to manage — not time to waste.
12. Float Changes When the Schedule Changes
Suppose a project crashes one critical path and shortens it by several days.
Another path may suddenly become much closer to the project completion date.
That path may therefore lose much of its schedule flexibility.
Likewise, fast tracking may change:
- dependencies,
- sequencing,
- activity relationships,
- available float.
So after major schedule changes:
Recalculate the network rather than assuming float remains the same.
This reinforces a broader principle:
Criticality and float are dynamic characteristics of the schedule.
13. Project Reasoning Lab: Four-Question Float Test
When a PMP scenario gives you float information, ask:
1. What kind of float is being discussed?
Is it:
- total float,
- or free float?
2. How much delay is occurring?
Compare the delay with the flexibility available.
3. What will the delay affect?
Will it affect:
- the successor’s early start,
- the project finish date,
- both,
- or neither yet?
4. How much flexibility remains afterward?
Determine whether the path is becoming:
- less flexible,
- near-critical,
- or critical.
The reasoning sequence becomes:
Identify → Compare → Impact → Recalculate
14. Five Common PMP Traps
Trap 1: Float = Extra Time We Can Spend
No.
Float is schedule flexibility, not permission to delay unnecessarily.
Trap 2: Two Activities With Five Days of Float = Ten Days Available
Not necessarily.
Float may be shared across the same path.
Trap 3: Delay Within Float = No Impact
Not necessarily.
The finish date may remain unchanged while schedule flexibility and risk deteriorate.
Trap 4: Total Float and Free Float Mean the Same Thing
No.
Total float relates to project completion.
Free float relates to the successor’s early start.
Trap 5: Float Never Changes
No.
Float can change as durations, dependencies, constraints, sequencing, and actual performance change.
Final Takeaway
When an activity slips, do not ask only:
“Is the project late?”
Ask:
What kind of float exists?
How much has been consumed?
Does the successor move?
Does the project finish date move?
How much flexibility remains?
Then reassess the schedule.
Total float tells you how much flexibility exists before project completion is affected. Free float tells you how much flexibility exists before a successor’s early start is affected.
And the broader Project Reasoning Lab principle is:
Float is not spare time. It is network-derived schedule flexibility that can be consumed, shared, and changed as the schedule evolves.
