Definition: The critical path method (CPM) is a scheduling technique that finds the longest chain of dependent tasks in a project. That chain sets the earliest possible finish date. A task on it has zero float, so any delay to that task delays the whole project.
You already sense this in your own projects. Ten things are in flight, but one of them, the approval, the build, the shipment, is the one everybody is quietly waiting on. CPM finds that one with arithmetic instead of instinct, and it tells you exactly how much room every other task has.
TL;DR: CPM lists every task with a duration and its dependencies, runs a forward pass to get the earliest times and a backward pass to get the latest times, then calculates float. Tasks with zero float form the critical path. Protect those tasks first. See the links on a Gantt view. Map your project free →
Why the Critical Path Method Matters in 2026
A project rarely fails because every task ran late. It fails because a few specific tasks ran late and nobody knew which ones counted. CPM is the method that names those tasks. It is old, but the question it answers is the one every schedule review still asks: what actually decides the date?
CPM was developed in the late 1950s by Morgan R. Walker of DuPont and James E. Kelley Jr. of Remington Rand, according to Wikipedia's article on the critical path method. The U.S. Navy and Booz Allen Hamilton developed PERT at about the same time. The two methods share the idea of a longest path through a network of tasks. CPM uses one duration per task. PERT was built to handle uncertain estimates.
Modern teams use it for a practical reason. When work is spread across people, tools, and time zones, the calendar hides the real constraint. A due date on every task looks equally urgent. CPM separates the tasks that set the finish date from the tasks that have slack, so your attention goes where a slip costs you the launch.
How the Critical Path Method Works
CPM turns a task list into a network. Each task is a node, each dependency is an arrow, and each node carries a duration. You then walk the network twice, once forward and once backward, and compare the two answers. The tasks where the answers match have no float, and they are your critical path.
- List every task. Pull the tasks from your work breakdown structure so nothing is missing. Give each task one duration in days.
- Link the dependencies. Record which tasks must finish before another starts. Most links are Finish-to-Start. See the 4 dependency types.
- Run the forward pass. Start at zero. Early Finish (EF) equals Early Start (ES) plus duration. When a task has several predecessors, its ES is the largest EF among them.
- Run the backward pass. Start from the project finish date. Late Start (LS) equals Late Finish (LF) minus duration. When a task has several successors, its LF is the smallest LS among them.
- Calculate float. Float equals LS minus ES, which also equals LF minus EF.
- Trace the critical path. Follow the tasks with zero float from start to finish. Their durations add up to the project duration.
The forward and backward rules match the standard method described by Asana's CPM guide and PMI's CPM basics.
What Is Float (Slack)?
Float is how long a task can slip without moving the project end date. Zero float means no room. A task with 6 days of float can run 6 days late and the launch date stays the same, as long as nothing else changes. Float is a shared budget, not a personal allowance. When two tasks on the same path use the float together, they can consume it twice.
Critical Path Method Example
Take a small website launch with six tasks. Durations are in working days. The critical path is the chain with zero float.
| Task | Duration and depends on | ES to EF | LS to LF | Float |
|---|---|---|---|---|
| A. Kickoff and brief | 2 days, none | 0 to 2 | 0 to 2 | 0 |
| B. Design | 5 days, after A | 2 to 7 | 2 to 7 | 0 |
| C. Write copy | 3 days, after A | 2 to 5 | 4 to 7 | 2 |
| D. Build pages | 6 days, after B and C | 7 to 13 | 7 to 13 | 0 |
| E. Legal review | 2 days, after C | 5 to 7 | 11 to 13 | 6 |
| F. Launch | 1 day, after D and E | 13 to 14 | 13 to 14 | 0 |
Read the table this way. Task D starts on day 7 because it waits for the slower of B (day 7) and C (day 5). Task C finishes early and has 2 days of float. Task E has 6 days of float. The critical path is A, B, D, F, and 2 + 5 + 6 + 1 equals 14 days. If Design slips by 1 day, the launch moves to day 15. If Legal review slips by 4 days, nothing moves.
That is the payoff. You now know that Design and Build decide the date, and that the copy and legal work can flex. A manager with this table can move a writer to help Design, and can stop chasing Legal for a status update on day 6.
Critical Path vs Gantt Chart vs PERT
CPM is a calculation. A Gantt chart is a picture. PERT is a related calculation with three time estimates per task. They work together, not against each other.
| Tool | What it does | Best for |
|---|---|---|
| CPM | Finds the zero-float chain and the finish date | Deciding where to focus |
| Gantt chart | Draws tasks and links on a timeline | Sharing and tracking the plan |
| PERT | Uses optimistic, likely, and pessimistic estimates | Work with uncertain durations |
| Project timeline | Shows the schedule at a glance | Stakeholder updates |
Common Critical Path Mistakes
- Missing dependencies. An unlisted link makes a task look free when it is not. The critical path is only as good as the network behind it.
- Padding every estimate. If every task carries a hidden buffer, float appears everywhere and the critical path blurs. Estimate honestly and hold buffer at the end.
- Ignoring resources. CPM assumes people are free when their tasks start. If one person owns two parallel tasks, the real path is longer. See resource allocation.
- Setting the path once. Durations change and float gets used up. A task with 2 days of float can become critical after two small slips. Recalculate at every milestone.
- Watching only zero float. Near-critical paths with 1 or 2 days of float can turn critical fast. Track them too.
Connection to Taskade
Taskade does not calculate float for you, and this page does not claim it does. What Taskade gives you is the place where the network lives. Tasks carry owners and due dates, and the Gantt Chart view, a paid-plan view in the More Views menu, draws the links between tasks on a timeline. You do the forward and backward pass once, note the zero-float tasks, and mark them with a custom field such as "Critical: yes". Then a Table view filtered to that field is your watch list.
Automations can help you act on it. An automation can notify the next owner when a critical task is marked done, or message the team when a critical task passes its due date. An AI agent can read your task list and draft the network from a plain description, and you confirm the durations.
What You Would Build in Taskade
Describe the project, and Taskade Genesis builds a critical-path tracker. Imagine one Table with every task, its duration, its predecessors, a float column, and a "Critical" flag. A summary tile counts critical tasks that are overdue. A reliable automation pings the owner of the next critical task the moment its predecessor closes. You get one screen that shows what decides the date. Describe yours and build it free →
Related Terms and Concepts
- Dependencies: The links that form the network CPM walks.
- Work Breakdown Structure: The task list CPM starts from.
- Gantt Chart: The chart that draws the path on a timeline.
- Project Timeline: The schedule that CPM validates.
- Milestone: The checkpoints where you recalculate float.
- Resource Allocation: The constraint CPM ignores unless you add it.
- Project Life Cycle: The phases in which the schedule is built and updated.
- Blog: A guide to using CPM in project management.
Frequently Asked Questions About the Critical Path Method
What is the critical path in project management?
The critical path is the longest chain of dependent tasks from project start to finish. Its total duration is the shortest time the project can take. Every task on it has zero float, so a delay to any of them delays the finish date.
How do you find the critical path?
List the tasks and durations, link the dependencies, run a forward pass for earliest times and a backward pass for latest times, then calculate float for each task. The chain of zero-float tasks is the critical path. Check your work: the critical task durations must add up to the project duration.
What is float or slack in CPM?
Float is the time a task can slip without delaying the project end date. It equals late start minus early start, or late finish minus early finish. Zero float means the task is critical. Positive float means the task has room.
Can a project have more than one critical path?
Yes. If two chains have the same total length, both have zero float, and you must protect both. Near-critical paths, with only a day or two of float, also deserve attention because a small slip can make them critical.
What is the difference between CPM and PERT?
CPM uses one duration per task and suits work you can estimate well. PERT uses three estimates per task, optimistic, likely, and pessimistic, and suits work with uncertain durations. Both find the longest path through a task network.
Can the critical path change during a project?
Yes. Tasks finish early or late, scope changes, and float gets used up. A task that had 2 days of float can become critical after two small slips. Recalculate the path at each milestone or whenever the plan changes.
How do you shorten the critical path?
Only work on the critical path shortens the project. Add resources to a critical task, split it so parts run in parallel, or change a Finish-to-Start link to overlap with a lead. Cutting a task with float saves nothing.
Does CPM work for Agile projects?
CPM fits best where work has fixed order and known durations, such as construction, launches, and migrations. Agile teams that plan in short sprints use it less, but a cross-team release with hard handoffs can still use it at the release level.