The Proving Problem: Why Every Capital Project Shifts From Building to Substantiating
For the first months of a capital project, the work is tangible: drawings, mobilisation, sequencing, the daily physical discipline of turning money into a structure. Then, without any formal announcement, the project changes shape. The meetings stop being about what happens next and start being about what happened — and whether you can show it.
This transition is not scheduled. It appears on no Gantt chart. But every experienced project manager has lived through it — the week the project pivots from forward-facing to backward-facing. According to XNM's analysis of capital project delivery, this shift is the thread that runs through nearly every overrun, delay, and claims dispute, regardless of sector.
The Shift Is Arithmetic, Not Attitude
By roughly month six of a build, the project has accumulated a past — and the past generates obligations the way the work generates dust. Progress claims must be substantiated. Change orders must be justified against a baseline that nobody has looked at since spring. Deficiencies must be tracked, closed, and evidenced. Someone wants a monthly report, and someone else wants the same numbers in a different format for a different audience.
None of this is optional and none of it is waste. It is how a capital asset becomes a defensible one — something that can be handed over, insured, reported against, and drawn on for decades. But it is a fundamentally different kind of work than what everyone was hired to do, and it competes for exactly the same hours.
What the Drift Actually Costs
The real overrun mechanism on a great many projects is not a bad estimate or a bad contractor. It is a slow migration of the most experienced person on the project — the one who holds the context — from directing the work to explaining it. Hours that were once spent on sequencing and trade coordination shift to reconstruction, reporting, and claims preparation.
There is a compounding effect that makes this worse. A decision recorded properly at the time it was made takes minutes. The same decision reconstructed a year later, under a payment dispute, involves multiple people, produces a weaker document, and costs far more than anything the decision itself was worth. The cost is invisible while it accumulates and appears all at once when someone files a claim.
Three Habits That Belong to the First Five Months
You cannot prevent the shift from building to proving — it is structural. What you can do is decide whether it arrives as a surprise or as a plan. Three habits carry most of the weight, and all of them belong to the first months of the project, which is precisely why they get skipped.
Record decisions when they are cheap. One paragraph, at the moment, in the place the document lives. This is the highest-return discipline in project work and it costs minutes at the time and months in recovery if you skip it.
Staff the proving half before you need it. Someone owning records and reporting from month one is not overhead — they are the reason your project manager is still managing the project in month eighteen. The role exists on every successful large build; the only question is whether it is filled proactively or improvised under pressure.
Make the monthly report a by-product. If reporting is assembled from records that already exist, month six is a busy month. If it is assembled from memory and email, month six is where the project changes shape and the project manager's calendar changes permanently.
Recognising the Turn in Advance
The signal that the shift is approaching is subtle. Meetings start to spend more time on what was agreed three months ago than on what needs to happen next week. The project manager starts pulling old emails to answer questions. Reporting starts taking longer than it did the month before. None of these individually is alarming; together they are the early warning.
The point is not that the proving half of the project is unmanageable. It is not. Projects complete all the time with full records, clean handovers, and settled accounts. What distinguishes them from the ones that end in disputes is almost always the same thing: they staffed and prepared for the proving half in the building half. The difference shows up not in month six but in month twenty-four, when the file can answer for itself.
Every project you have ever worked on made this turn. The good ones simply saw it coming.
Source: Why Capital Projects Become Paperwork Projects by Month Six, XNM Technologies
This content was generated by AI.
Comments