A fourteen part syllabus on AI for UK construction
Most writing about AI in construction is either a vendor pitch or a warning. This is neither. It is a course, with a sequence, an evidence base, and an assessment at the end of every part.
Why does construction need a syllabus rather than another opinion piece?
Because the industry has moved past the stage where the interesting question is whether AI can read a subcontract. It can. The interesting questions now are who signs the assessment it produced, what happens when it worked from a superseded revision, and how a firm proves any of that eighteen months later in an adjudication.
Those are governance and competence questions, and they are answerable. They are also cumulative: you cannot sensibly classify AI use by consequence until you know where it is being used, and you cannot design human oversight until you have classified it. A sequence of essays published in whatever order they were written does not teach that. A syllabus does.
The audience is deliberately wide. A graduate quantity surveyor, a site manager, a design lead, a commercial director, and an owner of a twelve person subcontracting business all have a stake in this, and each needs a different part of it most. Read out of order and each part still stands up. Read in order and the matrix in part 6 is built on the classification in part 5, which is built on the register in part 4.
What does the evidence say about where the industry actually is?
It says the gap is not between construction and technology. It is between talking about AI and doing anything durable with it. Surveyed separately, 69 per cent of project managers and 67 per cent of quantity surveying professionals expect AI to help surveyors deliver greater value. On separate evidence drawn from construction specifically, almost nobody works somewhere that has built the conditions for that to happen.
That combination is unusual and it is the reason for the sequence below. Where the constraint is enthusiasm you run a demonstration. Where the constraint is that nobody can say which decisions currently depend on a model output, a demonstration achieves nothing at all.
How is the syllabus structured?
Four modules across thirteen taught parts. The order is a dependency chain, not a preference.
| Date | Part | Module | What you get out of it |
|---|---|---|---|
| Mon 17 Aug | 1. The depth problem | Position | A defensible read on where your firm sits against published benchmarks |
| Tue 18 Aug | 2. Shadow AI | Position | Why unrecorded use is a governance failure, not a discipline one |
| Wed 19 Aug | 3. The dutyholder argument | Position | The legal reason white collar construction roles are not going away |
| Thu 20 Aug | 4. The AI register | Control | A discovery exercise you can run in four weeks |
| Fri 21 Aug | 5. Classification | Control | Green, Amber and Red judged by consequence, not by brand |
| Sat 22 Aug | 6. Human in the loop | Control | What meaningful human involvement now means in law |
| Sun 23 Aug | 7. Failure modes | Control | The eight ways construction AI actually goes wrong |
| Mon 24 Aug | 8. Project management | Practice | Compressing information assembly without touching judgement |
| Tue 25 Aug | 9. Design management | Practice | Coordination, cascade and the second order effects |
| Wed 26 Aug | 10. Commercial management | Practice | The challenge function and the evidence chain |
| Thu 27 Aug | 11. Discipline agents | Practice | Architecture that scales without watching people |
| Fri 28 Aug | 12. Measurement | Proof | Six categories that beat hours saved, and a six week cycle |
| Sat 29 Aug | 13. Competence and clients | Proof | Training, disclosure, insurance and a ninety day plan |
How should you work through it?
Read the executive summary, then the parts, then attempt the five questions before the next part arrives, and mark yourself honestly against the answers at the top of the following part. The questions are not comprehension checks. Each one has a defensible answer that the following part sets out, and several have answers that will be specific to your business rather than general.
Two habits make the difference. First, answer the questions against your own organisation rather than in the abstract: "who approves a variation over fifty thousand pounds here" is a better use of five minutes than agreeing that someone should. Second, keep a note of every place where you cannot answer. That list is the beginning of the register built in part four.
If your firm is already further along than most, the syllabus still assumes nothing. It is common to find a firm with an AI policy, no register, and no idea which of its people are pasting subcontract clauses into a consumer tool. Related reading while you wait: what a proper AI audit looks like, controlled adoption rather than blanket bans, and what a good AI pilot looks like.
What five questions should you be able to answer now?
Attempt these before tomorrow. Each has a defensible answer, and each is answered at the top of the next part.
- What proportion of UK construction businesses use any AI at all, and how does that compare with the economy as a whole?
- What is the difference between the breadth of AI adoption and its depth, and which one is construction short of?
- Which three barriers to adoption do construction professionals themselves rank highest?
- Why is enthusiasm among professionals a poor predictor of whether a firm will get value from AI?
- If a firm wanted one honest measure of how far it has actually got, what would it be?
Which sources is this part built on?
Every figure quoted above resolves to one of these. Each was checked before publication.