Chennai HQ · serving India, UAE, Saudi Arabia and Omaninfo@projectassure.inCall us 24/7 +91 94895 88922
Project Assure
Schedule Quality

Total float and negative float in scheduling: what they mean and how to fix negative float in P6

Total float shows how far an activity can slip before it affects the finish. Negative float shows how far a path already is from meeting a date imposed on it.

In short

Total float is the time an activity can slip without delaying the project finish or a constrained date, calculated in P6 as late finish minus early finish. Negative float means the late finish is earlier than the early finish, usually because a constraint or required finish date is earlier than the logic allows. The DCMA 14-point threshold for negative float is zero, and the fix is to test the constraint, the logic and the durations, or to resolve the date contractually.

Total float is the amount of time an activity can slip without delaying the project finish or a constrained date. Negative float means an activity's late finish is earlier than its early finish: the logic cannot achieve a date that has been imposed on it, usually a constraint or required finish date that is earlier than the network allows.

Negative float is not a calculation error. It tells you, in working days, how far the programme is from meeting a date someone has committed to. This guide covers how P6 calculates float, what causes negative float, how to find and resolve it, and the standards reviewers use to judge float.

What is total float?

Total float (also called total slack) is the time an activity can be delayed without delaying the project finish date or any activity carrying a late-date constraint. P6 calculates it from the forward pass (early dates) and the backward pass (late dates):

  • Total float = Late Finish minus Early Finish (finish float), or
  • Total float = Late Start minus Early Start (start float).

Which one P6 uses is set in the scheduling options under "Compute Total Float as": Start Float, Finish Float, or Smallest of Start Float and Finish Float. On a single calendar with no progress the results usually match. They can differ on in-progress activities and where calendars differ.

  • Positive total float: the activity has room to slip before it affects the finish or a constrained date.
  • Zero total float: the activity has no room to slip. It is critical under P6's default definition (total float less than or equal to zero).
  • Negative total float: the activity is already late against a required date, by the amount shown.

Total float vs free float: what is the difference?

Free float is the time an activity can be delayed without delaying the early start of any of its successors. Total float is the time it can be delayed without delaying the project finish or a constrained date. In a normal network, free float is never more than total float, and most schedule analysis focuses on total float.

MeasureProtectsCalculated fromTypical use
Total floatProject finish date and late-date constraintsLate dates minus early datesCritical path, float erosion, delay analysis, DCMA float checks
Free floatEarly start of the immediate successorsEarliest successor early start minus the activity's early finish (allowing for lags)Deciding how far one activity can slip before it disturbs the next

An activity can have plenty of total float and no free float: any slip moves its successors, but the chain still has room before the finish date.

What is negative float in a schedule?

Negative float occurs when an activity's late finish is earlier than its early finish. The forward pass works out the earliest the activity can finish given its logic, durations and progress. The backward pass works out the latest it can finish and still meet the dates imposed on the schedule. When the latest permissible date falls before the earliest achievable date, total float is negative.

This almost always happens because a late-date requirement is earlier than the logic allows: a Finish On or Before or Mandatory Finish constraint on a milestone, or a project "Must Finish By" date. Without any such date, the backward pass starts from the project's early finish and float cannot go below zero.

Example: the logic shows that a handover milestone can finish no earlier than day 20 (early finish). The milestone carries a Finish On or Before constraint of day 15 (late finish). Total float is 15 minus 20, which is minus 5 days. Every predecessor on that chain also shows at least minus 5 days.

What does negative float mean in P6?

In P6, negative total float on an activity means the current logic and durations cannot meet a date that has been imposed on that path. The value is the number of working days the path must recover to meet the date. It means one of two things:

  • The programme is genuinely late against a contractual or committed date, because progress or delay events have pushed the early dates beyond it.
  • The schedule is unrealistic: a constraint or required date was set earlier than the planned logic and durations could ever achieve.

Either way, P6 treats activities with negative float as critical under the default definition. A schedule where large numbers of activities show negative float has a critical path that cannot be met without a recovery plan, a revised date or both.

How do constraints create negative float?

Constraints that set or cap late dates are the usual cause. In P6, the common sources are:

  • Finish On or Before: caps the late finish. If the logic cannot finish by that date, the activity and its predecessors show negative float. It does not move the early dates.
  • Start On or Before: caps the late start in the same way. If the logic cannot start the activity by that date, negative float appears.
  • Mandatory Finish and Mandatory Start: fix the activity's dates regardless of logic. The backward pass takes the imposed date, so predecessors that cannot meet it show negative float, and the constrained activity can be scheduled in breach of its own logic.
  • Start On and Finish On: set both early and late dates to the constraint date. If predecessors push the activity later, negative float appears.
  • Project Must Finish By date: set in the project's dates. It drives the late dates of activities with no successors, so an end date earlier than the logic allows produces negative float across the critical path.

