A near-critical chain and the critical path can sit three days apart on the report, and almost nobody treats them the same way.
One gets tracked every single update. The other gets a passing glance, right up until the three days disappear, and it becomes the path actually controlling your finish date.
On a project I worked on, that shift happened inside six weeks, and the update explaining how it happened was already two reports behind by the time anyone noticed.
- The critical path is the chain with zero float, the one controlling completion today.
- A near-critical chain carries a small amount of float, close enough that one bad week can hand it control of the project.
- Float gets spent by delay events. Once it’s gone, criticality moves, sometimes from one chain to a completely different one, more than once across a project.
- There’s no fixed number of days that stay safe. What counts as near critical depends on how much float is left against how fast it’s being used up.
- Track only the zero float path each update, and you’ll catch a shift in criticality the month after it happened, not the month it actually happened.
Float, in one line: the spare time an activity can absorb before it starts pushing the finish date. Near critical means that spare time is almost gone.
The path that matters next month is rarely the one making headlines this month. It’s the one quietly running out of room right now.
