Why PPC Does NOT Work!

Why Percent Plan Complete Only Works With Takt Planning: The Insight That Changes How You Measure Progress

There is a moment in most lean construction implementations when the team sets up a weekly work plan, tracks which activities were completed on time, calculates the Percent Plan Complete score, does a root cause analysis on the misses, and then looks at the results six weeks later and realizes nothing has actually improved. The PPC score bounces around. The root causes are the same ones every week. The countermeasures do not seem to change outcomes. And the team quietly starts to wonder whether the whole system is working or whether they are just adding administrative effort to a project that still runs the same way it always did.

Jason Schroeder has seen this pattern more times than he can count and has been frustrated by it for years. This episode is where he finally articulates why it happens, and the answer is not that PPC is a bad concept. The answer is that PPC applied to a CPM schedule is measuring deviations from a plan that was never real in the first place. And measuring deviations from a fake baseline produces fake root causes, fake countermeasures, and real frustration.

The Pain That Shows Up When Measurement Has No Anchor

The weekly work plan conversation is supposed to produce honest commitments from trade partners about what they will complete in the coming week, followed by an honest accounting of what actually got done and a genuine root cause analysis when commitments were missed. The intent behind that structure is sound. The problem is what happens upstream of that conversation. The activities in the weekly work plan come from a master schedule. And on most construction projects, that master schedule is a CPM schedule built on guesses.

The foreman who says this framing sequence will take two days is guessing. The superintendent who says this trade can start on Tuesday based on the predecessor activities is guessing against a plan that itself was built from guesses. Research shared by Felipe Engineer-Manriquez through Scrum methodology shows that human beings estimate time with errors as large as four times the actual duration early in a project, narrowing as the work approaches but never achieving the precision that a production system based on quantities and historical production rates can produce. When the weekly work plan is built from that kind of estimation, the activities on the plan are not commitments against a real production design. They are commitments against a shared guess.

The System That Makes PPC Meaningless

Three specific conditions in CPM-based scheduling combine to make PPC measurement produce nothing actionable.

The first is that durations are guessed rather than derived from quantities and production rates. When a trade partner commits to completing an activity in a duration that was estimated rather than calculated, missing that commitment does not reveal anything about the production system. It reveals that the estimate was wrong. The root cause is always the same: we guessed and the guess was incorrect. That is not a countermeasure. That is a restatement of the problem.

The second is that batch areas are often too large. When the scope of work assigned to a time window is too large for the crew size and the available time, the trade partner will not complete it regardless of how motivated they are. The root cause analysis will identify the trade partner as not complete, which is accurate but useless. It does not identify that the batch size was wrong from the beginning. There is no way to generate that insight from the PPC analysis because the batch size problem is invisible in the data.

The third is trade stacking. When a CPM schedule puts multiple crews in the same area simultaneously, or sequences work in a way that forces crews to context switch between areas, the resulting loss of productivity is real and measurable. But the PPC analysis will attribute the missed commitments to the trade partners rather than to the production design that required them to work in conditions that made meeting their commitments impossible. The system failed them. The measurement blamed them.

What Real Variances Look Like

Here is the contrast that clarifies everything. When a business owner reviews their profit and loss statement and sees that gross profit came in at four and a quarter percent against a target of six percent, the gap is a real number. Every dollar that went somewhere other than the target is a real dollar. The root cause analysis that follows can find real things: excess fuel costs, inefficient use of temporary labor, rework charges, estimate errors in the original bid. These are real causes of a real variance, and countermeasures can actually address them.

Jason describes doing this analysis on a civil project and being able to trace an eighty-thousand-dollar fade in gross profit to specific, identifiable causes: a crew change that affected productivity, rain delays in specific weeks, rework in a specific area. He could see each one because the Takt plan gave him a real baseline to measure against. The production design was based on quantities and production rates. The batch areas were properly sized. The trades were not stacked. When something deviated from plan, the deviation was caused by a real thing in the real world, not by an error in the original guess.

What Takt Planning Changes About PPC

Here is what a Takt-based weekly work plan produces that a CPM-based one cannot:

• Activity durations are derived from quantities and historical production rates, not estimated from experience or intuition
• Batch areas are sized through leveling so that the scope of work in each Takt wagon matches the crew capacity and the Takt time
• Trades are sequenced to flow through zones without stacking, so productivity loss from context switching is not built into the baseline
• The schedule is practiced and vetted the first time through, so subsequent iterations begin with a calibrated rather than an assumed production rate
• When a commitment is missed, the deviation is caused by something that happened in the field, not by something that was wrong in the plan

