Critical path analysis identifies the chain of activities that determines the earliest forecast completion date in a CPM schedule. A delay to any activity on that chain moves completion day for day. A delay elsewhere does not, until it has used up the float on that activity.
That definition sounds simple, and it is why schedule reviewers, owners and claims consultants all start in the same place. But the answer the software gives is only as reliable as the logic, calendars and status data behind it.
How the critical path is calculated
CPM software runs a forward pass to find each activity's earliest dates and a backward pass to find its latest dates. The difference is total float. Activities whose total float is at or below a chosen threshold, commonly zero, are reported as critical.
Primavera P6 also lets a schedule define the critical path as the longest path instead of by total float. The two settings can produce different answers when constraints, multiple calendars or open-ended activities are present, so confirm which definition your contract specification requires before anyone reports on it.
Critical path, driving path and near-critical paths
- Critical path: the chain that controls project completion.
- Driving path: the chain of relationships that controls the date of a specific activity or milestone, such as an interim milestone or a phase turnover.
- Near-critical path: a chain with float below an agreed threshold. It is one bad week away from becoming critical.
The critical path is not fixed. As progress is recorded and logic is revised, the controlling path can shift from one chain of work to another, which is why an update should say what moved and why.
What quietly distorts the critical path
- Open ends. Activities with no predecessor or no successor hide how work really connects to completion.
- Hard constraints. Mandatory dates override calculated dates and can create false criticality or mask a delay.
- Lags and leads. Used to plug gaps in logic, they make the path look continuous when the work is not.
- Calendar mismatches. A five-day activity tied to a seven-day activity changes the float without anyone noticing.
- Out-of-sequence progress. Retained logic, progress override and actual-dates handling produce different forecasts from the same status.
- Over-long activities. A 90-day activity can hide the very sequence that controls the finish.
A review routine for every update
- Confirm the data date and that actual start and finish dates match the field record.
- Check for open ends, constraints and unexplained lags before trusting any float value.
- Trace the longest path from the data date to completion and read it back as a sequence of real work. If it does not read like a construction sequence, the logic needs attention.
- Compare it with the previous update: what changed, who caused it, and what did it do to completion?
- Report near-critical paths alongside the critical one.
- Write the narrative while the events are still fresh.
A quick sanity check is to add a large duration to one critical activity in a copy of the file. If the completion date does not move by the same amount, the path is not what it appears to be.
Why it matters when a delay occurs
Only delays to critical work normally extend completion. Delays to non-critical work consume float, and who owns that float is a contract question. That is why a Time Impact Analysis or a forensic delay analysis depends on knowing what the critical path was at the time of the event, not what it looks like in hindsight.
Industry references such as AACE International Recommended Practice 49R-06 (Identifying the Critical Path) and 29R-03 (Forensic Schedule Analysis) describe how to establish and test critical paths. Contemporaneous updates and narratives are what make those methods usable later.
HADVEN builds and reviews schedules with this in mind. See our CPM scheduling and Primavera P6 services, or read how a formal schedule quality review checks the logic behind the path.