We didn't adapt a project tool. We built the clause logic first.
ContractIQ's claim engine is built to be configured against any contract form's notice, timebar, and determination procedures — not a generic “task and deadline” system with construction terms bolted on. FIDIC and JCT are fully built in today.
Generic tools miss the clause. That's how claims get lost.
A project management tool tracks tasks. A spreadsheet tracks dates. Neither understands that a Sub-Clause 20.1 notice under FIDIC has a strict 28-day timebar that extinguishes the claim if missed — or that JCT's Relevant Event provisions run on a different clock entirely. ContractIQ's data model starts from the clause, not the task — which is what makes it possible to configure against any contract form your projects run on, not just the two we ship with today.
- FIDIC Yellow Book
- FIDIC Red Book
- JCT Standard
- JCT D&B (in dev)
Three contract forms live today, a fourth in development — and the clause engine is configurable to any form beyond them.
What's mapped today
FIDIC Yellow Book (2017)Live
Cl. 20 Contractor's Claims procedure — Notice of Claim, Engineer Validation, Fully Detailed Claim, Consultations, Engineer Determines. 28-day timebar, UK bank holiday calendar.
FIDIC Red Book (2017)Live
Equivalent Cl. 20 procedure configured per project.
JCT Standard Building ContractLive
Relevant Events, Loss & Expense claims. Contract administrator response windows.
JCT Design & BuildIn development
In development — get in touch to prioritise your form.
Your contract, whatever form it's in.
Every project runs its own amendments and negotiated timebars — and not every project runs FIDIC or JCT at all. Claim flow templates let your commercial team configure step durations, counting rules, and owners against any contract form, so the system reflects the contract you actually signed.