“Refurbish the Store” Is Not a Scope. It’s an Intention.
Written and narrated by Serguei Poppeleer.
Retail brands invest millions fitting out shopfronts in new markets across Africa, the Gulf and Europe.
Three words cost one project €400,000 more than the contract said: “Refurbish the store.”
Nobody behaved badly. The contractor was experienced. The relationship was good. The brief described what was wanted. The contractor priced their interpretation of it. Those two things were not the same project.
Here’s what nobody says when that brief gets circulated:
The pattern across store refurbishments:
The scope document still says “refurbish the store.” No manufacturer references. No dimensions. No material standards. The contractor prices their interpretation of the render.
But what “done” means was never written down before the first week of work. At handover, both parties have a different definition. The dispute was designed into the project before mobilisation.
Nobody can agree on what “complete” means because it was never defined in writing before the contractor started. The checklist captures the dispute. It does not resolve it.
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 fundamentals that prevent disputes before they form:
“Ceramic floor tiles” is a description. “Ceramic floor tiles, 300×300mm, RAL 7047, installed to BS EN 14411” is a specification. Only the second one prevents a dispute at handover.
The items that generate the biggest disputes are usually ones the client assumed were excluded but never wrote down. HVAC. Structural modifications. Work outside the demised area. These belong on the out-of-scope list before mobilisation.
If “done” is not defined before the contractor starts, it will be defined by the contractor at handover. That definition will reflect their commercial interests, not yours.
What cross-border retail delivery needs is not better design technology. It is the discipline of replacing the intention-based brief with a specification before the contractor is approached — not after the invoice arrives.
This isn’t about architects or project managers. They work within a procurement culture that has always accepted intention-level documentation as a brief. It is about an industry that moves from decision to mobilisation without pausing to write down what was actually decided.
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.
The assumption that makes the contractor the scope author
Most project teams on store refit programmes operate on a version of the same belief: “We have worked with this contractor before — they know our standards and what we expect.”
Familiarity reduces the probability of bad faith. It does not eliminate scope ambiguity. A contractor who has delivered for you before will interpret an unclear brief consistently with their previous experience — which may not match your 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.
When a scope document describes outcomes rather than specifications, the contractor becomes the de facto designer for every element the document does not specify. This is not a flaw in the contractor’s approach. It is a predictable response to ambiguity. The contractor prices what they understand the scope to mean. Their interpretation is shaped by what they can source, what their subcontractors can install, and what their margin requires.
Why intention-based briefs produce contractor-authored projects
Most scope documents for store refits are assembled after the decision to proceed has already been made. The brief comes from emails, meeting notes and a walk-through of the space. Materials are described generically. Acceptance criteria are absent. The out-of-scope list does not exist because nobody has worked through what could be misread as included.
The ceiling specification gets upgraded on site because it looks better and the contractor assumed an upgrade was in scope. The partition wall gets added because the site manager and the client’s local contact had a conversation on a Tuesday. 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%.
The second failure is the absence of an out-of-scope list. A scope document that describes what is included but says nothing about what is excluded is half a document. 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.
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 including structural modifications, HVAC, electrical works outside the demised area, and signage.
The contractor priced exactly what would be built. The final account closed within 3% of the contracted amount. Zero commercial disputes. Zero claims at handover. The fourteen-page scope document was not bureaucracy. It was the single document that closed every dispute before it opened.
Five questions that tell you where your scope discipline actually stands
If producing it requires significant effort, it does not exist in the form that protects you commercially.
Not scope changes — scope interpretations. Items both parties believed were their reading of the original brief.
If not, every category that could plausibly be misread as included is a potential dispute waiting to form.
Are they technically competent to specify materials by reference, state dimensions and write acceptance criteria? Or are they producing the brief and calling it a scope?
Before contractor approach, before contract signature, or after mobilisation? Only the first produces a project both parties are building to the same specification.
The objections this always raises
“We have a contract — the contractor is legally obligated to deliver what was agreed.”
The contract defines the commercial framework. If the scope within the contract is ambiguous, the legal obligation is to deliver the contractor’s interpretation of the ambiguity. The dispute will be about what was agreed, not whether it was agreed. A contract on top of an ambiguous scope is a commercial framework sitting on a disputed foundation.
“Producing a fourteen-page scope document takes too long before mobilisation.”
A fourteen-page scope for a standard store refit takes three to five days to produce from a LiDAR scan. A final account dispute takes three to six months to resolve. The scope document is not a delay to mobilisation. It is the investment that makes mobilisation commercially safe.
“The designer will sort out the details during the design stage.”
The design stage produces drawings. The scope document establishes what those drawings must specify. Without a scope document that defines materials, dimensions and acceptance criteria before the design stage begins, the designer will produce drawings that reflect their interpretation — which may differ from the client’s expectation and the contractor’s pricing.
AI tools can now generate scope documents from LiDAR scan data — extracting dimensions, identifying existing conditions, cross-referencing standard specifications and flagging elements commonly subject to interpretation disputes. The time required to produce a fourteen-page scope from a scan has dropped from days to hours on some platforms.
This acceleration is valuable. It does not change what needs to be in the document. AI applied to a brief that describes outcomes will produce a more detailed brief faster. It will not write the out-of-scope list, define the acceptance criteria, or make the commercial judgment about what the contractor should price and what they should not. Those decisions still require someone who understands both what the client wants and what a contractor needs to price accurately.
AI can accelerate scope production. It cannot replace the discipline of deciding what “done” means before the contractor interprets it.
What a scope document that prevents disputes looks like
It is produced before any contractor is approached. Every material is specified by reference — manufacturer, standard, colour code, installation requirement. Every dimension is stated. Every workstream has written acceptance criteria. The out-of-scope list covers every category that could plausibly be misread as included.
When a contractor prices from this document, they are pricing what they will actually be required to deliver. The final account reflects what was agreed at the start. The handover is a verification exercise, not a negotiation. The dispute does not arise because the ambiguity was closed before work began.
“Refurbish the store” is an intention shared between two parties.
It becomes a project when someone writes down, in precise technical language, what the finished store will be made of.
Until then, it is an opportunity for each party to have a different project.
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 →