Near Critical Path

Quick definition: A Near Critical Path is the second-longest (or third, fourth, and so on) sequence of linked tasks running to the project finish. It isn't driving the finish date today, but it's the likeliest candidate to become the Critical Path if conditions change.

Like the Critical Path, a Near Critical Path is made up of Work Packages, Planning Packages, or lower-level tasks linked by schedule logic. They're ranked by duration: the second, third, fourth, and subsequent longest sequences of tasks from Time Now to the project end date. Where a schedule carries no date constraints, those same paths also hold the next-lowest Total Float, which is why the concept is often described in float terms instead. The two views separate once date constraints or multiple Working Calendars are in play, so duration ranking is the more reliable basis. Because a Near Critical Path is only slightly shorter than the Critical Path, a modest delay or resequencing can make it the longest — and therefore the new Critical Path.

Why it matters

Schedulers watch Near Critical Paths because they are the leading indicator of where a new Critical Path is likely to emerge. Ignoring them can mean being caught out when a secondary path suddenly becomes the one driving the finish date. They also matter for acceleration: the Critical Path is normally examined together with the secondary and tertiary paths, with mitigation applied where they intersect, since compressing the Critical Path on its own often just promotes the next path in line.

See also

FAQ