Most program teams stare at one number — the longest critical path — and treat the rest as background. That is half right. CP1 is the schedule constraint by definition, so it earns close attention. The other half is dangerous. The paths sitting behind CP1 quietly consume their buffer faster than CP1 is being pulled in, and one morning they wake up as the new CP1, with a thin pull-in plan and weeks of slip already baked in.
Figure 1. Critical path snapshot showing the nine top activities ranked by gap to the 6/30/2027 target. Anonymized; structure preserved from a real program review.
What the data actually says
The headline reads as a CP1 problem. The top activity is 65 days late, has zero buffer remaining, and lands on 9/3/2027 against a 6/30/2027 target. Three pull-in actions are open. The 9-week sparkline saw-tooths; over the last seven weeks the team has pulled in 2 days. That activity is being managed.
The story below the headline is the one to worry about. CP2 has slipped 59 days over seven weeks, with 18 of them in the two weeks since 04/22. Buffer remaining: 13 days. CP3 has slipped 40 days over seven weeks, 12 of them since 04/22. Buffer remaining: 25 days. Both sparklines climb monotonically — no resistance in the system. The Pull-in Actions column for CP2 and CP3 is empty.
Run the math at the recent rate. CP2 is burning buffer at about 9 days per week, so its 13 days disappears in roughly 10 days. CP3 is burning at about 6 days per week, so its 25 days lasts about 4 weeks. If nothing changes, CP2 becomes the new CP1 inside two weeks; CP3 follows within a month.
What makes this a red flag rather than a maybe: CP1's recent change is 0 (it has stabilized), while CP2 and CP3 are still slipping at their fastest recent rate. Pull-in attention is concentrated where it has already worked. The paths that need it next are invisible to the team.
Buffer-burn rate is the leading indicator. Current buffer tells you where you stand. Buffer-burn rate — slip days per week over the last two or three weeks — tells you when each path becomes the next constraint. Sort the top five paths by buffer divided by recent burn rate and you have a ranked list of which path will hurt you next, and how soon.
What to do about it
Three moves keep a program ahead of this pattern. Broaden the watch list to the top three to five critical paths every week, not just CP1. Score each path by buffer-burn rate, not just current gap; a small slip with a high burn rate is a bigger risk than a large slip that has already stabilized. When CP1 stabilizes, redirect that pull-in capacity to CP2, CP3, and out to CP4 and CP5 if the team has the bandwidth to spread it that wide. Pull-in work is cheapest while there is still buffer to defend; once a path becomes CP1 the options narrow and the cost rises.
Assume CP1 is getting shorter, not longer. Most teams plan around the implicit assumption that CP1 will get longer — schedules usually slip, and the planning reflex accommodates that. When CP1 lengthens, every path behind gains buffer, and those owners quietly absorb the extra room. They take it. They start working to the later date. Then they slip too. That is the mechanism behind most multi-month program slips.
The discipline that breaks the pattern is to assume the opposite, and to shorten CP2 through CP5 in step with CP1. When every path is accelerating with the same intent, slack does not accumulate, owners do not relax, and the program holds its target. In the snapshot above, CP1 has stopped slipping. The team should treat that stabilization as freed-up capacity and push it immediately at the next four paths, preferably in the same week the data says so.
CP Analysis is one of the standard functions in fastProjectAI. It surfaces the top critical paths, computes buffer-burn rates, ranks the paths by time-to-overtake, and flags cases where pull-in actions are concentrated on a stabilized path while the next path is unattended. Used in a weekly schedule review, it turns the silent slippers into Monday's conversation, not the one a month later when the new CP1 is locked in.
Download the full briefing (PDF): The critical path you're not watching