Construction planning and control (PCP): the method that separates the project that delivers from the one that blows up

Construction planning and control isn't the pretty schedule you sign off on at the kickoff meeting — it's what happens, or fails to happen, over the following six months, once the site starts disobeying the paper. Let me open with the scene every construction company owner knows.

Start of the project. The planning team hands over a flawless schedule: color-coded MS Project, critical path marked, S-curve climbing nicely, milestones tied together. Everyone signs off, shakes hands, the project begins. Three months later you look at that same schedule and it's fossilized — the last update was weeks ago, done the night before a meeting, with a percentage the site manager remembered off the top of his head. The project moved forward, but the plan stood still. And when the overrun shows up — the phase that never started because material was missing, the crew that stalled waiting on a decision, the measurement that came in lower than forecast — nobody can explain where it came from. It just did.

I spent my career inside industrial pulp and paper projects, multi-billion-real developments for Suzano, Klabin and others, where one day of delay costs a fortune and production planning and control isn't a slide, it's the discipline that keeps dozens of crews moving in the same rhythm. And I learned something that applies just as much to a giant plant as to your R$ 30 million building: almost every construction company knows how to plan. Almost none control. It's in the control — not the plan — that the project that delivers separates from the project that blows up.

In this article I want to show where most companies fail at the PCP math, how to tie the schedule to procurement and the daily standup so the plan doesn't die on paper, and why control depends on something almost nobody treats as part of the method: information flowing through the site.

Planning vs. controlling: where most projects fail

The acronym PCP has two letters that matter — planning and control — and the whole industry treats the second as if it were the same thing as the first. It isn't. They're two different jobs, and the second one is the hard one.

Planning is an event. You sit down with the project, build the schedule, budget it, set milestones and reorder points. It's laborious, but it has an end: one day the plan is ready. It's the part most construction companies do reasonably well, because it has a fixed date and a clear deliverable.

Controlling is a process. It's comparing, every single day, what was planned against what actually happened on the ground, spotting the deviation while it's still small, and acting on it. Control has no end, no scheduled hour, and produces no pretty deliverable to present. That's why it's the first thing to go when the project gets tight. The engineer is putting out fires, planning turns into an update rushed through the night before the monthly meeting, and control — which should be daily — turns into a snapshot taken once a month, already stale by the time it's presented.

Here's the gap: the plan nobody controls isn't planning, it's guesswork wearing the costume of method. It gives you the feeling of control without the control. You have a schedule, so you think you're in command — until the day the deviation, which had been quietly growing for weeks, gets too big to hide. The project doesn't blow up all at once. It blows up a little every day, and real PCP exists precisely to catch that "little bit" on the day it's still cheap to fix.

It's no accident that industry surveys point to waste as construction's number one problem — something around 73% of the sector acknowledges it. Much of that waste isn't born from a lack of a plan. It's born from the gap between the plan and execution that nobody is measuring in time to act.

From schedule to reorder point to daily standup: where the plan becomes execution

A schedule, by itself, builds nothing. It's a promise. To become a building, it needs to connect to two things that happen on the ground every day: the material that arrives and the crew that executes. That's where PCP stops being a spreadsheet and becomes a method.

From the schedule to the reorder point. Every phase of the schedule consumes material, and every material has a delivery lead time. PCP ties the two ends together: if finishing work starts in week 12 and the supplier delivers in 15 days, the order has to go out in week 10 — with margin. When that link exists, the Friday emergency purchase — the one that costs 28% more on average because you're buying from the only supplier who can deliver in time — simply stops happening. It isn't bad luck; it's the symptom of a schedule that never talked to procurement. Not coincidentally, about 88% of project delays are tied to materials and supplies — it's the plan that never reached procurement. I detailed this mechanism in Construction procurement planning: how to buy material at the right time (without idle inventory).

From the schedule to the daily standup. The plan says what was supposed to happen today on each crew. The daily site meeting is where you find out what actually happened — and, most importantly, what got stuck. Without the daily, control turns into that stale monthly snapshot. With the daily, each crew's deviation shows up that day, not at month's end. The problem is that a well-run daily is exhausting: it turns into you chasing status from everyone, becoming the annoying one always pushing for updates. How to do this without that toll is the subject of Daily construction site meeting: how to align the site without becoming the nag.

Notice the shape of it: schedule in the center, reorder point on one side, daily standup on the other. It's that triangle that turns the plan into control. Break any one of the sides and PCP goes back to being just a pretty file.

Milestones, blockers and mitigation: the cycle that closes the loop on control

Controlling isn't just watching the progress percentage. Percentage is the scoreboard after the game — it tells you you're losing, not how to stop losing. Useful control rests on three concrete things: milestones, blockers and mitigation.

