What a Project Closed Within 3% of Budget Actually Looks Like
Written and narrated by Serguei Poppeleer.
The store refit closed at 3% above contract value. No disputes. No claims. No lawyers. Handover took one meeting.
The scope document from before mobilisation was on the table. Each acceptance criterion was checked against the delivered work. Everything matched. The contractor signed. The client signed. Nobody needed a forensic exercise to reconstruct what had been agreed eighteen months earlier.
Most people who hear this say: “That’s exceptional.”
It isn’t.
The project that closes within budget is not better resourced, better staffed or better located than the project that closes at 42% over. It is better governed. The difference is entirely in the operating architecture installed before mobilisation.
The same contractor market that produces projects closing 30 to 40% over budget produced this. Here is what was different:
Fourteen pages. Every material by manufacturer reference. Every dimension to 10mm. Acceptance criteria for every workstream. Eleven categories on the out-of-scope list. The contractor priced exactly what would be built. Ambiguity belonged to the document, not to the contractor.
Every programme date verified against actual capacity, customs clearance timeline and lead times before it entered the schedule. No aspirational commitments inherited. No port delays that arrived as surprises.
One plan that all parties used. Updated every Monday. Decisions closing in 48 hours with stated consequences. Slippage visible eight days before it compounded. The site and head office described the same project every week.
What this result demonstrates:
Not because everyone behaved well. Because the scope was specific enough that “what was agreed” was never in dispute.
It is the product of acceptance criteria written before the contractor started — so handover is a verification exercise, not a negotiation.
The result did not depend on an exceptional project manager or an unusually cooperative contractor. It depended on five conditions applied consistently from before mobilisation to handover.
The system travels. The chaos does not. That is the whole argument.
Why the result feels exceptional when it should be standard
Most cross-border retail projects do not apply all five conditions. Scope documents describe intentions. Vendor dates are accepted without verification. Decision logs track items without closing them. The operating plan and the site plan diverge by week two. There is no fixed cadence — only status calls that report what has already happened.
Under those conditions, a project closing at 30 to 40% above budget is not a failure of execution. It is the predictable output of a delivery system designed to produce that result. The overrun was not caused by the contractor. It was enabled by the governance architecture — or the absence of one.
The five conditions that produced the outcome
Not before contract signature. Before mobilisation. Fourteen pages. Manufacturer references. Dimensions to 10mm. Acceptance criteria. Out-of-scope list covering eleven categories. The contractor priced the project that would be built. The final account reflected what was agreed on day one.
Updated every Monday. Built at site-level granularity. When something changed on site, it changed in the plan that week. The steering deck and the site plan described the same project. When the plan showed a milestone at risk, it was at risk.
Named owner. Specific deadline. Stated consequence. No item drifted for weeks. No provisional orders that had to be cancelled. No nine days of programme lost to a materials substitution that stayed open too long.
Supplier capacity confirmed in writing. Customs clearance timeline obtained from the clearing agent. Lead times checked against current availability. The programme contained verified commitments, not optimistic estimates.
45 minutes. Same inputs, same outputs. Updated plan, closed decisions, reconfirmed vendor dates two weeks forward. Slippage caught before it compounded. No discovery at steering. No surprises at handover.
Part of a store expansion across several African countries, French- and English-speaking, each with its own legal system and customs regime. Across Liberia, Burkina Faso, Burundi and Uganda, simultaneously: no project exceeded budget by more than 4%. Zero contractual disputes across all four. Decision closure time reduced from an average of eleven days to under 48 hours. Supply chain slippage caught on average eight days earlier after the weekly cadence was established. Reporting time reduced from 90 minutes per project per week to under 20 minutes.
The same governance architecture applied consistently across four different contractor markets, four countries, four currencies. Consistent results.
Five questions that tell you how close you are
Scope lock, one operating plan, decision closure, verified vendor dates, control cadence. The weakest of the five is where your next overrun will come from.
What is the largest source of uncontrolled variation currently sitting inside the project?
That percentage is the cost of the missing conditions.
If not — what would need to be resolved, and when did the dispute first become visible in the project?
The answer to that question is the value of the delivery system.
The objections this always raises
“Our projects are more complex — a store refit is not comparable to our programme.”
The five conditions have been applied on programmes ranging from a single store refit to a €850M cross-border gas pipeline. Complexity does not make the conditions less relevant. It makes them more urgent. The larger the programme, the more expensive an unresolved ambiguity, an unverified commitment or an open decision becomes. The conditions scale. The cost of omitting them scales faster.
“Setting up this governance architecture before mobilisation takes too long.”
Producing a fourteen-page scope document from a LiDAR scan takes three to five days. Setting up a decision log with a consequence architecture takes an afternoon. The cadence takes 45 minutes per week once running. The total front-end investment is approximately one week. The time saved at the back end — in recovery, rework, variation negotiation and final account dispute — is measured in months.
“We don’t have the internal resource to maintain this across multiple projects simultaneously.”
Four projects. Four countries. 45 minutes per project per week. Under 20 minutes of preparation when the format is fixed. The governance architecture described here is not resource-intensive. It is discipline-intensive. The constraint is not time — it is the willingness to design the system before mobilisation rather than fix the problems it would have prevented.
AI tools can now accelerate every element of the five conditions — generating scope documents from scan data, monitoring decision log compliance, tracking vendor date verification and surfacing cadence insights in real time. The technology that makes this architecture faster and more precise is available today.
The architecture still has to exist for AI to accelerate it. AI applied to a project without a scope document will not generate one. AI applied to a decision log without consequences will surface the drift more efficiently. AI applied to a control cadence that does not exist will not create the rhythm.
AI accelerates the system. It cannot build one where none was designed.
What the prize actually looks like
The final account is a formality, not a negotiation. The scope document from before mobilisation defines what was included. The variation log documents what changed and why. The final account is the sum of those two things — assembled in real time during the project, not reconstructed retrospectively.
The handover meeting is a verification exercise. Acceptance criteria were written before the contractor started. Every workstream is checked against them. Items that meet the criteria are signed off. There is nothing to dispute because the standard was defined before the work began.
The project that closes at 3% over is not better resourced than the project that closes at 42% over.
It is better governed.
The difference is entirely in the operating architecture installed before mobilisation.
How close is your programme to No-Surprises Delivery?
The Delivery Score measures your governance architecture across the five dimensions of The 5Cs Framework™. Fifteen Yes/No questions. About four minutes. Instant result.
Get my Delivery Score — free → Read the Special Report →