Log In

The Critical Path Method: A Practical Guide for Project Managers

Decorative critical path method title card

The critical path method (CPM) identifies the longest sequence of dependent activities in a project schedule, and that sequence sets the minimum time the project can finish. Every activity on that path carries zero total float, meaning any delay there pushes the end date by exactly the same amount. That is why CPM sits at the center of serious project scheduling, from construction timelines to product launches.

Three things to know before reading further:

  • Calculate forward first. Run a forward pass to find each activity’s Earliest Start (ES) and Earliest Finish (EF), then run a backward pass for Latest Start (LS) and Latest Finish (LF).
  • Zero float = critical. Activities where Total Float equals zero form the critical path and deserve your closest monitoring.
  • The path shifts. Resource constraints, scope changes, and actual progress can move the critical path mid-project, so recalculate regularly.

Key Takeaways

The critical path method identifies the longest zero-float sequence in a project network, and that sequence sets the project’s minimum finish date, requiring continuous monitoring as resources and scope evolve.

Point Details
Zero float defines the critical path Activities where Total Float equals zero form the critical path and control the project finish date.
Two-pass algorithm Run a forward pass (EF = ES + Duration) then a backward pass (LS = LF – Duration) to compute float for every activity.
Compression has tradeoffs Crashing adds cost; fast tracking adds rework risk. Both can create new critical paths after compression.
Resource constraints shift the path A non-critical activity can become effectively critical when its required resources are reallocated or unavailable.
Management and Strategy Institute The Lean Six Sigma Black Belt Certification covers CPM and schedule optimization methods with all materials included at one price.

Table of Contents

What is the critical path method in project scheduling?

CPM is a deterministic scheduling technique that models a project as a network of activities connected by logical dependencies. You assign a fixed duration to each activity, run the two-pass algorithm, and the network reveals which sequence of tasks controls the finish date. The Project Management Institute includes CPM in its PMBOK Guide as a core schedule network analysis method, and it remains the dominant approach for projects with well-defined scopes and fixed deadlines.

CPM was developed in the late 1950s by Morgan R. Walker and James E. Kelley Jr., originally for chemical plant maintenance scheduling. It has since expanded to include resource-based scheduling extensions like resource leveling and resource smoothing, as documented in the Wikipedia overview of CPM.

CPM works best when durations are known with reasonable confidence: construction projects, manufacturing rollouts, regulatory submissions, and procurement-heavy programs all fit well. When duration estimates carry high uncertainty, PERT (Program Evaluation and Review Technique) is a better starting point, though hybrid approaches combining both are common in practice.

Core CPM components and terms you need to know

Before running the algorithm, get these definitions straight:

  • Activity: A discrete, schedulable unit of work with a defined start, finish, and resource requirement.
  • Duration: The estimated time to complete an activity, expressed in consistent units (days, weeks).
  • Dependency (logical relationship): The rule governing when one activity can start relative to another. Finish-to-Start (FS) is the most common: the successor cannot start until the predecessor finishes.
  • Milestone: A zero-duration activity marking a key event or deliverable.
  • ES (Earliest Start): The earliest an activity can begin, given its predecessors.
  • EF (Earliest Finish): ES plus Duration.
  • LS (Latest Start): The latest an activity can begin without delaying the project.
  • LF (Latest Finish): LS plus Duration.
  • Total Float: The amount of time an activity can slip without delaying the project end date. Formula: LS minus ES (or LF minus EF).
  • Free Float: How much an activity can slip without delaying any immediate successor.
  • Critical Path: The sequence of activities with zero total float. It is the longest path through the network and determines project duration.
  • Near-Critical Path: A path with very small (but non-zero) float. Worth watching because minor slippage can make it critical.
  • Critical Path Drag: A concept that quantifies how much a specific critical activity extends the project completion date. Wikipedia’s CPM article explains it this way: drag equals the activity’s duration when nothing runs in parallel with it, or the lesser of its duration and the smallest float of any parallel activity when parallel work exists. Drag is the most precise tool for targeting compression efforts.
  • Activity-on-Node (AON): The modern diagramming convention where each node (box) represents an activity and arrows represent dependencies. AON has largely replaced Activity-on-Arrow (AOA) because it handles complex dependency types more cleanly and is what virtually all scheduling software uses today.

How does the CPM algorithm calculate the critical path?

The CPM algorithm runs two passes through the network, then computes float for every activity.

