The National Underground Asset Register is moving from pilot to everyday tool. It promises a single, current view of buried utilities to cut service strikes and wasted time. For contractors under programme pressure, this isn’t an optional extra; it reshapes pre‑construction, RAMS, permit‑to‑dig and how the supply chain plans digs. The question is no longer whether to use NUAR, but how to wire it into UK site practice without slowing production or inflating prelims.
TL;DR
/>
– Get organisational access to NUAR, name a responsible person, and bake it into RAMS and permit‑to‑dig.
– Use NUAR alongside PAS 128 investigations and HSG47‑aligned safe digging; it does not replace scans or verification.
– Push NUAR data to field devices and control versions; capture as‑found conditions and close the loop.
– Update supply chain orders to cover licences, data use, and liability for service protection.
– Pilot on one scheme to settle training, device setup and change control before scaling.
A playbook to make NUAR part of live UK works
# Stage 1: Mobilise your access, roles and rules
/>
– Secure NUAR access for your project team and key subcontractors early, with clear account ownership. Treat it like a controlled system in your information security plan.
– Appoint a NUAR lead (often the utilities coordinator or temporary works/engineering manager) to control who sees what, how data is issued and how updates are tracked.
– Decide where NUAR extracts will live in your CDE, how they’re named, and how long they’re valid. Give the permit‑to‑dig authority the power to refuse out‑of‑date extracts.
– Write NUAR into your project execution plan, RAMS templates and induction. Tool‑box talks should show screenshots and device workflows, not just words.
– Build it into orders and subcontracts: who provides access, who supplies devices, and who is accountable if a dig proceeds without the latest NUAR data.
# Stage 2: Set a utility strategy that merges NUAR with proven practice
/>
– Pull NUAR data at tender and again at pre‑start to inform risk, programme and temporary works. Use it to spot congested corridors, diversion needs and street works constraints.
– Run statutory plant enquiries and commission PAS 128 surveys where risk demands. NUAR is the starting map, not the verification.
– Agree trace and verification methods (CAT/Genny, GPR, vacuum excavation) based on asset criticality and ground conditions. Record them in RAMS and method statements.
– Lock a review gate before breaking ground: design, temporary works and traffic management must align with the NUAR picture and survey outputs.
– Configure a simple “known unknowns” register for suspect or missing assets; assign actions and dates, and escalate any blockers to the Principal Contractor.
# Stage 3: Plan the dig and push data to the front line
/>
– Create dig zones with clear extents linked to NUAR layers. Export the right slices to tablets or handhelds used by gangers and site engineers.
– Overlay NUAR with setting‑out control, phasing plans and permit boundaries so supervisors can see what matters in one view.
– Build “stop work” triggers into the permit‑to‑dig: if a feature isn’t where NUAR or plans indicate, the team pauses, escalates and re‑validates.
– Prepare for poor connectivity. Cache map tiles and asset layers on devices, and brief how often downloads must be refreshed.
– Brief plant ops and groundworkers visually. Mark‑up on the ground still matters, but the screen in a supervisor’s hand should match the paint on the deck.
# Stage 4: Execute with verification and live change control
/>
– Start with verification passes using CAT/Genny and GPR for the day’s zones. Compare findings to NUAR and survey records; note any variance.
– Escalate conflicts fast. Use your change control: hold points, revised RAMS where needed, and client notification if programme or scope is hit.
– Record as‑found positions with photos, coordinates and depths where practical. Keep it simple: a standard form in your CDE tied to the zone, not a new bureaucracy.
– Capture near‑misses and hits with root causes. Don’t bury them in monthly reports; use them to update methods that same week.
# Stage 5: Close out and feed improvements forward
/>
– Update as‑builts and service records for handover. Where you’ve verified better positions, pass corrections through the client and asset owners’ established channels.
– Review performance: how many permits required re‑validation, where did NUAR add value, where did it cause delay? Bring those lessons into your next pre‑start.
– Keep an eye on integration. As APIs and plugins mature, expect smoother links between NUAR, GIS, BIM and permit systems—plan for that in your digital roadmap.
# A live UK scenario: congested high street, no slack in the programme
/> A civils contractor takes on a town‑centre public realm upgrade with new drainage, ducting and kerb realignment. Access windows are tight due to retail trading, and the local authority has embargo periods. The utility coordinator pulls NUAR early and sees gas, fibre and legacy cables stacked under the footway where the new crossing is planned. PAS 128 surveys confirm some, but not all, of the assets; records from a smaller operator are patchy. The team redraws the sequence, moving the crossing works to a night shift and designing a temporary ramp to maintain access while trial holes verify unknowns. On site, the supervisor’s tablet shows the NUAR layer in the permit zone; when a cable appears 450 mm off the expected line, they pause, photograph, notify the permit authority and adjust the method. The change takes a night, not a week, and the street doesn’t lose power.
# Site‑ready NUAR checklist
/>
– Arrange NUAR access for the Principal Contractor and named subcontractors; confirm device and offline use plans.
– Nominate a NUAR lead and define a simple approval path for extracts in permit‑to‑dig.
– Set rules for when NUAR must be refreshed and how conflicts trigger hold points.
– Align NUAR layers with PAS 128 survey outputs and statutory plans in one shared folder structure.
– Equip supervisors with rugged tablets, cached maps and clear instructions for daily verification passes.
– Capture as‑found positions and photos in a standard form linked to zone and date.
– Update orders to clarify who pays for access, who provides verification, and how liabilities flow.
# Common mistakes
/>
– Treating NUAR as the single source of truth. It’s a powerful aggregation, but not a substitute for competent detection and on‑site verification.
– Letting PDFs float around WhatsApp. Without version control, crews dig on stale layers; lock it into your CDE and permits.
– Ignoring the supply chain. If your groundworks firm can’t access or read NUAR outputs, the plan falls apart at the trench edge.
– Failing to brief plant and sequencing. NUAR insights that don’t reach the machine seat won’t stop a bucket from pulling a cable.
What to watch: expect more asset owners to connect their datasets and more clients to mandate NUAR‑based planning. The smart move now is to pilot, document the benefits and snags, and get your permit‑to‑dig and RAMS templates NUAR‑ready before the requirement lands by default.
FAQ
# Does NUAR replace utility searches and PAS 128 surveys?
/> No. NUAR gives a consolidated, near‑current view of underground assets, but it doesn’t remove the duty to obtain plans from statutory undertakers or to investigate to an appropriate level. Use NUAR to target surveys and plan sequences, then verify on the ground with recognised methods.
# How should access and licensing be handled across subcontractors?
/> Treat NUAR access like any controlled system: define who needs it, how they’ll use it, and how long access lasts. Put responsibilities and any cost allocations into orders, and make sure supervisors who issue permits can see whether subcontract teams are using current data.
# How do we evidence NUAR use in RAMS and permits?
/> Embed screenshots or export references with dates and layer names directly in RAMS and permit‑to‑dig packs. Add a step in the permit process that confirms the NUAR extract age and the verification method for that day’s work, then file as‑found records in the same folder.
# What if NUAR conflicts with what we find on site?
/> Stop, make the area safe and escalate via your permit authority. Record the variance, adjust the method if needed, and notify the client and relevant asset owner through their established channels so future records can be improved.
# Can NUAR be used offline or integrated with our existing GIS/BIM tools?
/> Plan for patchy connectivity by caching maps and layers to field devices before shifts. Some platforms already support GIS overlays and CDE links; keep your workflow simple now, but be ready to adopt integrations as APIs and plugins mature and your client’s information requirements evolve.
