Back online
Construction Glossary · Scheduling

Total & FreeFloat

Float is the room an activity has to move before something breaks. Total float protects the finish date; free float protects the next activity in line.

Definition

Total float is the number of days an activity can slip from its early start without delaying the project completion date. Free float is the number of days it can slip without delaying the early start of any successor. Total float is shared along a path; free float belongs to a single activity. An activity with zero total float is on the critical path, and negative total float means the schedule is already late against a constraint.

How far it can slide, and before what breaks

This activity can slide six days before the project finish moves, its total float. But after only three days it would push its successor, so its free float is three. The first number protects the end date; the second protects the neighbor.

ActivitySuccessorFinishTotal float 6dFree 3d

Total, free, and negative

Three float readings a scheduler acts on differently. Zero total float is the critical path; negative float is a plan that does not work yet.

ReadingMeansWhat to do
Total float > 0Slack before the finish movesMonitor; it is shared along the path
Total float = 0On the critical pathProtect it — any slip moves the finish
Free float > 0Slack before the successor movesYou can shift this activity alone
Negative floatLate against a constraint alreadyCompress, resequence, or revise the date

Zero total float is the critical path; eating an owner’s delay into float is central to compensable delay.

How POD reads float

POD reads each activity’s total float from the Primavera P6 or Microsoft Project schedule you import, so the activities with no slack, the critical ones, are visible alongside the field data rather than buried in a scheduling file few people open. When a daily report shows an activity slipping, its float tells you immediately whether that slip threatens the finish or is absorbed. POD reads the float the scheduling tool calculated; it does not run the forward and backward pass itself or decide how float is owned under your contract. It surfaces the number so the slip can be judged the moment it is reported.

Critical path method guide

Frequently asked questions

Float is computed; variance is measured

Float comes from the schedule logic itself, the forward and backward pass over the current network. What you measure against the frozen baseline is variance: how far the plan has drifted. That is the baseline's job.

Last updated: October 2026