What is CPM in Project Management

What Is CPM and Why It Is Destructive to Construction Projects

There is a scheduling system that balloons Work in Progress above the capacity of the people and resources required to accomplish it, eliminates the buffers that protect production flow, stacks trades on top of each other in ways that are neither natural nor safe, and when things go wrong recommends crashing activities by adding labor, overtime, and resources a response that is known to push projects into a downward productivity spiral. That system is CPM, the Critical Path Method, and it is the dominant scheduling framework used across the construction industry.

This blog is not an argument for using CPM differently at the margins. It is an argument for understanding exactly what CPM does, why it does it, and what the evidence says about the results so that teams can make an informed decision about whether to continue using a system that, as Jason has argued in The 10 Myths of CPM, was chosen over better alternatives in part because it was more abusive to contractors.

For those who are committed to CPM for contractual or organizational reasons, this guide also covers the minimum changes required to make it workable. But the most direct answer is the simplest one: there is a better way.

What CPM Actually Is

Critical Path Method is a time-by-deliverable scheduling format. Activities are organized in a Work Breakdown Structure, logic-tied to each other, and processed through a forward and backward pass algorithm. The forward pass calculates the earliest each activity can start. The backward pass calculates the latest each activity can finish without delaying the project. The algorithm then identifies the activities that have zero float the ones where any delay directly extends the project completion date. That chain of zero-float activities is the critical path.

The critical path is not the ideal path. It is not the optimized path. It is the path that, by the algorithm’s calculation, determines the project’s end date and any delay anywhere on that chain cascades directly to the milestone. The CPM schedule is then issued to the trades, who are expected to understand it, build from it, and execute it.

They cannot. A CPM schedule is mostly text and logic, organized in a format that is readable by schedulers and largely inaccessible to the foremen and crews who actually build the work. The trades in the field cannot see where they are in the building, how their work relates to the work happening around them, or what they need to do next to protect the flow of the other trades. They cannot use it to make daily production decisions. They throw it away when they leave the trailer because the format does not serve the people who need to build from it.

The Mechanics That Hurt Projects

Three specific features of CPM are directly destructive to construction production. Understanding them is not an academic exercise. They are the mechanisms that produce the trade stacking, budget overruns, and schedule failures that CPM-managed projects experience repeatedly.

The first is the early start default. CPM moves every activity to its earliest possible start. The forward pass calculates when each predecessor finishes and places the successor activity to begin as soon as its predecessors allow. The result is that every trade is pushed to begin as early as the logic allows, regardless of whether the crews, materials, and conditions they need are actually ready. Multiple trades enter the same area simultaneously. The work area becomes congested. Productivity drops. The schedule falls behind and the CPM response is to crash the activities, which adds more people to the same congested area and drops productivity further.

The second is the elimination of buffers. In CPM as practiced, buffers and schedule contingency are typically compressed out of the schedule. The theory prefers to show the earliest possible completion dates, which requires removing the float that would allow production to absorb variation. A project without buffers has no protection against the variation that is present on every construction site weather, material delays, design changes, trade performance variations, inspection failures, and the thousands of other events that are genuinely unpredictable. The schedule shows the project finishing on time right up until it does not.

The third is the batching of work. CPM does not sequence trades through zones. It assigns activities to large areas and tracks them to completion by percentage. The result is large batches of work, multiple trades in the same area at the same time, and no systematic sequencing of who goes where and in what order. Trade stacking too many trades in one area and trade burdening one trade in too many areas at once are natural outputs of this approach. Both destroy productivity and create safety hazards.

What Crashing Costs

When a CPM schedule falls behind, the standard response is crashing the critical path. Crashing means adding resources more labor, more crews, overtime, expediting to activities on the critical path to compress their duration. In theory, adding resources shortens activity durations. In practice, on a congested construction site where the problem is too many people in too small an area, adding more people makes the situation worse.

The research on crashing confirms what field experience shows. Adding labor to an area that is already overcrowded increases coordination overhead, reduces the space available for each worker, creates safety conflicts, and drops the productivity of everyone on site including the crews that were performing before the additional resources arrived. The project does not accelerate. It enters a downward productivity spiral where each additional intervention produces diminishing returns until the team is burning resources at maximum rate and the schedule is still slipping. That is the designed outcome of a CPM schedule that has been crashed.

If You Will Not Stop Using CPM: The Minimum Requirements

