The Cost of Drift.
Written and narrated by Serguei Poppeleer.
Your governance framework is in place. The deck says green. Then you call the site, and the site says something else.
That gap has a name. Drift. And it has a cost most programmes never put a number on — because by the time it’s visible, it’s already spent.
Drift is never dramatic. That is exactly the trap.
It’s a transformer delivery that slips a week. A fire-suppression package nobody priced. A cable-routing decision left open “until the next meeting.” None of these is a crisis. Each one is survivable on its own. Stacked, over a quarter, they’re a claim.
On the programmes I’ve worked — transport hubs, power plants, pipelines — drift never announces itself. It gets discovered. And it is always discovered later than it happened. By the time the dashboard turns amber, the money is already gone; you’re just reading the receipt.
A worked model — how small becomes a claim
Take one quarter on a mid-sized cross-border programme. None of the following is a crisis. Watch them stack.
Nobody flags it; it looks recoverable. But the trade that followed was sequenced against the original date, so it now waits too.
The work proceeds. The commercial position does not move with it. The change is now a future argument nobody has had yet.
Provisional work starts against the likely answer. When the real answer differs, that work is reversed — paid for twice.
Now it is one event: a delayed milestone with an unpriced variation and abortive work attached. Ten quiet weeks of latency, presented as one expensive surprise. Each item was small. The compounding was not.
What happened: drift cost six months — six months of idle.
Why nobody stopped it: nobody owned the delay, because nobody believed they were the one causing it. Each party’s slip was small and defensible. The sum of them was neither.
Why it mattered: by the time it surfaced it had become a €30M+ conversation. The position was recovered and the exposure held in real time. The six months were recovered within the original programme window. The cost was how long it took anyone to call it.
The distance between reporting and control is where claims are born.
Where drift walks in
This is what the 5Cs exist to stop. Each C is a door drift walks through. Scope that was never contained. A plan that splits in two. A decision that never closed. A vendor date taken on trust. A cadence that meets but doesn’t control. Close the five doors and drift has nowhere to enter quietly.
The objections this raises
“A week here and there is normal — we always recover it.”
You recover the visible slip. You rarely recover the latency around it — the resequencing, the unpriced change, the abortive work. Those don’t show as the slip. They show later, as the claim.
“We can’t put a number on drift.”
You can’t put a precise number on it after the fact — which is the point. You can measure the leading version: decision latency, unverified dates, unpriced change. Watch those climb and you are watching the cost form, not reading the receipt.
Drift is a latency problem, and latency is exactly what AI can compress. Monitoring the 5C inputs continuously, it can surface the slip, the unpriced change and the open decision while each is still a week old — not a quarter old.
But it monitors against a standard you have to set first. Define the controls, then let the machine watch them. Automate before you standardise and you simply discover the drift faster while still doing nothing about it.
The cost of drift gets paid whether you measure it or not.
The line worth keeping
A control is only real if it changes what happens next week. Reporting tells you where you were. Control changes where you’re going.
A governance framework that documents drift instead of stopping it is just a very professional way to be surprised.
The only real choice is whether you see it in time to act — or read about it later, in the claim.
Drift gets paid whether you measure it or not. Measurement just decides who reads the bill, and when.
What is drift already costing you?
The Delivery Score maps where control is leaking across the 5Cs — and which gap is compounding fastest. Fifteen Yes/No questions. About four minutes. Instant result.
Get my Delivery Score — free → Read the RESOLVE Special Report →