Critical Path Method (CPM): How to Calculate the Critical Path in a Project

The critical path method becomes valuable when a project schedule is full of activity but still unclear about what truly controls the finish date.

A team may be managing dozens or hundreds of tasks, each labelled urgent, yet a delay in some activities has little effect while one missed dependency can shift the entire project. CPM brings structure to that uncertainty by linking activities, durations and dependencies, then showing which sequence has the least scheduling flexibility.

In project management, CPM helps teams distinguish operational noise from genuine schedule risk. 

This guide from LOTC explains how to identify the critical path, calculate it step by step and use the result to make better scheduling and delivery decisions.

The critical path method is a network-based scheduling technique used to determine the sequence of activities that controls the earliest possible project completion date. It combines activity durations with predecessor and successor relationships, then analyses the different paths through the schedule to identify where delay matters most.

The practical critical path meaning is therefore not “the most important work”. An activity may be expensive, high-risk or highly visible to a client and still sit outside the critical path if sufficient scheduling flexibility exists around it.

PMI guidance on time management and critical path analysis similarly presents CPM as a method for determining project duration and identifying the activities critical to completing the project on time.

The calculation is only as reliable as the activities, estimates and dependencies behind it.

You need five basic inputs:

1. A complete activity list
2. Realistic duration estimates
3. Defined predecessor and successor relationships
4. Clear start and finish logic
5. A network showing how the activities connect

The sequence begins before CPM scheduling itself. A work breakdown structure defines what the project must deliver; the activity list identifies the work required to produce those deliverables; dependencies establish the logical order; and duration estimates show how long that work is expected to take.

This distinction matters because a critical path calculation cannot compensate for weak schedule logic. If a dependency is missing, unnecessary or incorrectly sequenced, the resulting project critical path may be misleading even when every duration has been calculated correctly.

Before trusting the result, therefore, validate the network with the people who understand how the work will actually be performed.

Calculate the critical path by moving through the activity network twice: first forwards to find the earliest possible dates, then backwards to determine how much scheduling flexibility each activity has.

For the calculations below, use a Day 0 convention consistently: the first activity starts at time 0, so an activity lasting three days has an Early Finish of 3.

1. Build the Activity Network

List every activity with its:

• Duration

• Immediate predecessor or predecessors

• Immediate successor or successors

Then connect them in logical sequence to create a critical path diagram or CPM diagram. The purpose is not to produce an attractive chart; it is to represent the real dependencies between activities accurately.

2. Run the Forward Pass

Move from the beginning of the network towards the finish and calculate:

• Early Start (ES): earliest time an activity can begin

• Early Finish (EF): earliest time it can finish

Use:

EF = ES + Duration

If an activity has several predecessors:

ES = highest EF of its immediate predecessors

This matters because the activity cannot begin until all required predecessor work is complete. The final Early Finish reached through the network gives the earliest possible project completion time.

3. Run the Backward Pass

Now calculate backwards from the project finish:

• Late Finish (LF): latest time an activity can finish without delaying project completion

• Late Start (LS): latest time it can start without causing that delay

If the network has one final activity, set its LF equal to the project completion time. If several activities have no successors, use the highest Early Finish among those terminal activities as the common project finish point before calculating backwards.

Then use:

LS = LF − Duration

For an activity with several successors:

LF = lowest LS of its immediate successors

The backward pass reveals how late each activity can move before affecting downstream work or the project finish date.

4. Calculate Total Float and Identify the Critical Path

Calculate total float using either:

Total Float = LS − ES

or:

Total Float = LF − EF

In the simple unconstrained CPM network used in this article, activities with zero total float are critical. Trace those activities as continuous paths from project start to finish to identify the critical path or paths. A project can contain more than one critical path when multiple continuous sequences have no available float.

The durations along each critical path should equal the calculated project duration.

This final check matters. Critical path analysis does not identify the longest individual activity; it identifies the connected sequence, or sequences, whose timing currently controls project completion.

Apply the critical path method to a simple system launch project. The team must define requirements, prepare two parallel workstreams and bring them together before testing and launch.

The network contains two main paths:

Path 1: A → B → D → F
2 + 3 + 4 + 2 = 11 days

Path 2: A → C → E → F
2 + 2 + 3 + 2 = 9 days

The longer connected sequence is therefore:

Critical Path: A → B → D → F
Earliest project completion: 11 days

The forward and backward passes confirm the result:

Activities A, B, D and F have zero total float, confirming that they form the critical path. The C–E branch has two days of scheduling flexibility: it could absorb up to two days of delay before it begins to affect Activity F and the project finish date.

This critical path example also shows why CPM is more useful than simply comparing activity durations. D is not critical because it is the longest individual task; it is critical because it belongs to the connected sequence that currently controls completion.

Use the critical path as a decision tool, not simply as a calculation result. Once the path is identified, the project manager can focus attention on the activities most likely to affect the finish date and judge where intervention will have the greatest scheduling impact.

A well-managed CPM schedule should help the team:

• Prioritise monitoring of critical and near-critical activities

• Protect work with little or no available float
• Assess whether delays will move the project finish date
• Decide where acceleration could genuinely shorten the schedule
• Recheck assumptions, dependencies and duration estimates

• Evaluate the schedule impact of approved changes

However, non-critical activities should not be ignored. Float can be consumed, and a path with flexibility today may become critical after delays or changes elsewhere in the network.

The Critical Path Is Dynamic

The project critical path can change when durations, dependencies, constraints or scope change, or when actual progress differs from the original plan. Effective CPM scheduling therefore requires the network to be updated and recalculated throughout delivery.

The purpose is not to protect one path permanently, but to maintain a current view of which sequence is controlling completion now. When a formal scope or schedule change is approved, the revised logic should also be reflected in the schedule so that priorities remain based on current information.

Avoid treating the critical path as a static label or a list of the project’s most important tasks. CPM only works when the underlying schedule logic is realistic and kept current.

Common mistakes include:

• Assuming high-cost or high-visibility activities are automatically critical

• Using weak or optimistic duration estimates
• Missing, unnecessary or incorrect dependencies
• Looking for the longest individual activity instead of the longest connected path
• Assuming a project can have only one critical path
• Treating float as “free time” that can always be used without consequence
• Calculating CPM once and never updating the network

• Trusting scheduling software without checking the logic behind the result

A project can have more than one critical path, which makes the schedule more sensitive because several sequences may have little or no flexibility at the same time.

The final check is simple: software calculates the schedule you model; it does not prove that the model is correct. Reliable CPM therefore depends on sound dependencies, credible estimates and regular review, not on the tool alone.

Understanding the critical path does not remove schedule risk; it shows where lost time is most likely to change the project finish date.

Understanding the critical path is only one part of reliable schedule control. Project teams also need to build realistic activity logic, manage dependencies, respond to resource constraints and keep schedules updated as delivery conditions change.

LOTC develops these capabilities through:

• Essential Skills for Project Scheduling and Planning, covering dependencies, critical paths, resource constraints and practical schedule control.

• Project Management with Primavera P6, developing hands-on capability in WBS, activity relationships, scheduling, resource-loaded plans and project monitoring.

LOTC can also tailor corporate training around real project schedules and planning challenges. Speak to the LOTC team on WhatsApp to discuss the right programme.