What Project Controls Really Do
The subway map problem
If you're an owner on a large commercial project, you've probably had this experience: someone hands you a schedule that looks like a subway map for a city you've never visited, a cost report thick enough to stop a door, and a confident verbal summary that everything is "tracking." Six months later you find out what "tracking" meant.
Project controls is the discipline that keeps that from happening. I've practiced it for more than twenty years on large commercial programs, from preconstruction through closeout — including a vice-president tenure at Porter Consulting — and today through my own practice, Pacific Project Controls. Here is what the job actually is, in plain English.
Three questions
Strip away the acronyms and project controls answers three questions, continuously, for the life of the project: Where were we supposed to be? Where are we actually? And what will it take — in time and in money — to close the gap?
Every report, every update meeting, every forecast is one of those three questions wearing a suit. If a document you're paying for doesn't answer one of them, ask why it exists.
Schedule health
A schedule is only useful if it's honest. Honest means real logic between activities — not a list of dates someone typed in to match a promise. It means float you can trace to a reason. It means updates that record what actually happened, even when the news is bad, because a schedule that only carries good news isn't a schedule; it's a press release. A beautiful Gantt chart nobody updates is wall art.
Health is measured, not asserted: are the planned durations proving out against actuals? Is the critical path stable, or does it wander every month? Did last month's forecast survive contact with this month? Those checks are quick, they're cheap, and they tell you more than any executive summary.
Cost discipline
On cost, the number that matters is the forecast at completion — not the budget you approved a year ago, and not the invoices paid to date. Discipline means that forecast moves when reality moves, not when someone finally runs out of ways to avoid admitting it. Commitments get recorded when they're made. Changes get priced when they're identified, not when they're convenient.
The pattern to watch for is the quiet one: a forecast that never changes is not a stable project. It's usually an unexamined one.
Risk you can defend
"Risk management" too often means a register that gets opened twice a year and a heat map in the monthly deck. Defensible risk is something else: a documented basis for the schedule and the budget — what you assumed, what you knew, and when you knew it — kept current as the job moves.
Here's why it matters. On a long enough program, a dispute eventually shows up. When it does, opinions evaporate and contemporaneous records don't. The measurement habit — the whole argument of Measurement Beats Opinion — is cheap insurance for years before it ever has to be evidence.
The software is not the discipline
None of this comes from a platform. I've seen immaculate scheduling systems wrapped around terrible controls, and I've seen modest tools run with real discipline that kept very large programs honest. The tool records; the discipline decides what's worth recording and then makes someone confront what it says. Buy better software without changing behavior and what you get is faster, prettier fiction.
That's the honest version of what my practice sells: not charts. The habit of telling the truth about time and money — installed, maintained, and checked against reality every reporting period.