On January 22, 2026, the Privy Council handed down [2026] UKPC 2 — Uniform Building Contractors Ltd v The Water and Sewerage Authority of Trinidad and Tobago — overturning a TT$13.9 million award in favor of the contractor. UBC had been engaged to design, supply, and install approximately 28 kilometres of pipeline under a contract incorporating the FIDIC Yellow Book 1999 Edition with Conditions of Particular Application. Disputes arose during execution. UBC advanced four categories of claim for additional payment: for cutting and excavating asphalted roadway, disposing of unsuitable spoil, importing suitable backfill, and undertaking night working.
The Privy Council found that UBC had known about the events giving rise to those claims by late 2007. Sub-Clause 20.1 of the FIDIC Yellow Book required notice within 28 days of the contractor becoming aware of the triggering event. No notice was given in time. The Privy Council held that clause 20.1 operated as a condition precedent. Failure to comply with it was fatal to every claim. TT$13.9 million — reinstated from the Court of Appeal's 2023 award — was lost not because the work was not done, but because the contractual obligation to notify was not tracked.
FIDIC contracts are long. The Yellow Book 1999 Edition runs to over 70 pages of conditions before adding the Conditions of Particular Application, Employer's Requirements, and schedules. The contract for the Rio Claro to Mayaro pipeline was not unusual in its complexity. What is unusual is for any organization executing that contract to have clear visibility — clause by clause — of which provisions operate as conditions precedent, which have notice periods attached, and what those periods are in calendar terms.
In practice, complex contracts are read at signing and then managed by memory, precedent, and the assumption that the project manager knows what to do and when. That assumption fails in projects with disputes, scope evolution, or extended programmes. UBC knew about the disputed works in late 2007. Nobody tracked the 28-day clock. By the time the claims were formally advanced, the window had closed.
Project management tools track programme milestones. Quantity surveying systems track cost. CLM platforms track contract execution and renewal dates. None of these are built to parse the procedural obligations embedded in a FIDIC contract and produce a structured register of which provisions operate as conditions precedent, which carry notice periods, and what those requirements are. The project team's awareness of Sub-Clause 20.1's 28-day window depends entirely on whoever read the contract at signing still being on the project, still remembering the detail, and recognising that the specific works now underway constitute a triggering event.
Generic AI tools reading unstructured FIDIC documents face a compounding problem. The notice provisions are present in the text, but their classification as conditions precedent, their interaction with specific claim types, and their application to events in the field requires structural understanding of the document — not pattern recognition across its text. An AI generating a summary of a FIDIC contract will not reliably distinguish which notice periods are conditions precedent and which are not. The Privy Council spent considerable analysis reaching that conclusion about Sub-Clause 20.1. A tool reading an unstructured PDF will not replicate that reasoning at scale, across every clause, in real time during project execution.
Sub-Clause 20.1 is exactly the kind of provision that requires noise-free, structurally parsed contract data — not a read-through and a summary.
AffiniCore processes the executed contract: the base FIDIC conditions, the Conditions of Particular Application, and all amendments. It identifies and captures Sub-Clause 20.1 as a named, structured notice obligation — extracted from 70-plus pages of contract conditions, with its trigger, its 28-day timeframe, and its classification as a condition precedent clearly defined. The result is a noise-free foundation that reflects what the contract actually requires, not what a project team recalls it to say two years into execution.
AffiniAI traverses that foundation. When disputed works arise, the question "does this require a notice?" has an immediate, navigable answer grounded in the contract itself. Any member of the project team can query "what notice requirements apply to claims for additional payment?" and navigate directly to Sub-Clause 20.1 — with the 28-day window visible and the condition precedent status confirmed at the source clause. Affinitext does not auto-detect triggering events or start a countdown when disputed works begin. That determination still requires human judgment on site. What changes is this: the obligation is no longer buried in a filed contract that nobody re-reads during a busy construction programme. With the notice requirement extracted, named, and accessible — and with regular reminders prompting teams to review live obligations — the question gets asked when events arise, rather than surfacing for the first time in a court filing seventeen years later.
FIDIC contracts of any edition — Yellow Book, Silver Book, Red Book — contain provisions that operate as conditions precedent. Not all of them are flagged as such in the document structure. The Privy Council confirmed in [2026] UKPC 2 that Sub-Clause 20.1 is one of them.
If your organization is currently executing FIDIC contracts, identify every Sub-Clause 20.1 notice obligation that is or may become live. Map the trigger events. Map the 28-day windows. If your current contract intelligence system cannot surface that with a navigable, source-linked answer, you cannot demonstrate compliance with the conditions precedent — and you cannot recover the claims if you miss them. The Rio Claro to Mayaro pipeline project ended with TT$13.9 million lost not because the work was disputed, but because the obligation register did not exist.
• Mondaq — Procedural Failures Fatal to Variation Claims Under FIDIC Yellow Book (2026)
• Clyde & Co — Uniform Building Contractors Ltd v The Water and Sewerage Authority of Trinidad and Tobago (February 2026)
• Pinsent Masons — Privy Council sets aside £1.5m appeal ruling over FIDIC contract clause
.jpeg)