Clear milestones. A fuzzy milestone controls nothing. "Structure underway" isn't a milestone; "4th floor slab poured by 03/20" is. A milestone is the point where you compare plan and reality with no room for interpretation: either it was hit, or it wasn't. A project without hard milestones lives in a comfortable fog where everyone has a different expectation of the date and nobody is technically wrong — until delivery day exposes who was.

Logged blockers. This is the most valuable piece of information in PCP, and the one most often lost. Every time a crew stops, there's a reason: material was missing, a decision was missing, the design had an error, the previous subcontractor was late. That blocker is gold for two reasons. First, because it's the root cause of the delay — attacking the blocker attacks the deviation at the source. Second, because it's your defense: when the delay wasn't your construction company's fault, the logged blocker is what proves it in a change order or a penalty dispute. A blocker that lives only in the foreman's head or in someone's WhatsApp audio message controls nothing and protects no one.

Mitigation that's followed up. Logging the blocker is half the job. The other half is: someone was made responsible for solving it, with a deadline, and someone is following up on it. This is where most controls die — the deviation gets identified in the meeting, noted in the minutes, and the minutes sleep in a folder until the next meeting, when it turns out nobody touched the issue. Control without follow-up on mitigation is diagnosis without treatment. Milestone, blocker and mitigation form the cycle: measure the deviation, understand the cause, act on it — and measure again. That cycle, running every day, is PCP. The rest is reporting.

Why control depends on information flowing

Now for the part almost no PCP manual says, and the real reason control fails. Control doesn't fail for lack of method. It fails for lack of information arriving on time.

Think about what control actually requires. To compare plan and reality, you need to know each crew's real progress — today, not last week. To anticipate a material shortage, you need the real inventory balance crossed with projected consumption. To attack a blocker, you need to know it exists on the day the crew stalled. Every one of these pieces of information exists on your site right now. The problem is where it lives: progress in the site manager's head, the balance in the warehouse keeper's notebook, the blocker in a lost audio message in one of fifteen WhatsApp groups. The information exists, but it's trapped — and trapped information controls nothing.

That's PCP's real enemy, and it isn't your team: it's trapped information. As long as site data depends on someone remembering to transcribe it into a spreadsheet, control will always arrive late — because the spreadsheet, however good it is, doesn't know what happened on site today and will never tell you on its own. It waits for you to update it. And you, in the middle of the fire, update it when you can — which is always too late for control to be useful for action.

That's also why the most expensive professional on your site, the engineer, spends a large part of the day being a messenger for information: chasing status, transcribing numbers, building the spreadsheet at night. His time doesn't turn into building — it turns into administering information that should flow on its own. That's the hidden cost of manual PCP, and it disappears diluted into the team's payroll, exactly like the emergency purchase disappears diluted into "materials."

Active coordination: how to close the PCP loop without relying on memory

If control fails because information arrives late, the answer isn't yet another system for the team to feed — that only adds data-entry work to people who are already overloaded. The answer is to flip the logic: instead of a passive dashboard waiting for you to look at it, an agent that acts on the plan. It's the difference between a dashboard you consult and active coordination. That's exactly our thesis: your project doesn't need another dashboard to check; it needs coordination that runs the PCP cycle for you.

In the practice of planning and control, active coordination looks like this:

The schedule becomes alive, not a snapshot. Instead of the plan being a file someone updates the night before the meeting, it connects to what's reported that day — by voice, on the phone, in the daily standup. Real progress rolls up into the schedule without anyone having to transcribe cell by cell. If you want to see this concept applied to the indicator everyone has and nobody uses, I wrote about it in S-curve and Earned Value (EVM) on site: how to know a project will be late before it's late.

The deviation becomes an alert, not a late discovery. The agent cross-checks plan and reality constantly. When a material's consumption hits the reorder point, it warns days ahead of the shortage, with time to buy calmly. When a crew hasn't reported, it follows up — in the engineer's place. Control stops depending on someone remembering to do the math at the right time.

The blocker becomes automatic logging and follow-up. Whatever stalled gets documented the moment it happens, with an owner and a mitigation deadline, and the agent chases progress until it's resolved. The minutes stop sleeping in the folder. And the record that protects your construction company in a change order starts existing by default, not by someone's heroic discipline.

The effect on the team is measurable: our Communication Hub gives back about 10 hours a week to each project manager — more than a full workday, every week, of qualified people going back to controlling the project instead of chasing data. That's the one number I'll stand behind, because it's our own measurement. The broader savings model for well-executed PCP — avoiding the emergency, cutting rework from deviations caught late, freeing up team capacity — we estimate at something in the order of 3.6% to 7.6% of project value. That's a conservative, bottom-up estimate from our model, not a result measured with a client — our pilot is less than a month old. I'd rather tell you that than sell you a number I haven't measured yet; you can check the math yourself against your own data.

