The National Underground Asset Register is moving from pilot status to live service in parts of the UK, and it’s already changing how ground is broken on public realm, utilities, civils and housing schemes. For contractors, NUAR is not a silver bullet, but it is becoming an expected part of pre-construction planning, permit-to-dig, and clash avoidance. The short version: build NUAR into your information flow now, treat it as a decision aid not a guarantee, and make sure site teams know how to use it alongside CAT/Genny, surveys and trial holes.
TL;DR
/>
– Secure access, define who uses NUAR at each project stage, and bake it into your permit-to-dig workflow.
– Use NUAR to reduce blind spots early, then verify with PAS 128-style surveys, streetworks records and trial holes.
– Agree data responsibilities: who annotates, who stores marked-up outputs, and how they’re controlled in the CDE.
– Expect patchy coverage and variable accuracy; brief teams on confidence levels and always validate on site.
– Track integrations with GIS/BIM tools and local authority processes to avoid duplicating effort.
NUAR in plain English: what it is, and what it isn’t
/> At its core, NUAR is a shared digital map that shows where underground pipes and cables are believed to be, compiled from data supplied by asset owners. It aims to reduce service strikes, speed up planning and provide a single view rather than chasing separate utility plans. Access is via a secure portal and, in time, through integrations with common GIS and design tools.
Crucially, NUAR is not a guarantee of exact positions or depths, and it doesn’t remove the need for competent surveying, locating and safe digging. Think of it as a higher-quality “first pass” utility overview: it helps you spot conflicts, set out trial hole locations more intelligently and brief groundworkers with better context. NUAR also doesn’t replace industry guidance like HSG47 safe digging practices, or established survey specifications such as PAS 128 where clients require them. Treat NUAR as one input to your method statements and risk assessments, not the whole method.
Coverage will continue to improve as more asset owners contribute and refresh their data, but there will be gaps and legacy inaccuracies. That means contractors should plan for variable confidence levels between urban and rural areas, between older and newer networks, and between utility types. Your workflow needs to acknowledge that reality from day one.
How NUAR plays out on a live UK job
/> Picture an urban streetscape upgrade running alongside bus routes and shopfronts. The main contractor’s pre-construction manager has price pressure and night-time working windows. The utilities coordinator logs into NUAR during tender stage and sees a likely clash between new tree pits and a cluster of telecoms ducts doglegging across the footway. That triggers an early change: the landscape architect adjusts tree positions and the engineer shifts drainage gullies, all before traffic management drawings are finalised.
On site, the site agent uses NUAR overlays during the permit-to-dig briefing, passing printed extracts to the groundworks supervisor. CAT/Genny is run in daylight hours on a quiet Sunday; markings are cross-checked against NUAR and the existing utility drawings provided by each stat. Two trial holes confirm one duct run is shallower than expected, so the night team modifies the breakout sequence to prevent a strike. The client sees the avoided delay and accepts a minor redesign, rather than a week’s standstill and emergency utility call-outs.
Pitfalls and practical fixes for contractors
/> – Over-reliance on screen views. NUAR maps can look tidy on a laptop, but footway slabs rarely match the neatness. Fix: use NUAR to plan where to look, then verify with multiple locate methods and trial holes before committing to mechanised excavation.
– Poor role clarity. If everyone can see NUAR, no one owns it. Fix: nominate a NUAR lead per project who controls access, produces controlled extracts for the CDE, and records what was checked, when and by whom.
– Confusion over “latest version”. Data may update during your programme and annotated PDFs can proliferate. Fix: include NUAR extracts in your document control with clear revision stamps, and reissue at key gateways (design freeze, TM approval, start on site, phase change).
– Ignoring licensing and data-sharing terms. Lifting screenshots into public documents or passing to third parties can breach conditions. Fix: brief teams on permitted use and route all sharing through your information manager.
# Common mistakes
/>
– Treating NUAR as a full PAS 128 survey. It isn’t; you still need survey scope aligned to project risk, plus validation on site.
– Printing NUAR once at tender and never updating it. Coverage and inputs can change; refresh at each gateway.
– Delegating NUAR to a single GIS-savvy individual and keeping it siloed. Supervisors and engineers need usable extracts, not just a log-in they never use.
– Skipping the CAT/Genny because the map “looks clear”. That’s how avoidable strikes still happen under pressure.
Immediate actions to get NUAR-ready
/>
– Assign responsibility: appoint a NUAR information lead at framework and project level, with deputies for holiday and night shifts.
– Secure access early: set up organisation access, define who gets credentials, and test log-ins before the first permit-to-dig.
– Build into process: add NUAR extracts to your permit-to-dig pack alongside utility plans, RAMS, service avoidance briefings and trial hole records.
– Align with surveys: specify when a PAS 128-style survey is triggered by risk, and use NUAR to target survey effort efficiently.
– Control information: store NUAR outputs in the CDE with clear revisions; keep redlines, trial hole photos and survey reports linked to the same location references.
– Train the supply chain: brief groundworkers, SMSTS/SSSTS supervisors, and plant operators on what NUAR shows, what it doesn’t, and how it feeds into safe digging.
Integration on real programmes: interfaces and timing
/> Tender stage: use NUAR to spot showstoppers and provisional sums early. If the view suggests heavy congestion, flag survey allowances and trial pits in your methodology and programme, rather than absorbing risk.
Design development: share curated NUAR extracts with designers to inform alignments, slab build-ups and drainage depths. Keep design managers aware of confidence levels so they don’t set unbuildable assumptions.
Pre-construction: refresh NUAR data when traffic management and phasing are fixed. Coordinate with any streetworks notifications so that trial holes and ground-penetrating radar can be scheduled within permit windows.
Delivery: keep the latest NUAR extract in the RAMS briefing and toolbox talks. After validation on the ground, update redlines and close out the day’s dig with photos and notes linked to chainage or grid references.
Close-out: while contractors typically don’t upload to NUAR directly, provide verified as-builts to the client and relevant utilities in their requested format, so asset owners can improve records over time.
What to watch next in the UK NUAR landscape
/> Expect broader coverage and more frequent refreshes as asset owners standardise their feeds. Integrations with mainstream CAD/GIS platforms and CDEs will reduce the copy-paste burden and improve version clarity. Local authority processes and streetworks systems may begin to reference NUAR more directly, making it the default starting point for permits and TM discussions. As apprentices and supervisors get NUAR-literate, the cultural shift will matter as much as the technology.
The bottom line: build NUAR into your workflow now, but keep the spades-and-sense discipline that actually prevents strikes. Used well, it shortens decision time, de-risks early design, and helps you keep plant moving on congested ground without gambling the programme.
FAQ
# Is NUAR a replacement for utility searches, CAT/Genny and trial holes?
/> No. NUAR gives a consolidated view, but it doesn’t guarantee exact positions or depths. Use it to plan where to investigate, then verify on site with established locating methods and trial holes before using mechanical excavation.
# How do contractors actually get access, and who should hold log-ins?
/> Access is organisation-based and role-controlled, so set it up centrally and assign named users for pre-construction, engineering and supervision. Test log-ins before a live dig, and avoid the “single GIS champion” trap by issuing controlled extracts to those who don’t need portal access.
# Can subcontractors use NUAR, and what about data ownership?
/> Subcontractor access depends on your organisational setup and any use conditions attached to the data. If subs don’t have credentials, issue them with controlled extracts via the CDE and record what was shared and when. Keep ownership and attribution consistent so annotated outputs don’t drift into uncontrolled circulation.
# Does NUAR change what goes into a permit-to-dig?
/> It should strengthen the permit pack but not replace existing elements. Include current NUAR extracts alongside utility plans, survey outputs and RAMS, and brief crews on what confidence level applies. Record the verification steps taken on site so the permit reflects both desk study and ground truth.
# What if the NUAR view is incomplete or conflicts with other information?
/> Treat NUAR as one source among several. If there’s a mismatch, plan additional locating and trial holes, and escalate the issue early with the designer, client and any affected asset owner. Document decisions and keep the latest agreed position in the CDE so the site team works to a single source of truth.
