Construction management software features, in plain English

A plain-English guide to what construction management software features actually do on a UK site, and which ones earn their keep once the team is trained.

The short version

Vendor feature lists are written to win a demo, not to run a Tuesday on site. Every platform advertises a long grid of modules, and most of that grid is noise until you know which features touch your day and which sit unused. This is a plain walk through the features that matter on a UK site, what each one actually does, and the one condition that decides whether any of them pay for themselves.

SiteTech Coach is independent. It teaches how the software is used and is not the vendor. It is not affiliated with, endorsed by, or sponsored by Trimble, Viewpoint, or Field View. Product names are used descriptively only.

Why the feature list confuses people

A pricing page lists thirty features because the buyer scanning it wants to feel covered. On site, a supervisor uses maybe six of them every day and never opens the rest. The gap between the grid and the daily reality is where money gets wasted: firms pay for a tier full of modules they never adopt, then blame the tool when records stay thin.

The honest way to read any feature list is to sort it into three buckets: features your team will use every day, features you will use occasionally at handover or audit, and features that sound impressive but will never be opened. The daily bucket is small. Get those right and the software works. Ignore them and no amount of the other two will save the rollout.

The features that earn their keep

Site diary and daily logs

The daily site diary is the backbone. It records who was on site, what was done, weather, deliveries, and delays, timestamped and in one place. Done well it replaces the paper book that lives in a van and gets water-damaged, and it becomes the first thing anyone reaches for in a delay dispute. If a platform gets the diary wrong, nothing else matters, because this is the record you lean on months later. For the detail on this one, read keep a site diary that protects you.

Inspections, snagging and quality records

This is the feature that turns a walk round the site into a defensible record. You issue an inspection, attach photos, assign a defect to a subcontractor, and track it to close. The value is not the checklist, it is the audit trail: a closed item with a before photo, an after photo, a timestamp and an owner. That chain is what wins a quality dispute and what a client wants to see at handover.

Photo evidence with metadata

A photo on its own proves little. A photo attached to the right record, with a timestamp and a location, proves a great deal. The feature to look for is not a camera, every phone has one, it is how tightly the photo binds to the record and how hard it is to lose. Thin photo discipline is the single most common reason a strong case falls apart later.

RAMS, permits and safety records

Risk assessments, method statements and permits to work are legal weight, not paperwork. The feature that matters is version control and a clear record of who signed what and when. When an inspector or a client asks for the current RAMS, you want one tap, not a search through email. See the RAMS template explainer for how this fits a real site.

Document control

Drawings, specifications and revisions change constantly, and the expensive mistake is a subcontractor building to a superseded drawing. Good document control means the current version is the one everyone sees and the old one is unmistakably marked as old. This is an occasional-use feature that prevents a very costly error, so it belongs in the middle bucket, valuable but not daily.

Reporting and the audit trail

Reporting is where the daily records pay you back. A weekly progress report, an open-defects list, a records-completeness view: these turn the data your team entered into something a client, a director or an insurer will read. The feature only works if the daily entry underneath it is honest, which brings us to the part no feature grid mentions.

The feature that is not on the list

None of the above matters if the team does not use it. The most complete platform on the market produces nothing but empty fields if the site team was shown it once in an induction and left to it. Adoption is the hidden feature, and it is the one the vendor cannot sell you, because it is not in the software. It is in how the software is taught and turned into a daily habit.

This is the honest test to apply to any feature during a demo: not "can it do this?" but "will my team actually do this, every day, without being chased?" A modest tool the crew uses beats a powerful one they avoid. If you want the numbers behind that trade-off, read what construction management software actually costs in 2026, because the licence is the small part of the cost and the learning curve is the large part.

What good looks like

A site manager should be able to open the tool at 14:00, see today's open inspections in a couple of seconds, tap one, take the photos, assign it to a subcontractor, and be back on site inside two minutes, with the RAMS one tap away if anyone asks. The feature set that supports exactly that, and no more theatre, is the right feature set for a site. Everything beyond it is a nice line on a pricing page.

What to do next

Sort your platform's feature list into the three buckets and be ruthless about the daily one. Then make sure the team can actually run those daily features without thinking, because that is the only thing that converts a feature list into a return. The fastest way to get there is short, task-shaped training delivered at the point of use, which is exactly the format the SiteTech Coach training library is built in. Team and per-seat options are on the pricing page.