The Critical Path Changes Every Week. What Does That Mean?
A changing critical path can be legitimate. Understanding why it moved is essential to making the schedule useful.
Civil Engineering Jobs editorial team
Start with what the term means
The critical path is the connected sequence of activities that determines the earliest forecast completion of a chosen milestone in the schedule model. A near-critical path has little remaining float: the time it can slip before affecting that milestone. [1]
It is a result of the current model, not a permanent label attached to one trade. Specify which milestone and which status date are being discussed.
Why the path can move
Progress, remaining durations, dependencies and calendars can alter which sequence controls completion. A near-critical sequence may become critical. [1]
In a simplified hypothetical example, two parallel sequences lead to handover. One has twenty working days remaining and the other nineteen. If the second gains three days of work, it can become the controlling sequence, even if the first was critical last week. A shift by itself does not demonstrate poor planning.
Why weekly changes make follow-up difficult
A report that says only “the critical path has changed” gives the team a new list without explaining what to do. Ask what changed in the work or the model, what caused it, which decisions are needed and whether the completion forecast also moved.
Review activities close to critical as well as the current controlling sequence. Otherwise, a team may pursue this week’s urgent task while another constraint is about to become decisive.
Distinguish an update from a rewritten commitment
The United States Government Accountability Office (GAO) distinguishes updating actual progress from maintaining the approved baseline used for comparison. [1]
A current forecast should reflect reality. It should also remain possible to compare it with the approved commitment. Preserve dated versions and an explanation of meaningful changes. Frequent changes caused by missing links, incorrect progress or unexplained constraints call for a model review; frequency alone does not prove manipulation.
For a job interview, ask who maintains schedule logic and how the team explains a change to the critical path. Scheduling software is useful only if the model and its updates can be understood.
Source and why it was chosen
[1] United States Government Accountability Office — Schedule Assessment Guide: Best Practices for Project Schedules (2015). A detailed American public-sector technical reference, used for scheduling concepts. It does not establish Canadian contractual rights or prescribe a weekly update frequency.
https://www.gao.gov/products/gao-16-89g