A missed milestone is a lagging indicator. Float erosion is visible months earlier — if anyone is measuring it. We interrogate the baseline before you approve it, verify progress against evidence rather than claims, and read delay while it is still a decision.
Illustrative engagement telemetry — live engagements display from the actual record.
A baseline programme arrives looking like an engineering document. It is also a commercial one. Float can be hidden inside durations so that it belongs to the contractor rather than the project. Activities can be left open-ended. Sequences can assume design information that nobody has committed to issuing. Every one of those choices is defensible in isolation, and every one of them will be cited later, in a claim, as evidence of what the owner agreed to.
The region makes this sharper than most. HKA's CRUX research finds Middle East projects extending their planned schedules by 80.9% on average — the highest rate in the world, against a global average near 67%, with 82% of regional projects running off schedule. The leading causes it identifies are not construction failures: scope change, late issuance of design information, and construction beginning against incomplete design. Those are decisions and omissions, recorded in documents, months before the date moves.
Conventional oversight meets that with a monthly report assembled from the contractor's own percentage-complete claims. By the time a variance appears in it, the event is six weeks old, the recovery options have narrowed, and the contractor's position is already priced. The report is accurate. It is simply describing something that has finished happening.
Three disciplines run continuously, on the same live record the other seven governance disciplines use.
The baseline is interrogated before it is approved. Logic integrity, open-ended activities, suppressed float, and sequencing stress-tested against the information-release programme — because a sequence that depends on drawings nobody has undertaken to issue is not a sequence, it is a claim in preparation.
Progress is verified, never accepted. Installed quantities, delivery and inspection records, and field evidence are reconciled against the claimed percentage before it updates the programme. The gap between claimed and verified progress is tracked in its own right: a widening gap is often the earliest signal a project produces.
Float is treated as the leading indicator it is. Consumption is tracked per trade and per path against planned burn. A package eating float at twice its planned rate is announcing a delay a quarter early — while re-sequencing still costs a conversation rather than an acceleration claim.
Read the chart as an owner would: the package burning float fastest is not yet late. Nothing has slipped, no milestone has moved, and a monthly report would show it green. That is precisely the window in which a delay is still cheap — and precisely the window sampling misses.
And when the extension-of-time claim arrives — on a fast-track programme it will — it meets a contemporaneous record. Delay events, their causes, and their programme impact were recorded as they happened, with evidence attached, by a party with no interest in the answer. A claim argued against that record is a different negotiation from one argued against a reconstruction.
Before you approve it, the programme is tested as a document that will later be used against you: logic integrity and open-ended activities, float that has been hidden inside durations, sequencing that assumes information nobody has committed to delivering, and resource loading that does not survive arithmetic. A baseline is not a plan. It is the datum every future claim will be measured from, which is why it is worth more scrutiny than it usually gets.
Against evidence. Installed quantities, delivery and inspection records, field data, and photographic evidence tied to location — reconciled against the claimed percentage before it enters the programme. Claimed progress and verified progress diverge on almost every project; the size of that gap is itself an early indicator.
Because a missed milestone is a lagging indicator — by the time the date slips, the recovery options have already narrowed and repriced. Float is the leading one. A trade consuming its float at twice the planned burn rate is announcing a delay a quarter before the date moves, while re-sequencing is still cheaper than acceleration.
It meets a contemporaneous record built from week one rather than a reconstruction assembled under dispute pressure. Delay events, their causes, and their programme impact are recorded as they occur, with the evidence attached. That is the entire difference between defending a claim and negotiating one.