Construction Software Adoption: How UK Site Teams Make It Stick

Most software rollouts fail because they demand new habits from stretched teams. Discover the UK evidence on adoption and a step-by-step plan to make digital tools stick.

By James Shorter ·

Construction Software Adoption: How UK Site Teams Make It Stick

Site team records a visible plastering snag

Software gets adopted on site when it asks the team to change almost nothing. Most rollouts fail because the tool demands a new habit from people who are already stretched. The fix is a tool that works like the chat your team already uses, with one record per job underneath, and a rollout that starts small. That is how we built BRCKS, and it is the approach this guide follows: what the UK evidence says, why adoption stalls, what it costs, and a step-by-step rollout for a builder or small contractor.

BRCKS
Make Site Software Easier to Adopt
BRCKS works like a simple chat, turning job updates into snags, orders, site visits and checklist items in one record per job.
Visit

TL;DR

  • UK adoption is uneven: plenty of firms use cloud tools, but few use digital tools on every project, and paper and spreadsheets remain common.
  • The main barrier is commitment and willingness to change, not the software itself or the training.
  • Pick a tool your site team can use on day one. If it feels like a second job, it will be dropped.
  • Start with one job, one lead and two or three habits. Bring subcontractors and clients in without making them install anything.
  • Judge success by what stops happening: chasing photos, re-typing notes, arguing over who agreed a variation.

Table of Contents

Where UK construction software adoption stands

The headline picture is mixed. Cloud tools are widespread, but joined-up use is not.

The RICS Digitalisation in construction report 2024 found that only 12% of respondents used digital tools on all projects. 43% used no digital technologies on any project across the six functional areas it measured, up from 40% in 2021. RICS describes the progress as slow and stagnating. The survey ran in Q4 2023, so it is a snapshot, but the direction matters.

The NBS Digital Construction Report 2025, based on 559 construction professionals, found 86.3% using cloud-based solutions, up from 80% in 2023. So the cloud is normal. What is missing is the habit of using it consistently on every job.

The paper problem shows up in a Bluebeam survey reported by Construction Briefing. 84% of UK firms planned to increase technology spending, yet 89% had not reached full digital integration. 53% still used paper in design, 49% in planning, and 43% relied on physical signatures and approvals.

A July 2026 Construction Management survey puts it more bluntly. 83% of firms still used spreadsheets as a primary data-analysis tool, 76% said departments worked from different systems, and only 15% worked from a unified system. Firms are collecting plenty of information. They are not keeping it in one place.

Survey figures on construction data systems

For a builder with five to fifty people, this translates into something familiar: photos in one phone, a snag list in a notebook, a variation agreed in a voice note, drawings in someone’s email. Adoption is not about buying software. It is about getting everyone to use the same record.

Why adoption stalls on site

The GIRI report on digital technology on site is useful here. It identified organisational commitment as the main barrier to adopting technology, with employee resistance close behind. Training and software-installation resources ranked as lesser barriers. Its authors conclude that without company commitment and willingness to adapt, project teams will never see the benefits.

That matches what most site managers will tell you. The software rarely fails on features. It fails on four things.

It adds work instead of removing it

A site manager who has to write up the day at night, in a system, on top of the real day, will stop doing it by week three. If the tool needs a separate login, a form and a desktop to do something that a photo and a message did before, the team goes back to the group chat.

Nobody owns it

When the owner buys it and no one on the job is responsible for how it is used, the first busy fortnight kills it. Commitment has to show up as a named person and a clear rule, not a launch email.

Subbies and clients are left out

Your electrician, plumber or plasterer does not want another account. If the tool only works when every subcontractor signs up, half the job stays outside it and the record is incomplete again. Clients are the same: they want to see progress and approve things, not learn a platform.

The tool is built for a different kind of firm

Software designed for large contractors assumes a back office, dedicated document controllers and a standard process on every job. A residential builder running six jobs with a handful of trades has none of that. Heavy systems get bought, half configured and then ignored.

What a tool needs to get used

