On a small project, you can hold the plan in your head. On a capital project — hundreds of activities, multiple contractors, a budget measured in tens or hundreds of millions, and a schedule spanning years — you cannot. Project controls are the systems that make a project of that scale visible, measurable and steerable. Get them right and problems surface early; get them wrong, or skip them, and you find out you are late and over budget only when it is too late to do much about it.
What project controls actually cover
"Controls" is an umbrella term for a set of connected disciplines:
- Planning and scheduling — building and maintaining the programme (typically in Primavera P6 or MS Project), and knowing what sits on the critical path.
- Cost control — tracking committed and actual cost against budget, and forecasting the final outturn.
- Change management — capturing every variation to scope, time or cost so the baseline stays meaningful.
- Risk management — maintaining a live register with owners, actions and quantified exposure.
- Reporting — turning all of the above into a clear, decision-ready picture on a fixed cadence.
The value is in how they connect. Schedule without cost tells you half the story; cost without schedule tells you the other half; together they tell you whether the project is actually healthy.
The baseline is everything
Controls only work against a defensible baseline — an agreed programme and budget that everyone signs up to. Without it, there is nothing to measure against, and "on track" becomes a matter of opinion. A weak or unagreed baseline is the single most common reason controls fail to give early warning, and the reason so many claims later collapse.
Earned value, in plain terms
Earned value management (EVM) sounds technical, but the idea is simple: it compares three numbers.
- Planned Value (PV) — the value of work you planned to have completed by now.
- Earned Value (EV) — the value of work you have actually completed.
- Actual Cost (AC) — what that completed work has cost you.
From those three, two ratios tell you almost everything:
- Schedule Performance Index (SPI = EV / PV). Below 1.0 means you are doing less work than planned — you are behind.
- Cost Performance Index (CPI = EV / AC). Below 1.0 means the work is costing more than budgeted — you are over.
The power of EVM is that it exposes trouble early. A CPI drifting below 1.0 in month three, on a three-year project, is a warning you can still act on. The same information arriving as a budget overrun in the final year is just bad news.
Good controls don't tell you the project failed. They tell you it is about to — while you can still change the outcome.
Leading indicators, not just lagging ones
Most reporting is backward-looking: what did we spend, what did we complete. Strong controls add leading indicators — trends in productivity, float erosion, the ageing of open risks and unapproved changes — that point to where the project is heading, not just where it has been. That shift from rear-view mirror to forecast is what separates real controls from status reporting.
Why capital projects fail without them
Large projects rarely fail in one dramatic moment. They fail through the accumulation of small, unmanaged variances that no one connected until the total became unavoidable. Controls are the discipline that catches those variances while each is still small. They are not overhead — they are the cheapest insurance a capital project can buy, and the foundation everything else, including any future delay claim, is built on.