06 / Headline 3 — M-PD Programme & Delays
From slip to substantiated delay event, in one workflow.
Programmes upload. Baselines lock. Slippage is captured contemporaneously — with cause, clause, cost and concurrency. A year of compounding loss collapses from a forensic dispute into a single auditable register.
Cranebank · Hall B Storey 2 · 350 days slip across 7 events · auditable
The forensic problem
Delay claims fail because the evidence didn't exist when the delay did.
UK construction loses billions in extension-of-time claims every year — not because the events didn't happen, but because the contemporaneous record didn't capture the cause, the clause, the cost and the concurrency at the moment the slip occurred. Six months later, the delay analyst is reconstructing the project from emails and CCTV.
The contract administrator rejects half of it on the grounds that "the contractor cannot demonstrate causation". This is true — but it is a documentation problem, not a fact problem.
Delay event register · 7 entries · 350 days total
Captured as it happened — not reconstructed afterwards.
MV transformer rooms added — Hall B
Phoenix Digital instructed addition of two MV transformer rooms post-baseline. WBS B.2.MEP-04 impacted. Compensation event filed under NEC4 60.1(1). 84 days net impact after concurrency analysis.
Nimbus DNO milestone shift
DNO Nimbus revised grid connection date by 12 weeks. Cascade impact on power-up, commissioning and witness-test sequence. EWN issued under NEC4 16.1; programme update logged.
Fire compartmentation re-design
Building Safety Regulator gateway 2 feedback required revised fire compartment strategy across pods 13–24. Lead architect issued IFC revision; sub-contractor re-mobilisation required.
Storm Eira — three weeks of crane stand-down
Sustained wind speeds above safe-lifting threshold for 21 consecutive working days. Independently substantiated against Met Office data. Relief event under contract clause 2.29.
Frostline package re-tender
Cooling package sub Frostline went into administration mid-package. Re-tender and re-mobilisation. Concurrent with DEL-02; net independent impact 38 days.
Building Safety Regulator gateway 2 hold
BSR gateway 2 approval period extended beyond statutory expectation; works at risk if commenced. Compliance lead recommended pause; pause logged contemporaneously.
IFC drawings late — pod 31–36 grouping
Pod-fit-out drawing release lagged the contractual information release schedule by 9 weeks. Lead architect attribution; partial concurrency with DEL-03 reviewed and netted.
350 days
Net impact across 7 substantiated delay events. Concurrency reviewed event-by-event. Each entry has its cause, clause, cost and signed competent-person sign-off — auditable end to end.
Why it works
Every entry has the four facts. Every entry is signed by a person.
- Cause
- The single root cause, taxonomy-bound. Configurable per project under Principle 1.
- Clause
- The contract clause that governs the event — drawn from the Contract-Aware Engine vault. Auto-suggested, human-confirmed.
- Cost
- The forecast cost impact — decomposed into prelims, sub-package and head-office overhead. Editable; recorded version-by-version.
- Concurrency
- Other delay events live at the same time. The system surfaces overlap; the analyst signs off the net impact.
- Sign-off
- Competent-person tile. Locked declaration. Records role, signatory, time, IP, document hash.
"If the entry was made when the event happened, the dispute starts and ends with the entry. If the entry was made six months after, the dispute starts." Phase 2 PM decision-ledger · M-PD-12