From those barriers, a simple test follows. Before you commit to any construction software, ask these questions.

  1. Can the site team use it without training? If the main screen is a chat, they already know how.
  2. Does it capture things as they happen? A snag, an order or a site visit should be created from the moment it is mentioned, not retyped later.
  3. Does it keep one record per job? Photos, actions, files and decisions should sit against the job, not scattered across phones.
  4. Can subcontractors and clients take part without installing anything? Otherwise you are back to chasing.
  5. Does it leave an audit trail? Variations and RFIs need a dated record of who asked, who agreed and what changed. If you want the reasoning behind this, our piece on why digital workflows matter in construction projects goes further.
  6. Is the price per seat predictable? You should be able to work out the annual cost before the trial ends.

If the answer to the first two is no, the rest will not matter. This is the reasoning behind a chat-first design, which we cover in digital communication strategies for construction teams.

A rollout plan that works for a builder or small contractor

You do not need a transformation programme. You need one job, one lead and a few habits. Here is the sequence we would use.

Step 1: Pick one live job

Choose a job that is a few weeks in, with a site manager or foreman who is reasonably tech-comfortable. Do not start with your most difficult project, and do not start on day one of a new build when everything else is chaotic. The aim is a quick, visible win.

Step 2: Name one owner and write down three rules

Give one person responsibility for the rollout on that job. Then set three rules only. For example: all site photos go in the job chat, every snag is raised from the message it came from, and variations are logged before the work starts. Three rules are remembered. Fifteen are not.

This is where the firm’s commitment, the main barrier in the GIRI research, becomes practical. The boss follows the rules too, including when it is inconvenient.

Step 3: Bring in subbies and clients via WhatsApp

Do not ask them to download an app. Use a tool like BRCKS that lets them message a WhatsApp number which then routes into your job record. They carry on as they were, but you get the data in the right place.

Step 4: Review after one month

Do not judge it after a week. Habits take time. After a month, ask the site lead: is it easier to find photos? Are we arguing less about what was agreed? If yes, add the next job.

What adoption looks like when it works

When software sticks, the atmosphere on site changes. It is not about "digital transformation"; it is about less friction.

  • The "Where is that photo?" conversation disappears. Every photo is in the job record, dated and often tagged to a room or a snag.
  • Variations are captured, not remembered. When a client asks for an extra socket, it is logged and approved there and then. No more "I thought that was included" at the final invoice.
  • Handover is a button, not a week of admin. Because the record was built as the job happened, the O&M manual or the final snag list is already 90% done.
  • The office knows what is happening without calling. The director can see progress photos and snag counts from their own desk.

What construction software costs in the UK

Cost is rarely the reason a rollout fails, but it is often the reason it never starts. For a small UK builder, the market splits into three.

  1. Free/Generic tools: WhatsApp and spreadsheets. Cost: £0. Risk: Data is scattered, no audit trail, hard to search.
  2. Enterprise systems: Procore, Autodesk. Cost: Often thousands per year, sometimes tied to project value. Risk: Too complex for small teams, high training burden.
  3. Team-focused tools: BRCKS, Fieldwire. Cost: £20–£50 per seat per month. Risk: Needs a consistent habit to be worth the spend.

At BRCKS, we charge £20/month for Solo and £40/seat/month for Teams (billed annually). Subcontractors and clients are always free. For a typical project, this is a tiny fraction of the margin saved by avoiding one disputed variation or one day of re-work.

How to tell whether adoption is working

Look for these three signs after the first month.

  1. The "Silent Record": Updates are happening in the tool without the boss having to ask for them.
  2. The "WhatsApp Drop": The old, messy group chat for that job has gone quiet because the useful stuff is in the job record.
  3. The "Subbie Reply": A subcontractor has sent a photo of a completed task back through the system because it was the easiest way to show they were done.

Try it on one live job

Adoption is a choice, not a purchase. If you want to see if your team will actually use a digital record, start with one job and a tool that feels like a chat. You can start a 14-day free trial of BRCKS here. No credit card, no long sales call—just a job record that works the way your team already talks.

Our view: adoption is a design problem

We believe the reason UK construction software adoption has stagnated is not because builders are "old fashioned." It is because most software is designed for the person who buys it, not the person who uses it. If you design for the site manager first, adoption takes care of itself. That is why BRCKS looks like a chat and works on WhatsApp. It is not a new job; it is a better way to do the one you have.

FAQ

How long does it take to roll out construction software on a small team?

