Critical Path Method: How to Find Your Project's Critical Path (With Example)

Every project has a handful of tasks that decide the finish date. If one of them slips by two days, the whole project slips by two days. Other tasks have some breathing room and can move without anyone noticing. The critical path method (CPM) is how you tell the two apart before the schedule surprises you.

This guide explains what the critical path is, how to find it step by step with a forward and backward pass, how to read float, and how to use the result to protect your deadline. A worked example runs through the whole process, and there are short notes for construction, healthcare operations and small business teams.

What is the critical path?

The critical path is the longest chain of dependent tasks from the start of a project to its finish. Because it is the longest chain, its total duration equals the shortest possible length of the project. Any delay on a task in that chain delays the end date by the same amount, unless you change the plan.

Tasks on the critical path have zero float (also called slack). Float is how long a task can be delayed without pushing back the project finish. Tasks off the critical path have some float, which is exactly why they are less urgent to watch day to day.

Key terms in plain words

• Duration: how many working days a task takes.
• Dependency: a rule that links two tasks, for example "painting starts after drywall finishes" (Finish-to-Start).
• Early Start (ES) and Early Finish (EF): the earliest a task can start and finish, given its predecessors.
• Late Start (LS) and Late Finish (LF): the latest a task can start and finish without delaying the project.
• Float: LS minus ES (or LF minus EF). Zero float means the task is critical.

Why the critical path matters

• It tells you where to focus. Instead of chasing every task equally, you watch the few that actually control the finish date.
• It gives honest answers about deadlines. If the client asks for the project two weeks earlier, you know which chain has to get shorter, and by how much.
• It shows where you can borrow time. Tasks with float can absorb small delays or wait while people help on critical work.
• It makes change requests easier to discuss. When a new task appears, you can check whether it lands on the critical path and say clearly what it does to the end date.

How to find the critical path in 6 steps

1. List every task

Start from your work breakdown: the deliverables split into tasks small enough to estimate. Keep tasks at a level where one person or one crew owns each one. Very large tasks hide the real sequence; very tiny ones make the network hard to read.

2. Estimate durations

Give each task a realistic duration in working days. Ask the person who will do the work, not only the person who wants it done. If a task is uncertain, note it; uncertain tasks on the critical path belong in your risk register.

3. Map the dependencies

For each task, write down what must happen first. Most links are Finish-to-Start (B starts when A finishes). Some are Start-to-Start (B can start once A starts) or Finish-to-Finish (B finishes only after A finishes). Only record real dependencies, the ones caused by the work itself, materials, approvals or shared crews. Imaginary dependencies make the path look longer than it is.

4. Do the forward pass

Go from the first task to the last. A task with no predecessor starts at day 0. For every other task, the Early Start is the latest Early Finish among its predecessors. Early Finish is Early Start plus duration. The largest Early Finish at the end is your project duration.

5. Do the backward pass

Now go from the last task back to the first. The final task's Late Finish equals the project duration. For every other task, Late Finish is the earliest Late Start among the tasks that follow it. Late Start is Late Finish minus duration.

6. Calculate float and mark the path

Float is Late Start minus Early Start. Every task with zero float is on the critical path. Connect them in order and you have it. Some projects have more than one critical path, or a "near-critical" chain with only a day or two of float; treat those with nearly the same attention.

Worked example: a small office fit-out

The numbers below are a made-up illustration, not data from a real project. A team is fitting out a small office. Durations are in working days, and every link is Finish-to-Start.

• A. Site survey (2 days), no predecessor
• B. Order materials (5 days), after A
• C. Demolition (3 days), after A
• D. Electrical rough-in (4 days), after C
• E. Plumbing rough-in (3 days), after C
• F. Drywall (4 days), after B, D and E
• G. Painting (3 days), after F
• H. Furniture delivery (2 days), after B
• I. Final inspection (1 day), after G and H

The forward and backward pass results

Reading the result

The project takes 17 working days. The critical path is A, C, D, F, G, I: site survey, demolition, electrical rough-in, drywall, painting and final inspection (2 + 3 + 4 + 4 + 3 + 1 = 17 days).

• Plumbing rough-in has 1 day of float. It is near-critical, so a small slip there quickly becomes a project delay.
• Ordering materials has 2 days of float. If the supplier runs late by more than two days, drywall cannot start on time and the path changes.
• Furniture delivery has 7 days of float. It can move around freely, which is useful if the delivery window is hard to book.

If the client wants the office three days sooner, shortening furniture delivery achieves nothing. The team has to shorten tasks on the critical path, for example by adding a second electrician or overlapping painting with the end of drywall where the work allows it.

How to shorten a project using the critical path

• Crashing: add people, equipment or overtime to a critical task to cut its duration. It usually costs more, so check your budget first.
• Fast-tracking: run tasks in parallel that were planned in sequence, often by changing a Finish-to-Start link to Start-to-Start. It saves time but adds the risk of rework.
• Re-checking dependencies: remove links that are habits rather than real constraints.
• Removing scope: agree to move a non-essential deliverable to a later phase.

After any of these changes, run the passes again. Shortening one chain can make another chain the new critical path.

Critical path examples by team type

Construction and field teams

Inspections, permits and long-lead materials often sit on or near the critical path. Shared crews matter too: if the same team does framing and drywall, those tasks cannot run at the same time even when the drawings say they could, so add that link.

Healthcare operations

For a project like moving a department to a new floor or rolling out a new check-in process, staff training and equipment readiness tend to control the go-live date. Approvals from several departments can quietly become the longest chain, so give each approval its own task and duration.

Small business

For a product or website launch, supplier lead times, content creation and final review are typical critical tasks. Owners often do several tasks themselves, which means those tasks run in sequence, not in parallel. Plan them that way.

Common critical path mistakes

• Calculating it once and never again. The path changes as real dates come in. Revisit it at every status update.
• Ignoring near-critical tasks. A task with one day of float deserves almost the same attention as a critical one.
• Optimistic durations. A critical path built on best-case estimates gives a finish date nobody can hit.
• Forgetting non-work waits. Approvals, deliveries, curing times and client reviews take calendar time, so include them as tasks.
• Missing people constraints. If one person owns two tasks, they usually cannot do both at once.

Planning the critical path with GanttMaster

In GanttMaster on iPhone and iPad, you can turn the steps above into a working schedule. Break the project into tasks and subtasks with start and end dates, then link them with Finish-to-Start, Start-to-Start or Finish-to-Finish dependencies from each task's Dependencies tab.

The interactive Gantt chart then draws the linked bars, so the chain you identified in your forward and backward pass is visible on one timeline. Giving critical tasks a high priority makes them easy to spot in task lists, and project checkpoints such as "Inspection passed" can be added as short tasks linked to the work they depend on.

Assign each critical task to a person or team, add the uncertain ones to the Project Risks card with an owner and mitigation plan, and keep the cost of crashing visible in the Budget card. The Today view with reminders helps owners see what is due each day, and because there is no extra cost per team member, everyone who works on the critical path can be in the project.