When every change hides the true position: getting one honest read on a hard project
The situation I walked into
I was brought onto a first-of-a-kind engineering project inside a large organisation. It was a major build, the sort where nobody had done quite this thing before, and by the time I arrived it had grown well beyond the budget it had been let at.
The reason was ordinary enough, which is rather the point. The price had been fixed while the design was still immature. On a first-of-a-kind job that is almost unavoidable, but it meant the real scope kept turning up after the number was already set in the contract. So the job absorbed change after change, and every one of those changes had to be tracked somewhere.
That is where the numbers stopped telling the truth. The way costs were coded, each change request opened its own new heading, its own little pocket in the reporting. Sensible in isolation, because you do want to see what a change costs. But it kept happening, and before long you did not have one project you could read at a glance. You had dozens of tiny projects buried inside the project. The true position was still in there somewhere, it was just sliced into too many pieces to add back up. Nobody could give a straight answer to a simple question, because the honest answer was scattered across a hundred cost lines.
What I did
First, I want to be straight about my role. I was an enabler working to the project directors, not someone who rode in and fixed it single-handed. This was a project with hundreds of people on it. The direction was theirs. My job was to get them the right information and to establish what was actually true, so they could steer.
So I started by reading the job honestly. Where the reporting really stood, where the engineering deliverables really were against what had been promised, where we stood against the contract itself. Not the version in the last status pack, the real one.
Then I went at the structure, because the coding was the thing fragmenting the picture. I simplified it. Instead of every change spawning its own new pocket, an approved change folded back into the one project scope under the same coding, and progress was managed through a single plan. Fewer headings, one shape you could actually read.
Alongside that I put a proper reporting rhythm in place. Weekly and monthly reporting to a defined standard, refreshed on a set beat rather than pulled together in a scramble whenever someone senior asked. I was firm about the quality of it, because the reports I inherited were largely box-ticking. They gave the client nothing they could act on. The client had even drifted into dictating what the reports should say, which is not how it is meant to work, so I reset that relationship alongside the project director and got the cadence back to where it belonged. The moment the reporting was honest, the real issues surfaced instead of staying hidden.
I also ran a reconciliation of cost against cash, checking the reported figures against the actual transactions moving through the system. That matters most when the money is passing through a system changeover, which it was, because that is exactly when the reported position and the real one quietly drift apart. And on the document side I built a simple dashboard, one view showing what had genuinely been delivered against what had been promised, so nobody had to chase status across a dozen silos to know where the job actually stood.
Then I owned the monthly report to the directors. I verified the numbers, showed where things stood and where the gaps were, had each discipline lead present and justify their own part, and chased down every open query rather than letting it roll into next month.
The outcome
The position stopped being a guess. The directors could see one honest read, on time, and make calls against it instead of arguing about which version of the number was right. The overrun did not vanish, no reporting fix does that, but the truth of it was visible early enough to act on, and that is the whole point. You cannot manage what you cannot see, and for a long stretch nobody could see it.
What it means for you
Most owner-led businesses end up cutting their numbers a lot of different ways as they grow. A new job, a new line, a one-off, and each one gets its own pocket because it made sense at the time. It is not a mistake, it is just what happens when you are building the thing and carrying it at the same time. The trouble only shows up on the day you need the real position and cannot find it, because it is spread across too many pieces to add up.
That is the work I do with owners under "grip the numbers". Simplify how the numbers are cut so changes stop fragmenting the picture, put a steady reporting beat behind them so the position refreshes on a schedule rather than on demand, and reconcile what is reported against the cash that has actually moved. One honest, timely read, early enough to steer by. If any of this sounds familiar, I am happy to talk it through.
The Ratio Check is a free, five-minute read on where your business actually stands, and it is the best place to start.