Critical Path Expected Completion Time: How to Find It

This guide shows you how to calculate the expected completion time of a project using the Critical Path Method (CPM). You’ll identify the longest sequence of dependent tasks, add their durations, and that total is your project’s expected finish date. Before you start, you’ll need a list of all project activities, their estimated durations, and which tasks depend on which.

What You’ll Need

  • A complete list of project tasks or activities.
  • The estimated duration for each task (in days, hours, or any consistent unit).
  • Dependencies: for each task, know which tasks must finish before it can start.
  • A pencil and paper, a spreadsheet, or project management software.

Step-by-Step

  1. List all activities and durations. Write down every task in the project. Include a duration estimate for each. If you’re using a tool, enter them there.
  2. Identify dependencies. For each task, note which other tasks must be completed first. For example, “pour foundation” depends on “dig hole.” If a task has no dependencies, it can start immediately.
  3. Draw a network diagram. Create a visual flow: each task is a box (or node), and arrows show dependencies. Start with tasks that have no predecessors, then connect each task to its successors. This is your project network.
  4. Calculate the Early Start (ES) and Early Finish (EF) for each task. The Early Start is the earliest time a task can begin, which is the latest Early Finish of all its predecessor tasks. The Early Finish is ES + duration. For the first task(s), ES = 0.
  5. Find the project’s earliest finish. The Early Finish of the final task(s) gives you the overall earliest completion time. If there are multiple final tasks, take the largest EF.
  6. Calculate the Late Start (LS) and Late Finish (LF) for each task, working backward. The Late Finish is the latest time a task can finish without delaying the project. For the final task(s), LF = project earliest finish. For other tasks, LF = the smallest LS of all its successor tasks. The Late Start is LF – duration.
  7. Compute the float (slack) for each task. Float = LS – ES (or LF – EF). This is how much a task can be delayed without affecting the project end date.
  8. Identify the critical path. The critical path is the sequence of tasks with zero float. These tasks cannot be delayed without delaying the whole project. There can be more than one critical path.
  9. Add up the durations of the critical path tasks. The sum of the durations along the critical path is your project’s expected completion time. This matches the project’s earliest finish you found in step 5.

Common Mistakes

  • Forgetting dependencies. If you miss a dependency, your network will be wrong, and the critical path will be incorrect.
  • Using the longest path instead of the critical path. The critical path is the longest path in terms of duration, but only after you’ve correctly modeled dependencies. Sometimes a path with many tasks has a shorter total duration than a path with fewer but longer tasks.
  • Ignoring multiple critical paths. If two paths both have zero float, both are critical. Delaying either will delay the project.
  • Using average durations without considering uncertainty. The expected completion time assumes your duration estimates are accurate. If estimates are rough, the result is only as good as those estimates.
  • Not updating the diagram. If a task takes longer than planned, the critical path can change. Recalculate after any significant delay.

Tips

  • Use a spreadsheet. You can set up columns for ES, EF, LS, LF, and float. Formulas make recalculation easy when durations change.
  • Double-check your forward and backward passes. A common error is miscomputing the latest start or finish. Verify with a small example.
  • Keep durations realistic. Use historical data or expert input rather than optimistic guesses.
  • Remember that the critical path can change. If a non-critical task gets delayed enough, it may become critical. Monitor float regularly.
  • Consider using project management software. Most tools automatically calculate the critical path and expected finish date, but you should still understand the logic.

Troubleshooting

  • You get a negative float. This means your project cannot finish by the target date with current durations. You’ll need to shorten tasks (crashing) or change the target.
  • Your critical path seems too short. Check that you included all tasks and dependencies. A common oversight is forgetting a task that is not on the main flow but is still required.
  • Two tasks have the same name. Ensure each task has a unique identifier to avoid confusion in the network.
  • The network diagram has loops. Dependencies should be one-way. If you have a cycle, you’ve made an error—go back and review the dependency list.
  • You’re unsure about a dependency. Ask the person responsible for the work. Guessing can lead to an incorrect critical path.

Frequently Asked Questions

What exactly is the critical path?

The critical path is the longest sequence of dependent tasks in a project. It determines the shortest possible project duration. Any delay on this path delays the entire project.

Can there be more than one critical path?

Yes. If two different sequences of tasks both have zero float, both are critical. Delaying any task on either path will delay the project.

What does float (slack) mean?

Float is the amount of time a task can be delayed without affecting the project’s finish date. Tasks on the critical path have zero float.

How do I handle uncertain durations?

Use a technique like PERT (Program Evaluation and Review Technique) that uses optimistic, pessimistic, and most likely estimates to calculate an expected duration. This gives a more realistic critical path.

Do I need special software to find the critical path?

No. You can do it manually with a network diagram and simple arithmetic. Software helps with large projects and automatic updates, but the logic is the same.

What if my project has hundreds of tasks?

Manual calculation becomes impractical. Use project management software that can handle complex networks and recalculate the critical path as you update progress.