Diagram of CPM forward and backward pass calculation

Forward pass: finding earliest times

Set the first activity’s ES to 0. Then apply these two rules throughout the network:

EF = ES + Duration

For any activity with multiple predecessors, its ES is the maximum EF among all predecessors:

ES = max(EF of all predecessors)

Work forward through every activity until you reach the last one. The EF of the final activity is the project duration.

Backward pass: finding latest times

Set the final activity’s LF equal to the project duration (the EF you just calculated). Then apply:

LS = LF – Duration

For any activity with multiple successors, its LF is the minimum LS among all successors:

LF = min(LS of all successors)

Work backward through every activity until you reach the first one.

Computing float and identifying the critical path

For each activity:

Total Float = LS – ES (equivalently, LF – EF)

Free Float = ES(successor) – EF(activity)

Activities with Total Float = 0 are critical. The sequence connecting them from project start to finish is the critical path. When two or more paths both carry zero float, the project has multiple critical paths, each requiring equal monitoring attention.

Pro Tip: When setting up a manual calculation, always verify that the backward pass LS for your first activity equals 0. If it does not, you have a calculation error somewhere in the network.

A worked example: calculating the critical path step by step

The example below uses six activities. Reproduce it in a spreadsheet to practice before applying it to a real schedule.

Activity table

Activity Duration (days) Predecessors
A 3 None
B 4 A
C 2 A
D 5 B
E 3 C
F 2 D, E

Forward pass

  1. Activity A: ES = 0, EF = 0 + Duration.
  2. Activity B: ES = EF(A), EF = ES + Duration.
  3. Activity C: ES = EF(A), EF = ES + Duration.
  4. Activity D: ES = EF(B), EF = ES + Duration.
  5. Activity E: ES = EF©, EF = ES + Duration.
  6. Activity F: ES = max(EF(D), EF(E)), EF = ES + Duration.

The project duration is the EF of the final activity.

Backward pass

  1. Activity F: LF = project duration, LS = LF – Duration.
  2. Activity D: LF = LS(F), LS = LF – Duration.
  3. Activity E: LF = LS(F), LS = LF – Duration.
  4. Activity B: LF = LS(D), LS = LF – Duration.
  5. Activity C: LF = LS(E), LS = LF – Duration.
  6. Activity A: LF = min(LS(B), LS©), LS = LF – Duration.

Float and critical path

Critical path: A → B → D → F, with a total duration of 14 days.

Activities C and E each carry 4 days of float, so they form a near-critical path worth watching. If either slips more than 4 days, it joins the critical path and the project finish moves. A step-by-step worked example with templates from ProjectManager.com lets you reproduce this calculation in a downloadable spreadsheet.

How to visualize the critical path with diagrams and Gantt charts

Activity-on-Node diagrams

An AON diagram represents each activity as a box (node) and each dependency as an arrow. Inside each node, schedulers typically display a six-cell grid: activity ID and name in the center, ES and EF across the top, LS and LF across the bottom, and Total Float in a corner cell. The critical path is drawn with a thicker or colored arrow connecting the zero-float nodes from start to finish.

AON diagrams are the standard output of scheduling software and are what you will see in most PMBOK-aligned project plans. They make dependency chains immediately visible and let you trace the critical path by following the highlighted arrows.

Mapping CPM results to a Gantt chart

A Gantt chart is a visualization tool that can display the critical path, but it is not the scheduling algorithm itself. The CPM calculation happens in the network; the Gantt chart simply renders the results as horizontal bars on a timeline. Most scheduling software lets you color-code critical activities in red and near-critical activities in orange, giving stakeholders an at-a-glance status view without requiring them to read the network diagram.

For stakeholder updates, the Gantt view is usually clearer. For schedule analysis and compression decisions, go back to the network. Visuals without the underlying CPM analysis hide which delays will actually move the finish date, a point worth making explicitly to any stakeholder who treats the Gantt as the schedule rather than a picture of it.

Near-critical paths (those with small float) deserve their own color on the chart. A path with only one or two days of float in a 60-day project is practically critical, and treating it as non-critical is a common scheduling mistake.

CPM versus PERT, and the critical path versus a Gantt chart

CPM versus PERT

CPM uses fixed, deterministic durations and is best for projects where activity durations are known from historical data or expert judgment. PERT uses three-point estimates (optimistic, most likely, pessimistic) to model duration uncertainty and calculate a probability-weighted expected duration.

