The National Underground Asset Register is moving from a pilot niche to a working tool that will sit in the middle of streetworks planning and ground risk on UK jobs. For contractors, the shift isn’t abstract policy. It’s the difference between waiting days for a bundle of inconsistent utility plans and having a permissioned, aggregated view ready when the permit-to-dig is raised. NUAR will not replace HSG47 controls, competent locating or trial holes, but it changes the workflow, the procurement language, and who is accountable for underground information at each stage. If project teams act now, they can reduce service strikes, de-risk traffic management windows and remove a chunk of administrative waste from early site set-up.
TL;DR
/>
– Embed NUAR into pre-construction and permit-to-dig so it becomes the first view of underground assets, not an afterthought.
– Keep HSG47, competent locating, and PAS 128 surveys in place; NUAR complements rather than replaces them.
– Assign a named NUAR lead, set access rights, and link the viewer/API into your CDE and RAMS templates.
– Update procurement and subcontract orders to require use of NUAR data and clear handback of verified as-builts.
– Expect patchy coverage and variability as asset owners onboard; plan for gaps and validate critical routes on site.
NUAR in plain English: powerful, useful, but not the whole picture
/> NUAR is a digital service that aggregates data from utility and telecoms owners so authorised users can view where buried assets are likely to be. Think of it as a shared viewer, available via web and in some cases API, that reduces the legwork of contacting multiple providers for plan extracts. It is being rolled out in phases, with data quality and coverage that varies by area and asset owner. The principle is simple: put all available official plans in one place, with standardised symbology and metadata, so you can plan more safely and quickly.
What it is not: a guarantee of exact locations, depths, or current status of services. It does not remove the need to follow HSG47, carry out utility detection by competent persons, or confirm alignment with trial holes before digging. It won’t show every private lateral or legacy asset, and it may lag behind recent diversions or term-maintenance works. Used well, NUAR narrows uncertainty early, flags risk corridors, and gives everyone the same picture, but it still relies on engineering judgement and site verification.
Putting NUAR to work on UK sites
/> The practical value of NUAR appears as soon as you link it to established processes. Pre-construction managers and utility coordinators can open a NUAR view during design freeze meetings to check whether proposed drainage runs clash with comms or LV routes. Planners can use it to sequence temporary works knowing where duct banks cross intended haul roads. During delivery, the permit-to-dig pack should include a timestamped NUAR export alongside the validated utility survey. The Principal Contractor keeps control by making NUAR access part of induction for supervisors and by nominating a single point who issues the agreed layers for each work area.
For short-duration streetworks, having NUAR at tender stage helps decide whether to bid, how to price risk, and what lead time to allow for surveys. For larger civils or infrastructure, teams can bring NUAR into the Common Data Environment so designers, site engineers and the groundworks subcontractor are working from the same baseline. Where your client operates asset networks, they may control access and expect you to contribute verified as-builts back into their model on completion. On rural jobs, expect sparser records and prioritise detection; in dense urban cores, expect more layers and the need for clearer controls on who sees what and when.
# A live streetworks scenario
/> A highways team in a Midlands market town has a two-night road closure to install new gullies and a duct crossing. The contracts manager is worried: there’s a bus diversion penalty if the road isn’t reopened by 05:30, and the groundworks subcontractor wants to mobilise a second crew to hit the window. The utility coordinator pulls the NUAR view for the crossing and sees overlapping comms and LV bands hugging the kerb, with a gas main offset into the carriageway. They export the relevant layers, upload them to the CDE, and walk the TM zone with the supervisor the afternoon before. The CAT and Genny confirm the LV runs and hint at an unrecorded spur; a small trial hole finds an old clay duct not shown in NUAR. The team shifts the crossing by 1.2 metres on the RAMS, updates the permit-to-dig pack with the revised sketch, and re-sequences the excavation to start further from the congested area. The closure opens on time, and the as-built gets filed ready for client handover.
Avoiding traps: controls that make NUAR valuable
/> To make NUAR actually reduce risk, your project controls need to change with it. Start by naming a NUAR lead who understands both GIS basics and site delivery, then wire access into your induction and permit processes. Use NUAR to set the “red zone” early in design and temporary works, and to decide which corridors must have detection and trial holes before big plant arrives. Keep an audit trail: capture the export date, visible layers, and any gaps noted, and tie these to the method statement and inspection records.
When you manage multiple subcontractors, lock down who can draw or annotate against the NUAR view and how changes are fed back. If your CDE supports geospatial data, host a controlled copy there rather than relying on screenshots in emails. Where your client mandates specific survey standards, make NUAR the first pass that guides where higher-resolution PAS 128 surveys are targeted, rather than trying to survey everything blindly. For live service strikes investigations, a clear NUAR snapshot plus evidence of detection and trial holes will matter.
# Common mistakes
/>
– Treating NUAR as a precise map. It’s indicative and must be validated with competent detection and safe digging.
– Printing a screenshot and forgetting the date and visible layers. Without context, you can’t prove what was seen at the time.
– Giving blanket access to the whole supply chain. Control roles and avoid uncontrolled copies that breed confusion.
– Assuming coverage is complete. Build in time and cost for surveys and trial holes where NUAR shows gaps or conflicts.
# Immediate action checklist
/>
– Nominate a NUAR lead for each project and set role-based access for managers, supervisors, and utility specialists.
– Embed a dated NUAR export in permit-to-dig packs and RAMS, with a note of any missing datasets or suspected private services.
– Tie NUAR layers into design coordination and temporary works reviews to eliminate clashes before the method is fixed.
– Specify in ITTs and subcontracts that NUAR must be consulted and that verified as-builts are to be delivered back in agreed formats.
– Align coordinate systems and file formats in the CDE so NUAR data, survey outputs, and as-builts overlay correctly.
– Use NUAR to focus PAS 128 and trial hole effort on critical corridors, rather than blanket surveying.
– Record deviations found on site and feed them back promptly to the project model and the client’s records as required.
The procurement and governance angle you can’t ignore
/> Commercially, NUAR shifts assumptions about who obtains utility information and how early it lands. Clients may expect Principal Contractors to integrate NUAR into programme risk and pricing. Frameworks and local authorities will likely begin referencing NUAR in their streetworks conditions and information requirements. That means your bid library, pre-construction checklists and supply chain briefs should mention NUAR as standard, including how gaps will be handled and what level of verification is priced.
Data governance matters. NUAR access is permissioned, and the data it displays originates from different owners with varied terms. Treat it like any other controlled information source: don’t copy it wholesale into public drawings, don’t strip the context from exports, and don’t rely on it for positional accuracy beyond what is stated. Where you deliver design and build, agree with the client how NUAR-informed corridor decisions are recorded and what evidence will satisfy CDM and QA obligations.
The bottom line: act now to make NUAR a normal part of pre-start, permits and coordination, but keep the golden rules of safe digging intact. The next few months will likely bring broader coverage, API refinements and clients asking how you will use NUAR on bids—better to have the answer ready than retrofit it under programme pressure.
FAQ
/>
Does NUAR replace utility surveys and trial holes?
No. NUAR gives a faster, consolidated view of underground assets, but it doesn’t guarantee exact positions or depths. For critical work, you still need competent detection and, where required, PAS 128 surveys and trial holes to verify what’s actually in the ground.
# How should NUAR fit into the permit-to-dig process?
/> Include a dated NUAR export for the specific work area in the permit pack, alongside survey outputs and method statements. Supervisors should brief crews on what the NUAR view suggests, then confirm on site with CAT and Genny and any pre-agreed trial holes before breaking ground.
# Can subcontractors access NUAR directly?
/> Yes, but access should be controlled. Many main contractors will nominate a NUAR lead to issue the correct layers for each work area and maintain an audit trail. Avoid forwarding unmanaged screenshots; use your CDE to host the approved view where possible.
# Who owns the data and are there costs involved?
/> The underlying asset data remains with the respective utility owners, and NUAR provides a permissioned way to view it. Access models and any associated costs depend on organisational arrangements and rollout phases, so clarify responsibilities at contract award and ensure compliance with usage terms.
# How do we integrate NUAR with our BIM or CDE setup?
/> Decide the coordinate system and file formats you’ll use so NUAR exports, survey data and design models align. Store exports with clear metadata (date, layers shown, area) and link them to relevant work packages and permits. If you have GIS capability or an API route, connect NUAR to your map layers to avoid manual rework and keep a controlled master view.
