Do we need an AI policy?

You need a short, readable one covering information handling and the judgement boundary. A twenty-page policy nobody reads is worse than a one-page rule everyone follows.

How long does team training take?

A focused half-day on live work changes more than a series of generic sessions, provided the shared workflows exist before the session rather than after it.

What if part of the team is resistant?

Resistance in construction is usually well-founded scepticism about tools that add admin. Start with a task that removes work rather than adding a system, and the argument resolves itself.

Adoption · 6 min read

Why AI stalls in property and construction teams — and what fixes it

The tools are rarely the problem. Unclear boundaries and no shared standard are.

Published 19 August 2026

A typical pattern: two people in the business become quietly brilliant with AI, everyone else uses it occasionally for emails, and nobody knows what is or is not allowed with client or site information.

That is not an adoption problem to solve with more licences. It is a standards problem.

The three things teams need agreed

Adoption becomes straightforward once these are written down and understood by everyone, including the people who will not use AI daily.

The judgement boundary: which tasks always end with a qualified human, and which do not
The information rule: what may be put into which tool, and what never leaves the business
The evidence habit: what gets recorded when an AI output influences a decision

Shared prompts beat individual skill

Individual prompting skill does not scale and leaves with the person. A small library of agreed, tested workflows for the tasks the business repeats — site briefs, quote comparisons, weekly reports — makes quality consistent and onboarding trivial.

Train on live work, not examples

Workshops that use invented scenarios do not change Monday. Sessions built on the team's own live site, live tender and live report land differently, because people leave with something finished rather than something understood.

Measure adoption honestly

Track whether the workflow is used on the next three real jobs. That is the only metric that predicts whether the change survives — usage of a tool tells you nothing about whether the work improved.

FAQ

Common questions

Do we need an AI policy?: You need a short, readable one covering information handling and the judgement boundary. A twenty-page policy nobody reads is worse than a one-page rule everyone follows.
How long does team training take?: A focused half-day on live work changes more than a series of generic sessions, provided the shared workflows exist before the session rather than after it.
What if part of the team is resistant?: Resistance in construction is usually well-founded scepticism about tools that add admin. Start with a task that removes work rather than adding a system, and the argument resolves itself.

Keep reading

Related notes

Project controls when the record lives in WhatsApp
The decision trail on most SME projects is scattered across six tools and one person's memory. That is the risk worth fixing first.
AI for UK property developers: what actually works in practice
A grounded look at where AI earns its place in a UK development workflow — and the tasks it should never touch.

Discuss your workflow See all services