AI for Contract Review in Construction: Time Bars, Flow Down and Variations

Construction contracts fail differently from commercial contracts. A software agreement usually hurts you at the end, when someone tries to terminate or claims damages. A building contract hurts you on a Tuesday in month four, because a site instruction was treated as a verbal request, nobody issued a notice within the window the contract required, and an entitlement worth six figures quietly expired while the work carried on regardless.

That is the specific problem worth pointing an agent at. Not "can AI read a contract", which is settled, but whether the operative obligations in a main contract and its subcontract chain can be extracted, dated, flowed down and checked against what is happening on site. Below is what that looks like for a contractor, subcontractor or developer, and where it stops.

Pre-signature review against your own risk position

Before signature, the useful question is never "is this contract fair". It is "where does this document sit against the positions we have already decided we will and will not accept". Most firms have those positions, even if they live in a commercial director's head rather than a document. The first job is writing them down: acceptable liquidated damages rates and caps, whether you accept fitness for purpose obligations above reasonable skill and care, design liability, uncapped heads of loss, net contribution, set-off rights, termination at will, and the notice periods your site teams can realistically meet.

The agent reads the incoming contract, the particulars or contract data, every schedule and every appendix, and produces a position sheet: the clause, what it says in the counterparty's words, which of your positions it engages, and whether it sits inside, outside or partly outside that position. Anything it cannot map cleanly, and construction contracts always contain some of this, comes back quoted verbatim and unresolved rather than guessed at. Your commercial lead opens a marked-up risk register instead of a 180 page PDF.

Flow down from main contract to subcontract packages

Flow down is where money leaks, because the mismatch is invisible until it matters. You accept a fourteen day notification window upstream, then issue a subcontract giving your subcontractor twenty eight days to tell you about the same event. You are now liable for something you can no longer pass on.

An agent handling flow down reads the executed main contract and every subcontract package together, then builds a side by side obligation map. For each obligation it records the upstream requirement, the downstream requirement, and the gap: notice periods longer downstream than upstream, programme obligations that do not reference the master programme, damages that are not stepped down, insurance limits short of what you promised the employer, design responsibility that stops at your level, and warranty or defects periods that expire before yours do.

The output is a gap list per package, ordered by exposure, with the exact wording on both sides so a quantity surveyor can check it in seconds. It runs again every time a package is let, which is the part manual review never manages once twenty packages are in procurement at once.

The notice regime as a live obligations calendar

The clauses that decide whether you get paid for disruption are usually not the ones anyone argues about at signature. They are the procedural ones: what event triggers a duty to notify, how many days you have, whether the clock starts when the event occurs or when you became aware of it, who exactly must be told, in what form, and whether failure to comply bars the claim entirely or merely affects assessment.

An agent extracts every one of these into a structured register: trigger, deadline, calculation basis, recipient by contractual role, required form, whether a time bar attaches, and the clause it came from. That register becomes a live calendar rather than a document. When a delay event, an instruction, an employer's act of prevention or a change in statutory requirements is recorded, the agent works out which notice obligations that event engages, calculates the deadlines from the contract's own rules, and raises them with the named person who owns them, with the countdown and the consequence stated plainly.

What it reads

The contract and its amendments, the accepted programme and its revisions, site diaries and daily allocation sheets, labour and plant returns, the instruction and RFI logs, progress photographs with their metadata, weather records where the contract makes them relevant, progress meeting minutes and project correspondence. It reads them continuously, not when somebody suspects a claim.

Variations and change instructions against the change mechanism

Every experienced site team knows the pattern. A design change is described in a meeting, restated in an email from a project manager, and picked up by the trade before anyone tests whether it was validly instructed.

The agent checks each candidate change against what the contract requires: was it issued by the person named as authorised to instruct, was it in the required form, does it fall within the definition of a variation at all or is it a correction of the contractor's own work, does the mechanism require a quotation before proceeding, and what deadline applies to submitting cost and time effects. It maintains the change register itself, matching instructions to quotations to valuations to certified sums, and flags the two failure modes that cost most: work proceeding on something that has not been validly instructed, and a valid instruction where the time or cost submission deadline is running out unnoticed.

