Four Countries. Four Contractors. One 45-Minute Weekly Call.

Written and narrated by Serguei Poppeleer.

Wednesday. 08:00. Four countries on the call. Liberia. Burkina Faso. Burundi. Uganda.

45 minutes later the call ended. Five decisions closed. Three vendor commitments reconfirmed against current supply chain conditions. Two slippages caught eight days before their programme dates.

No site visit that week. None needed.

Here’s what nobody says about how this was possible:

The call worked not because the technology improved. It worked because the workflow was designed before the technology was installed.

What the 45-minute call replaced:

→
Four separate reporting streams — two running a week out of sync.

Replaced by one fixed weekly cadence. Same inputs. Same outputs. All four sites covered in sequence. Preparation time reduced from 90 minutes per project to under 20 minutes — because the format was fixed and the inputs were defined.

→
Status calls that reported what had already happened.

Replaced by a control cadence that reviewed vendor commitments two weeks forward. Slippage caught on average eight days earlier — because the cadence looked ahead, not behind.

→
Governance that depended on physical presence to function.

Replaced by a rhythm that made the site reality visible every week from head office. Zero governance-related claims across all four projects over three years. Control was not in the presence. It was in the rhythm.

Control is not about where you are. It is about the rhythm you have established and what that rhythm surfaces every week.

The fundamentals that made the 45 minutes produce this result:

→
Fixed inputs — the same information required every week, from every site.

Updated operating plan. Closed decision log. Vendor date reconfirmations for the next two weeks. No agenda variation. No preparation uncertainty. The call produced decisions — it did not receive updates.

→
Fixed outputs — the same decisions produced every week.

Reconciled plan. Cleared items. Verified commitments. Identified risks for the week ahead. Every participant left knowing the operating truth of their project and the two most critical decisions to close before the next call.

→
Forward visibility — two weeks of confirmed commitments reviewed every week.

A vendor delivery due in ten days that had not been reconfirmed surfaced in the cadence with ten days of response time. Under the reporting model it would have surfaced after it slipped.

A weekly status call answers: what happened last week? A control cadence answers: what is about to happen in the next two weeks — and what do we need to decide now to control it? The first manages the past. The second manages the near future.

Four countries. One call. Wednesday morning. The operating truth of all four projects visible by 09:00. That is what a control system looks like.


Why rhythm produces results that reporting cannot

A status call creates a snapshot. A cadence creates a pattern. The pattern is what catches slippage early.

When the same inputs are reviewed every week, deviation becomes immediately visible. A vendor commitment confirmed last week that is not confirmed this week surfaces in two minutes. A decision assigned last week that has not been closed surfaces with its consequence attached. A progress claim that does not match the operating plan surfaces before the invoice arrives.

Only one of them catches slippage while recovery is still cheap.

A retail brand — East Africa store (Uganda)

Part of a store expansion across several African countries, French- and English-speaking, each with its own legal system and customs regime. Four overseas stores running simultaneously across different time zones. A single 45-minute weekly control cadence replaced four separate reporting streams, two of which had been running a week out of sync. Slippage was caught on average eight days earlier under the cadence model than under the reporting model.

Site visit frequency was reduced. Preparation time dropped from 90 minutes per project per week to under 20 minutes. Zero governance-related claims across all four projects over three years. The control was in the rhythm, not the presence.


Five questions that tell you where your control cadence actually stands

1
Does your current project have a fixed weekly control call with defined inputs and defined outputs?

If yes — are the inputs actually fixed, or does the agenda vary based on what the team has prepared? Variable agenda calls are status calls. Fixed-format calls are cadence calls.

2
At your last status call: how many issues discussed had already consumed programme float before they were raised?

That number is the cost of reporting on the past rather than managing the near future.

3
What is the current forward visibility on your largest active project?

Can you identify the three items most likely to affect programme in the next two weeks — not from the risk register, but from the actual current operating condition?

4
How long does it currently take to confirm that a vendor commitment for next week is still valid?

What is the process, and when in the weekly cycle does it happen? If the answer is “when something goes wrong,” verification is reactive, not systematic.

5
If your project’s weekly rhythm were disrupted for two weeks, at what point would you expect to discover the impact?

If the answer is weeks after the disruption, the rhythm is the control system — and its absence would not be immediately visible. That is the architecture that needs strengthening.


The objections this always raises

“45 minutes is not enough to cover four sites properly.”

It is enough when the format is fixed and the inputs are defined. The preparation happens before the call, not during it. Each site takes approximately eight to ten minutes when the operating plan is updated, the decision log is cleared and the vendor confirmations are in. The call does not discover problems — it resolves the ones the fixed format has already surfaced.

“Our projects are too different to use the same agenda for all of them.”

The format is fixed. The content is project-specific. The same question — what are the three vendor commitments due in the next two weeks and have they been reconfirmed? — applies to every distributed project regardless of sector, country or contractor. Standardising the format removes preparation uncertainty without removing project specificity.

“We already review vendor dates in our monthly steering meeting.”

Monthly review catches slippage after it has consumed float. A vendor delivery due in two weeks that has not been reconfirmed surfaces in the weekly cadence with ten days of response time. It surfaces in the monthly steering report after it has already slipped. The cost difference is the float that was consumed between the two.


AI Reality Check

AI tools can now automate the preparation for a control cadence — pulling updated progress data, flagging vendor commitments due in the next two weeks, surfacing decision log items approaching their deadline and generating the pre-call summary automatically. Preparation time can drop from 20 minutes to near zero.

This automation accelerates a cadence that is already functioning. It does not create the cadence. It does not define the consequence architecture behind the decision log. It does not verify that the vendor commitments it surfaces have been confirmed against actual supply chain conditions. The rhythm has to exist for AI to make it faster.

AI can make the cadence preparation instant. It cannot replace the rhythm, the fixed format and the consequence architecture that make the cadence produce decisions rather than updates.


What the 45 minutes actually produces

An updated operating plan that all parties have seen and agreed. A decision log with no items more than 48 hours overdue. Vendor commitments for the next two weeks, reconfirmed since the last call. Two to three identified risks for the current week, with owners and response actions assigned.

The preparation takes under 20 minutes when the format is fixed and the inputs are defined. The call itself takes 45 minutes when it is run as a decision meeting, not a status meeting.

Four countries. One call. Wednesday morning.

The operating truth of all four projects visible by 09:00.

That is what a control system looks like.

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 →