Negative Native Float

Negative Native Float occurs when an activity’s early dates fall later than its late dates in the source scheduling tool, such as Primavera P6 or Microsoft Project. It means the work can’t be finished as currently planned in time to meet a required date. The value shows how many days need to be recovered.

Ex: The substantial completion milestone has a “Finish On or Before” constraint set to the contract date, but the schedule logic can’t reach that date. The milestone shows -20 days of float, which means the schedule is forecasting a 20-day miss against the contract date.

How negative native float can affect the schedule:

• It usually comes from a date constraint the schedule logic can’t achieve, such as a contract completion date, an interim milestone, or a project must-finish date. It can also come from progress updates showing work behind plan, which pushes early dates past a fixed deadline.
• Scheduling tools flag every path with zero or negative float as critical, so a schedule can show several critical paths at once, even though only the most negative path controls the project finish.
• Paths driving to different constraints are measured against different dates, so their float values can’t be compared directly.
• Float values change whenever a constraint date changes, even if no work has moved in the field.

How SmartPM handles negative float:

SmartPM doesn’t show negative float. Scheduling tools like P6 only see one update at a time, so they need a constraint date to measure delay against. SmartPM keeps every schedule update for a project, so it measures delay by comparing the current forecast to the baseline and to prior updates. This keeps the critical path at zero float and lets every other path show how far it can slip before it becomes critical.

The delay information isn’t lost. Instead of showing -20 days of float on the completion milestone, SmartPM shows the forecast completion 20 days past the baseline, along with when the slip happened, which update introduced it, and which activities drove it.

Best Practices:

• Start by finding the most negative path to the project finish. That’s usually the true driving path.
• Identify which constraint each negative-float path is measured against, so interim milestones aren’t confused with project completion.
• Compare float values against the longest path, which is based on logic and doesn’t depend on constraint dates.
• Track how negative float on key milestones changes from update to update instead of relying on a single snapshot.