On one live job with a chat-style tool, the core team can be working within the first week. The habit takes longer, so plan on a month before you judge the result. Add the next job only once the first one is running without reminders.

Do my subcontractors have to download anything?

Not with BRCKS. Subcontractors and clients use BRCKS on WhatsApp, which is free, and they install nothing. Their messages and photos go into the same job record as the core team's.

How much does construction software cost for a small UK builder?

BRCKS Solo is £20/month. Teams is £40/seat/month billed annually, or £50/seat/month billed monthly. Subcontractors and clients are free, and there is a 14-day free trial. Digital tools are typically a small share of a project's budget, as the GIRI interviews showed.

What is the biggest reason software rollouts fail on site?

The GIRI research points to organisational commitment first and employee resistance second. In practice, that means no named owner, too many rules, and a tool that adds admin. Keeping the first rollout small and the tool simple addresses all three.

Should I replace the WhatsApp group straight away?

No. Keep it as the way subbies and clients talk to you, and let the job record sit underneath. Your core team works in the app, and everyone else carries on as they are.

Sources

1">Step 3: Put the core team on the app

The core site team needs the proper app on their phones. With BRCKS, that is BRCKS Chat on iPhone and Android, with BRCKS Web for the office on a bigger screen. It is the same job and the same record on both. Because the main screen works like a chat, people post updates the way they already do. One tap on a message turns it into a snag, a materials order, a booked site visit or a checklist item, and it lands in the one list for that job. That removes the evening write-up that causes most abandonment.

Step 3: Put the core team on the app

Step 4: Bring subcontractors in through WhatsApp

Subbies are best left where they are. BRCKS on WhatsApp is the free route for subcontractors and clients, who install nothing. Their updates come into the same job record as everything else. You are not asking a sparky on a ladder to learn a platform. You are asking him to carry on sending photos, and the photos end up in the right place.

If WhatsApp groups are where your jobs currently live, our page on ending WhatsApp mayhem on site explains how the two fit together.

Step 5: Run the first two weeks hard

In the first fortnight, check the job list every day. Ask the site manager what was captured and what was missed. If photos are still going to personal phones, say so and fix it. Early reinforcement matters more than any training session.

Step 6: Review, then add the next job

After a month, compare notes with the team. What stopped being chased? What is still done on paper? Then roll the same three rules onto the next job. Do not add features until the basics are second nature. Site diaries, variations and RFIs with audit trails, versioned drawings and RAMS, and the shared team calendar can follow once the habit is set.

What adoption looks like when it works

Bigger firms that report results tend to report them in hours and pounds saved on routine admin. The evidence is from large contractors, but the logic carries down to a small firm.

  • Taylor Woodrow’s workforce management system saved four hours of administration per month, worth £2,400 per project per year, according to the Digital Construction Awards 2023 shortlist.
  • A Mace commercial project reported in Building saw automated planned-versus-actual reporting save each user two to three hours a week. Mace also names fragmented workflows, version control and siloed communication as the key challenge during construction.

That last point is the one a small builder recognises. The problem is rarely a lack of data. It is that updates sit in too many places. For our own claim, we say BRCKS saves site teams 30+ minutes a day, mainly by removing the re-typing and chasing that follow a day on site.

What construction software costs in the UK

The cost question is usually asked too narrowly. The licence is a small part of what a project spends on digital tools.

In the GIRI interviews, ten of eleven interviewees estimated their project digital spend. None was below £5k and one was above £50k. A £104m project spent just 0.048% of its budget on digital tools, while a £3.5m project spent about 1.43%. Digital spend, even where firms support it, is a small fraction of project budgets.

The real cost of a failed rollout is therefore not the subscription. It is the time lost on a tool nobody uses, and the cost of the mistakes it was meant to prevent.

Our own pricing, as published on the BRCKS pricing page:

Plan Price Who it is for
Solo £20/month One person running their own jobs
Teams, billed annually £40/seat/month Core site and office team
Teams, billed monthly £50/seat/month Same, with monthly billing
Subcontractors and clients Free Invited via WhatsApp, nothing to install

You pay per seat for the core team only. Your subbies and clients cost nothing, which keeps the cost tied to the people who run the job. There is a 14-day free trial, which is enough to run steps 1 to 3 above on a live job.

