3 March 2026

What we learned training sceptical construction teams on AI

Construction people are professionally sceptical. They have watched software arrive with fanfare and die in a folder. They have sat through training days for platforms nobody uses. They can smell a salesman three rooms away. When you put AI in front of a room like that, the scepticism is not a problem to overcome. It is the most useful thing in the room.

Here is what actually works, learned the practical way.

Start with their Tuesday, not the technology

The fastest way to lose a construction audience is to open with what the technology is. Nobody in the room cares. Open with the worst recurring hour of their week instead: the Friday report, the 47 consultant comments, the RAMS pack that needs briefing to the site team, the meeting minutes owed since Monday.

Then do that task, live, with their material. Not a polished demo file, their actual tender, their actual minutes, warts and all. The moment a site manager watches his own rambling voice note become a clean, structured diary entry, the conversation changes from whether to how.

Let it fail in front of them

This is the counterintuitive one. The most persuasive part of any session we run is when the tool gets something wrong, and we point at it.

Sceptics do not trust a tool that claims to be perfect, because nothing in their world is. Show them a confident wrong answer, show them how a reviewer catches it, and you have taught the two most important lessons at once: this is genuinely useful, and it still needs you. That pairing is exactly right, and construction professionals grasp it instantly because it is how they already treat a keen graduate: valuable output, checked before it goes out the door.

The trust that survives seeing a failure is the only kind that lasts past the first week.

Respect the guardrail questions

Someone will ask about confidentiality. Someone will ask who is liable when it is wrong. Someone will mutter about jobs. These are not resistance; they are the professional instincts that keep buildings standing, and they deserve straight answers.

What goes in which tools, and what never does. Who signs off what, and why a named person always stays responsible. And honestly, what this means for roles: the tasks being removed are the ones this room complains about at every appraisal. In our experience, the person most relieved by automation is the one currently drowning in the admin.

Make the first fortnight frictionless

The session is the easy part. Adoption is decided in the two weeks after, and it is decided by friction. Each person leaves with two or three specific uses for their own role, set up and working, not a list of possibilities. There is one named human they can ask daft questions without an audience. And someone collects the early wins and circulates them, because a QS hearing that another QS saved four hours lands harder than anything a trainer says.

Then measure it a month later. Who is still using it, on what, saving how long. If the answer is nobody, the training failed, whatever the feedback forms said.

The room you want

The goal was never a room of enthusiasts. Enthusiasm fades. The goal is a room of professionals who treat AI the way they treat any other tool of the trade: knowing what it is for, what it is not for, and how to check its work.

Scepticism, taken seriously, converts into exactly that. Which is why we would rather train a hostile room of thirty-year site veterans than a friendly room of people who will agree with anything. The veterans, once convinced, stay convinced, and they take the rest of the site with them.