Start On or After does not create negative float by itself. It can push early dates later and use up float, and negative float then appears only if a late-date requirement exists further down the same path. Always check the constraint type, its date and the path it sits on. For a fuller treatment of each constraint type, see Primavera P6 constraints explained.

How do you find negative float in P6?

  1. Reschedule the project (F9) at the current data date so the float values are current.
  2. Add the Total Float, Primary Constraint and Primary Constraint Date columns to the Activities view.
  3. Sort or filter on Total Float less than zero. The most negative values show the paths furthest behind.
  4. Group the results by path, or trace each one back with the Trace Logic view, to find the constraint or required date at the end of each negative chain.
  5. Review the schedule log, which lists constrained activities alongside other scheduling exceptions.

The DCMA 14-point assessment also tests for negative float: the threshold is zero, so any activity with negative float fails the check. A schedule-checking tool or a standard P6 report can list these activities in bulk.

How do you fix negative float?

Negative float is a symptom. Resolve the cause rather than the number:

  • Test the constraint. If a constraint has no contractual or external basis, remove it or replace it with logic. If it reflects a real commitment, keep it: the negative float is accurate information.
  • Review the logic. Check that relationships reflect how the work will actually be built. Where work can genuinely overlap, model it with Start-to-Start or Finish-to-Finish relationships and justified lags, not negative lags (leads), which DCMA expects to be zero.
  • Review durations. If a duration is overstated, correct it on the basis of quantities and productivity, not to make the number disappear.
  • Plan recovery. Add resources, extra shifts or a changed method where these are realistic, and show them in the schedule. Beware compression that the site cannot deliver.
  • Resolve the date. If the required date cannot be met, the answer is contractual: an extension of time, an agreed acceleration or a revised completion date. Rebaselining does not remove negative float, because P6 calculates float from the current schedule's dates and constraints, not from the baseline.

Never delete a contractual constraint just to clear negative float. It hides the delay from the people who need to manage it.

What are the industry standards for float management in P6?

  • DCMA 14-point assessment: negative float, zero activities. High float (more than 44 working days), fewer than 5% of incomplete activities. Hard constraints, fewer than 5%. High float usually points to missing logic or open ends rather than genuine flexibility.
  • Critical path definition: P6 lets you define critical activities as "Total Float less than or equal to" a value (zero by default) or as the longest path. State which one the programme uses, because negative float and multiple calendars can make the two differ.
  • Float ownership: who may use float is set by the contract. Where the contract is silent, the Society of Construction Law Delay and Disruption Protocol treats float as available to the project rather than to either party, which affects how delay events are assessed. This matters in any forensic delay analysis.
  • Trend reporting: report float on the critical and near-critical paths every update, so erosion is visible before the float goes negative.

How do you avoid negative float?

  • Use constraints sparingly and let logic drive dates.
  • Schedule forward from the project start, and set a Must Finish By date only where it reflects the contract completion date.
  • Run a DCMA 14-point check every update: it catches negative float, high float, long durations and missing logic.
  • Status progress accurately at each data date, so float reflects the real position rather than an unprogressed plan.
  • Explain to the team that a constraint changes float, so a new constraint should be agreed before it is added.

Negative float shows that a programme is under pressure against a committed date. Once you know whether the cause is the logic, the constraint or real delay, you know whether the fix sits in the schedule or in the contract.

FAQ

Common questions

What is negative float in scheduling?
Negative float (or negative slack) occurs when an activity's late finish is earlier than its early finish, so the logic cannot meet a date imposed on that path. It is usually caused by a constraint or required finish date that is earlier than the logic and durations allow.
How do constraints cause negative float in Primavera P6?
Late-date constraints such as Finish On or Before, Start On or Before and Mandatory Finish cap the late dates. If the logic gives a milestone an early finish of day 20 but a constraint caps its late finish at day 15, total float is minus 5 days on the milestone and its predecessors.
What is the difference between total float and free float?
Total float is the time an activity can slip without delaying the project finish or a constrained date. Free float is the time it can slip without delaying the early start of any successor, so in a normal network it is never more than total float.
How do I find negative float in P6?
Reschedule at the current data date, add the Total Float and Primary Constraint columns to the Activities view, and filter on Total Float less than zero. Trace each negative chain to the constraint or required date at its end.
Is negative float always bad?
It always needs investigating, because it means a committed date cannot be met on the current logic, or the date was unrealistic from the start. Removing a genuine contractual constraint to hide it is not a fix: the answer is recovery or a contractual resolution of the date.
Chennai city skyline at dusk under a vivid pink and violet sky

Bring this discipline onto your programme.

Every insight comes from live mandates. A principal replies within one working day.