Negative float

Last reviewed 9 September 20262,195 words10 min read

What it means and what to do about it

🟩 In one line Negative float means the logic says you'll finish later than a date you've told P6 you must hit. The number is how many working days you're short. It's not a forecast — it's a warning light.

👤 Who this is for Junior planners seeing red numbers for the first time and not sure whether to panic. Mid-level planners who need to explain −22 days to a project manager without either of them panicking. Senior planners dealing with clients who demand "no negative float" in every submission.

e / c

First, let's be honest about why this page exists

Negative float frightens people, and the fear makes them do stupid things.

The most common reaction to a schedule full of negative float is to make it go away — delete the constraint, shorten some durations, switch a setting, re-run, and breathe out when the column turns black again. The project hasn't changed. The site is exactly as late as it was ten minutes ago. But the schedule no longer says so, and somehow that feels better.

It isn't better. It's worse, because now the one document that was telling the truth isn't.

So let's take the fear out of it. Negative float is one of the most useful things a schedule can show you — as long as you understand where it comes from, what it's measuring, and what the sensible responses are.

🟨 The standard — what "good" looks like

Negative float occurs when an activity's late dates fall earlier than its early dates. The logic (forward pass) says the activity finishes on date X. A constraint or required finish (backward pass) says it must finish by date Y. If Y is before X, float is negative by the difference.

What the standards and clients say about it:

