Ask a capital intensive mining business what it has spent on its active projects and you will usually get a clean answer. Ask what has actually been built for that money and this is harder to define.
Spend and progress are not the same thing, yet they are often governed as though they are. The gap between money out of the door and value in the ground, is where most budget surprises quietly begin.
It is tempting to treat the symptoms one at a time. A sharper report here, tighter invoice handling there, a standard variation form for everyone to use. Each helps but the same challenges keep resurfacing across different mines, different teams and different systems because they share a single root. The way capital is governed across the project lifecycle was never designed as one joined up thing. It grew, piece by piece, around the work.
That root is the Target Operating Model (ToM) and it’s the difference between numbers you hope are correct and numbers you can stand behind.
What A Target Operating Model Really Is
A ToM is a clear, deliberate picture of how an organisation needs to function in order to realise its strategic goals. For capital control specifically, there are four questions that drive the TOM:
#1 What is the process from concept to capitalisation?
#2 Who holds which responsibilities and at what threshold?
#3 What data must everyone work from?
#4 How is this governed end-to-end?
Most mining businesses have never sat down and answered those four questions as a single set. Each project, function and system have addressed them in their own way over time. A fragmented target operating model exists by accident rather than design, making control feel harder than it should.
The value is in creating a clear, unified the model. When the four questions have one shared answer, the everyday symptoms that drain confidence start to resolve on their own.
The Symptoms Are Model Gaps In Disguise
Three patterns show up again and again in mining capital portfolios. Each look like its own challenge but is really operating model gaps showing through.
The first is visibility. Cost data often sits at a high level showing top line figures only. By the time a report reaches the right desk it is already out of date and nobody can say with confidence how much of a project is genuinely complete rather than simply paid for. That is a data question. When progress and commitment are captured in the same structure as cost, the top line stops hiding what sits beneath it.
The second is timing. An invoice rarely tells you anything new. By the point it lands, the order has gone out and the money is, in practical terms, already committed. If spend is only registered once it is billed, commitments made weeks earlier sit outside the picture entirely. That is a process and control question. When a commitment is recorded against the budget the moment it is made, the forecast reflects what has actually been agreed, not just what has been billed.
The third is consistency. Most portfolios run on more variance processes than they realise, each project manager shaping their own way of raising and approving changes. None of it is wrong exactly. It is just inconsistent, which makes a single view across the portfolio almost impossible to build. That is a governance question. One agreed way to raise, approve and track variances ties every change to the budget it affects and lessons then travel between projects rather than being relearned on each.
Three symptoms, one cause. Design the model and you address all three at once, rather than chasing each in turn.
Design The Model, Then Let The System Hold It
Technology matters here but the Target Model is the glue that hold systems, processes and data together. A well configured project and finance system links project delivery to financial control. Commitments are visible when they are made, not when invoices arrive. Budgets are phased to reflect how work is built, not simply how money is spent. This enables project teams a clearer view of progress, forecast costs and remaining budget.
The system does not decide how capital should be controlled, the operating model does.
Configure any platform around a model you have deliberately designed and it consistently holds good practice in place. Configure it around whatever exists today and you simply make the current confusion run faster. This is why a technology project that skips the operating model so often disappoints. It automates the gaps instead of closing them.
We saw the difference this made on a major project for a leading mining organisation. Commitments were checked against remaining budget the moment they were raised, not once the invoice arrived and budgets were phased to follow the build. Control over spend followed quickly and the investment paid for itself inside six months. The software enabled it but a deliberately designed operating model was the major success factor.
The Honest Summary
The mining organisations that trust their capital numbers are not the ones with the most reporting or the newest system. They are the ones that decided, deliberately, how capital should flow and be governed and then chose tools to match that decision rather than the other way round.
We have been delivering this work at scale in the mining industry for more than twenty years, bringing the experience and practical expertise needed to design operating models that drive lasting value. If any of these patterns feel familiar, that is the conversation worth having. Not about a single report or a single process but about the target operating model underneath them all. We are here when you are ready to have a chat with our experts.
