The Invoice Arrived 42% Over. Nobody Could Say When the Project Changed.

Written and narrated by Serguei Poppeleer.

Retail brands are spending billions opening and refitting shopfronts across Africa, the Gulf and Europe.

Most of those projects will close 30 to 40% above contract value.

Not because the contractor failed. Because the delivery system failed first.

Here’s what nobody says in the boardroom:

We have digitized the reporting of cost overruns. We have not eliminated the system failures that create them.

The pattern I see everywhere — across 30 countries and more than 20 years of cross-border project delivery:

→
Real-time project dashboards installed.

But the scope document still says “refurbish the store.” No manufacturer references. No dimensions. The contractor prices their interpretation of what that means.

→
Digital reporting tools deployed.

But vendor commitments are still accepted on trust. The date was never verified against actual lead times. The dashboard shows green. The materials are still in Rotterdam.

→
RAID logs introduced.

Thirty-four items are open. Eleven have owners. None have consequences. The log tracks the problem. It does not close it.

Technology accelerates a broken delivery workflow faster. We don’t need better dashboards. We need better delivery architecture.

The fundamentals that keep getting missed:

→
What is explicitly in scope — by material reference and dimension?

Written down. Agreed. Before the contractor is approached.

→
What does “done” actually mean — for each workstream?

Acceptance criteria. Agreed in writing. Before the first week of work.

→
Who owns every open decision — and what happens if it stays open?

One named person. One date. One stated consequence. Without the consequence, the deadline is a suggestion.

What cross-border retail delivery needs is subtraction — and workflow redesign before the next project starts. Not more tools running on top of ambiguity that was never closed.

This isn’t about the project managers fighting this battle every week. It is about organisations that default to adding tools when the actual problem is a delivery architecture that was never built.

Ambiguity belongs to whoever interprets it. In a cross-border refit, that is always the contractor — until the scope document closes the gap first.


The assumption that creates the gap

Most project teams operate on a version of the same belief: “The contractor is experienced, the relationship is good, and our brief is clear enough — they know what we want.”

This belief is the source of most overruns on cross-border retail projects. Not bad faith. Not contractor error. A brief that described an intention, and a contractor who priced their interpretation of it.

When the ceiling specification gets upgraded on site because it looks better. When a partition wall gets added because the site manager and the client’s local contact had a conversation on a Tuesday. When the floor finish gets substituted because the original was out of stock and nobody wanted to delay the programme for a written variation.

Each change is individually reasonable. Collectively, they are the 42%.

A scope document that describes what a space should feel like is a brief. A scope document that describes what it should be made of is a contract. Only the second one prevents disputes.

Why scope documents fail before the work starts

Most scope documents are assembled after the decision to proceed has already been made. The brief comes from emails, meeting notes and a site visit. Materials are described generically. Acceptance criteria are absent. Out-of-scope items are not listed because nobody has thought through what could be misread as included.

The document looks like a scope. It functions like a list of intentions.

The second failure is timing. Most scope tightening happens after kickoff — after supplier quotes come back, after site surveys reveal constraints, after the brief evolves. By then the contractor has priced on their own interpretation. Every subsequent clarification is either a variation they did not price or a dispute about whether it was in scope at all.

Scope lock must happen before mobilisation. Not before contract signature — before mobilisation. Before a single supplier is approached.

What scope precision actually requires: every material specified by manufacturer reference or standard. Every dimension stated to the nearest measurable unit. Acceptance criteria written for each workstream. And an explicit out-of-scope list covering every category of work that could plausibly be interpreted as included.

Writing the out-of-scope list is not pessimistic. It is the discipline that prevents a €2,000 interpretation dispute from becoming a €40,000 claim six months later.

A retail brand — East Africa store

Part of a store expansion across several African countries, French- and English-speaking, each with its own legal system and customs regime. The scope was produced from a remote LiDAR scan before any contractor was approached. Fourteen pages. Every material specified by manufacturer reference and colour code. Every dimension to the nearest 10mm. Acceptance criteria written for each workstream. The out-of-scope list covered eleven categories. The contractor had no ambiguity to exploit. The final account closed within 3% of the contracted amount. Zero commercial disputes. Zero claims at handover. Decision closure time averaged 36 hours from issue to sign-off.


Five questions that tell you where your scope discipline actually stands

1
Can you produce the scope document for your three largest active projects right now?

Not the contract — the scope. With measurements, materials by reference, acceptance criteria and an explicit out-of-scope list. If producing it requires significant effort, it does not exist in the form that protects you.

2
When the last scope change was made on site, what was the documented process for pricing it?

Who owned that process, and what happened when it was not followed?

3
How many scope interpretation disputes arose on your last five completed projects?

What percentage traced back to an ambiguity in the original scope document?

4
Can you state in writing what “done” means for each active workstream on your current project?

Not the milestone date. What the completed, accepted, signed-off version looks like.

5
At what point in the project cycle is your scope document produced?

Before contractor approach, before contract signature, or after mobilisation? The answer determines your exposure.


The objections this always raises

“We use standard contract templates — we have a scope document.”

Standard contract templates define the commercial framework. They do not specify materials by manufacturer reference, state dimensions to 10mm, or write acceptance criteria for each workstream. A contract template with a vague scope attached is a commercial framework sitting on an ambiguous foundation. The dispute lives in the scope, not the contract.

“Our contractor has delivered for us before — they know what we want.”

Familiarity reduces the probability of bad faith. It does not eliminate scope ambiguity. A contractor who has delivered before will interpret an unclear brief consistently with their previous experience — which may not match the current expectation. The dispute that arises from a familiar contractor misinterpreting a brief is harder to resolve than one with a new contractor, because both parties believe they are right.

“We sort scope issues through the variation register as they arise.”

A variation register manages scope changes that happen during the project. It does not prevent disputes that arise from scope that was never specified precisely enough to begin with. Managing scope retrospectively through variations is more expensive, slower and more contentious than writing a precise scope before mobilisation. The variation register is the correct tool for genuine changes. It is not a substitute for scope discipline at the start.


AI Reality Check

AI tools can now analyse scope documents for ambiguity — flagging undefined terms, missing dimensions and gaps in acceptance criteria faster than any manual review. Some platforms cross-reference scope language against standard specifications and identify clauses that have generated disputes on comparable projects.

This is useful when the scope document is specific enough to analyse. AI applied to a brief that describes outcomes will identify ambiguity in a document that was never intended to be precise. It surfaces the problem accurately. It does not produce the fourteen-page specification that prevents it.

AI can accelerate scope review. It cannot replace the discipline of designing the workflow correctly before the contractor mobilises.


What redesigning the workflow actually produces

The contractor prices accurately because the scope is specific. Variations are identifiable because the baseline is unambiguous. Acceptance criteria are agreed in advance, so handover is a verification exercise rather than a negotiation.

The client does not need to be on site to know what was agreed. The scope document is the single source of truth. Every question about what was included has a written answer. Every dispute about what was changed has a paper trail from the moment the change was identified.

The additional time invested at the front end is measured in days. The time saved at the back end is measured in months. The disputes avoided are not counted because they never happened.

The 42% overrun was approved long before the invoice arrived.

It was approved the day work started from a brief instead of a specification.

Where does your delivery system actually stand?

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 →