The Critical Path Method: A Practical How-To Guide
Of all the scheduling techniques available to project managers, the Critical Path Method (CPM) is the most foundational. It was developed in the late 1950s — alongside PERT — for large engineering and construction programmes, and it remains the backbone of scheduling in MS Project, Primavera P6, and every other professional scheduling tool. Understanding it is not optional for anyone managing complex projects.
What the Critical Path Is
The critical path is the longest sequence of dependent activities that determines the earliest possible completion date for the project. Every project has a network of activities linked by dependencies (Finish-to-Start, Start-to-Start, etc.). The critical path is the chain of activities for which any delay directly delays the project end date. Activities on the critical path have zero float.
Calculating the Critical Path: Forward and Backward Pass
CPM uses two passes through the network:
Forward pass: starting from Day 0, calculate the Early Start (ES) and Early Finish (EF) of each activity by moving left to right through the network. The EF of the last activity in a chain becomes the ES of the next. The project's Early Finish is the highest EF among all end activities.
Backward pass: starting from the project's Late Finish (usually equal to the Early Finish), calculate the Late Start (LS) and Late Finish (LF) of each activity by moving right to left. Work backwards: LF of an activity = the smallest LS of all successor activities.
Float (or Total Float): LS − ES (equivalently, LF − EF). Float tells you how much an activity can slip without delaying the project. Activities with zero float are on the critical path.
What Float Means and How to Use It
Float is a resource, not a buffer to be consumed carelessly. When a non-critical activity uses its float, it joins the critical path. Project managers use float to smooth resource loading — shifting non-critical work to periods when resources are less constrained — and to absorb unexpected delays without impacting the schedule.
Note that float is shared across a chain of activities. If Activity A has 5 days of float and Activity B (its successor) also shows 5 days, they share the same 5 days — using A's float eliminates B's.
Compressing the Critical Path
When the calculated project end date is later than required, you have two main options:
Crashing: adding resources to critical-path activities to shorten their duration. Crashing increases cost. You crash the activity that offers the smallest cost increase per day of schedule compression, and you stop when cost exceeds the value of the time saved.
Fast-tracking: performing critical-path activities in parallel rather than sequentially. Fast-tracking increases risk. Dependencies that were treated as Finish-to-Start become Start-to-Start overlaps. This often introduces rework when the predecessor activity changes after the successor has already begun.
Both techniques have limits. Once you have crashed every activity that can be crashed economically and fast-tracked every dependency that can safely overlap, the remaining duration is the project's true minimum.
Why the Critical Path Shifts During Execution
The critical path calculated during planning is not permanent. As activities complete early or late, as scope changes are approved, and as risk events materialise, float is consumed and created. A path that had 10 days of float at project start may become critical by mid-project. This is why schedule updates — at least weekly on active projects — are not optional. A schedule that is not updated is a fiction.
CPM in Software Tools
MS Project and Primavera P6 both calculate the critical path automatically once you have entered activities, durations, and dependencies. Common configuration mistakes include:
Using date constraints (Start No Earlier Than, Must Start On) instead of dependencies. Hard constraints override the CPM logic and can hide real critical paths.
Forgetting to assign resources before analysing float, since resource levelling changes activity timing and float.
Treating the Gantt chart as the schedule. The schedule is the logic network; the Gantt is just a visual representation of it.
Common Mistakes
Ignoring resource constraints. CPM in its pure form assumes unlimited resources. Real projects do not have unlimited resources, so a CPM schedule must be resource-levelled to be credible.
Not updating after changes. Every approved scope change or major risk event should trigger a schedule update.
Focusing only on the critical path and ignoring near-critical paths. A path with only 2 days of float is almost as dangerous as the critical path itself.
XNM Consulting brings rigorous scheduling discipline to complex capital and infrastructure projects. Learn more about our project and programme delivery services.