UK Construction Compliance Software Guide

Choosing UK Construction Compliance Software

UK construction now runs on evidence. The Building Safety Act 2022, the CDM Regulations 2015, the Construction Industry Scheme (CIS), ISO 19650 information management and the UK's legislated Net Zero commitments each demand that a contractor can prove (with dated, attributable records) what was done, by whom, and on what authority. Most construction software was designed to store documents; compliance demands a record that is built as the work happens and holds up under scrutiny years later.

This guide walks through the main UK compliance regimes and what each genuinely requires from software, then sets out an evaluation checklist for buying. Two things it deliberately does not do: it does not claim any software makes you compliant (the duties sit with dutyholders and directors, not with tools), and it does not quote vendor statistics. Regulatory facts, stated generally, are more useful than either.

Building Safety Act 2022: The Centre of Gravity

The Building Safety Act reshaped who is accountable for building work in England. Through amendments to the Building Regulations it created a dutyholder regime (clients, principal designers, principal contractors, designers and contractors) with explicit duties to plan, manage and monitor work so it complies with building regulations, and a competence requirement: anyone carrying out design or building work must have the skills, knowledge, experience and behaviours for it, and organisations must have the capability to perform their role. Those duties apply to all building work, not only tall buildings.

For higher-risk buildings (broadly, buildings at least 18 metres or seven storeys with two or more residential units) the Act adds the golden thread: a digital, accurate, accessible, structured and transferable record of the information needed to understand and manage building safety, maintained from design through occupation. It also adds the gateway regime run by the Building Safety Regulator (BSR):

1. Gateway one (planning): fire safety matters addressed at the planning application stage.
2. Gateway two (before construction): BSR approval of the full design and construction proposals before building work starts: a hard stop, not a notification.
3. Gateway three (before occupation): a completion certificate application supported by as-built evidence of what was constructed and the golden thread handed to the accountable person.

What Golden Thread Support Really Requires from Software

• Records anchored to the building: evidence organised by floor, elevation, location and element, not by folder name, so information about a specific part of the building can actually be found.
• Change control with history: who changed what, when, and under which approval, tracked from design through construction so the as-built record reflects reality.
• An audit trail that cannot be silently edited: attributable, timestamped entries that survive scrutiny in a dispute or a regulator's information request.
• Structured, transferable handover: evidence packs that can be exported in an organised form for the principal contractor, client or accountable person, not a zip file of PDFs.
• Evidence captured as work happens: photos, QA checks and sign-offs recorded at the workface with time and location, because a golden thread reconstructed at handover is a contradiction in terms.

We cover this regime in depth in our guides to Building Safety Act compliance software and golden thread software. One warning worth repeating from both: treat any product described as "BSA certified" or "BSA compliant" with suspicion. There is no such certification. Software can keep the evidence behind your duties organised and demonstrable; it does not replace your dutyholder responsibilities.

Competence Records

The competence duties make workforce records a compliance surface in their own right. Software should hold qualifications, training, certification schemes and CPD against individual people, show whether a person was eligible for a task at the time the work was done, and connect that status to the work records themselves. A training matrix in a spreadsheet answers "do we hold a certificate?"; a compliance record answers "was the person who signed off this work qualified to do so on that date?" That is the question a regulator or claimant will actually ask.

CDM Regulations 2015

CDM 2015 applies to virtually all construction work in Great Britain. Projects must be notified to HSE (form F10) where work is scheduled to last more than 30 working days with more than 20 workers on site simultaneously, or to exceed 500 person-days. Beyond notification, the practical software burden is recordkeeping: the construction phase plan, the health and safety file, risk assessments and the evidence that dutyholders cooperated and coordinated as the regulations require.

• Dutyholder clarity: who holds client, principal designer, principal contractor, designer and contractor roles on each project, and the records of appointments.
• Construction phase plan: a living document maintained through delivery, not a PDF produced once for the file.
• Health and safety file: structured compilation as work proceeds, ready for handover rather than assembled at the end.
• Inspection-ready audit trail: RAMS acceptance, inductions, and site records that can be produced quickly when HSE asks.

Construction Industry Scheme (CIS)

CIS creates tax compliance obligations for contractors paying subcontractors: verification of subcontractor status with HMRC, deduction at the correct rate (20% for registered, 30% for unregistered subcontractors, or gross payment where held), monthly CIS300 returns, and payment and deduction statements. HMRC penalties for late or incorrect returns escalate quickly, and poor records compound into disputes with subcontractors as well as with HMRC. Software should verify status, calculate deductions, separate material from labour costs, and keep the monthly submission history in one place.

BIM Standards and ISO 19650

Structured information management under ISO 19650 remains the expectation on UK public sector work and is increasingly demanded on private projects. In practice this means a common data environment with the work-in-progress, shared, published and archived states; BIM execution plans; staged information delivery against project milestones; and COBie or equivalent structured handover for facilities management. The overlap with the golden thread is deliberate and useful: an ISO 19650-shaped information process is a strong foundation for BSA evidence duties, provided the field record, what was actually built and checked, feeds it.

Environmental and Net Zero Compliance

The UK's Net Zero 2050 target and its interim carbon budgets (including a 78% reduction by 2035 against 1990 levels) are legislated, and they reach construction through procurement and planning long before any direct mandate. Public frameworks and major clients ask for carbon plans at tender; some planning authorities, notably in London, require whole-life carbon assessments on larger schemes; and the UK Net Zero Carbon Buildings Standard (pilot version published in 2024) gives the industry a common yardstick for operational and embodied carbon. The software requirement that follows is evidential: material records and quantities that support embodied-carbon assessment, supplier EPD references, and reporting that reflects what was installed rather than what was specified.

Data Protection

Compliance software itself must comply. Workforce and competence records are personal data, so UK GDPR and the Data Protection Act 2018 apply: role-based access controls, retention policies, the ability to answer subject access requests, and breach notification processes. Ask vendors where data is hosted and how access is logged; an audit trail should cover the record system itself, not only the construction work.

What to Evaluate Before You Buy

Feature lists converge; the differences that matter show up under awkward questions. When shortlisting UK construction compliance software, test these directly:

• Is evidence created as the work happens, or assembled afterwards? A compliance record built retrospectively is weaker in every forum that matters: gateway three, an HSE inspection, adjudication.
• Is every record anchored to a place in the building? Ask the vendor to retrieve the evidence for one specific location (for example, the fire-stopping records for a single riser on a named floor) and watch whether the answer arrives with location and history attached or as a file search.
• Can the audit trail be edited? If records can be changed without trace, the system produces documents, not evidence.
• Are competence records connected to work records? Two systems that must be reconciled by spreadsheet are the failure mode you are buying your way out of.
• What does export look like? Request a structured evidence pack for a sample of work before signing anything, and show it to whoever receives your handovers.
• Will the workforce use it? Field adoption decides whether the record exists at all. Pilot on a live package with a real crew before committing the business.

Finally, weigh integration honestly: connections to HMRC services for CIS, to your CDE for ISO 19650 delivery, and to payroll and accounting reduce double-keying, but no integration substitutes for a trustworthy underlying record.

EU Compliance Overlap

Many UK compliance workflows map to EU requirements on digital records and sustainability reporting. Building a single compliance workflow helps teams deliver across UK and EU portfolios.

• Align golden thread records with EU digital construction expectations
• Connect carbon reporting to sustainability assessment workflows
• Maintain audit-ready evidence across regions

Related pages: Building Safety Act compliance software, Golden thread software, Audit Ledger, EU BIM mandate guide, Golden Thread + Sustainability.