Key differences:

  • Duration input: CPM uses one fixed estimate per activity; PERT uses three.
  • Output: CPM gives a single project duration; PERT gives an expected duration with a probability distribution.
  • Best fit: CPM suits construction, manufacturing, and procurement programs with well-defined activities. PERT suits R&D, software development, or any project where duration estimates carry significant uncertainty.
  • Hybrid use: CPM and PERT are often combined, as noted in the Wikipedia CPM article. Run CPM for the deterministic baseline, then apply PERT to the critical path activities where duration uncertainty is highest.

Critical path versus Gantt chart

The critical path is an analytic result derived from the schedule network. A Gantt chart is a display format. You can have a Gantt chart with no CPM analysis behind it, and you can run CPM without ever producing a Gantt chart. The confusion matters in practice: a project manager who relies only on a Gantt chart cannot tell which task delays will move the finish date and which will not.

Use CPM for analysis and decision-making. Use the Gantt chart for communication and progress tracking.

Schedule compression: crashing and fast tracking

When the critical path is too long, two techniques can shorten it: crashing and fast tracking. Both change the critical path, and both carry tradeoffs.

Crashing adds resources to critical path activities to reduce their duration. You spend more money to buy back time. The most cost-effective crash targets are activities with the lowest cost-per-day-of-schedule-reduction, which is why calculating crash cost before committing is standard practice.

Fast tracking overlaps activities that were originally planned in sequence. Instead of waiting for design to finish before starting procurement, you begin procurement on the portions of design that are already stable. Fast tracking costs little or nothing in direct expense but increases rework risk if the overlapped work turns out to be wrong.

Technique Cost Impact Schedule Risk Best Used When
Crashing Increases (added resources) Low to moderate Budget is available; duration must be reduced with minimal rework risk
Fast tracking Minimal direct cost Moderate to high Activities have independent portions that can safely overlap

A practical example: in the worked example above, crashing Activity D from 5 days to 3 days (at added cost) would reduce the project from 14 days to 12 days. Fast tracking B and D by starting D two days before B finishes achieves the same result but requires that the first two days of D’s work not depend on B’s final output.

One important consequence: compression often creates new critical paths. After crashing D, check whether path A → C → E → F (currently 10 days with 4 days of float) has closed the gap. If the project is now 12 days, that path’s float drops to 2 days and becomes near-critical.

Practical limitations and monitoring tips for real projects

Resource constraints change everything

The theoretical critical path assumes unlimited resources. Real projects do not. Resource constraints can shift which path is effectively critical: a task with 3 days of float that shares a key engineer with a critical activity may have zero effective float once resource availability is factored in. This is the concept of a resource-critical path, which is distinct from the theoretical critical path and requires separate tracking in resource-leveled schedules.

Resource leveling (adjusting the schedule to stay within resource limits, even if it extends the project) and resource smoothing (adjusting within float to reduce resource peaks without extending the project) both affect which activities end up on the critical path. After either operation, recalculate.

Monitoring tips for active projects

  • Recalculate after every status update. The critical path is dynamic. As activities finish early or late, new paths can emerge, as the Wikipedia CPM article notes explicitly.
  • Use a status date. Set the data date in your scheduling tool to today, and let the software recompute remaining durations and float from that point.
  • Watch critical path drag. Rather than monitoring all critical activities equally, calculate drag for each one. The activity with the highest drag is where shortening effort yields the most schedule recovery.
  • Update dependencies when scope changes. New activities or changed sequences invalidate the existing network. Treat scope changes as a trigger for a full network review.
  • Track near-critical paths separately. Any path with float below 10% of remaining project duration deserves the same attention as the critical path.
  • Audit the as-built schedule carefully. As-built critical path analysis (used after project completion to analyze delays) is sensitive to errors and has been criticized when applied in legal or contractual disputes, per the Wikipedia CPM article. Use it with caution and document assumptions.

Pro Tip: Experienced schedulers target drag reduction rather than spreading attention across every critical task. Calculate drag for each critical activity, rank them, and focus compression resources on the top two or three. Cutting drag on a low-drag activity wastes effort; cutting it on the highest-drag activity shortens the project the most per dollar or hour spent.

For project quality and communication management, keeping stakeholders informed about critical path shifts is as important as the calculation itself. A schedule update that does not reach the right people in time is nearly as damaging as no update at all.

Hands organizing project sticky notes on calendar

What tools and software support CPM calculations?

Spreadsheets