In that context, PPC becomes genuinely useful. A trade partner who commits to completing a zone and does not complete it because materials were not pre-staged has revealed a real problem: the make-ready process did not confirm material availability before the commitment was made. A trade partner who commits to a zone and does not complete it because a new crew was assigned after the experienced crew was pulled for COVID isolation has revealed a real workforce management issue. A trade partner who commits to a zone and does not complete it because the preceding trade held them up by a day has revealed a real sequencing problem that the buffer management process needs to absorb or address. Every one of those is a real root cause that can generate a real countermeasure.

Signs That Your PPC Measurement Is Not Working

If any of these patterns are present on your project, the measurement system is not producing actionable information:

• The same root cause categories appear week after week without the underlying conditions changing
• Trade partners report activities as complete at the end of the week to avoid a poor PPC score, even when the quality or finish condition does not fully meet the definition of done
• The PPC score fluctuates week to week without correlation to any observable change in production conditions
• Root cause analysis conversations feel like a blame exercise rather than a genuine investigation into what the production system needs
• Countermeasures identified in root cause analysis are not implemented or do not produce any change in the following week’s results

None of those are failures of effort or honesty. They are the predictable output of measuring commitments against a baseline that was not real.

The Business Analogy That Completes the Picture

Jason draws a direct parallel to financial reporting that makes the logic undeniable. When reviewing a company’s monthly financials, a portion of the variance from target gross profit is always historical: old projects with write-downs still affecting the current period, liquidated damages from a completed job still showing up in the numbers, accounts receivable timing creating apparent losses that are not current-period problems. A skilled CFO has to separate the old and unmoveable variances from the current and addressable ones before any countermeasure makes sense. Applying a countermeasure to a historical variance is wasted effort. Applying it to a current, real, addressable problem is how the business improves.

The same distinction applies to construction scheduling. The CPM schedule mixes real production problems with guessing errors, batch sizing errors, and trade stacking problems in a way that makes them indistinguishable. The Takt schedule, built on real quantities and production rates with properly sized zones and sequenced flow, removes the guessing layer. What remains in the variance is real. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Measure What Is Real, Fix What Is Real

The closing challenge from this episode is direct: do not abandon PPC. Abandon the conditions that make PPC produce nothing useful. Build a Takt plan from quantities and production rates. Size the zones through leveling. Sequence the trades to flow without stacking. Vet the plan the first time through and calibrate the production rates. Then implement PPC within that system and for the first time, measure something real. When a commitment is missed, you will know why. When a root cause is identified, it will point to something that can actually be fixed. And when a countermeasure is implemented, it will change the outcome rather than just documenting that the problem was noted.

As W. Edwards Deming taught: without data, you are just another person with an opinion. The data that PPC is supposed to generate is only as real as the schedule it is measuring against. Make the schedule real and the measurement becomes real. Make the measurement real and the improvement becomes possible.

On we go.

FAQ

Why does PPC fail when applied to a CPM schedule?

Because CPM schedules are built on guessed durations, oversized batch areas, and trade-stacked sequences, so any deviation from plan reflects errors in the original guess rather than real production problems. You cannot find real root causes or implement real countermeasures from fake baselines.

What makes Takt planning produce a real schedule?

Takt plans are derived from quantities and historical production rates, leveled so batch areas match crew capacity, and sequenced to flow without trade stacking. The result is a production design rather than a time estimate, which means deviations are caused by real field conditions.

What is the difference between a real variance and a fake one in construction scheduling?

A real variance is a deviation caused by something that actually happened in the field, like a crew change, a material delivery delay, or a quality problem that required rework. A fake variance is a deviation caused by an error in the original estimate, meaning the plan was never achievable regardless of what the crew did.

What signs indicate that PPC measurement is not producing useful information?

The same root cause categories appear week after week without conditions changing, trade partners inflate completion reporting to protect their score, and countermeasures identified in root cause analysis do not produce any change in subsequent weeks.

Can PPC work alongside Takt planning?

Yes, and Jason Schroeder explicitly advocates for it. When the master schedule is a real Takt plan built from quantities and production rates, PPC measures real commitments against a real baseline, producing real root causes and actionable countermeasures for the first time.