“Yes, We Can Start Monday.”
Written and narrated by Serguei Poppeleer.
Cross-border retail projects depend on supply chains spanning three continents.
One unverified vendor date can erase three weeks of float before anyone at head office sees the source.
“Yes, we can start Monday.”
Three of the most expensive words in cross-border construction. Not because the contractor is dishonest. Because the contractor believed it when they said it. And nobody checked.
Here’s what nobody says when that date gets entered into the programme:
The pattern across retail projects from West Africa to the Gulf:
The supplier confirmed verbally. The customs clearance time was estimated from memory. The actual clearance timeline was never checked with the clearing agent.
The materials were still in a European port. Had been for eleven days. Nobody on the client side had checked. The dashboard showed the commitment as on track.
The date was aspirational. Not evidence-based. The programme was built on it anyway. When Monday arrived, the conditions that would have made it true did not exist.
A confirmed date is not what a supplier says when asked. It is what the supply chain, the customs schedule and the site access conditions will actually support on that day.
The fundamentals that must be verified before any date enters the programme:
A verbal confirmation reflects intent. A written confirmation with quantity, date and terms reflects a commitment. Only the second one belongs in the programme.
In cross-border construction, customs is where aspirational dates go to die. The timeline varies by port, by period, by documentation. It must be verified, not assumed.
A supplier who delivered in three weeks last year may face six weeks this year. Supply chains change. The verification must reflect current conditions.
What cross-border retail delivery needs is not better procurement software. It is the discipline of replacing optimism with evidence before any date enters the programme.
This isn’t about procurement teams. They work with the information contractors give them. It is about a project culture that treats a verbal commitment as a confirmed date because checking feels like distrust.
The cost of a verification conversation is twenty minutes. The cost of a failed commitment built into the programme is measured in weeks of delay — and the cascade that follows.
The assumption that creates the cascade
Most project teams on cross-border programmes operate on a version of the same belief: “Our contractor is reliable — if they say Monday, it will be Monday.”
Reliability is a track record, not a guarantee. A contractor who has delivered reliably before will commit to dates based on their optimistic assessment of the supply chain — because that is how they maintain the relationship and secure the next award. They are not lying. They are estimating. And the estimate does not account for the customs backlog, the port delay, or the specialist who is still finishing the previous job.
The difference between a commitment and a verified date
A commitment is what a supplier or contractor says when asked if they can meet a date. It reflects their intention and, if they are professional, their best current estimate. It does not reflect a checked supply chain, a confirmed subcontractor booking, or a verified permit timeline.
A verified date is different. Supplier capacity has been confirmed in writing. The subcontractor has confirmed availability against the specific scope. The permit authority has provided a processing timeline. Frozen drawings have been issued and received. Every upstream dependency has been resolved.
The specific risk in frontier markets is import logistics. A contractor in Ouagadougou or Kampala will commit to a delivery date based on their experience of typical timelines. Typical is not current. A port backlog, a documentation issue, or a new import restriction can extend a three-week clearance to six. Nobody tells the programme. The date passes. The materials are still at the port.
Every date accepted without verification is an optimistic promise the client has agreed to inherit. When it fails, the delay belongs to the programme — not because the client caused it, but because they accepted a commitment they did not verify.
Part of a store expansion across several African countries, French- and English-speaking, each with its own legal system and customs regime. A contractor committed to a delivery date for imported ceiling fixings without checking the customs clearance time from the country of origin. The assumed clearance was three weeks. The actual clearance took six. The programme had been built on the committed date. Three weeks of float disappeared before the source was identified.
After introducing a pre-commitment verification step — supplier lead time confirmed in writing, customs clearance timeline obtained from the clearing agent, both documented before any date entered the programme — this category of delay did not recur across the remaining store projects. Average schedule variance on verified dates: under four days.
Five questions that tell you where your vendor discipline actually stands
As opposed to accepted from contractor commitments. The distinction determines your exposure.
Not estimated from past experience. Verified against current conditions at the specific port of entry.
Was it a supply chain factor that a verification check two weeks earlier would have surfaced?
What evidence is required before a date enters the programme? If the process is not documented, the answer is: none.
Supply chains change. A verified date from six weeks ago may no longer be valid.
The objections this always raises
“Asking contractors to verify their dates damages the relationship.”
A contractor who cannot provide written evidence of capacity and lead times is giving you a date they cannot guarantee. Requesting evidence is commercial clarity, not distrust. The contractors who push back most on verification are usually the ones whose dates fail most often. The conversation is uncomfortable once. The cascade is uncomfortable for months.
“We have used this supplier for years — we know their lead times.”
Past performance reflects past conditions. Supply chains change. A supplier who delivered in three weeks last year may face six weeks this year due to factors neither of you can see from the contract. The verification takes twenty minutes. The recovery from a failed commitment takes weeks and consumes float that cannot be replaced.
“We don’t have time to verify every date.”
You are already verifying them — after they fail, in the recovery meeting, during the cost claim negotiation. The question is whether you spend that time before the date is in the programme or after it has consumed your float and triggered a cascade. The front-end investment is twenty minutes per commitment. The back-end cost is weeks of recovery.
AI tools can now monitor supply chain conditions in real time — flagging port backlogs, customs processing delays and supplier capacity constraints before they affect programme dates. Some platforms integrate directly with logistics networks to surface risks weeks before a delivery window closes.
This intelligence is valuable when the dates in the programme are evidence-based to begin with. An AI tool monitoring a programme built on unverified commitments will identify supply chain risks more efficiently. It will not convert aspirational dates into verified ones. The verification discipline has to exist before the technology can accelerate it.
AI can flag that the commitment is at risk. It cannot replace the conversation that should have happened before the commitment entered the programme.
What programme certainty actually requires
Every date in the programme is evidence-based before it is accepted. Supplier capacity confirmed in writing. Lead time verified against current availability. Customs clearance timeline obtained from the clearing agent. Drawings issued and received. Every upstream dependency resolved.
That process adds two to three days to the front end of programme loading. It removes weeks from the back end of programme recovery. It eliminates the cascade that starts when Monday arrives and the conditions that would have made it true do not.
The programme built on verified commitments is not a programme that will never slip. It is a programme where slippage is visible early — because the evidence is tracked, and deviation from it surfaces in days, not at the point where recovery has become expensive.
“Yes, we can start Monday” is a commitment.
What the supply chain will support on Monday is a fact.
Only one of those two things belongs in the programme.
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 →