Spot a change Tuesday. Plan to log it Wednesday. Never log it. Margin leaks weekly.
Commercial recovery is the most under-systematised value-protection workflow in construction. Change events get spotted but not logged. Notice windows close while the team is busy. Evidence bundles get assembled from email threads at 5pm Friday. Variations get rejected because the cause → effect → entitlement chain isn’t there. Year-end brings a ledger of unclaimed change.
Capture it. Notice it. Argue it. Evidence it. Value it. Submit it.
Click any stage to expand · inputs / outputs / time / human role
The Radar
Log the change at the moment of recognition. Classify against the contract (NEC clause 60.1, JCT clause 5, bespoke). Set the notice clock.
- COLLAPSEThe Clock
Track the contractual notice requirement. Date served, party, method, acknowledgement. Time-bar windows surfaced before they close.
+ EXPANDThe Case
Build the cause → effect → entitlement chain. What changed, what followed, why entitled. Every claim source-traced to drawing, instruction or RFI response.
+ EXPANDThe File
Pull supporting evidence: drawings, instructions, RFI responses, photos, daywork sheets, programme extracts. Bates-numbered, source-linked.
+ EXPANDThe Count
Defined Cost build: labour, plant, materials, subcontractor, prelims, OH&P. Every layer source-traced to current rates and the contract pricing mechanism.
+ EXPANDThe Drop
Compile variation narrative, evidence index, valuation, entitlement statement to the Project Manager's template. Audit trail logged. The pack hits the assessor’s desk.
+ EXPANDCompetent-person judgement and sign-off — a named person from your firm approves every document.
Pricing judgement — rates, margins and commercial positions are yours, never generated.
Every document carries a named approver from your firm. Nothing is issued unsigned.
Your documents stay confidential — processed by the team you deal with, never training data.
Judge the output the way an assessor would.
Illustrative · Crestfield Phase 2 is a fictional worked projectCE-009 – the HV switchgear design change from 11kV to 33kV on Crestfield Phase 2 – is a complete, audit-grade worked example: one fictional change event carried from recognition to submitted quotation, with every document the workflow produces on the way. £43,039 and 1.5 weeks, submitted ten days inside the clause 62.3 deadline and still awaiting the Project Manager's assessment. Read the entitlement narrative end to end, or browse the full library.
Worked example — fictional project, real output formatCE-009 entitlement narrative
Every change event, on one running ledger.
Illustrative model · worked example (Crestfield CE-009), not a live accountScrub the period, D+0 to D+15, and CE-009 climbs the contract gates — logged, noticed, narrated, valued, submitted. It stops there: the quotation went in ten days inside the clause 62.3 deadline and the assessment has not come back. Every sibling event holds its place on the same ledger, each notice inside its window.
Fourteen Structured Deliverables. The whole change account, from first notice to final-account position.
Zero time-barred notices. Agreed first time.
The variation account holds.
Illustrative model · targets, not measured client resultsNotice tracker watches every contract clock, windows surfaced before they close.
Stronger narratives, indexed evidence, contract clauses cited inline, assessors push back less.
Every change captured at the point of recognition, not at month-end. Pipeline value visible.
From CE detection to assessor-ready submission pack, same process, same rhythm, every period.
Change control on NEC and JCT contracts – capture, notices, entitlement narratives, evidence, valuation – has become a workflow AI can draft and a QS can govern. The contractors who systematise commercial recovery first will keep the margin everyone else writes off at final account.
A change that lives in an inbox is an anecdote; a change that lives on the ledger is an entitlement.
Built with working QSs and commercial leads who argue entitlement for a living. Pilot results will be published named, or not at all.
The AI builds the file.
The QS holds the position.
On a live contract the judgement calls are commercial ones: whether an event is a compensation event, what the entitlement argument is, which rates to defend, when to concede and when to escalate. The kit drafts the notices, narratives, evidence indexes and valuations around those calls. It never makes them – that stays with your QS and commercial manager.
Reads and structures contract documents, instructions, correspondence, drawings and programme extracts
Classifies change events against the contract, variation, compensation event, instruction
Tracks notice requirements (NEC ECC, JCT, bespoke) and surfaces deadlines before they close
Drafts variation narratives, cause, effect, entitlement, in the structured form an assessor expects
Indexes evidence automatically against change events as documents arrive
Make commercial decisions, that stays with the QS / commercial manager
Agree variations, that’s the contract administrator / employer’s agent
Issue notices on the contractor’s behalf, a contractually significant act stays human
Interpret contract clauses authoritatively, the legal position is the QS’s call
Replace contract review by qualified commercial / legal teams
BuiltAI is run by Dominic Hobson, who has spent his career in construction and M&E delivery — the packs exist because he needed them.
Send us the variation the Project Manager parked at month-end.
Thirty minutes. The change event, the contract clause, your evidence to date. We hand back a structured variation narrative, evidence bundle index and entitlement statement, assessor-ready, contract-grounded.
Priced as an annual licence by company size, plus usage credits — the pricing page explains the model. How the pack is priced →
You'll deal with Dominic Hobson, Founder, BuiltAI — not a sales team.
Under NDA if you want one. Your document is seen by the team that processes it, is never training data, and is deleted on request.