The 5Cs of Refit.
How to reduce site visits, replace routine surveys, and prevent disputes in cross-border refit delivery. Written and narrated by Serguei Poppeleer.
Cross-border retail refit projects fail not because contractors are incompetent, but because the governance architecture around delivery was never built. The contract gets signed. The control architecture does not.
Unverified vendor dates (2–4 week delays). Informal scope variations (uncontrolled claims). Multiple reporting streams (false progress visibility). Open decisions with no consequence (drift that becomes cost). Final accounts 30–40% above contract value.
RESHAPE™ — built on The 5Cs Framework™: Contain the Scope, Command One Plan, Close Every Decision, Confirm Vendor Dates, Control Tower Cadence.
Consistent delivery across distributed store portfolios without permanent site presence. Final accounts closed within contract values. Handover against written scope. No disputes. Proved across four African stores simultaneously for a retail brand.
RESHAPE™ is built on The 5Cs Framework™ — a governance architecture that holds when the site is remote, the contractor is local, and the client is in Brussels.
The invoice arrived at week thirteen. It was 42% above the contracted amount. The contract had been signed in a Brussels boardroom on a Tuesday. Scope of works: store refurbishment at an African store. Timeline: twelve weeks. Budget: agreed, initialled, filed.
By week four, the contractor had started work. By week seven, the scope had quietly changed — new ceiling specification, different floor finish, additional partition walls that “made more sense on site.” Nobody sent a formal variation. The changes were communicated via WhatsApp, ratified by a thumbs-up emoji, and added to a running tab nobody was keeping.
The dashboard stayed green while the project drifted.
This is not an unusual story. Ask anyone who has managed distance-managed real estate delivery from a European headquarters. The geography creates distance. The distance creates gaps. The gaps — in scope, in decisions, in vendor commitments — fill themselves. Usually with cost. The instinct is to blame the contractor. Sometimes that is fair. But if you trace the overrun back to its source, you find the same thing: the governance architecture around the project was never built.
Distributed delivery projects fail in a predictable sequence. A scope document that describes outcomes rather than measurements. A project plan that lives in a steering deck rather than in the contractor’s hands. Open decisions that nobody closes because nobody owns them. Vendor dates that are aspirational rather than verified. Status calls that report what happened last week rather than catching what is about to go wrong next week.
I have run projects in more than thirty countries. The pattern I have seen more often than any other is not incompetent contractors or difficult clients. It is competent people operating without the right governance architecture — and finding out too late. When you are managing delivery from a distance — when your project is in Liberia and you are in Brussels, when your contractor is in Burkina Faso and your designer is in London — every gap in governance that might take months to surface at home surfaces in weeks.
Why the Standard Playbook Leaks Money
The conventional approach to multi-country real estate delivery has three pillars: fly in for site visits, hire a local surveyor, manage contractors remotely via email and WhatsApp. It is widely used. It is also reliably expensive. Not because the tools are wrong. Because none of them solve the actual problem.
A site visit feels like control. You are physically present, you walk the space, you make decisions on the spot. It costs €2,000 to €5,000 in travel and time. And it solves one day’s worth of problems. You visit on a Thursday. The site behaves well. You return to Brussels on Friday. The governance vacuum reasserts itself on Monday morning. Unless the control architecture changes — the scope document, the decision log, the vendor confirmation process, the weekly rhythm — the problems that caused the visit regenerate.
More site visits don’t fix the governance gap. They substitute for it.
Local surveyors produce reports. Reports go to the client. Questions come back. The cycle takes days, sometimes weeks, and creates a telephone game between the client’s requirements and the site’s reality. When the scope drifts or the contractor misses a date, the surveyor documents it. The governance problem — the actual decision that needs to be made, the consequence that needs to be enforced — still sits with the client in Brussels.
WhatsApp-managed contractors are not the disease. They are the symptom of a governance vacuum. When there is no structured decision log, no written scope, and no formal weekly rhythm, people default to the path of least resistance. Nobody knows which version of reality is contractual. That sentence describes the situation on most informally-managed remote projects by week six.
| Governance Failure | Typical Impact |
|---|---|
| Unverified vendor dates | 2–4 week programme delay; contractor resequencing adds unbudgeted cost |
| Open design decisions | Idle labour on site; rework when late approval reverses provisional work |
| Multiple reporting streams | False progress visibility; slippage invisible until recovery is no longer cheap |
| Informal scope variations | Uncontrolled claims exposure; final account disputes that take months to resolve |
| No decision consequence | RAID items drift for weeks; decisions made under crisis pressure, not clarity |
| No written acceptance criteria | Contractor and client disagree on what “done” means at handover |
The compounding effect is what makes these costs dangerous. A vendor delay triggers contractor resequencing. Resequencing triggers a variation. The variation reopens scope. The scope dispute delays handover. None of this was in the risk register. None of it had to happen.
The 5Cs Framework™
The framework was developed across thirty countries of project delivery and refined during three years of multi-country real estate work for a retail brand across four African stores. It is not theoretical. It is the distillation of what actually works when the standard playbook does not.
| # | Pillar | Name | What It Does |
|---|---|---|---|
| C1 | CONTAIN | Contain the Scope | Fuzzy requirements → written scope with measurements, materials, and acceptance criteria |
| C2 | COMMAND | Command One Plan | Deck governance → one operating plan that matches how the site actually runs |
| C3 | CLOSE | Close Every Decision | RAID drift → every open item has an owner, a deadline, and a consequence |
| C4 | CONFIRM | Confirm Vendor Dates | Optimistic promises → capacity, lead times, and proof of readiness verified |
| C5 | CONTROL | Control Tower Cadence | Reactive calls → fixed weekly rhythm; slippage caught before it compounds |
Most refit disputes do not start with a contractor who builds the wrong thing. They start with a scope document that described what was wanted without specifying what that meant. “Refurbish the store” is not a scope. It is an intention. A scope is: 87 square metres, ceramic floor tiles (300x300mm, colour reference RAL 7047), suspended ceiling at 2,600mm finished height, four fixed seating units to drawing reference SP-007, electrical to IEC standard 60364. Out of scope: HVAC works, structural modifications, all works outside the demised area. The difference between those two documents is the difference between a project that closes on budget and one that closes with a dispute.
The Reshape scan-to-refit approach removes the need for a site visit to produce that scope. A local contact scans the space using an iPhone with LiDAR capability — approximately twenty minutes, producing data accurate enough for most refit scopes, subject to specialist validation where structural or MEP precision is required. That data becomes a written scope document: verified measurements, a layout drawing, and a list of assumptions and constraints. The designer works from this brief remotely.
The Monrovia scope was produced from a remote LiDAR scan and site photographs. The scope document ran to fourteen pages, specifying every material by manufacturer reference and every dimension to the nearest 10mm. The contractor had no scope ambiguity to exploit. The final account closed within the contracted amount. Decision closure time averaged under 48 hours from issue to sign-off.
On almost every distributed real estate project I have reviewed, there are two project plans. The first goes to steering committees — Gantt chart, RAG status, narrative summary. It looks like control. The second is the plan the contractor actually uses: in their project manager’s head, in a WhatsApp thread, or in a notebook on site. It bears little resemblance to the steering deck version. Command One Plan means collapsing those two documents into one — updated weekly, showing actual progress against actual commitments, including open decisions and overdue actions.
Three separate reporting streams were feeding the Brussels project office — all describing different versions of progress. The switch to one operating plan, updated every Monday and shared with all parties, removed the discrepancy. When the plan said a milestone was at risk, it was. Reporting time per project dropped from 90 minutes to under 20 minutes per week.
Every distributed project accumulates open decisions. RAID logs are the standard governance tool. They almost universally fail to close them — because most RAID logs record what an item is without recording who owns it, when it must be resolved, and what happens if it is not. Close Every Decision means every open item has three attributes without exception: an owner, a deadline, and a consequence.
Without a consequence, a deadline is a suggestion.
A materials substitution decision sat open for over ten days. During that time, the contractor ordered provisional quantities of an alternative finish. When the approved specification came through, the order had to be cancelled — costing nine days of programme. After introducing a 48-hour decision rule with automatic escalation, this category of delay was eliminated from all subsequent projects.
“Yes, we can start Monday.” One of the most expensive sentences in distance-managed construction. Contractor date commitments made without verified capacity are aspirational. Confirm Vendor Dates is the discipline of replacing optimism with evidence: supplier capacity confirmed, lead times checked, customs clearance timelines factored in for cross-border material movements — before any date enters the programme.
A contractor committed to a materials delivery date for imported ceiling fixings without checking the customs clearance time from the country of origin. Actual clearance time was several weeks longer than assumed. After introducing a pre-commitment verification step — supplier lead time confirmed in writing before any date entered the programme — this category of delay did not recur across the remaining overseas stores.
Most project status calls answer one question: what happened last week? A project running in this rhythm is managing the past. Control Tower Cadence manages the near future. Fixed inputs — the updated operating plan, the closed-item log, confirmed vendor dates for the next two weeks. Fixed outputs: a revised operating plan, an updated decision log, verified commitments for the coming week. Same agenda. Same format. Every week. If a vendor has not confirmed a delivery due in ten days, that surfaces in the weekly cadence and triggers a phone call — not an urgent scramble when the delivery fails to arrive.
Four overseas stores running simultaneously across different time zones. A single 45-minute weekly cadence call replaced four separate reporting streams, two of which had been running a week out of sync. Slippage was caught around one week earlier on average. Preparation time dropped from 90 minutes per project to under 20 minutes. Zero governance-related claims across the four projects.
Four Stores, One Framework
The stores sat in several African countries, French- and English-speaking: Liberia, Burkina Faso, Burundi and Uganda. Each had its own legal system, its own customs regime and its own way of doing business, so the framework had to hold across all of them.
Between 2022 and 2025, the author served as Senior Project Manager, Real Estate & Construction for a retail brand — covering the full property portfolio: long-term real estate strategy, lease negotiations, facility projects, training centre development, and store relocations. It also covered the African stores.
Liberia, Burkina Faso, Burundi, Uganda: four different countries, four different construction markets, four different supply chains, four different contractor relationships. The challenge was maintaining consistent delivery governance across all four simultaneously, from Brussels, without the budget for permanent site presence at each location.
- Final accounts closed within agreed contract values across all four projects
- Zero contractual disputes on any of the four store projects
- Decision closure time reduced from over ten days to typically under 48 hours
- Supply chain slippage caught around one week earlier after switching to the weekly cadence
- Reporting time reduced from 90 minutes per project per week to under 20 minutes
- Site visit frequency reduced without any reduction in delivery governance quality
Governance Maturity — Where Does Your Operation Sit?
| Level | Operating Reality | What This Looks Like on the Ground |
|---|---|---|
| Level 1 | WhatsApp Delivery | No written scope. Contractor managed by message thread. All decisions informal. |
| Level 2 | Reporting Without Control | Stage gates and dashboards exist. The site runs on a completely different plan. |
| Level 3 | Multi-Plan Confusion | Steering deck, site plan, and supplier schedules are three separate documents with no reconciliation. |
| Level 4 | Verified Governance Cadence | One plan. Decision log in use. Vendor dates confirmed. Weekly rhythm established. |
| Level 5 | 5Cs-Controlled Delivery | Full framework operating. Slippage caught early. Handover against written scope. No surprises. |
Three Objections, Answered
“Our contractors need physical supervision.”
Physical supervision is one form of quality control. What contractors actually need is clarity: a precise scope, a plan they understand, decisions that close on time, and a weekly rhythm that surfaces problems before they compound. The 5Cs provide all of that without requiring anyone to be on site. Where physical quality inspection is genuinely required — for structural work or specialist installations — the Reshape model uses local inspection contacts for targeted, evidence-based visits at defined milestones.
“iPhone scans aren’t precise enough for refit work.”
LiDAR scanning on current iPhone hardware produces point clouds accurate enough for contractor-grade drawings across most refit categories — store refurbishments, office fit-outs, hospitality spaces, operational infrastructure. Where the scope involves structural modifications or detailed MEP coordination, a specialist survey is scoped separately. For the majority of refit work, the scan is faster and significantly cheaper than a traditional measured survey.
“Designers won’t work distance-managed without site visits.”
The Reshape designer network is built for this. Remote-first is how they operate, not a workaround. For clients with a preferred designer, Reshape works with them. The scan-to-brief workflow and The 5Cs Framework™ apply regardless of who the designer is.
Assess Your Delivery Governance Exposure
If this Special Report has described a problem you recognise — distributed refit projects that drift, overruns you struggle to explain, delivery you are responsible for but cannot directly control — there are two ways to take the next step.
Fifteen Yes/No questions covering the five controls of The 5Cs Framework™. About four minutes. It produces an immediate, specific picture of where your current governance architecture is strong and where the gaps are creating commercial exposure. No sales conversation required.
If you have a specific project on the table — a distributed refit in planning, a portfolio of remote properties, or a project already showing signs of drift — the review call is the fastest way to define the problem and scope the right engagement. No obligation to proceed.
Serguei Poppeleer, Founder, Contracts & Commercial. Civil engineer with over 20 years on major construction and EPC contracts in Europe, Africa and the Gulf, working for both contractors and owners. 30+ countries.
The contract was signed. The control architecture wasn’t.
The Delivery Score maps your governance exposure across the 5Cs and tells you which gap to close first. Free, about four minutes, instant result.
Get my Delivery Score — free → Book a Free 45-Minute Call →