Most owners call for project controls when something has already gone wrong. The bid came in high. The contractor's first schedule update shows a slip nobody can explain. The board wants a forecast and nobody trusts the one on the table. By then the expensive decisions are made, and controls can only measure the damage. The real work of controls starts much earlier, while the project is still a business case, a budget and a date someone has promised out loud.
Cost and time are decided early and spent late
A project's cost and duration are largely fixed by a handful of early choices. The scope. The delivery model. The phasing. The procurement strategy for long-lead equipment. Each of those decisions is cheap to change in a workshop and expensive to change once it is in a contract.
The money, though, gets spent years later. That gap is where programs get into trouble. A scope that grew a little at every design milestone shows up as a budget overrun at bid, and a milestone date set before anyone built a schedule shows up as negative float on the first update. Neither problem started where it was found. Both started in a meeting with no controls in the room.
Every overrun I have analyzed had a birthday. It was almost never the day it was reported.
Yusuf Balogun, Founder & CEO, KonradBeck
What controls look like before the first estimate
Early controls are not a lighter version of construction-phase controls. They are a different job, focused on making the first commitments honest.
- A basis of estimate, not a number. Every early budget should say what it includes, what it excludes and what class of estimate it is under AACE recommended practices. A Class 5 number presented as a Class 2 number is how boards get surprised.
- A planning schedule built in Primavera P6. Even at concept, a logic-driven schedule shows whether the target date is possible. If the permit path, procurement and commissioning do not fit, it is better to learn that now than at the first contractor update.
- A risk register with owners and dollars. Not a list of worries. Each risk gets a cause, an owner, a probability, a cost and schedule range and a response.
- A contingency strategy. How much is held, who controls it and what has to happen before it is released. Contingency without rules is just a second budget.
- A reporting rhythm. The monthly executive report should exist before there is anything to report, so the first real update lands in a format leaders already trust.
The decisions that need a controls voice
There are three moments when an owner most needs someone whose only job is to read the numbers. The first is setting the budget. The second is choosing a delivery model, because each model moves risk to a different party at a different price. The third is setting the completion date, because once a date is announced it stops being a forecast and becomes a promise.
At each of those moments, the controls question is the same: what would have to be true for this number to hold? If nobody can answer, the number is a hope.
What it costs to wait
When controls arrive late, the first three months go to archaeology. Rebuilding a baseline that was never approved. Reconciling a budget that was never broken into a cost breakdown structure. Reconstructing a change log from email. That is time the owner pays for twice, once in fees and once in decisions made blind.
When controls arrive early, the baseline, the budget and the risk register grow up with the project. The first contractor schedule is reviewed against something. The first cost report has a starting point. And the first hard conversation happens while there is still room to act on it.
We turn complexity into clarity, and clarity is cheapest at the start. If your program is still on a whiteboard, that is exactly the right time to call us.
