How to Find the Critical Path (With a Simple Example)
Your sponsor asks one simple question: “When will it be done?” You open your plan. There are twenty tasks, a few arrows, and a date you picked weeks ago. You know some tasks matter more than others, but which ones really decide the finish date?
That is exactly what the critical path tells you. In this guide you will learn how to find the critical path in five simple steps, with a small worked example you can follow with a pen and paper. If you would rather skip the arithmetic, try the free Critical Path Calculator and check your numbers in seconds.
What the Critical Path Really Means
A project is a set of tasks, and some tasks must wait for others. Line the tasks up by their dependencies and you get several routes from start to finish. Each route has a total duration.
The longest route is the critical path. It sets the shortest possible time for the whole project.
If a task on the critical path slips by one day, the project finishes one day late.
Tasks off the critical path have breathing room. That spare time is called float (or slack). Critical tasks have zero float. That is the whole idea.
How to Find the Critical Path in 5 Steps
Step 1: List every task with a duration
Write each task and your best estimate in days. Keep tasks small enough to estimate honestly. If you can’t estimate it, split it.
Step 2: Note what each task depends on
For every task, ask: “What must be finished before this can start?” Write the answer next to it. Tasks with no answer can start on day one.
Step 3: Draw the network and list every path
Draw boxes for tasks and arrows for dependencies. Then trace every route from the first task to the last one. On a small project this takes minutes.
Step 4: Add up each path and pick the longest
Add the durations along each path. The biggest total is your critical path, and that total is the project duration.
Step 5: Calculate float for the other tasks
Float is how long a task can slip without moving the finish date. The simple way: float = late start minus early start. You get both numbers from a forward pass and a backward pass, which the example below shows.
A Worked Example: Releasing a New Feature
Say your team is releasing a small feature. Here are the tasks, in days.
| Task | Description | Days | Depends on |
|---|---|---|---|
| A | Gather requirements | 3 | None |
| B | Design | 4 | A |
| C | Backend development | 6 | B |
| D | Frontend development | 5 | B |
| E | Set up test environment | 2 | A |
| F | Integration | 3 | C, D |
| G | Testing | 4 | E, F |
| H | Release | 1 | G |
Now list every path from A to H and add the days.
| Path | Calculation | Total |
|---|---|---|
| A → B → C → F → G → H | 3 + 4 + 6 + 3 + 4 + 1 | 21 days |
| A → B → D → F → G → H | 3 + 4 + 5 + 3 + 4 + 1 | 20 days |
| A → E → G → H | 3 + 2 + 4 + 1 | 10 days |
The longest path is A → B → C → F → G → H at 21 days. That is your critical path, and 21 days is the earliest the feature can ship.
Checking the float
Run a forward pass to get the earliest start for each task, then a backward pass from day 21 to get the latest start. Here is what you get.
| Task | Earliest start | Latest start | Float |
|---|---|---|---|
| A | 0 | 0 | 0 (critical) |
| B | 3 | 3 | 0 (critical) |
| C | 7 | 7 | 0 (critical) |
| D | 7 | 8 | 1 day |
| E | 3 | 14 | 11 days |
| F | 13 | 13 | 0 (critical) |
| G | 16 | 16 | 0 (critical) |
| H | 20 | 20 | 0 (critical) |
Look at what this tells you. Frontend development (D) can slip one day and nobody notices. The test environment (E) can slip almost two weeks. But one lost day on backend development (C) pushes the release by a day.
Now you know where to spend your attention. You’re not guessing any more.
What to Do With the Critical Path
- Watch critical tasks daily. Ask for early warning, not a status update at the deadline.
- Protect your best people. Don’t pull someone off a critical task to help with a task that has float.
- Shorten it only where it counts. Adding people to task C can cut the project. Adding people to task E cannot.
- Recalculate often. Once task D uses up its one day of float, it becomes critical too. The critical path can move.
A common mistake is treating the critical path as fixed. It’s not. Estimates change, scope changes, and a different path can take over. If scope is shifting on your project, this guide on managing scope changes without hurting quality will help.
Common Mistakes to Avoid
- Hidden dependencies. A task that “obviously” follows another but isn’t written down will break your calculation. Ask the team, don’t assume.
- Padding every estimate. If each task carries a quiet buffer, the real critical path gets hidden. Estimate honestly, then add one clear buffer at the end.
- Forgetting people. Two tasks may look parallel on paper, but if one person owns both, they run one after the other.
- Calculating once and filing it away. A plan from week one is a guess by week six.
Fix these four and your critical path becomes something you can trust, not just a chart on a wall.
Simple Action Plan
- Pick one real project, even a small one.
- List 8 to 12 tasks with durations and dependencies.
- Add up every path and mark the longest one.
- Work out float for the rest.
- Check your answer with the Critical Path Calculator.
- Review it again every week.
Conclusion
The critical path is not a fancy theory. It is the longest chain of dependent tasks, and it decides your finish date.
Find it once and you know what to protect. Ignore it and every task looks equally urgent, which means none of them are.
Try it on your current project this week. It takes less than an hour.
Try It Yourself
Open the free Critical Path Calculator, enter the example tasks above, and see the 21-day result for yourself. More tools like it are on the Free Tools page.
FAQs
What is the critical path in simple words?
It is the longest chain of tasks that must happen one after another. Its total length is the shortest time your project can take.
Can a project have more than one critical path?
Yes. If two paths have the same longest duration, both are critical. That makes the project riskier, because you now have two chains to protect.
What does zero float mean?
It means the task has no spare time. If it starts late or takes longer than planned, the project finish date moves.
Can I find the critical path without software?
Yes, for a small project. List the paths, add up the durations, and pick the longest. Software helps once you have dozens of tasks, because the paths multiply quickly.
How often should I recalculate the critical path?
Whenever estimates, dependencies or scope change, and at least at every milestone. During execution the critical path can shift as real durations replace estimates.
What if the critical path is longer than my deadline?
You have three options: cut scope, run some critical tasks in parallel, or add resources to critical tasks. Each has a cost, so talk to your sponsor early.
Atul Sharma PMP
IT professional with 20+ years of experience and author of books on communication, AI and career growth for testers, project managers and IT professionals.
