The AI Reads Contracts Literally
Rosie identifies compensation events by analysing contracts as written. It does not assume mutual understanding. It does not give benefit of the doubt. It reads literally and applies mechanically.
This approach has revealed something uncomfortable about construction contracts: they often contain Z clauses that parties informally ignore until disputes arise.
Three Categories of Problematic Z Clauses
1. Contradictory Clauses
Z amendments that directly conflict with standard form provisions. The AI flags both as applicable, creating immediate confusion. Which takes precedence? The drafter intended one outcome, the parties assumed another, and the contract supports both interpretations.
2. Unintended Consequence Clauses
Reasonable provisions that create absurd outcomes when applied systematically. A minor amendment intended to clarify one situation becomes commercially devastating when the AI applies it to every qualifying event.
3. Mutual Misunderstanding Clauses
Ambiguous language where parties held different interpretations from day one. Both sides proceed based on their assumptions until the AI applies the actual wording and neither recognises the result.
The Commercial Risk
Commercial risk becomes subjective rather than quantifiable when contracts contain contradictory or ambiguous provisions. You cannot price risk you cannot measure.
Disputes escalate when informal understandings disappear. The project manager who knew what the parties really meant moves on. The quantity surveyor who negotiated the original deal retires. Knowledge walks off-site and the written contract remains.
The AI Amplification Effect
Manual contract administration naturally incorporates human judgement. The QS reads a problematic clause and interprets it reasonably. The PM encounters an edge case and applies common sense.
AI does not interpret reasonably. It applies literally. Every edge case triggers the written provision. Every ambiguity gets resolved by the actual wording, not the intended meaning.
This says less about AI and more about contracts. It exposes the gap between what is written and what the parties actually intended.
Recommendations for Better Contracts
Stop Adding Z Clauses Without Proper Review
Every amendment should be reviewed by someone who understands how it interacts with the rest of the contract. Copy-paste from previous projects creates accumulated contradictions.
Document Mutual Understandings Explicitly
If both parties agree on an interpretation, write it down. Side letters, meeting minutes, and agreed clarifications become critical when the project team changes.
Use Standard Forms Properly
NEC4 works as drafted. Heavy amendments undermine the mutual obligations that make the contract function. If you need extensive Z clauses, question whether NEC is the right form.
Conduct Contract Health Checks
Before project start, review the contract systematically. Flag contradictions and ambiguities. Resolve them before they become disputes.
What This Reveals
The AI taught us that many construction contracts are held together by mutual goodwill rather than precise drafting. When goodwill evaporates, the written contract determines outcomes, and it often says something neither party intended.
The AI did not create these problems. It made them visible. Fixing them takes better contract drafting, not smarter AI interpretation.
Key Takeaways
- A Z clause is the contract you actually have. Ignore it and the notice is late against the wrong clock.
- Write the event that day in the site diary.
- Rosie reads those entries against the Z clauses, not just the printed NEC4.
Gather turns your site diaries into commercial evidence and flags compensation events before the eight week time bar closes. Book 15 minutes and see it run against one of your own projects.
Book a 15 minute demo



.webp)




