A project schedule can look comfortably on track until one delayed activity pushes a milestone, consumes contingency, or exposes a critical path. Knowing how to calculate schedule float gives project professionals a clear view of which activities can move and which require immediate control. It is a core Critical Path Method (CPM) skill for real project planning and a frequent concept in PMP, CAPM, Primavera P6, and Microsoft Project discussions.
Float is not permission to delay work casually. It is schedule flexibility created by the network logic, durations, calendars, constraints, and required completion date. Used correctly, it helps project managers prioritize resources, assess change requests, and focus reporting on the work that can truly affect delivery.
What Schedule Float Means
Schedule float, also called slack, is the amount of time an activity may be delayed without causing an unwanted impact on the schedule. The type of impact matters. Some delay may be acceptable as long as the project completion date remains unchanged. Other delay may be acceptable only if it does not delay the next activity.
The two measures professionals use most often are total float and free float.
Total float is the time an activity can slip without delaying the project finish date or a specified milestone. It is the most common form of float shown in CPM schedules and scheduling software.
Free float is the time an activity can slip without delaying the early start of any immediate successor. Free float is narrower than total float. An activity can have total float but no free float when a delay would affect downstream work while still leaving enough time to protect the final project date.
An activity on the critical path normally has zero total float. That does not mean it is automatically high risk in every situation, but it does mean any delay to that activity can delay the project finish unless the team takes corrective action elsewhere.
How to Calculate Schedule Float Step by Step
To calculate float manually, begin with a properly developed network diagram or logic-linked schedule. Every activity needs a duration and a defined predecessor-successor relationship. A schedule with missing logic, excessive constraints, or disconnected activities cannot produce dependable float values.
1. Complete the forward pass
The forward pass identifies the earliest dates on which each activity can start and finish. Start with the first activity at the project start date, then move through the network from left to right.
For a simple finish-to-start relationship with no lag:
- Early Start (ES) is the earliest possible start based on predecessor completion.
- Early Finish (EF) equals ES plus activity duration.
When an activity has multiple predecessors, its early start is determined by the predecessor that finishes last. This is why parallel work streams eventually converge and why one delayed path can become critical.
2. Complete the backward pass
The backward pass identifies the latest dates activities can start and finish without delaying the required project completion date. Begin with the final activity or required finish milestone, then work backward through the network.
For a simple finish-to-start relationship with no lag:
- Late Finish (LF) is the latest allowable finish.
- Late Start (LS) equals LF minus activity duration.
When an activity has multiple successors, its late finish is controlled by the successor with the earliest late start. That successor places the tightest limit on the activity.
3. Apply the total float formula
Once early and late dates are available, use either version of the total float formula:
Total Float = Late Start – Early Start
or
Total Float = Late Finish – Early Finish
Both calculations should produce the same result when the schedule logic and calculations are consistent.
If an activity has an early start of Day 3 and a late start of Day 5, its total float is two days. The activity can start two days later than planned without moving the project finish date.
4. Calculate free float when needed
For finish-to-start relationships with no lag, free float is calculated as:
Free Float = Earliest Start of Successor – Early Finish of Activity
If an activity finishes on Day 5 and its next activity can start as early as Day 7, the activity has two days of free float. A two-day delay will not affect the successor’s early start.
Relationship types and lag change the calculation. Start-to-start, finish-to-finish, and lead or lag relationships require the scheduler to account for the relevant dates and offsets. In complex schedules, Primavera P6 or Microsoft Project can calculate float automatically, but professionals still need to understand the underlying logic to validate the results.
A Simple Schedule Float Example
Consider a project with four activities, using a Day 0 project start and finish-to-start links:
| Activity | Predecessor | Duration | ES | EF | LS | LF | Total Float | |—|—:|—:|—:|—:|—:|—:|—:| | A: Design | None | 3 days | 0 | 3 | 0 | 3 | 0 days | | B: Procurement | A | 4 days | 3 | 7 | 3 | 7 | 0 days | | C: Site Preparation | A | 2 days | 3 | 5 | 5 | 7 | 2 days | | D: Installation | B and C | 3 days | 7 | 10 | 7 | 10 | 0 days |
The forward pass shows that Activity D cannot begin until both Procurement and Site Preparation are complete. Procurement ends on Day 7, while Site Preparation ends on Day 5. Therefore, Installation starts on Day 7 and the project finishes on Day 10.
During the backward pass, Installation must start no later than Day 7. Site Preparation can finish as late as Day 7, although it is scheduled to finish on Day 5. Its total float is therefore two days:
Total Float = LF – EF = 7 – 5 = 2 days
In this example, Site Preparation also has two days of free float because its successor, Installation, has an early start of Day 7. Procurement, however, has zero float. A delay to Procurement immediately delays Installation and the final completion date.
What Negative Float Tells You
Negative float is a warning signal, not a favorable scheduling condition. It means the current plan cannot meet an imposed completion date, contractual milestone, or schedule constraint. For example, if the calculated project finish is Day 12 but a mandatory completion milestone is Day 10, activities on the driving path may show negative two days of float.
Negative float should trigger a focused schedule review. The project team may need to revise sequencing, add qualified resources, shorten durations, remove unnecessary constraints, negotiate a milestone date, or use approved acceleration techniques. Crashing work by adding resources can reduce duration, but it often increases cost and may create quality, safety, or coordination risks. Fast tracking can overlap activities, but it raises rework risk.
The right response depends on the cause of the negative float. If it comes from unrealistic logic or an outdated calendar, correcting the schedule model may resolve it. If it reflects a genuine contractual deadline, the project needs a recovery decision rather than a cosmetic schedule update.
Common Errors When Calculating Schedule Float
The most common mistake is treating total float as time owned by one person or department. Float belongs to the schedule network. If one team consumes it, the flexibility available to downstream work is reduced. Project managers should communicate float use through the schedule update process, not allow each activity owner to treat it as hidden contingency.
Another error is relying on dates without reviewing logic. A task may appear to have float because it has an open end, a missing successor, or an incorrect relationship. A valid CPM schedule should have clear logic ties, realistic durations, appropriate calendars, and limited hard constraints.
Calendar settings can also change the result. Five working days do not equal five calendar days when weekends, holidays, shift patterns, or resource calendars apply. This matters particularly in construction, engineering, shutdown, and multi-location projects where work calendars vary across disciplines.
Finally, do not assume the critical path is fixed. It can shift after progress updates, approved changes, delayed deliveries, or revised forecasts. Recalculate the schedule after each status update and review near-critical activities, not only the activities with zero float. A path with one or two days of float may become critical quickly.
Use Float to Make Better Project Decisions
Float becomes valuable when it supports action. During a weekly schedule review, use total float to identify activities that need close monitoring, assess the effect of late information or material delivery, and decide where resource adjustments will have the least impact. Use free float when coordinating handoffs between teams and protecting successor start dates.
For certification candidates, the essential distinction is straightforward: total float protects the project completion date, while free float protects the early start of the immediate successor. For working project professionals, the practical standard is higher: understand why the float exists, verify whether the schedule logic is credible, and monitor how quickly that flexibility is being consumed.
Accurate float calculations turn a schedule from a reporting document into a management tool. Build the logic carefully, update it with real progress, and treat every day of float as decision-making time that can protect project delivery.