Frequently asked questions

1. What's the practical difference between construction planning and control? Planning is building the plan — schedule, budget, milestones, reorder points — and it has an end. Control is comparing the plan against what actually happened on site every day, spotting small deviations and acting on them; it has no end. Most projects do the first reasonably well and the second poorly, because control has no fixed hour and no pretty deliverable, and it's the first thing to go when the project gets tight. It's in control that the project that delivers separates from the one that blows up.

2. I already have a schedule in MS Project and control spreadsheets. Isn't that enough? Schedules and spreadsheets are great for planning and terrible for controlling, for a simple reason: they're passive. The spreadsheet doesn't know what happened on site today and will never tell you — it waits for you to update it, and you update it late, in the middle of the fire. What's missing isn't a better planning tool; it's site information arriving on time and the deviation becoming an alert instead of a discovery at next month's meeting.

3. I already pay for Sienge/TOTVS. Doesn't the ERP handle that control? The ERP records what happened — measurements, invoice entries, balances, actual costs. It's a good system of record and you should keep it. But it's passive: it doesn't cross the schedule with inventory to warn before a shortage, doesn't follow up on a blocker's mitigation, doesn't chase the crew that hasn't reported. Active coordination is a different layer, one that acts on what's happening. That's why we integrate with the ERP, not replace it.

4. R$ 10 thousand a month to "coordinate" is expensive for what I already do in a spreadsheet. Compare it to what you're already paying blindly. A single avoided emergency purchase — with the average 28% markup — usually covers a good part of the month. It's half the salary of a mid-level engineer for a manager that runs the PCP cycle 24 hours a day, across every crew, and never forgets to cross-check the schedule against inventory: about 1% of the project cost to attack the percentage points that loose control leaks away today. What's expensive isn't active control. It's the overrun it prevents.

5. My field team won't feed yet another control system. That's the right objection, and the answer defines the outcome. Control that depends on the team filling out forms and transcribing spreadsheets becomes decoration — it fails. That's why the right model is an agent that asks instead of waiting, accepts answers by voice and by phone on site, and follows up with whoever hasn't answered. The team doesn't get more data-entry work; it gets the data rolling up into the plan on its own. And that's why we come in with engineers during onboarding: without a method designed together with your team, the best tool in the world controls nothing.

How TrackBuild closes the PCP loop in practice

Everything this article described — the plan that fossilizes, the deviation that only surfaces at the monthly meeting, the blocker trapped in a WhatsApp audio message — comes from the same root: control depends on information that doesn't arrive on time today. That's exactly the gap between plan and execution that TrackBuild was built to close:

• AI Project Manager — pulls the schedule into the routine: collects each crew's progress at the daily standup, logs blockers with an owner and deadline, and follows up on mitigation until resolved. Control runs every day, without turning into the stale monthly snapshot.
• Purchase alert tied to the schedule — cross-checks each phase's projected consumption against the real balance and the supplier's lead time, and warns at the reorder point, days before the shortage. The emergency dies at the source: it becomes a planned order, with time to get quotes.
• Communication Hub — the project's living memory, which answers any question with its source and gives back the hours the team currently spends hunting for data to control the project. This is where the time the manager reclaims to run the project comes from.
• Engineers in onboarding — control doesn't get implemented by dropping software in the team's lap. We come in with method and engineering people to design the PCP routine together with your team, so the cycle actually runs on your site.

And since pricing is per module, with unlimited users, the construction company, the field engineer and the subcontractor all control the project in the same flow — no per-seat toll and no blocker trapped in someone's WhatsApp. Already have an ERP? Even better: we integrate, we don't replace.

Find out where loose control is costing you margin

Poorly executed PCP doesn't show up on a line in the budget. It hides in the emergency purchase the reorder point would have prevented, in the crew that sat idle waiting on a decision that got stuck, in the rework from a deviation nobody caught in time, in your engineer's hours spent building spreadsheets instead of running the project. Each one disappears into the overall numbers — and added up, they're worth more than any overrun you can actually see.

If you want the number for your project before deciding anything, the Leak Diagnosis is a free 30-minute call where we calculate, with your own data, how much loose control is costing you per month in emergencies, rework and locked-up capacity — no strings attached.

Talk to us

---

Felipe Barreto is co-founder of engineering at TrackBuild. A civil engineer with a master's degree in civil engineering from UFMG, an MBA from IESE Business School and PMP certified, he managed the construction of plants for Suzano, Klabin and other pulp and paper industry leaders — multi-billion-real developments. TrackBuild puts AI agents and specialized engineers into the project's daily routine, with unlimited users, so information stops getting trapped and margin stops leaking.