Defining the Critical Path in Microsoft Project

The critical path is the longest path through the network based on task duration. This measures the shortest amount of time in which the project can be completed. Tasks not on the critical path have slack, while tasks on the critical path have zero slack. Slack is the amount of time that a task can be delayed without impacting the project end date.

A project activity network looks like this:

Project Activity Network

Calculating the Critical Path

There are plenty of tools like Microsoft Project that can calculate the critical path for you. But even when using software, it’s helpful to know how it is calculate and understand what factors will affect it.

Calculating the critical path requires some assumptions and estimation. Some of the key assumptions include:

◆ All tasks are known: If you forget to add some tasks and add them later, the original critical path may change. Most project plans are missing tasks when they are initially built.

◆ All links are accurate: A complicated plan with hundreds of tasks is likely to have some incorrect task dependencies defined.

◆ All estimates are accurate: Inaccurate estimates can cause the original critical path to change.

◆ Other non-critical paths may have small amounts of slack: A complicated activity path can have multiple noncritical paths. A change in any one of these paths can cause the original critical path to change.

Given the amount of assumptions we rely on in our analysis, the only time you know the actual critical path is after project completion.

Despite these potential problems, the critical path method gives the project manager a good indication of where to focus attention. The most important application of CPM is to realize a late task on the critical path will cause the project end date to change.

The following shows an example of calculating the critical path.


Length of Path



9 days



12 days



11 days


Note that tasks 3, 4, or 6 can be up to 3 days late without changing the critical path. These tasks each have three days of slack.

Also note that the tasks on the 1-2-5-7-10 path are on the critical path and have zero days of slack. If any task on the critical path is late, the project end date will be later.

◆ What would happen if Task 2 consumed five days instead of three days?

◆ What would the length of the 1-2-5-7-10 path become?

In this case would the 1-2-5-7-10 path still be critical?

Further Reading

There are a couple of other related terms that can be useful in understanding more about the critical path. One of those is CPM, which is simply an acronym for the Critical Path Method. For a comprehensive guide on the Critical Path Method, we recommend’s article.

Another similar concept is Program Evaluation and Review Technique (PERT). PERT evaluates a probable outcome based on three scenarios: a best-case, expected-case, and worst-case scenario. The outcome in question may be the duration of a task, its start date, or its finish date.

Click here for a guide on identifying the critical path in Microsoft Project. For the most comprehensive look at how to manage projects using project management software, you can purchase our training guide on Microsoft Project.