Why Your Site Managers Hate New Software (And How to Fix It)

Published 28 May 2026 | 8 min read | SiteTech Coach

The short version

Site managers do not resist software because they are stuck in the past. They resist it because the rollout ignored how construction sites actually work. Fix the rollout, and the resistance disappears.

Why this matters now

Every construction firm in the UK is pushing digital adoption. Head office buys the software, sends an email, books a training session, and expects the site to fall in line. Six weeks later, half the team is back on paper and the project director is asking why the investment is not paying off.

The blame usually lands on the site managers. "They are resistant to change." "They are old school." "They just need to get with the programme."

That is almost never the real problem. The real problem is that the rollout was designed by someone who has not stood on a live site in years. Here is what is actually going on.

Reason 1: It adds time to their day without removing anything

A site manager's day is already full. Morning briefings, walkrounds, subcontractor coordination, delivery management, quality checks, safety checks, client visits, progress reporting. There is no slack in the schedule.

When new software arrives, it is positioned as "an addition." Log your diary digitally AND do your walkround. Take photos on the app AND brief the team. Complete the digital permit AND manage the actual work.

Nobody removed anything from the workload. The software was layered on top of an already packed day. Of course they resist it.

The fix: identify what the software replaces, and remove the old task completely. If daily diaries are going digital, the paper diary is gone. If photo records go through the app, emailing photos stops. The new tool has to replace something, not sit alongside everything.

Reason 2: The training did not match how they learn

Most people on construction sites learn by doing. They pick up a tool, try it, get it wrong, try again, and then it clicks. That is how they learned to read drawings. That is how they learned to manage a pour. That is how they will learn software.

Instead, they get a 90-minute presentation in a portakabin with 25 slides and a login link emailed afterwards. That is how office staff learn. It is not how site staff learn.

The fix: task-based training with real project data. Day one: log in and take a photo. Day two: complete a diary entry. Day three: log a snag. Short, practical, on their own device. Five minutes, not ninety.

Reason 3: The software was not tested on a real site first

Head office demos the software in a meeting room with full Wi-Fi, a laptop plugged into a projector, and clean test data. Everything works perfectly. Then the site manager tries to use it standing in the rain, wearing gloves, on a phone with a cracked screen and no signal.

The buttons are too small. The upload fails. The form times out. The app crashes when they try to add a photo. The experience is completely different from the demo.

The fix: test the software on site before you roll it out. Not a demo. An actual field test. Can someone complete a snag record while standing in a stairwell with one bar of signal? If not, either fix the setup or pick different software.

Reason 4: Nobody told them why it matters to them

Site managers hear "we need better data" and "the client wants digital records" and "head office requires it." None of those reasons are about the site manager's own problems.

What they actually care about: getting home on time, not spending evenings fixing incomplete records, being able to prove what happened when a dispute comes up, and not looking incompetent in front of their team.

The fix: frame the software around what it does for them personally. "This means you stop spending Friday afternoons re-doing the site diary." "This means when the subcontractor disputes the snag, you have a timestamped photo on record." "This means your progress report writes itself from the data you have already entered."

Reason 5: They have been burned before

This is rarely their first software rollout. Many site managers have been through three or four platform changes in the last five years. Each time, they invested effort learning the system. Each time, the company switched to something else 18 months later.

Why would they invest effort again? From their perspective, the pattern is clear: learn it, use it, company changes its mind, start again.

The fix: be honest about this. Acknowledge that previous rollouts have not stuck. Explain what is different this time. And most importantly, show commitment by removing the old system completely. If paper is still available, they will assume this software is temporary too.

Reason 6: The people pushing it do not use it themselves

The project director mandates the software but still asks for email updates. The contracts manager requests data from the system but never logs in. Head office tracks "adoption metrics" but has never completed a single snag record.

Site teams notice this instantly. If the people above them are not using the tool, why should they?

The fix: leadership has to use the system visibly. The project director reviews the digital dashboard in progress meetings instead of asking for a separate PowerPoint. The QA manager raises snags through the app, not by email. Adoption is not a site-level problem. It is a project-level behaviour.

Reason 7: There is no support when things go wrong

The training happens on Monday. The trainer leaves on Tuesday. On Wednesday, someone's data does not sync and nobody knows who to call. The IT helpdesk does not understand construction workflows. The software vendor's support line has a two-hour wait. The site manager ends up spending their own time troubleshooting something they never asked for in the first place.

The fix: assign an on-site floor walker for the first two weeks. Someone who already knows the software and can answer questions quickly. Most problems take 30 seconds to solve. But if nobody is available to solve them, people give up.

What good looks like

When a rollout is done properly, site managers do not hate the software. They barely think about it. It becomes part of their day, the same way checking drawings or doing a walkround is part of their day. The goal is not enthusiasm. The goal is habit.

That happens when the software replaces something instead of adding to it, when training matches how site teams learn, when leadership uses the system themselves, and when support is available in the first two weeks.

What to do next

If you are planning a software rollout and want it to actually stick, start by reading the reasons above through the eyes of your site managers. Which of these apply to your situation? Fix those first, and adoption follows.

Get your team trained without the classroom sessions

SiteTech Coach delivers construction software training in short, practical lessons that site teams complete on their phone or tablet. No 90-minute sessions. No death by PowerPoint. Just clear steps your team can follow at their own pace.

Start with the free lessons