The National Underground Asset Register is now live, bringing a single digital view of buried water, gas, electric and telecoms assets into everyday planning. For contractors, the win is fewer strikes, tighter coordination and cleaner handovers — but only if onboarding is done deliberately. Treat NUAR as a new control point in your permit-to-dig flow, not a nice-to-have map.
TL;DR
/>
– Nominate an internal NUAR admin, set user roles, and mandate MFA and access logs.
– Define how Areas of Interest are requested, named, exported and filed in the CDE with date stamps.
– Build NUAR into permit-to-dig alongside HSG47 practice: detection, trial holes and vacuum excavation.
– Train supervisors on reading layers and known gaps; brief subcontractors on data-use limits.
– Capture as-built changes and trial-hole results back into your records so learning sticks.
The NUAR contractor playbook
# Step 1 — Set up your organisation and permissions
/> Appoint a NUAR organisation admin who is close to utilities coordination rather than IT alone. Establish who needs access (precon planners, site managers, utility surveyors, SHEQ) and set permission levels accordingly. Enforce multi-factor authentication and a joiners/leavers routine so access doesn’t outlive projects. Record how you will evidence access history for audits and incident reviews.
# Step 2 — Prepare your naming and data governance
/> Create a simple convention for Areas of Interest: project code, chainage or grid reference, and date. Decide where NUAR exports live in the CDE, how they link to RAMS and permits, and how they are versioned. Make date-stamped PDFs mandatory in site packs, with the digital source also stored for traceability. Set a retention policy that aligns with your client’s requirements and PI expectations without assuming NUAR is your system of record.
# Step 3 — Wire NUAR into permit-to-dig
/> Insert a NUAR check into your pre-excavation workflow before ground radar, tracing or trial holes. The permit issuer should verify that the NUAR pack covers the exact dig footprint and has a fresh date. Add a stop/go gate: no excavation without NUAR pack, detection results and agreed control measures. For reactive works, define who has delegated authority to fast-track a request and still meet safe digging standards.
# Step 4 — Coordinate with asset owners and the client
/> Even with NUAR, you’ll still need to contact some asset owners directly for consents or detailed plans. Agree during pre-start who makes enquiries (PC or specialist subbie) and how responses are logged. If the client maintains private networks, establish how those records will be blended into the NUAR view or flagged as separate layers. Capture any conditions set by asset owners into the method statements so they reach the crews.
# Step 5 — Site use: from digital layers to ground truth
/> Train supervisors to read the layers critically: look for mismatches, blank spots and legacy markers that suggest historical works. Use the NUAR map to target your detection and trial holes efficiently rather than blanket scanning. On the day, ensure the pack is on the tablet or in print at the workface, and redraw the dig boundary if the team shifts position. Record discrepancies: if a pipe is not where NUAR suggests, capture coordinates, photo evidence and who witnessed it.
# Step 6 — Close-out and feed information back
/> At section completion, compile a concise utility close-out note in the CDE: the NUAR pack used, detection results, trial-hole logs, any services protected or diverted, and as-built positions where known. Share that pack with the client and relevant asset owners per contract. Update your internal playbook with lessons learned on data gaps and safer work controls. This is how onboarding becomes capability, not just compliance.
# Common mistakes
/>
– Treating NUAR as a replacement for on-site detection. It’s a planning tool; safe digging still needs scanning, tracing and controlled exposure.
– Letting supervisors rely on screenshots with no dates. Undated images kill traceability and weaken incident defence.
– Not briefing subcontractors on data-use limits. If the groundworks gang thinks NUAR is infallible, risk climbs the minute a layer is thin or missing.
– Ignoring private or temporary services. On retrofit and fit-out especially, client-side spurs and site-run power/water won’t always appear on shared layers.
A live-street civils scenario: onboarding meets the dig window
/> A civils contractor is replacing a collapsed foul sewer on a busy market street. The local authority grants a four-night traffic management window, with penalties if the road isn’t back open for the weekend. The site agent has a drainage crew, a vacuum excavator booked, and a telecoms subcontractor finishing a fibre pull two doors down. NUAR is used to map the spaghetti of low-voltage, water and fibre ahead of the first night shift. The Utilities Coordinator requests a precise strip 60 metres long, names it with the project code and date, and files the exports into the CDE with a permit-to-dig pack. On site, the gangers use NUAR to place trial holes where the layers show crossings; one telecoms duct is not where expected, so the agent halts until it’s located. The final as-built sketches note the true duct position and are shared with the client, avoiding a strike and a claim that would have blown the weekend reopening.
Quick onboarding checklist for site teams
/>
– Nominate a NUAR admin and publish a one-page access guide with contacts and escalation.
– Create a naming format for Areas of Interest and lock a folder structure in the CDE.
– Link NUAR packs to permits: include date, coordinates or polygons, and drawing scale.
– Brief all supervisors and subcontractors on reading layers and known gaps before they dig.
– Require the pack to be on the workface: tablet or printed, legible, and current.
– Log discrepancies and trial-hole results with photos, chainage or grid and witness names.
What to watch next for NUAR in UK delivery
/> Coverage will broaden as more asset owners publish data and as contractors feed back discrepancies through clients and forums. Expect clients and insurers to start asking for NUAR evidence in pre-start and incident investigations, and for APIs to appear in common data environments and GIS tools. The smart contractors will turn onboarding into a repeatable control that stands up in audits and helps the crews work faster and safer. The rest will be left explaining why a screenshot with no date was “good enough”.
FAQ
# Who in a contracting business should own NUAR onboarding?
/> Typically, utilities coordination sits between preconstruction, engineering and SHEQ, so an owner from that space works best. IT should support account setup and security, but operational ownership needs to live with the people issuing permits and RAMS. Clear responsibility stops NUAR becoming “everyone’s job” and therefore nobody’s.
# How do NUAR maps fit with PAS 128 and HSG47 practice?
/> Treat NUAR as an upstream source that informs where to survey and expose, not as a substitute for detection or trial holes. Align it with your PAS 128 survey strategy and your HSG47-style controls so every dig moves from plan to detection to controlled excavation. That sequence reduces surprises and provides a documented trail.
# Can subcontractors access NUAR or do we have to distribute packs?
/> Either model can work, but you must control consistency and versioning. If subs access NUAR directly, set permissions and brief them on naming and filing so outputs land in your CDE properly. If you distribute packs, time-stamp and lock them into the permit so the workface isn’t using stale information.
# What if an asset owner’s data is missing or looks wrong?
/> Flag gaps early and contact the asset owner through your agreed enquiry route; don’t assume absence means absence in the ground. Use targeted detection and trial holes to establish ground truth, then record findings with photos and coordinates. Share that evidence with the client and, where appropriate, with the asset owner through formal channels.
# How do we evidence use of NUAR if there’s an incident?
/> Keep the digital export and the printed pack with dates, user names and the exact polygon or boundary queried. Link these to the permit-to-dig, the detection results and any toolbox talks on the day. That bundle demonstrates reasonable steps were taken and shows where further controls may be needed in future.
