Utility strikes don’t usually happen because a crew “wasn’t careful”. They happen because information is partial, out of date, hard to access in the field, or disconnected from the way work is actually planned and delivered. With programme pressure, shifting traffic management windows and multiple subcontractors rotating through the same corridor, it only takes one missed handover or one misread plan for a shovel to find something it shouldn’t.
From 2025, NUAR (the National Underground Asset Register) going live nationwide changes the baseline. It won’t remove the need for ground investigation, permit control or safe digging, but it does change how quickly teams can get a joined-up view of mapped underground assets and bring that into the tools they already use: GIS in planning, BIM in design coordination, and on-site detection at the face.
Key concepts in plain English
NUAR is best thought of as a national way of accessing underground asset data in a more consistent, shareable form. Rather than chasing multiple utility responses, formats and drawing standards, the intent is that authorised users can view combined asset information through a single service and use it to inform design, planning and safe excavation.
GIS (Geographic Information Systems) is the “map view” of your project world: streets, parcels, constraints, asset corridors and layers of spatial data. It’s how many local authorities, utilities and highways teams manage networks and plan interventions.
BIM (Building Information Modelling) is the “model view” of your project: coordinated design information, geometry, attributes, and—when managed well—clear assumptions and tolerances. For linear infrastructure, BIM often becomes the common coordination space between highways, drainage, structures and M&E designers.
On-site detection is everything from CAT and Genny and electromagnetic locating to GPR and vacuum excavation where required. Detection tells you what’s likely in the ground today, at the location you’re about to break, and it’s still essential even when mapping looks good.
The important point: NUAR is a data access improvement, not a magic truth machine. You’ll still need to manage uncertainty, depth accuracy, legacy records and changes made in the ground that aren’t reflected in any map.
How it works in practice
The value comes when NUAR is treated as part of an end-to-end “information to action” workflow. In practical UK delivery terms, that means:
– Early optioneering and route selection (GIS): Planners and designers can screen constraints earlier, test diversions and understand where utility density is highest. It helps avoid late redesign when you discover you’re trying to thread a route through a congested corridor.
– Design coordination and clash thinking (BIM): NUAR-fed asset layers can inform design risk reviews and temporary works thinking. Even if you can’t rely on exact depths, the model can flag “high consequence zones” that need trial holes, protective slabs, revised sequencing or a change in method.
– Site set-out and permits (field workflow): Supervisors can use the same “single view” to brief crews, define exclusion zones and decide where to prove by hand dig, scan or pothole. The goal is consistency: fewer situations where the office has one picture and the gang has another.
– Evidence and assurance: Better traceability of what information was available, what was reviewed, and what controls were put in place supports investigations and client assurance—particularly on busy highway schemes where multiple parties share the same workbank.
Integration matters more than access. If NUAR sits in a separate portal that the delivery team checks once, prints, and never revisits, you’ve gained little. If it feeds your GIS layers, informs BIM coordination, and is referenced in RAMS, permits and briefings, you start to change behaviour.
Pitfalls and fixes
# Common mistakes
1) Treating NUAR output as “the record” rather than “a source”. Teams can over-trust a clean map view and under-invest in proving, especially when the programme is tight.
2) Leaving integration to the last minute. If GIS/BIM teams can’t consume NUAR data in the formats and coordinate systems they use, site ends up with PDFs and screenshots again.
3) Ignoring ownership and update discipline. Someone needs to own “what changed since last issue” and make sure revised information reaches the permit issuer and the supervisor, not just the designer.
4) Failing to connect detection results back to information management. Trial hole findings often live in notebooks or photos on phones; without structured capture, the next crew repeats the same uncertainty.
Fixes are mostly operational: set clear rules for when NUAR is checked, how it’s incorporated into design and permits, and how uncertainty is communicated. Make “what we don’t know” visible, not buried.
A short UK scenario: where it helps (and where it doesn’t)
A principal contractor is delivering a package of footway widening and drainage upgrades on an A-road through a Midlands town centre. The job is night-shift heavy, with traffic management windows that move week to week and a utilities presence that’s intermittent. Using NUAR early, the planner flags two junctions with dense telecoms and LV cables and shifts the drainage outfall location to reduce crossings. In design coordination, the BIM lead marks a “high consequence” zone and schedules trial holes before kerb line excavation starts. On site, the supervisor uses the same mapped view to brief the gang, but the CAT scan starts showing a signal running outside the mapped corridor. They stop, pothole, and find a legacy service that isn’t where any record says it is. The method changes: hand dig only within a defined box and the programme absorbs a small hit, but the job avoids a strike and a bigger shutdown.
The lesson is straightforward: NUAR improves the starting picture and reduces blind spots, but you still need permissions, proving, and a culture that allows a stop when reality doesn’t match the map.
The 7-day check
# What to do in the next 7 days
1) Map your current “utility information” workflow from enquiry to permit to excavation, and identify where NUAR output would replace or supplement existing steps.
2) Agree a single “source of truth” location where the latest NUAR-derived layers/exports are stored and version-controlled for the project.
3) Set a rule for supervisors: when NUAR must be re-checked (e.g., design change, change of phase, new excavation permit, or after a utility visit).
4) Update RAMS and permit templates to include an explicit “mapped vs detected” reconciliation step before breaking ground.
5) Start capturing trial hole and detection findings in a structured way (location, date, photo, sketch, depth confidence) so the information feeds back into planning.
Checklist: integrating NUAR with GIS, BIM and site detection
– Confirm coordinate reference systems and location accuracy assumptions before importing NUAR layers into GIS/BIM.
– Define an “uncertainty band” approach (what tolerance you assume, where you require proving, and how you mark confidence).
– Make NUAR review a named activity in the permit-to-dig process, with sign-off by the supervisor or permit issuer.
– Plan detection and trial holes as a programmed enabling activity, not a reactive task done with a shovel waiting.
– Record and share deviations found on site so subsequent shifts and subcontractors don’t repeat the same risk.
– Agree how design changes triggered by utility density or conflicts are governed and communicated to the site team.
What to watch
The UK market impact won’t come from the existence of NUAR alone, but from how clients, designers and contractors embed it into assurance and delivery. Watch for procurement documents that start asking for evidence of data integration, not just “utility searches completed”, and for site standards that require clearer proof of the mapped-to-detected reconciliation.
Three questions to take into the next project meeting are these: Where does NUAR sit in our permit-to-dig controls, who owns updates, and how are trial hole findings fed back into the design and plan? If you can answer those cleanly, you’re far closer to fewer strikes than any new portal will ever deliver.
