Beneath the pillar tools — Contract, Schedule, Cost, Risk, Field — sit five named layers they all run on. The power isn't in any one tool; it's in the layers that connect them.
A per-project home for everything an analysis needs: your contract form and Particular Conditions, the P6/MS Project programme, Contract Data and key dates, and the registers each tool produces. Upload once; every tool reads from it.
Full FIDIC General Conditions intelligence, fused with the way your Particular Conditions amend them. This is the layer a textbook-trained model cannot reproduce, because it reasons from your contract — not a generic template.
The layer that makes ControlsIQ more than a set of tools. It assembles your contract, programme and project data into a shared context every tool reasons from — so a schedule-health finding connects to entitlement, and a notice drafts from your actual clauses and dates. Connection is the moat.
Claims Digger — the conversational way to test entitlement to time, cost or both, under your FIDIC General and Particular Conditions. It answers from the Context Engine, with the clause citations that make a position defensible.
A record of how each answer was produced: a per-interaction AI audit log and an AI Use Summary, designed to support professional reliability decisions in line with the RICS AI standard. The layer that lets you stand behind what the tools produce.
Every tool below is live today, linked to its page.
Because the layers share one context, a finding in one tool means something in the next: schedule health connects to entitlement, a delay to a notice deadline, a risk to a claim head. That connection is what a generic AI cannot copy — because it needs your contract, not the textbook.