A well-structured spreadsheet is the right starting point for learning CPM and for small projects with fewer than 30 activities. Build columns for Activity ID, Duration, Predecessors, ES, EF, LS, LF, and Float. Use MAX and MIN formulas to automate the predecessor logic. The worked example template from ProjectManager.com is a practical starting point you can adapt directly.

The limitation: spreadsheets do not automatically redraw the network or recalculate when you add activities mid-project. Manual updates are error-prone on larger schedules.

Dedicated scheduling software

Tools like Microsoft Project, Primavera P6, and ProjectManager.com automate the forward and backward pass, highlight the critical path in the Gantt view, and recalculate instantly after status updates. Modern PM software computes CPM automatically and supports visual highlighting of critical and near-critical paths. For projects with more than 30 activities, or any project with complex resource constraints, dedicated software is worth the investment.

Primavera P6 is the standard in construction and engineering. Microsoft Project is widely used across industries in the U.S. and integrates with Microsoft 365. Both export to Gantt views and support resource leveling.

Integrated PM suites

Platforms that combine scheduling, resource management, and reporting in one environment reduce the risk of the critical path and the resource plan falling out of sync. When your schedule lives in a different tool from your resource assignments, resource-driven critical path shifts are easy to miss.

For teams exploring Agile project management fundamentals alongside CPM, integrated suites often support hybrid scheduling modes, letting you apply CPM to the deterministic portions of a project while managing iterative work in a separate backlog view.

Management and Strategy Institute provides training materials and certification programs that cover scheduling techniques including CPM, giving practitioners a structured path to apply these tools confidently on real projects.

Why CPM still matters for modern project managers

The tools have changed. The algorithm has not. CPM’s two-pass calculation, developed in the 1950s, is still the most direct answer to the question every project sponsor asks: “What is the earliest we can finish, and what would delay us?” No amount of dashboard software answers that question without the underlying network analysis.

What I see practitioners underestimate is how often the critical path shifts during execution. A project that starts with a clear single critical path frequently develops two or three near-critical paths by the midpoint, especially after resource reallocation or a scope change. Treating the initial critical path as fixed is one of the most common scheduling errors, and it is entirely avoidable with regular recalculation.

Certification in scheduling and process improvement methods gives practitioners the vocabulary and the analytical discipline to catch these shifts early. Management and Strategy Institute’s programs, used by over 300,000 certified alumni, build exactly this kind of structured analytical thinking, connecting scheduling theory to the process improvement skills that actually move projects forward.

Mastering CPM through structured certification

Knowing the CPM formula is one thing. Applying it under deadline pressure, with shifting resources and changing scope, is another skill entirely. Management and Strategy Institute’s Lean Six Sigma Black Belt Certification covers scheduling optimization, process improvement, and the analytical methods that make CPM work in practice, not just on paper. All study materials and the certification exam are included in a single all-in price, with no hidden fees and no fixed class schedule.

Lean Six Sigma Black Belt Certification

Professionals who complete the program come away able to apply CPM confidently, use schedule compression techniques with an understanding of cost and risk tradeoffs, and communicate critical path impacts clearly to stakeholders. With a 98% recommendation rating across more than 300,000 alumni, the program has a track record that speaks for itself. Start your certification at your own pace today.

Sources

The following sources support the formulas, history, and practical guidance in this guide:

FAQ

What is CPM with an example?

CPM (critical path method) identifies the longest sequence of dependent activities in a project. In the worked example above, the path A → B → D → F takes 14 days and carries zero total float, making it the critical path.

What is the formula for the critical path?

There is no single formula; CPM uses two. The forward pass computes EF = ES + Duration (with ES = max EF of predecessors for activities with multiple predecessors). The backward pass computes LS = LF – Duration (with LF = min LS of successors). Activities where Total Float = LS – ES equals zero form the critical path.

What is the difference between CPM and PERT?

CPM uses one fixed duration per activity and suits projects with well-defined, predictable tasks. PERT uses three-point estimates (optimistic, most likely, pessimistic) to handle duration uncertainty and is better suited to high-uncertainty projects like R&D.

What is the difference between a Gantt chart and a critical path?

A Gantt chart is a visualization tool that displays tasks on a timeline; the critical path is an analytic result derived from the schedule network. A Gantt chart can show the critical path visually, but it does not calculate it. Without CPM analysis behind it, a Gantt chart cannot tell you which delays will move the project finish date.