Why Construction Schedules Are Unrealistic

Why Are Construction Schedules So Unrealistic?

Here’s the deal. I have built dozens of CPM schedules myself. As a superintendent I was required to build them, and I know the software well enough to call myself a CPM expert. I am not badmouthing something I never learned. I am telling you what I found after years of doing it and then watching the same failures repeat on every project we analyze.

Construction schedules are unrealistic for two reasons, and neither of them is that your people are careless. The method is predictive, and it is built in a silo. Everything else follows from those two facts.

One Person, One Room, Somebody Else’s Work

Picture how the schedule gets made. There is one scheduler in a room. Good person, working hard, trying to do a professional job. And that one person is asked to predict, from start to finish, at level three detail or deeper, when every piece of work on a large project will happen.

Usually without trade partner input, without historical reference classes to compare against, and without a pull plan built by the people who will do the work. Frequently that person has never come up through the field at all, which means they are producing a prediction about the work of experts without access to the expertise. Even when the intent is to collaborate, the output happens in a silo. One head, one keyboard, one set of assumptions. Then the file becomes the contractual truth for hundreds of people who never got asked. That is not a character flaw in schedulers. It is a job description nobody could fulfill.

Humans Are Terrible at Guessing Durations

Now stack the second problem on top of the first, because this is the part that is scientifically documented and almost never discussed in a scheduling meeting.

Human beings are bad at estimating durations. Not slightly bad. When you plot what people guess against what the work actually took, the guesses tend to land either within about twenty five percent of reality or off by a factor of four in either direction. Four times too long, or four times too short. That is not a rounding error. I would not even call it an error. It is a mistake, and it is well documented in the research literature.

So consider what we do with that. We take one person’s best guess, which already carries a factor of four uncertainty baked in. We ask for it at a level of detail nobody can know, which multiplies the uncertainty rather than reducing it. We do it without field input to correct it and without reference classes to calibrate it. Then we put the result in a format where nobody can double check it. That is the honest description of how most project schedules come into existence. A human guess, made ten times worse by the process around it, then hidden where nobody can audit it.

The Format Defeats the People Using It

Here is the third failure, and it is the one that finishes the job.

A CPM schedule is a time by deliverable wall of black and white text. You cannot analyze anything meaningful in it. You cannot stand in front of it with a foreman and see whether next week is possible, or understand where the work will be crowded. The information may technically be in the file, but it is not accessible to a human being standing on a jobsite in boots.

I will give you a threshold from my own experience building these. Somewhere around five to eight hundred activities, you stop being able to hold your own schedule in your head. You turn on the logic view and think, whoa, where did all of this come from? You built it, and you have lost track of what is inside it. If the author cannot follow it, the field cannot either.

Watch for these signs the format has already beaten your team:

• Nobody in the field can describe next month’s sequence without opening the file
• Logic ties nobody can explain, including the person who built them
• Activity counts in the high hundreds with no zone or location structure

That is why these schedules are unpredictable and unreliable. It is not attitude. It is format.

Line CPM Up Against the Cores of Lean

People ask why I keep coming back to this. Here is my answer. Take the cores of Lean and test CPM against each one. Respect for people. Stability. Flow. Flowing together. Visual management with total participation. Quality. CPM fails all of them, and structurally, not accidentally.

It does not respect people, because it trade stacks and trade burdens them. Too many trades crowded into one area, or one trade asked to be in several areas at once with one crew. Both are produced by the method, and both land on human beings.

It does not create stability, because the plan is always moving and there is no standard for the work being done in a zone. Nobody knows what a normal week looks like, so nobody can improve one. It does not create flow either, because it is not focused on one piece flow. Crews are everywhere at once instead of moving through space in sequence, and because the plan is not organized by time and location, you have no zones on a rhythm and no way for trades to flow together. It is not visual, so people cannot participate in it. And it is not focused on quality at all. It is focused on getting things done as fast as possible, which is a different objective wearing the same clothes.

The System Failed Them, Not the Other Way Around

I want to speak to the superintendents and foremen reading this, because I have been where you are. You have probably been told the schedule slipped because your team did not execute. That is not what happened. You were handed a prediction made by one person, without your input, containing a documented factor of four error, at a detail level nobody could know, in a format you cannot verify or use. Then you were measured against it and asked what went wrong.

