AI in Construction: A Practical Guide for UK Contractors

Let's be blunt. Most of what gets called "AI in construction" right now is either basic automation dressed up in marketing language or genuinely useful tools that are narrower in scope than their vendors admit.

Actual AI in construction falls into three categories:

1. Pattern recognition on historical data. Predictive analytics that looks at past project data to forecast cost overruns, schedule slippage, or safety incidents. Balfour Beatty used this approach on civil and rail projects and reported a 20% reduction in material waste with budget accuracy hitting 94%. These tools work where you have large, consistent data sets. They struggle on novel project types.

2. Natural language processing (NLP) on documents. AI that reads contracts, site diaries, correspondence, and reports to extract structured information. This is where the genuinely new value is for commercial teams. An NLP model can read 500 site diary entries and identify which ones contain compensation event triggers under NEC4 clause 60.1. A human doing the same job takes weeks and misses roughly 40% of legitimate events.

3. Generative AI for drafting and analysis. Large language models used to draft correspondence, summarise reports, or generate first-cut analyses. Useful for productivity. Genuinely risky if you let the model draft contractual notices without a human expert reviewing them.

What AI is not doing on UK construction projects right now: autonomously managing contracts, replacing QSs, or making procurement decisions. Anyone telling you otherwise is selling something.

Understanding the mechanism matters. If you're evaluating an AI tool and the vendor can't explain this clearly, walk away.

The three-layer model

Layer 1: Data ingestion. AI needs structured input. Site diaries, allocation sheets, correspondence, and programme data all need to be in a format the model can process. This is where most implementation projects get stuck. The data exists. It's not clean or consistent.

Layer 2: Contract context. The model needs to know the contract terms to make useful judgements. For NEC4 projects, this means loading the contract data, the compensation event register, the Accepted Programme, and the key clauses that govern time and cost. A general AI tool without this context will produce generic output. A specialist tool trained on NEC4 produces actionable analysis.

Layer 3: Output and action. The AI surfaces findings. A human expert decides what to do with them. The best tools present findings with the underlying evidence, a confidence score, and a suggested action. The worst tools give you a score out of 10 with no explanation.

What good AI output looks like

That's actionable. Compare it with "potential compensation event identified in Week 11." The second is useless.

NEC4 is the dominant contract form for major UK infrastructure projects. It's used on HS2, Network Rail, National Highways, and most water company frameworks. If you're working on projects over £10M in the UK, there's a good chance you're working under NEC4.

NEC4 creates specific obligations around records, notifications, and timelines that make it an ideal environment for AI assistance. A few examples:

Clause 61.3: The eight-week time bar. The Contractor must notify a compensation event within eight weeks of becoming aware of it. Miss that window and the entitlement is gone, regardless of how legitimate the event was. AI that monitors site records in real time and flags potential CE triggers before the window closes is a genuine risk mitigation tool.

Compensation events under clause 60.1. There are 19 categories of compensation event in NEC4, ranging from physical conditions (60.1(12)) to Client instructions (60.1(1)). Each has a slightly different evidence requirement. AI trained specifically on NEC4 clause 60.1 can match site diary entries to the relevant categories with reasonable accuracy, reducing the chance of events being missed or miscategorised.

The Accepted Programme. NEC4 places more emphasis on the programme than almost any other contract form. The Accepted Programme is the baseline for both delay analysis and compensation event assessment. AI tools that track programme compliance and model the impacted programme for each CE reduce the workload considerably.

Disallowed Cost under clause 11.2(26). Poor records are one of the fastest routes to Disallowed Cost on NEC4 Option C and D contracts. If you can't prove resource was deployed as claimed, the Project Manager can disallow it. AI tools that cross-reference site diary records against cost submissions reduce this exposure.

For a deeper dive, see our NEC4 guide.

The site diary is where the commercial story of a project gets written, one entry at a time, usually by someone who has no idea that's what they're doing.

A foreman writing "access delayed 3 hours, waiting for Client's rep to clear the area" is describing a compensation event. They don't know that. The QS reviewing that diary six months later might spot it, might not. By the time it reaches final account, the window is closed.

This is the core data problem that AI addresses. The site diary contains the evidence. The evidence is unstructured, informal, and spread across hundreds of entries. AI reads it systematically, every entry, every day, looking for the patterns that indicate commercial events.

Good site diary practice and AI work together. An engineer who writes detailed, consistent records gives the AI better data to work with. The AI, in turn, can prompt engineers to capture the specific information that makes records commercially useful: the cause of a delay, the resources affected, the duration, and any verbal instructions received.

The combination reduces the risk of the most common commercial failure on UK construction projects: legitimate events that existed in the records but were never acted on.