The longest path is the continuous chain of activities and driving relationships that determines the project’s calculated finish, traced back from the finish to the data date. Primavera P6 offers it as an alternative to a total-float threshold for marking activities critical.
In a simple network with one calendar and no constraints, the longest path and the zero-float activities are the same set. In real schedules they often aren’t. A finish constraint, a must-finish-by date or mixed calendars can give activities zero or negative float without them driving the finish. A long chain on a short-week calendar can drive the finish while still showing float.
How it works
After the forward pass, every activity’s early start is set by one or more predecessors. The relationship that actually sets the date is the driving relationship. To find the longest path:
- Start at the project finish milestone.
- Find the predecessor whose relationship drives it.
- Repeat from that predecessor until you reach the data date or an in-progress activity.
The chain you walk is the longest path. Delay any activity on it, and the finish moves by the same amount unless another chain takes over.
The critical path is often defined differently: activities with total float at or below a threshold, often zero. Total float depends on late dates, which depend on the project’s finish constraint and on each activity’s calendar. That’s where the two views split.
Worked example
Illustrative: a building’s finish is driven by the chain Structure → Enclosure → Commissioning → Substantial completion. Separately, an interim milestone, Level 1 handover to owner’s IT, carries a finish-on-or-before constraint that the logic can only just meet.
| Activity | Total float | On longest path? |
|---|---|---|
| Structure | 0 | Yes |
| Enclosure | 0 | Yes |
| Commissioning | 0 | Yes |
| L1 fit-out | 0 | No |
| L1 handover milestone | 0 | No |
A zero-float filter flags all five. The longest path shows only the three that set the completion date. The L1 fit-out work is critical to its own milestone, which matters, but delaying it doesn’t move substantial completion.
Now the reverse case. Roof slab curing on the structure chain runs on a seven-day calendar and feeds roofing on a five-day calendar. Curing finishes at the end of a Friday, and roofing can’t start until Monday. Curing could have finished as late as Sunday without moving roofing, so it shows two days of total float on its own calendar, yet it is still on the chain that drives the finish. A zero-float filter would miss it; the longest path wouldn’t.
Longest path vs related views
| View | Defined by | Watch for |
|---|---|---|
| Longest path | Driving relationships to the finish | Ties, where two chains drive equally |
| Total float ≤ threshold | Late dates minus early dates | Constraints and calendars distorting float |
| Near-critical | Float within a set margin | A threshold chosen to tell a story |
| Multiple float paths | Ranked chains by float or by driving logic | Which option P6 used to rank them |
Why it matters
Delay analysis, recovery planning and narratives all depend on knowing which work actually drives the finish. Ties are common: two predecessors can drive an activity equally, so a single longest-path chain is one choice from a wider set of drivers. In a time impact analysis, a delay matters to the finish only if it lands on, or creates, the driving chain. Scheduling settings such as retained logic and progress override can change which chain that is.
Common mistakes
- Reporting the zero-float list as the critical path in a schedule with constraints or several calendars.
- Ignoring ties, so the narrative names one chain when two drive the finish.
- A longest path that starts mid-project, which usually means broken logic or a constraint is holding a date.
- Not re-checking the path each update. It moves as work progresses.
- Adding constraints to force a path instead of fixing logic.
The total float and free float guide and the GAO and DCMA review guide cover the checks in more depth.
How os.construction handles it
The scheduling engine returns the ordered longest-path chain, the full driving set (including tied drivers) and the driving predecessors of each activity. The grid and Gantt can focus on the longest path separately from the critical filter, and Why this date? traces show the chain behind any activity.
FAQ
What is the longest path in a schedule?
It is the continuous chain of activities and driving relationships that determines the project's calculated finish date. Starting from the finish, you follow each activity's driving predecessor back to the data date. Any delay along that chain delays the finish, unless the logic changes.
Is the longest path the same as the critical path?
In a simple network with one calendar and no date constraints, yes. In real schedules they can differ. If the critical path is defined as activities at or below a total float threshold, constraints and mixed calendars can put activities on it that don't drive the finish and leave off chain activities that do.
How do you show the longest path in Primavera P6?
In the schedule options, P6 lets you define critical activities either by a total float threshold or as the longest path. Choosing longest path flags the driving chain to the project finish as critical. Many reviewers check both views and compare them.
Can an activity on the longest path have float?
Yes. When activities on the chain use different calendars, or the project finish is constrained, total float on the driving chain may not be zero. That's one reason the longest path is often a better test of what drives the finish than a zero-float filter.
How is the longest path used in schedule assessments?
The GAO Schedule Assessment Guide treats a valid critical path as one of its best practices and discusses the longest path in that context. The DCMA 14-point assessment includes a critical path test and a critical path length index, both of which depend on knowing which chain actually drives the finish.