Nothing went wrong with you. The system failed you. You did not fail the system. The trade partner who could not hold his dates was not uncommitted, and the scheduler who produced the file was not incompetent. Everybody in that chain was doing their best inside a method that guarantees the outcome.

What to Build Instead

If the diagnosis is that the plan is a siloed prediction in an unusable format, then the fix has to change all three of those things. That is what Takt planning does.

Takt starts with time and location instead of a list of deliverables. You break the building into zones, then set a Takt time, which is the fixed duration a crew works in a zone before handing it off. Then you build a train of trades that moves through those zones at that steady beat. Now the plan is organized the way the work is actually organized, which is by place and rhythm.

Because the plan is built around zones on a rhythm, you get what CPM cannot give you. A standard for what happens in a zone, which is stability. One piece flow, because a crew finishes one area before moving to the next. Trades flowing together instead of colliding, because the sequence through each zone is defined. And a plan a foreman can read on a wall, which makes total participation possible instead of theoretical.

The estimating problem gets handled differently too. Instead of one person guessing hundreds of durations in isolation, you pull the plan with the trade partners who will do the work, use historical reference where you have it, and set a rhythm people commit to rather than a prediction imposed on them. You are replacing a hidden factor of four guess with a visible commitment plus real buffers to absorb what you could not predict.

Build People Before You Build Things

None of this is a software purchase, and I want to be blunt about that because I have watched teams try to buy their way out.

A Takt plan handed to an untrained team becomes wallpaper by month three. Somebody has to teach the superintendent how to run the board, hold a handoff, protect a buffer, and refuse a request that would burden a trade. Somebody has to teach the foremen what a ready zone looks like and what to do when it is not. Somebody has to help the trade partners believe this pull plan will be honored, because most of them have been burned before.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Most teams already know the schedule is unrealistic. What they need is somebody to build the replacement alongside them and stay long enough that it holds without a coach in the room. Tools like LeanTakt make the flow visible, and trained people keep it honest week over week.

Why This Matters Beyond the Bar Chart

An unrealistic schedule is not a paperwork problem. It converts directly into how people live. The crew works Saturday because a guess was wrong in January. The foreman stops training his apprentice because he spends every morning chasing access the plan promised and the building cannot provide. The trade partner stops raising problems early, because raising them has never changed anything. And the superintendent slowly concludes that chaos is simply what construction is, which is the most expensive belief in our industry.

Signals it is time to change the method rather than the effort:

• Recovery plans that add manpower instead of removing work from a zone
• Overtime authorized before anybody asks whether the plan was ever possible
• The same slip appearing every month with a different explanation

Craft workers deserve a clean, ready area, a defined amount of time, and a predictable week. That is what dignity looks like on a jobsite, and it is a planning decision before it is a values statement.

So here is the challenge. This week, take one area of your remaining work and do three things. Pull the sequence with the trade partners who will perform it. Organize it by zone and rhythm rather than by activity list. Put it on a wall where a foreman can read it in ten seconds. Then compare the next four weeks of that plan against what your CPM file promised, and let the difference make the argument for you.

1. Edwards Deming said it as plainly as it can be said: “It is not necessary to change. Survival is optional.” Our people are worth the change.

On we go.

FAQ

Is the scheduler to blame for an unrealistic schedule?

No, and that framing is part of the problem. Schedulers are asked to predict the work of dozens of expert crews at a detail level nobody can know, usually without trade input, without reference data, and without a pull plan. Any human given that assignment produces an unreliable result. Fix the assignment and the method, not the person.

How can a duration guess be wrong by a factor of four?

Because estimating durations is a known weak spot in human judgment. Studies of estimated versus actual durations show guesses clustering either fairly close to reality or off by roughly four times in either direction. On a project with hundreds of activities, those errors compound through the logic instead of averaging out, which is how a schedule can be impossible on day one.

Does Takt eliminate estimating uncertainty?

No. Nothing eliminates uncertainty on a construction site. Takt handles it by pulling the plan with the people who do the work, organizing by time and location, and placing real buffers where variation can be absorbed. You trade a hidden guess for a visible commitment with protection around it.