Near-Critical Path

A near-critical path is a sequence of activities whose total float is low but greater than zero — close enough to the critical path that a modest slip on any of its activities can push the path past the deterministic critical and make it the new driver of project completion. In practice, near-critical paths cause more programme overruns than the deterministic critical path does, because they go unwatched: the project team focuses on the zero-float critical path, an activity on a near-critical path slips by a few days, and the previously-comfortable secondary path silently becomes the new critical chain.

The DCMA 14-point assessment treats activities with 7 working days or less of total float as near-critical for monitoring purposes. The threshold reflects the working assumption that anything inside two working weeks of zero float is materially exposed to becoming critical given the duration uncertainty typical on infrastructure programmes. On long-duration programmes (nuclear, major civils) the threshold is often extended to 14 or 21 working days; on short construction packages it is sometimes tightened to 3-5 days. The principle is the same: identify the paths that are close enough to critical to deserve the same monitoring discipline.

Near-critical paths matter most on programmes with material duration uncertainty. On a deterministically planned project with point estimates that the team is confident in, the critical path is the path that drives completion and the rest can be safely ignored. On a project with realistic duration uncertainty — which is to say, every real project — multiple paths are statistically likely to become critical at different points, and the only durably useful answer to 'what should we be monitoring?' is 'the critical path AND every near-critical path within the float threshold appropriate for our duration uncertainty profile'. A QSRA criticality index analysis quantifies this directly: any activity with a criticality index above (say) 25% is, in practice, on a near-critical path that warrants planner attention.

The most common failure mode is reporting that lists only the deterministic critical path and presents it as 'the path the project is on'. This understates the monitoring perimeter and leaves the team blind to the paths that will actually drive overrun. A defensible programme status report identifies the critical path, the top 3-5 near-critical paths with their float values, and any activity moving toward the float threshold (e.g. paths whose float has reduced from 14 days to 8 days since last reporting period). On NEC4 contracts, this matters commercially as well as practically: compensation events assessed against a single-path critical-path view can understate the genuine schedule impact when the event tips a near-critical path into criticality.