For teams that cannot or will not move away from CPM for contractual or organizational reasons, there are changes that reduce the damage. None of them make CPM as effective as a Takt production plan, but they address the most destructive elements of the default implementation.

Use a time-by-location format. The schedule must show where the work is happening, not just what needs to be delivered. A time-by-location CPM format organizes activities by zone and phase, which makes Trade Flow visible and allows the schedule to be read by the people in the field. Without this, the schedule is a management document that never reaches the foremen who need to execute it.

Never trade stack or trade burden. This requires overriding the early start default for activities that would push trades into the same area simultaneously. The trades must be sequenced to flow zone to zone in a way that gives each one the space it needs to work effectively. This is not something CPM does automatically. It requires manual intervention to constrain the schedule in ways that the algorithm does not naturally produce.

Never run a true critical path without buffer. Replace the critical path concept with a longest path that carries explicit schedule contingency. Every phase and every sequence needs buffer capacity protection, time protection, space protection placed deliberately where the risk analysis shows the highest likelihood of variation. A schedule without buffer is a plan that assumes everything will go right. Nothing does.

Never balloon Work in Progress beyond capacity. Size the zones using the Takt calculator before building the schedule. The zone sizes determine how much work can be executed simultaneously without overloading the resources available to execute it. Zone sizing done in the Takt calculator, then applied to the CPM schedule, prevents the Work in Progress overload that crashing attempts to address after the fact.

The Better Alternative

The Takt Production System, implemented on a time-by-location format with diagonal Trade Flow, buffers placed deliberately, zones sized by the Takt calculator, and a pull plan that the trades build collaboratively, produces results that CPM cannot. The production plan is readable by the foremen in the field. The trades can see where they are in the building and where they go next. Variation is absorbed by buffers rather than cascading to the milestone. When delays occur, there are twelve recovery options in the Takt Production System none of which involve adding more resources to an already congested area. CPM’s recovery option is crashing. The Takt Production System’s recovery options are production management.

The Last Planner System runs on top of the Takt production plan, and the combination produces what CPM was always supposed to produce but never could: a schedule that the people building the project can actually use. For teams making the transition, the books Takt Planning, Takt Steering and Control, and The 10 Myths of CPM provide the foundation. For teams ready to implement, the Takt Production System and the First Planner System both trademarked by Elevate Construction provide the framework.

We are building people who build things. The teams that move away from CPM and toward a production system that respects Trade Flow, protects people from overburden, and manages variation with buffers rather than crashing are the teams whose projects finish on time, on budget, with crews that are not burned out by the time they reach substantial completion. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the transition from CPM to a production system that actually works.

A Challenge for Builders

Look at your current CPM schedule and ask three questions. Does it show where the trades are in the building, or only what they are supposed to deliver? Does it have explicit buffer placed at the phase level and at the major sequence boundaries, or is every activity running at its earliest start with no float? Are the trades currently working from the schedule in the field, or did it get filed away after the baseline was submitted? If any of those answers reveals a gap, the schedule is managing the contract rather than managing production. That gap is where time is lost.

As Jason says, “If the plan requires burnout to succeed, the plan is broken, not the people.”

On we go.

Frequently Asked Questions

What is the Critical Path Method and what does it actually produce?

CPM is a time-by-deliverable scheduling system that logic-ties activities and runs a forward and backward pass algorithm to identify the longest chain of zero-float activities the critical path. It moves every activity to its earliest possible start, which stacks trades, eliminates buffers, and balloons Work in Progress above the capacity of the resources available to complete it. The critical path identifies which activities will cascade delays to the project end date if they slip which, on a CPM schedule without buffers, is most of them.

What is crashing and why does it make CPM schedules worse rather than better?

Crashing is the CPM response to schedule slippage adding labor, overtime, crews, and resources to activities on the critical path to compress their durations. On a construction site where the problem is already too many people in too small an area, adding more people increases coordination complexity, reduces each worker’s effective space, creates safety conflicts, and drops productivity across the site.

What are the minimum changes required to make CPM less destructive if you cannot stop using it?

Switch to a time-by-location format so the schedule is readable by field crews. Override the early start default to prevent trade stacking and burdening. Replace the critical path with a longest path that carries explicit schedule contingency and buffer. Size zones using the Takt calculator before building the schedule to prevent Work in Progress from exceeding resource capacity.