02 / The problem
UK construction in 2026 has a contract-clause problem disguised as a productivity problem.
Six years on from Grenfell, four years on from the Building Safety Act, and the same fact still gets re-stated in eight places. We have not been slow at building. We have been slow at writing down what we already know.
Cranebank · contract pack · pre-execution · 1,840 pages
Symptom 01
The clause is in the contract. The team is in the dark.
JCT and NEC4 contracts run to hundreds of pages. The site team operates on the highlighted half of a project executive summary. When an event happens — a delay, a variation, a defect — the relevant clause exists, but it takes hours of legal review to find it, days to draft a notice that cites it, and weeks before the response loop closes.
By that point the moment has passed, the cost has been absorbed, and the contractual route has often quietly closed. Most contractual rights expire because nobody had time to exercise them in the window the contract specified.
Symptom 02
The Building Safety Act made the burden bigger, not smaller.
Post-Grenfell, the regulatory weight on higher-risk buildings — and increasingly on data centres treated as critical infrastructure — has multiplied. The golden thread, the gateway sequence, dutyholder competence, the principal designer / principal contractor shift in CDM — every one of those introduces evidence requirements that arrive in different formats from different teams at different times.
Compliance is not the bottleneck. Compliance reconciliation is. Eight forms of evidence; one regulator; zero patience.
Symptom 03
The same fact — written eight times.
01
The notice
A delaying event, written as a clause-cited letter to the contract administrator.
02
The programme
The same event, re-keyed against the WBS activity it impacts, with a new float calculation.
03
The early warning
NEC4 EWN — the same event, re-stated for the cost forecast register.
04
The RFI / TQ
If the cause was a design ambiguity — the same event, written for the design team this time.
05
The payment application
The same event, re-priced against the bill of quantities and inserted as a CE-line.
06
The site diary
A daily log entry — same event, written for posterity, never read again.
07
The board paper
The same event — abstracted, summarised, RAG-rated for the monthly steering meeting.
08
The audit / golden thread
Three years later — the same event, reconstructed from emails, for the regulator.
"The platform must be impeccable. The legislation takes absolute and total priority. And the system itself never decides — a competent person does." The three sentences that shaped every decision in the spec.
What we built in response