DCMA 14-Point Assessment, Metric 7 — no activities should have negative float. A schedule with negative float "does not reflect a realistic plan." The intent is right; the wording gets misused (more on that below).
GAO Schedule Assessment Guide — same principle: negative float indicates the schedule cannot achieve a constrained date and requires either recovery or a revised date.
Typical Gulf client specifications (ADNOC, Aramco, Qatar's Ashghal, most developer specs) — baselines must have zero negative float. Monthly updates vary: some require a recovery plan whenever negative float appears; some forbid negative float in the update itself, which forces the problem underground.
The contracts — FIDIC and NEC never use the phrase. But FIDIC 2017 Cl. 8.3 requires a revised programme whenever the current one is inconsistent with actual progress, and NEC4 Cl. 32.1 requires each revised programme to show how the Contractor plans to deal with delays. A schedule with negative float and no recovery narrative fails both.

🟢 The standard is not "never show negative float." The standard is "never leave negative float unexplained." A baseline should have none. An update may well have some. What it must also have is a paragraph saying why, and what's being done.

How it actually works

Float is the gap between the early dates (what the logic can achieve) and the late dates (what's allowed). Normally the late dates are later, and float is positive. Negative float just means the late dates have been dragged earlier than the logic can manage.

Something has to be doing the dragging. There are only a handful of suspects:

1. The project's Must Finish By date. Set under Project → Dates. If the logic runs past it, everything on the longest path goes negative by the overrun. This is the most common and the most legitimate source.

2. An activity constraint. Finish On or Before, Finish On, Mandatory Finish, and their Start equivalents. Each one starts its own backward pass. A Finish On or Before on an intermediate milestone will generate negative float on everything feeding it — even if the project finish is fine.

3. Progress against an already-tight path. Nothing changed in the network; you just statused actuals, remaining durations grew, and a path that was at +2 is now at −6. Float went negative because the work fell behind, not because of any setting.

4. Calendar changes. Switch a chain from a 6-day to a 5-day calendar and it gets longer. If it was tight, it goes negative.

5. The Scheduling Options. Retained Logic vs Progress Override can change forecast dates by weeks on an out-of-sequence project. If float went negative right after someone touched Tools → Schedule → Options, look there first. (See retained-logic-vs-progress-override.)

The important thing to understand about the number itself: −15 on an activity does not mean it will finish 15 days late. It means the path it sits on needs to recover 15 working days somewhere between the data date and the constrained date. The recovery could happen at that activity or anywhere downstream. And if two constraints are in play, the −15 might relate to an intermediate milestone while the project finish is only −4.

That last point trips up almost everyone at least once. Different constraints, different backward passes, different negative numbers on different parts of the same schedule.

🟥 Where people go wrong

1. Making it disappear instead of dealing with it. Deleting the constraint that caused it. Trimming durations with no basis. Switching to Progress Override because the dates look nicer. Every one of these produces a schedule that is now wrong rather than late. Late can be explained. Wrong gets you audited.

2. Reading negative float as the forecast. The forecast is the early finish date. Negative float is the difference between that forecast and what's required. If someone asks "when will we finish?", give them the early date. If they ask "how far behind are we?", give them the float. Don't mix them.

3. Panicking about the wrong number. A schedule shows −20 on fifty activities and −3 on the project finish milestone. People see −20 and start emergency meetings. The −20 is against an intermediate constraint — probably a Finish On or Before someone added to a milestone eight months ago and forgot about. Check which constraint is driving the negative before deciding how bad things are.

4. Letting several constraints pile up. One project I've seen had eleven Finish On or Before constraints, all set to dates from the tender. Every update produced a different pattern of negative float depending on which one was tightest that month. Nobody could explain it. Strip constraints back to the contractual ones — usually two or three — and the picture clears.

5. Reporting it with no recovery plan. A monthly report that says "the schedule shows 18 days negative float" and stops is half a report. The other half is: which path, why, and what are the options. If you don't provide that, the PM will invent it in the meeting, and you won't like what they invent.

6. Zeroing it in the baseline by stealth. Client says the baseline must have zero negative float. The logic genuinely doesn't fit the contract period. So someone shortens fifty durations by 10% and submits. Now you have a baseline you know can't be achieved, which will be used against you in every update for the next three years. If the logic doesn't fit, that's a conversation to have before baseline approval, not a number to hide. (See baseline-approval-and-control.)

📜 What the contract makes of it

Negative float in an update is, in practical terms, a statement that completion will be late unless something changes. That has consequences.

Under FIDIC (Cl. 20.2 in 2017, Cl. 20.1 in 1999), the Contractor must give notice of any event that may delay completion — within 28 days of becoming aware. A schedule showing negative float caused by an Employer event is evidence you were aware. Miss the notice and the entitlement can be lost regardless of how good the schedule is.
Under NEC4 (Cl. 61.3, 32.1), the eight-week early warning / notification window and the revised programme requirement work the same way. Negative float that isn't reflected in a revised programme showing how it'll be dealt with is a programme the Project Manager can reject.
In Gulf bespoke contracts, there is frequently a clause allowing the Engineer to instruct a recovery programme (sometimes at the Contractor's cost) whenever the schedule shows completion beyond the contract date. Negative float triggers it. Know whether your contract has this, because it changes how carefully you word the monthly report.

The point isn't to hide negative float from the contract. It's the opposite. Negative float, promptly reported, with the cause identified, is the beginning of a good EOT record. Negative float, hidden until it's undeniable, is the beginning of a bad one.

⚖️ When you're challenged

"Get rid of the negative float." "I can remove it three ways. I can move the finish date, which needs a contract change. I can show a recovery — re-sequence, add resource, or both — but that has to be real, and someone has to sign up to it. Or I can shorten durations with no basis, which I won't do. Which of the first two do you want?"

"Why is this milestone −20 but the finish is only −4?" "Two different constraints. The milestone has a Finish On or Before that's 16 days tighter than the project needs. Either that date is contractual — in which case we have a milestone problem, not a completion problem — or it's a planning target from tender that we should remove." Then check which. It's often the second.

"Last month it was −4, now it's −11. What happened?" Open both files. Schedule Comparison. Find the activities on the driving path whose remaining durations grew or whose actual finishes slipped. Name them. "Piling on Zone C finished 5 days late and the precast delivery moved 2 days. That's the 7." Facts, not adjectives.

"Can we just switch to Progress Override? The dates look better." "They look better because P6 is assuming out-of-sequence work has no consequence. On this job it does — the ceiling can't close before the ductwork test. Retained Logic is the conservative answer and it's what the client's spec requires. I'll show you both if you want, but we report Retained."

📄 Related pages

Total float — the calculation underneath this
P6 Constraint Types — the eight ways to create negative float, and the two that are legitimate
Retained logic vs progress override — the setting that can change negative float by weeks
Building a Recovery Plan — what to do once you've stopped panicking
Notice Requirements and Records — why prompt reporting of negative float protects the claim
Baseline Approval and Control — negative float at baseline stage

✏️ Worked example

Same substation as before. 6-day calendar. Data date 1 April. The transformer delivery slipped 14 days. Project Must Finish By = 5 April.

Before the slip, the transformer path had zero float and drove the finish exactly on 5 April. Now:

Activity	Dur	Early Finish	Late Finish	Total float
Transformer delivery (actual finish)	—	29 Mar	15 Mar	−12
Transformer set on plinth	3	1 Apr	18 Mar	−12
HV cable pull	6	8 Apr	4 Apr	−4
Energise milestone	0	8 Apr	5 Apr	−4

Three things worth seeing:

The negative number changes along the path. −12 on the transformer, −4 at the end. Same path. That's because the cable pull also had a parallel trench predecessor with 8 days of float. Once the transformer went 12 days late, the trench path's float absorbed 8 of those days at the merge point. What's left — 4 days — is the real damage to completion.
The forecast finish is 8 April, not "−4." Two different pieces of information. The forecast is the date. The float is the gap.
The recovery target is 4 days, not 12. If someone reads the −12 and orders a 12-day acceleration, they're paying for 8 days nobody needs.

The write-up in the monthly report:

Energisation forecast 8 April against a required date of 5 April (−4 wd). Driver: transformer delivered 29 March versus planned 15 March (supplier delay; notice issued 18 March, ref. L-0412). Trench works absorbed 8 days. Recovery options: (a) cable pull on 2 shifts, saves ~3 days, cost attached; (b) partial energisation of Bay 1 ahead of Bay 2, saves 4 days, requires client approval. Recommendation: (b).

That's a negative float paragraph. Fact, cause, notice reference, options, recommendation. Six lines.

📖 References

DCMA, 14-Point Schedule Assessment — Metric 7 (Negative Float)
US GAO, Schedule Assessment Guide (GAO-16-89G) — Best Practice 5
FIDIC Red Book 2017 — Cl. 8.3, 8.5, 20.2
NEC4 ECC — Cl. 32.1, 61.3
SCL Delay and Disruption Protocol, 2nd ed. — Guidance Part B §§ 1–4 (programme and records)

From the field

Experience from working planners. Unreviewed — read it as experience, not guidance.

Add what you know about negative float. What worked, what the consultant pushed back on, what you would do differently next time. A paragraph is plenty.

Contributors get their name and one link on the site — your own templates, course or consultancy. We take nothing and hold nothing.

Add your experience