Critical path
Factual definition
The critical path is the sequence of dependent activities that determines project duration under the current schedule’s dependencies and duration assumptions. Delays beyond available float can delay completion.
Check the assumed dependency before final valuation approval
Hypothetical: a deal team’s agreed schedule requires audited financials before its final valuation approval. If that dependency has no float, a delay can move the scheduled finish.
Other valuation work does not universally require an audit, and a noncritical task can become critical after consuming its float.
Compare the dependent paths
PMI’s calculation guide uses task durations and dependencies to calculate the finish date and available float. A task’s importance to the business and its position on the schedule are different questions.
Hypothetical schedule. Durations are working days; all dependencies are finish-to-start with no gaps, and resources permit the stated parallel work.
Preparation takes two days. Then analysis takes four days while a separate document review takes three days.
Final approval takes one day and cannot start until both are complete. The analysis path is 2 + 4 + 1 = 7 days; the document path is 2 + 3 + 1 = 6 days.
Under these assumptions, the project takes seven days.
The document review has one day of float. If it takes four days instead of three, the finish remains day seven and both paths are critical.
If it takes five days, the project takes eight days. Its two-day overrun uses the one-day cushion and moves completion by one day.
Recalculate after changes. Shortening a task that still finishes before the controlling path may not bring the project finish forward.
Delaying it far enough can make it the task that controls completion.
Where Critical path fits
Explore this term in the glossary cloud →