The three AI solutions every UK construction business needs right now
Three automations, sitting on top of the systems you already own: an AI site record, ISO 19650 compliance enforcement, and a private assistant over your own documents. No new software for your teams and no training days, because all three run on Microsoft 365, SharePoint, Outlook and WhatsApp.
Construction has a documentation problem and it presents identically in almost every business. Records scattered across personal devices. Compliance handled manually until the naming convention decays. Knowledge living in individual heads and inboxes, walking out of the door when someone leaves.
The stakes changed with the Building Safety Act 2022 and the dutyholder and competence regime in the Building Regulations etc. (Amendment) (England) Regulations 2023, which put information duties on ordinary building work rather than only on tall towers. Records were always a commercial risk. On in-scope work they are now a regulatory one too.
What are the three, and what does each one fix?
| What it does | The problem it removes | Where the value lands | |
|---|---|---|---|
| 1. AI site record | Transcribes voice notes, tags photos, logs group messages and emails against the project | Evidence stranded on personal phones | Contemporaneous records that hold up when money is on the table |
| 2. ISO 19650 automation | Enforces naming, metadata and classification on upload, generates the audit trail | The convention decaying weeks after mobilisation | Compliance that survives the whole project, not just mobilisation |
| 3. Private document assistant | Answers plain-language questions from your own documents, with sources | Hours spent searching for what you already have | Institutional memory that stays when people leave |
1. What does an AI site record actually do?
It turns what your teams already produce into a structured record without asking them to do anything differently.
Voice notes transcribed and summarised. Photos tagged, timestamped and filed. Group messages monitored and logged against the project. Emails linked into the record by project code. The output is a contemporaneous, ISO 19650-aligned project record with browser access and instant site reports.
The commercial argument is blunt: in disputes and adjudications the party with the better contemporaneous records is in the stronger position, and the arguments that cost real money never start big. It needs no training, because teams keep using WhatsApp, Outlook and their camera. The organising is the part that gets automated.
2. Why automate ISO 19650 compliance rather than train for it?
Because training is the thing that decays and enforcement is not.
Information management compliance is a contractual requirement on virtually every Tier 1 and Tier 2 project, and non-compliance quietly weakens your position in final account negotiations. Automation handles the parts humans reliably get wrong: naming to the convention on every upload, metadata validation, classification and folder structure enforcement, an audit trail generated as you go, and close-out reports on demand.
Every contractor already has a naming standard. What they do not have is a mechanism that holds it when the supply chain is busy, which is a different problem with a different solution.
3. What does a private assistant over your own documents change?
It turns the project record from a filing system into something you can question.
What curtain wall system is specified? What was the agreed cladding programme? What did the design team confirm about the parapet detail in July? Show me every RFI on the roof package. Plain-language questions answered from your own documents with the source referenced, so an answer can be checked rather than trusted.
Done properly this is fully private and your data never touches a public model, which is the distinction that decides whether it is usable at all.
How much time does this actually give back?
Honestly, it varies enormously with the state of your data, and any vendor quoting you a single percentage has not looked at your SharePoint.
What can be said from our own delivery rather than from a benchmark: the largest and most consistent returns show up in site management admin, in coordinator and project management time spent on document housekeeping, and in retrieval, where the saving is the difference between finding something in seconds and spending an afternoon on it. A business with a clean CDE gets a materially different result from one with ten years of unstructured folders.
Rather than take a number on trust, count the copying on your own office floor and price it at your own loaded rates.
Why do the three work better together?
Because they are really one pipeline rather than three products: capture everything as it happens, keep it compliant automatically, and make it answerable on demand.
Each is useful alone. Together, the second cleans what the first captures and the third is only as good as what the other two produced. That is what practical AI in construction looks like: not a platform, but a layer of advantage on what you already own.