The National Underground Asset Register is moving from pilot to wider availability, and that changes what “before you dig” looks like across UK sites. NUAR promises quicker, clearer visibility of buried plant, but it will not replace permits to dig, utility notifications, on-site detection or trial holes. Contractors who wire it into their workflow early will save days of back and forth and reduce strike risk; those who treat it as a last‑minute map grab won’t.
TL;DR
/>
– NUAR centralises underground asset plans but does not remove duties around detection, verification and permits to dig.
– Build NUAR requests into pre‑construction and temporary works planning, not the week you break ground.
– Align NUAR outputs with GPR/CAT results, traffic management, and utility owner notifications; expect data gaps and legacy assets.
– Agree access, roles and data retention with your client and supply chain; keep a controlled copy in the CDE.
– Use NUAR as the common map in briefings, then verify by trial holes before full excavation.
NUAR in plain English: what it is, what it isn’t
/> NUAR is a government-led platform that brings together underground asset information from utilities and other asset owners into one map-based service. It standardises disparate plan formats and can show depth estimates and attributes where providers supply them. Think of it as a faster route to utility plans, not a guarantee of what is actually in the ground.
It does not override asset owners’ plant-protection rules, nor does it substitute for competent detection and safe digging practices. Data quality depends on the source; some networks have modern GIS, others have legacy records. Access is organisation-based with role controls, so agree early who will request data and who will file it within the project CDE. Scotland operates under a different arrangements for street works data; if your footprint crosses borders, plan for dual processes.
How NUAR changes the before‑you‑dig workflow on real sites
/> On a real programme, NUAR belongs at RFI stage and during temporary works design, not at the gang box the morning you break ground. Use it to shape method statements and isolation plans, to target GPR and trial holes, and to brief groundworkers and plant ops with a single picture. For urban work, align it with traffic management and road space bookings so you’re not reopening the road to verify what you could have located in one visit.
Scenario: A civils team is installing new drainage connections and EV charger bases on a tight high street. The site manager has a 48‑hour traffic management window and a utilities coordinator across two jobs. The QS is holding a risk allowance for strikes, but the client wants handover in six weeks. The NUAR pull shows a cluster of low-voltage and comms near proposed kerb realignment, plus an unverified gas spur. The GPR subcontractor slots a focused survey for the hotspot rather than scanning the whole street. Trial holes confirm the gas spur is 600 mm off the drawn position; the kerb is offset and the TM window is used once, not twice.
Pre‑dig NUAR workflow checklist
– Define the exact work polygons early and request NUAR data for those bounds; avoid sprawling extents that hide the detail that matters.
– Export layers to your GIS/CAD/BIM environment and align to topo and setting‑out points; lock a version in the CDE with date and source noted.
– Compare NUAR outputs against any asset owner plans you already hold and flag mismatches into the risk register with targeted verification actions.
– Book GPR and CAT scanning to focus on conflict zones identified in NUAR; capture georeferenced results for overlay.
– Plan trial holes where clashes persist; sequence them with traffic management and temporary works design so you validate once and build once.
– Run a service avoidance briefing using the NUAR overlay, detection results and method statement; document who attended and when.
– Issue the permit to dig only after verification evidence is filed in the CDE and isolation/locking-off steps are confirmed where required.
NUAR can also reduce design churn. Designers can check viable corridors at concept stage rather than hoping the street is clear. For machine control and setting‑out, never push NUAR depths direct to plant; treat it as planning intel, not excavation instruction.
Pitfalls and fixes when relying on NUAR data
/> The biggest trap is assuming the platform removes the need to talk to asset owners. Many utilities will still require formal plant‑protection notifications or ticketing before excavation, and some will insist on supervision for high‑risk plant. Treat NUAR as your core map, then run the owner-specific processes in parallel.
Expect gaps. Some private networks, legacy industrial services or small operators may not yet be represented. Where NUAR is silent, escalate in your pre‑start: ask the client for private record drawings, scan wider, and assume unknowns until proven otherwise. The commercial angle matters too: allow in the prelims for robust detection, trial holes and possible re‑designs; these costs are smaller than programme days lost to strikes or emergency repairs.
Depths and offsets in any record drawing can be approximate. Use NUAR to nominate verification points rather than to fix line and level. Where diversion is on the table, get an early read on lead times and owner charges; NUAR can highlight constraints quicker, but it doesn’t shorten third‑party processes by itself.
# Common mistakes
/>
– Treating NUAR as a permit to dig. It is information, not authorisation; keep your permit workflow intact.
– Printing a snapshot and leaving it to gather dust. Keep the live dataset in the CDE and date-stamp the version you are building to.
– Ignoring private and building-fed services. NUAR coverage varies; scan and survey the last few metres into buildings and yards.
– Delegating the whole process to a subcontractor with no brief. Set the bounds, outputs and file formats you expect, and review before mobilisation.
Interfaces to manage: clients, utilities and the supply chain
/> Clarify with the client who holds the NUAR account, who requests data, and who pays for additional detection. For design‑and‑build jobs, put a line in your BIM Execution Plan or information protocol identifying NUAR deliverables, file types and retention. The principal contractor should own the master buried‑services model, but every subcontractor excavating should be issued a controlled view aligned to their work area.
Don’t drop plant-protection processes you already run. Until asset owners say otherwise, continue to raise notifications through their portals or intermediaries and gather clearances as you would normally. Where discrepancies arise between NUAR and owner drawings, brief the risk clearly: what you’ve verified, what you haven’t, and what protection measures apply.
Ownership of updates matters. If you relocate or install new services, capture surveyed as‑built positions and agree how they feed back into the wider data environment via the client. Project controls should link costs, programme shifts and clashes identified from NUAR into change control, not treat them as incidental site noise.
What to watch next is how fast asset owner coverage increases and whether highway permitting and utility notifications start to plug directly into the same ecosystem. In the meantime, the bottom line is simple: use NUAR to plan smarter, then verify like your programme depends on it—because it does.
FAQ
/>
Does NUAR replace utility notifications and plant-protection approvals?
No. Many asset owners still expect formal notifications through their own portals or intermediaries, and some impose supervision requirements for high‑risk work. Treat NUAR as the consolidated map you plan from, then follow the owner-specific approvals as normal. Keep records of both in your CDE.
# Can subcontractors access NUAR data, or does it have to sit with the principal contractor?
/> Access is typically organisation-based, so agree roles at pre‑construction. The principal contractor should control the master dataset and issue relevant extracts to supply chain partners. Make sure issued plans are versioned and tied to a specific work area and date.
# How should NUAR integrate with GPR and CAT on site?
/> Use NUAR to prioritise where to scan and what to verify, not to skip scanning. Overlay GPR/CAT findings against the NUAR layers and flag any conflicts into your permit-to-dig. Keep georeferenced outputs and photos in the CDE so they’re auditable.
# What if NUAR doesn’t show a private cable or old service that turns up during excavation?
/> Pause, make the area safe, and escalate through your incident and change processes. Update your buried-services plan, extend scanning to define the unexpected asset, and notify the relevant owner if identifiable. Capture the discovery for as‑built records so the client’s dataset improves for future works.
# Who is responsible for keeping NUAR-derived information current on a project?
/> Project teams should maintain their controlled copy within the CDE with dates and sources recorded. When works alter existing services or add new ones, agree with the client how surveyed as‑builts flow back into their asset information model and any wider data environment. Don’t overwrite historic data; archive versions to show the decision trail.
