Analyzing Near-Critical Paths
Tunnel vision on the zero-float critical path is a trap: a chain sitting at 3 days of float is one slipped week from becoming the new critical path while nobody is watching. Near-critical analysis widens the lens before that ambush happens. Built on AACE 92R-17.
What a near-critical path is
The critical path has zero float and controls the finish. But the finish date isn't protected by just one chain — it's protected by the gap between the critical path and the next-longest paths. When that gap is small, those near-critical paths are effectively co-drivers of the schedule, one delay away from taking over.
Why near-critical paths bite
- They become critical fast — a path with 3 days of float needs only a 4-day slip to go critical. On a busy site, that happens in a single bad week — and the critical path silently relocates.
- Multiple paths multiply risk — a schedule with many near-parallel paths of similar length is fragile: a delay almost anywhere pushes the finish. The more paths bunched near-critical, the higher the chance one of them lands on completion.
Setting the near-critical threshold
"Near-critical" needs a number. You pick a float threshold — say, anything with total float at or below 10 (or 15, or 20) working days — and treat every path under it as needing attention alongside the critical path.
The right threshold depends on the project's pace and risk. A fast, volatile job where a week of slip is common warrants a wide band (watch everything under ~15–20 days); a slow, stable job can use a tighter one. The key is to choose it deliberately and consistently, then report criticality in bands — critical (0), near-critical (≤ threshold), and the rest — rather than pretending only the zero-float path matters.
Managing near-critical paths
Once you can see the near-critical paths, you manage them almost like the critical path — with proportionate attention:
| Do this | Because |
|---|---|
| Monitor near-critical paths each update | They can become critical between any two periods |
| Track float erosion on them | A shrinking buffer is an early warning |
| Protect their resources too | Don't strip a near-critical path to feed the CP |
| Factor them into recovery & acceleration | Crashing the CP can make a near-critical path the new constraint |
Ten things to remember
- A near-critical path has small (not zero) float — one slip from becoming critical.
- The finish is protected by the gap between the CP and the next-longest paths.
- Watching only the CP is a trap — near-critical paths blindside projects.
- Many near-parallel paths = a fragile schedule — delay almost anywhere hurts.
- Set a float threshold deliberately (e.g. ≤ 10–20 days) tuned to project pace and risk.
- Report criticality in bands — critical, near-critical, the rest — not binary.
- Track float erosion on them — a shrinking buffer is the early warning.
- Don't strip near-critical resources to feed the CP — you'll just move the problem.
- After accelerating the CP, re-check near-critical paths — the constraint relocates.
- Near-critical analysis pairs with trending — catch a path heading critical before it gets there.
Glossary
- Constraint relocation
- When accelerating the CP makes a near-critical path the new critical path.
- Criticality bands
- Reporting paths as critical / near-critical / non-critical rather than binary.
- Float erosion
- Total float on a path decreasing over successive updates.
- Float threshold
- The chosen float value below which a path is treated as near-critical.
- Near-critical path
- A path with small total float, close to becoming critical.
- Parallel path
- An independent chain running alongside the critical path.
- Schedule fragility
- Vulnerability arising from many near-parallel paths of similar length.
- Total float
- Time a path can slip without delaying the project finish.