What is NRSWA compliance software?

NRSWA compliance software is software that helps UK utility contractors meet their obligations under the New Roads and Street Works Act 1991 and the associated Codes of Practice.

That definition is correct, useful, and tells you almost nothing about what good NRSWA compliance software actually has to do. The Act is dense. The Codes of Practice are denser. And the gap between "records permits" and "genuinely helps a contractor stay compliant" is enormous.

This post walks through what NRSWA compliance software actually needs to handle, in plain English — and why most of the tools sold under that banner fall well short.

 

What NRSWA actually requires

In broad terms, NRSWA covers:

•       Permits — every piece of street works needs a permit issued by the relevant Street Works Authority before work begins. Permit conditions specify timing, location, traffic management, reinstatement standards, and more.

•       Notices — different notice periods apply depending on the type of work (immediate, urgent, major). Getting the notice type wrong is a fineable offence.

•       Coordination — contractors must coordinate with each other to avoid clashes. The Streetworks Register is the central source of truth.

•       Inspections — Section 50 inspections, joint inspections, and post-reinstatement inspections all have their own evidence requirements.

•       Reinstatement standards — the Specification for the Reinstatement of Openings in Highways (SROH) specifies what good looks like. Failures cost money and can require redoing the work.

•       Training and qualifications — operatives and supervisors must hold valid NRSWA cards for the work they're doing. Cards expire.

•       Audit trail — Street Works Authorities, asset owners, and regulators may all request evidence at any time.

 

That's the high-level. The details — for anyone who has actually filled in a Section 50 form on a wet site — are where the real complexity lives.

 

What NRSWA compliance software has to do

Software that genuinely helps a contractor with NRSWA needs to handle, at minimum:

Permit management

Track the live status of every permit across every active scheme. Show when permits are about to expire, when extensions are needed, and when the work window is closing. Push notifications to the right people before, not after, a problem develops.

 

Pre-condition checks

Before crews are deployed, check nearby external street works — permits, closures, urgent works — to identify clashes and conflicts. Record the check itself as audit-ready evidence of due diligence. This is one of the most powerful compliance tools available, and most software ignores it entirely.

 

Section 50 workflows

Section 50 inspections require specific evidence — photos, dimensions, materials, sign-offs. The software should structure this capture so an operative on site can complete it correctly without remembering to do so.

 

Plant-to-person and training compliance

Match operatives to work based on the NRSWA cards they hold and their expiry dates. Block assignments where required training is missing or expired. Surface this to schedulers before crews leave the yard, not after a card is checked at a toolbox talk.

 

Defect tracking and reinstatement evidence

Photographic evidence at every stage — pre-work, during work, post-reinstatement. Linked to the permit, the site, the operatives, the time. Defensible months or years later.

 

Traffic management plans

Real plans, drawn against real road layouts, with signage and TM compliance built in. Not a PDF uploaded as evidence after the fact.

 

Audit trail integrity

Every change recorded with user, time, old and new values. Immutable during the contract. Exportable to regulators, asset owners, or internal audit on demand.

 

What "NRSWA software" usually means in practice

Most field service software sold to UK utility contractors handles a subset of the above and labels itself "NRSWA-aware". In practice this often means:

•       A field to enter the permit number, with no validation against the actual Street Works Register.

•       A form to upload photos, with no structured capture of what photos are required.

•       A training records table, with no enforcement when a scheduler assigns someone whose card has expired.

•       An audit trail of timestamps, with no protection against editing after the fact.

 

This is better than nothing. It is not what genuinely compliant operations need.

 

What good NRSWA software looks like

Genuine NRSWA compliance software has three properties that distinguish it from "NRSWA-aware":

•       Compliance is enforced at the point of work, not just recorded after the fact. The system blocks assignments that would breach NRSWA. The system requires evidence before allowing work to proceed.

•       Real data integration with external sources. Streetworks register data, asset owner systems, training certification authorities. Not just internal records that can fall out of sync with reality.

•       Audit-defensible. An immutable audit trail with full history. Exportable. Backed by the contractual and operational commitments needed for a regulator's enquiry.

 

Building software that meets that standard is hard. It requires understanding NRSWA in depth, knowing how the work actually happens on site, and engineering systems that hold up under scrutiny.

It's what UtilityWorkx was built to do. Native streetworks coverage, pre-condition intelligence, plant-to-person enforcement, immutable audit ledger, NRSWA-aware training matrix. Built by people who've been on the receiving end of NRSWA audits.

If your current software treats NRSWA as a label rather than a serious operational concern — and if you're tired of audit findings that should never have happened — UtilityWorkx is taking on a small number of founding customers ahead of broader release.