Critical Path Method (CPM) Explained for Schedulers

What Is the Critical Path Method (CPM)?

The critical path method (CPM) is a deterministic scheduling technique used to estimate the minimum project duration and identify the sequence of activities that cannot be delayed without extending the project finish date. Developed in the late 1950s, CPM is a cornerstone of modern project management and is implemented in tools like Primavera P6.

CPM requires a well-defined work breakdown structure (WBS) with activities linked by logical dependencies (finish-to-start, start-to-start, etc.). Each activity has an estimated duration. The method then calculates early and late start/finish dates for every activity, revealing the total float—the amount of schedule flexibility.

Forward Pass: Calculating Early Dates

The forward pass determines the earliest possible start and finish dates for each activity. Starting from the project start date (typically day 1 or a calendar date), you move forward through the network.

• Early Start (ES) = the earliest date an activity can begin, considering all predecessors.
• Early Finish (EF) = ES + duration − 1 (if using day units).

For activities with multiple predecessors, ES is the maximum EF of all predecessors. The forward pass ends with the project finish date, which is the maximum EF among all activities with no successors.

Backward Pass: Calculating Late Dates

The backward pass calculates the latest possible start and finish dates without delaying the project. Starting from the project finish date (set equal to the maximum EF from the forward pass), you move backward through the network.

• Late Finish (LF) = the latest date an activity can finish without delaying the project.
• Late Start (LS) = LF − duration + 1.

For activities with multiple successors, LF is the minimum LS of all successors. The backward pass ends at the project start date.

Float (Total Float) and Its Meaning

Total float (TF) is the amount of time an activity can be delayed without affecting the project finish date. It is calculated as:

TF = LS − ES = LF − EF

Activities with zero total float are on the critical path. A positive float indicates schedule flexibility; negative float means the project is behind schedule (the late dates precede early dates). Float is a key metric for schedule analysis and is used in DCMA 14-point checks to identify excessive float or critical path length.

How the Critical Path Is Identified

The critical path is the longest path through the project network in terms of duration. It consists of activities with zero total float. However, in practice, schedulers often consider a near-critical path (float less than a threshold, e.g., 5 days) for risk management.

To identify the critical path in Primavera P6:

• Run a schedule calculation (F9).
• Apply a filter for Total Float = 0.
• Review the Gantt chart; the critical path is typically highlighted (e.g., red bars).

Note that multiple critical paths can exist if several activity sequences have zero float. This is common in fast-tracked projects.

Why the Critical Path Shifts Between Updates

As the project progresses, actual dates and remaining durations change. When you update the schedule (e.g., weekly or monthly), the critical path can shift to a different sequence of activities. Common reasons include:

• Delays on non-critical activities that consume their float and become critical.
• Acceleration of critical activities (e.g., by adding resources) that reduces their duration and may make another path longer.
• Logic changes (new dependencies or activity additions).

Tracking the critical path over time is essential for earned value management (EVM) and forensic delay analysis. Tools like Project Assure allow you to compare baseline and updated XER files to see exactly how the critical path has changed—no upload required, everything runs in your browser.

CPM in Schedule Analysis and Compliance

CPM is the foundation for many schedule quality checks, including:

• DCMA 14-point assessment – checks for critical path length, BEI, and excessive float.
• GAO Schedule Assessment Guide – recommends a valid CPM schedule with a reasonable critical path.
• NASA schedule management – requires a critical path analysis for major milestones.

A healthy critical path typically represents 20–30% of total activities. If the critical path is too short (e.g., < 5% of activities), the schedule may lack logic or have excessive open ends.

Practical Tips for Schedulers

• Always run a forward and backward pass after any logic change.
• Use constraints (e.g., 'Start On') sparingly; they can distort float calculations.
• Review the critical path monthly at a minimum; more often for fast-paced projects.
• Document why the critical path shifted—this is vital for forensic delay analysis.

By mastering CPM, you can build defensible schedules, identify risks early, and communicate schedule status clearly to stakeholders. For a quick, free check of your XER file's critical path and DCMA compliance, try Project Assure—it parses your file locally in the browser with zero uploads.