The Handover With Nothing to Dispute

Written and narrated by Serguei Poppeleer.

The handover meeting lasted 40 minutes.

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 lawyer. Nobody needed a claims consultant. Nobody needed three months of correspondence to establish what had been agreed eighteen months earlier.

Most people who hear this say: “That’s exceptional.”

A handover with nothing to dispute is not exceptional. It is the natural result of a delivery architecture that closed the disputes before they were disputes — at the point they were still scope questions, vendor commitments and open decisions.

The 40-minute handover is not the result of a better final account process. It is the result of every dispute being designed out before the contractor started.

The same cross-border refit environment that produces six-month final account negotiations also produced this. The difference:

→
Same contractor market. Different scope architecture.

Ambiguity closed in fourteen pages before the contractor was approached. Not discovered at handover. Acceptance criteria written before the first week of work. Handover was a verification exercise, not a negotiation. There was nothing to dispute because what “done” meant had been agreed before the work began.

→
Same distance from head office to site. Different decision architecture.

Every open decision closed in 48 hours or escalated automatically. No items drifting for weeks. No provisional orders that had to be cancelled. Every decision that would later have become a handover dispute was closed in writing during the project.

→
Same final account process. Different result.

The final account reflected what was agreed on day one because what was agreed on day one was specific enough to be agreed. The variation log documented what changed and why. There were no informal agreements that one party remembered differently. The account was assembled in real time, not reconstructed retrospectively.

The dispute that looks inevitable at handover was usually created in the first two weeks of the project. A scope that described an intention. A date accepted without verification. A decision that stayed open until it became a delay.

The system travels. The chaos does not. That is the whole argument.


What each of the five conditions contributed to the handover

C1 — Contain
The scope prevented the disputes that never happened.

Fourteen pages before the contractor was approached. Every material by reference. Every dimension to 10mm. Acceptance criteria for every workstream. Eleven out-of-scope categories. At handover, the acceptance criteria were already written. There was nothing to negotiate — only work to verify against a standard that had been agreed before the contractor started.

C2 — Command
The plan prevented the surprises that never happened.

One operating plan, updated every Monday, shared with all parties. When something changed on site, it changed in the plan that week. The handover reflected the project that was actually built — not the project that was originally specified, nor a version assembled from disputed recollections.

C3 — Close
The decision log prevented the claims that never happened.

48-hour closure with stated consequences. Every materials substitution, design change and scope clarification resolved in writing during the project. At handover, there were no informal agreements that one party remembered differently. Every decision had a date, an owner and a written outcome.

C4 — Confirm
The verified dates prevented the delays that never happened.

Every programme commitment verified against actual supply chain conditions. The delays that arise from optimistic commitments were caught in the verification process before they consumed float. They did not arrive as surprises at the point when recovery would have been expensive.

C5 — Control
The cadence prevented the drift that never happened.

45 minutes every Wednesday. Slippage visible eight days earlier than under the previous reporting model. The final account was not a reconstruction of what had happened — it was the sum of what had been tracked, priced and agreed during the project, week by week.

A retail brand — four African stores (2022–2025)

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: every final account closed within 4% of the contracted amount. Zero contractual disputes. Zero governance-related claims. Zero handover certificates contested. The same governance architecture applied consistently across four different contractor markets in four different countries simultaneously.

The 5Cs Framework did not adapt to each location. It created the conditions in which each location could deliver consistently. The system travels. The chaos does not follow.


Five questions that tell you how close you are to this outcome

1
On your last three completed projects: how long did the handover process take from practical completion to final account agreement?

What were the primary sources of delay? Which of the five conditions, if applied, would have prevented them?

2
What percentage of the final account variance on your last completed project was traceable to variations assembled retrospectively?

Versus variations identified and priced during the project. That percentage is the cost of the missing conditions.

3
On your current active project: if works were to complete next month, is the governance architecture in place to support a dispute-free handover?

Are acceptance criteria written, decisions closed, and the variation log current? If not — what would need to happen in the next four weeks?

4
Can you identify the three items on your current project most likely to become handover disputes?

For each one — what would need to happen in the next two weeks to close them before handover rather than at it?

5
If the five conditions were applied consistently on your next project from before mobilisation: what would be different at handover?

The answer to that question is the value of the delivery system. It is also the value of not applying it — measured in the disputes, delays and final account negotiations that did not have to happen.


The objections this always raises

“Some disputes are inevitable in cross-border construction — it is the nature of the environment.”

The disputes that feel inevitable are almost always traceable to an ambiguity in the original scope document, a decision that stayed open too long, or a commitment accepted without verification. These are not environmental factors. They are governance architecture failures. The frontier environment exposes them faster. It does not create them.

“A 40-minute handover is not realistic for a complex programme.”

The complexity is in the project. The handover is a verification exercise. If the acceptance criteria are written before the work starts, the handover is checking completed work against a written standard. That process takes as long as the project requires — but it does not generate disputes. The 40-minute handover is for a standard store refit. The principle applies at any scale when the architecture is in place.

“Contractors always push back at final account — that is how the industry works.”

Contractors push back when the scope is ambiguous, when decisions were taken informally and when commitments were made without documentation. When the scope is specific, decisions are closed in writing and commitments are verified and documented, there is nothing to push back on. The contractor has been working to a defined standard throughout. The final account reflects it.


AI Reality Check

AI tools can now support every element of the five conditions in real time — generating scope documents from scan data, monitoring decision log compliance, tracking vendor date verification, surfacing cadence insights and flagging early signs of final account exposure. The technology to support a 40-minute handover on a complex cross-border project exists today.

The governance architecture has to exist alongside it. AI applied to a project without acceptance criteria will not generate them. AI monitoring a decision log without consequences will surface the drift more efficiently. AI accelerating a delivery system that is already functioning produces the 40-minute handover faster. AI applied to a project that was never governed correctly does not produce it at all.

The system travels. The technology accelerates it. The chaos does not follow — if the architecture was designed first.


What the prize actually looks like

The handover certificate is signed on the day works complete. The final account is agreed within two weeks because it contains only what was agreed during the project. The contractor’s team demobilises without outstanding correspondence. The client takes possession of a space that matches the scope document approved before mobilisation.

No claims consultant. No dispute resolution process. No six months of correspondence establishing what was agreed eighteen months ago.

The project is complete. The relationship is intact. The next project can begin from a position of demonstrated delivery rather than recovered dispute.

The 5Cs Framework did not adapt to each location.

It created the conditions in which each location could deliver consistently.

The system travels. The chaos does not follow. That is the whole argument.

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 →