Delay and disruption evidence against contractual entitlement

Delay claims are lost on evidence far more often than on principle. The entitlement exists, but the records do not support it, or not in a form anyone can assemble eighteen months later.

Here the agent works backwards from the contract. It reads the delay clauses to establish which events give time only, which give time and money, and what you have to demonstrate. Then it assembles, per event, a chronology: the trigger, the notice issued and its date against the deadline, the affected activities in the programme, the site records covering the period, the correspondence in which the other side acknowledged or disputed the position, and the resource records supporting any disruption argument. Gaps are stated as gaps. If the daily records for a claimed period are missing, that appears in the pack, because a claims consultant who discovers it later has already lost weeks.

Payment terms, applications and pay less notices

Payment is the most date-driven part of a construction contract and the most mechanical, which makes it well suited to an agent. The agent extracts the payment framework for each contract: due dates, the basis for calculating them, the final date for payment, the period for the payment notice, the deadline for a notice of intention to pay less and what it must contain.

It then runs the calendar in both directions. Upstream, it alerts the commercial team when an application is due, and checks that certificates and notices received arrive within the contractual period and in the required form. Downstream, it does the same for subcontractor applications, so a pay less notice is never late by accident. It reconciles applied, certified and paid amounts across the chain and reports the differences with the line items attached.

Retention, defects liability, warranties and insurance

These obligations outlive the site team, which is exactly why they are forgotten. An agent maintains a register of retention held and released, the trigger for each release, the defects liability or rectification period per package and its expiry, outstanding collateral warranties and third party rights with the beneficiaries the contract requires, and the insurance policies each party must hold, with limits, periods and evidence of renewal.

For insurance it compares the policy documents received against what the contract requires: cover type, limit of indemnity, per occurrence or aggregate, run off duration, and named or joint insured requirements. Missing or expired evidence is raised with the named owner rather than filed.

Amended standard forms against the unamended text

Most construction contracts arriving in your inbox are a standard form plus a schedule of amendments, and the amendments are where the risk lives. Reading them properly means holding the unamended clause in mind while reading a deletion, a substitution and three consequential changes elsewhere in the document.

An agent compares the incoming document against the unamended published version clause by clause and produces a complete deviation list: what was deleted, added or reworded, and, more usefully, what each deviation does to your position. A shortened notice period, a widened time bar, a deleted right to interest, a change from reasonable skill and care to fitness for purpose, a removal of the loss and expense route. Nothing is skipped because a reviewer was on the third document that day. Which deviations to push back on remains entirely a human decision, but it gets made against a complete list.

Where AI fails here

Legal advice is not on the table. Whether a clause is enforceable, whether a time bar is a condition precedent as drafted, how a court or adjudicator would construe an ambiguity, whether a prevention argument survives: these are questions for your solicitors, and an agent that answers them is producing something you cannot rely on and should not act on.

Commercial concessions stay with named people. Whether to accept a cap, trade a notice period for a better rate, or take a package on thinner terms to keep a client relationship is a business decision that depends on things no contract contains.

Anything that constitutes a contractual notice is never issued by an agent. Notices under a building contract have legal effect. They can start clocks, preserve or destroy entitlement, and be scrutinised line by line in adjudication years later. The agent drafts, cites the clause, calculates the deadline and puts it in front of the person authorised to issue it. That person sends it. This is a deliberate refusal, not a technical limit.

Two practical failures are worth naming. Handwritten site records, scanned drawings and photographed allocation sheets extract less reliably than clean digital records, so accuracy on those inputs is measured separately and reported honestly. And an obligations register built from a superseded document is worse than none at all, so it has to be rebuilt whenever a supplemental agreement, deed of variation or revised programme lands. Both are why Adopt AI Partners publishes an accuracy number measured on your own contested documents rather than a demonstration set, and stays until your commercial team owns the system.

If contract review on live projects is the thing your team never gets to until it is already late, write to hello@adoptaipartners.com.