When you compare quotes, work out the annual cost for your actual core team, then check whether subcontractors and clients are charged. For a firm of ten with four core users, the annual Teams total is four seats at £40 a month for twelve months, which is £1,920.

How to tell whether adoption is working

Most firms never check, and then drift back to old habits. You do not need a dashboard. After the first month on a job, look for these signs.

  • Fewer chasing messages. If you are no longer asking where a photo or a quote is, the record is doing its job.
  • Snags closed with a date. Every snag has an owner and a closing date, and the list matches the site walk.
  • Variations agreed before the work. Count how many variations were logged before the work started, compared with after. The aim is all of them before.
  • A usable diary. If a dispute arises, can you show what happened on a given day from the record alone?
  • Subbies still sending updates. If their messages continue without reminders, they have accepted the process.
  • Less evening admin. Ask the site manager how long the nightly write-up takes now.

Set a baseline before you start. Note roughly how many minutes a day the site manager spends on admin and how many variation disputes you had on the last job. After a month, ask again. The comparison tells you more than any vendor figure, including ours.

If you want a view across several jobs once the habit has spread, multi-site reporting pulls the same records into one place for the office.

Try it on one live job

If you want to run the plan above, BRCKS is built for it. It is the chat app for building sites: your team posts as they do now, one tap turns a message into a snag, order, site visit or checklist item, and everything lands in one list per job. Subcontractors and clients stay in WhatsApp for free. The core team pays £40/seat/month on annual billing, and there is a 14-day free trial. Details are on the BRCKS pricing page, and if you would rather see it first, you can book a demo. For more on how it suits smaller firms, see construction project management software for UK small builders.

BRCKS

Builders who work in residential can also read about digital tools in residential construction, and the wider case in digital solutions in UK construction.

Our view: adoption is a design problem

I started BRCKS after 20 years in construction, and the pattern never changed. A new system arrives, the office likes it, the site tolerates it for a month, then everyone is back in the WhatsApp group.

The research says the barrier is commitment and willingness to change. I would add that willingness is a function of effort. People will change if the change is small. Ask a foreman to learn a new system and you get resistance. Ask him to keep sending photos and messages, and have the system file them, and you get adoption.

That is why BRCKS works like a simple chat. One tap on a message makes it a snag, an order, a site visit or a checklist item, and it lands in one list for the job. Subbies and clients stay in WhatsApp and install nothing. Our aim is that no one writes it up at night.

My advice: start with one job, name one owner, keep the rules to three, and let the record build itself. Get the job out of the group chat.

James

FAQ

How long does it take to roll out construction software on a small team?

On one live job with a chat-style tool, the core team can be working within the first week. The habit takes longer, so plan on a month before you judge the result. Add the next job only once the first one is running without reminders.

Do my subcontractors have to download anything?

Not with BRCKS. Subcontractors and clients use BRCKS on WhatsApp, which is free, and they install nothing. Their messages and photos go into the same job record as the core team’s.

How much does construction software cost for a small UK builder?

BRCKS Solo is £20/month. Teams is £40/seat/month billed annually, or £50/seat/month billed monthly. Subcontractors and clients are free, and there is a 14-day free trial. Digital tools are typically a small share of a project’s budget, as the GIRI interviews showed.

What is the biggest reason software rollouts fail on site?

The GIRI research points to organisational commitment first and employee resistance second. In practice, that means no named owner, too many rules, and a tool that adds admin. Keeping the first rollout small and the tool simple addresses all three.

Should I replace the WhatsApp group straight away?

No. Keep it as the way subbies and clients talk to you, and let the job record sit underneath. Your core team works in the app, and everyone else carries on as they are.

Sources

Recommended


How BRCKS Can Help

Achieving long-term software adoption on site requires a balance of intuitive design and genuine utility for the teams on the ground. BRCKS is purpose-built to bridge this gap, replacing fragmented spreadsheets with a streamlined platform that site managers actually enjoy using. By simplifying daily reporting and communication, BRCKS ensures that digital transformation becomes a lasting reality rather than a temporary initiative. We invite you to discover how BRCKS can empower your workforce and bring greater clarity to your next project. Learn more at BRCKS and explore our full feature set.


Sources