Learn how the Critical Path Method works, calculate a critical path and float, and use CPM to make better schedule decisions.
The Critical Path Method (CPM) identifies the longest dependency-connected path through a project schedule. That path determines the earliest possible finish date: if a critical task finishes late and nothing else changes, the project finishes late too.
Verified August 7, 2026. This guide explains the scheduling method and its limits without treating a calculated date as a guarantee.
What is the critical path in project management?
The critical path is the sequence of dependent activities with the greatest total duration from project start to project finish. Tasks on that path normally have zero total float. A non-critical task can move by its available float before it affects the project finish or another constrained milestone.
Three ideas matter:
- Duration is the working time assigned to an activity.
- Dependency describes which activity constrains another.
- Float or slack is the amount of scheduling flexibility an activity has.
The critical path can change. A near-critical task that slips, a new dependency, or a changed duration can create a different longest path. That is why CPM is a recurring schedule-control practice, not a one-time diagram.
How do you calculate a critical path?
Build a network of activities, assign durations, connect valid dependencies, then perform a forward pass and a backward pass.
- List the activities needed to reach the finish milestone.
- Give each activity a realistic duration and calendar.
- Add predecessor relationships.
- Run a forward pass to calculate earliest start and earliest finish.
- Run a backward pass to calculate latest start and latest finish without delaying the project.
- Calculate total float as latest start minus earliest start, or latest finish minus earliest finish.
Consider this simplified network:
| Activity | Duration | Predecessor | Earliest finish |
|---|---|---|---|
| A: Define scope | 2 days | None | Day 2 |
| B: Design | 4 days | A | Day 6 |
| C: Prepare content | 3 days | A | Day 5 |
| D: Build | 5 days | B | Day 11 |
| E: Launch | 1 day | C and D | Day 12 |
The A → B → D → E path takes 12 days. The A → C → E path is shorter, so C has scheduling flexibility unless another constraint removes it. This example assumes simple finish-to-start links, one calendar, and no resource constraint.
What is the difference between critical path and critical task?
A critical task is one activity on the current critical path; the critical path is the whole connected sequence that controls the finish. Treating every high-priority task as “critical” makes the term useless. Priority describes business importance, while CPM describes schedule mathematics.
A task may also be operationally important without having zero float. Review near-critical work, external approvals, and scarce-resource assignments alongside the calculated path.
What can make a CPM calculation misleading?
CPM is only as reliable as the schedule model. Common causes of false confidence include:
- missing or illogical dependencies
- summary tasks linked like executable work
- durations entered as desired dates rather than estimates
- different calendars ignored
- fixed deadlines mistaken for network logic
- resource conflicts left unresolved
- actual progress and remaining duration not updated
CPM does not automatically solve resource overload, uncertainty, or scope control. Resource leveling can move tasks and change the critical path. For highly uncertain durations, a three-point method such as PERT can complement CPM.
How often should you review the critical path?
Review it whenever the schedule changes materially and at the project’s normal control cadence. A weekly review may suit a multi-month project; a release cutover may need daily review. Compare the current path with near-critical paths, validate remaining durations with task owners, and investigate negative float rather than merely reporting it.
Use the path to focus questions: What assumption changed? Which handoff is at risk? Can work be resequenced safely? Is added capacity useful, or is the constraint an approval that more people cannot accelerate?
When should you use CPM instead of PERT?
Use CPM when one working duration per activity is a useful planning approximation and dependency logic is the main scheduling concern. Use PERT-style three-point estimates when duration uncertainty itself needs explicit treatment. Many teams use a hybrid: three-point estimates for uncertain activities, then a dependency network to show the resulting schedule.
| Question | CPM | PERT-style estimation |
|---|---|---|
| Primary focus | Dependency-driven schedule | Duration uncertainty |
| Duration input | Usually one working estimate | Optimistic, most likely, pessimistic |
| Best output | Critical and near-critical paths | Expected duration and uncertainty discussion |
| Main risk | False precision from weak logic | False confidence in subjective estimates |
How can GanttFather help you review the critical path?
When is GanttFather useful for critical-path analysis?
GanttFather calculates the critical path from task dates and dependencies and lets you inspect it on the same interactive Gantt chart used to edit the plan. It is useful when a team needs to test a duration or dependency change and immediately see which path now controls the finish.
It does not replace estimate validation, risk analysis, or automatic resource leveling, and it has no dedicated baseline-overlay feature. Pair the calculated path with the float and slack guide and the dependency-types guide before using it for a commitment.
Build a dependency-based schedule in GanttFather and verify the logic with the people doing the work.
Frequently asked questions
Is the critical path always the longest path?
It is the longest duration path through the modeled dependency network that controls the finish. Constraints and calendars can affect the calculation, so “longest” refers to schedule duration, not the number of tasks.
Can a project have more than one critical path?
Yes. Two or more paths can have the same controlling duration. Multiple critical paths reduce flexibility because a delay on any one of them can move the finish.
Is zero float the same as high priority?
No. Zero float is a schedule result. Priority is a management decision about importance. A high-priority task can have float, and a low-visibility technical task can be critical.
What is negative float?
Negative float means the modeled network cannot meet a required date under its current assumptions. It is a signal to change scope, sequence, duration, capacity, or the imposed date—not spare time that can be used.
Does CPM account for limited resources?
Not by itself. Classic CPM calculates from activity logic and durations. Resource leveling or another capacity analysis is needed when people or equipment cannot perform all scheduled work concurrently.
Who developed CPM?
James E. Kelley Jr. and Morgan R. Walker documented the early critical-path scheduling work associated with Remington Rand and DuPont in the late 1950s. PERT was developed separately for uncertain research-and-development scheduling.
