The National Underground Asset Register is moving from pilot to live use across large parts of the UK, and contractors are feeling it on programmes, permits and preconstruction. NUAR is not a magic x‑ray of the street, but it is becoming the default starting point for understanding where buried services might be. If you dig, drill, pile or trial‑hole, your workflows, RAMS and commercial assumptions need to reflect NUAR’s availability, coverage and limits now—not when a road opening notice is refused or a cable strike report lands on the PM’s desk.
TL;DR
/>
– Get project teams enrolled for NUAR access early and bake it into permit-to-dig, RAMS and temporary works packs.
– Treat NUAR as planning intelligence, not a substitute for PAS 128 investigations or HSG47 controls.
– Define who maintains the “single source” of buried services info when NUAR data meets survey findings and as-builts.
– Check coverage and update schedules by region; design contingency around gaps and data lag.
– Align commercial allowances and programme float to the reality that NUAR may shift utility diversion scope.
NUAR in plain English: what it is and isn’t
/> NUAR is a government-backed platform, coordinated by the Geospatial Commission, that brings together digital maps of underground assets from participating utility and infrastructure owners. Think of it as a common, standardised view of where networks say their pipes, cables and ducts run, presented via a secure web interface and, increasingly, APIs. It aims to reduce accidental strikes, duplicated enquiries, and the long lead times of chasing individual plans for every street.
It is still rolling out by region and by asset owner. Coverage will vary; some layers will be more complete or more up to date than others. NUAR does not verify what’s in the ground and does not remove the need for site investigation under industry guidance such as PAS 128 or safe-digging good practice like HSG47. On any given job, NUAR is early intelligence and coordination glue: useful for planning and deconfliction, but only one part of your service avoidance and design assurance picture.
Where NUAR lands in real UK workflows
/> On a live programme, NUAR should appear in preconstruction as soon as a footprint, route or streetscape is known. Planners and design managers use it to scope utility risks, utility coordinators use it to shape C2/C3 requests and diversion strategies, and QSs reference it to flag provisional sums and float. As works approach, site engineers fold NUAR outputs into permit-to-dig packs alongside GPR results, trial pits, traffic management plans and temporary works designs. For street works, supervisors find NUAR evidence handy when discussing phasing, access, and protection measures with local authority inspectors and undertakers.
Crucially, NUAR didn’t replace your existing buried services workflow—it added a new, earlier lane to it. The project still commissions detection and verification to the desired PAS 128 level, still plans isolation and protection, and still writes RAMS that assume unknowns. But the conversation with the utility owner can start sooner and be better targeted. Where suppliers and subcontractors are involved—groundworks, civils, M&E, piling—contractors need to define who accesses NUAR, who extracts layers, who marks it up, and who is responsible for reconciling discrepancies against survey findings.
# Site-ready NUAR checklist
/>
– Set up NUAR access for precon, utilities coordination, site engineering and temporary works, with clear permissions.
– Capture a date-stamped export of relevant layers and annotate with chainage, grid and site references used on drawings.
– Record coverage gaps and low-confidence layers; flag these in the risk register and programme as survey triggers.
– Align NUAR outputs with PAS 128 survey scopes and trial pit locations before issuing to bidders and subcontractors.
– Integrate NUAR visuals into permit-to-dig packs, adding notes on isolation plans, no‑dig zones and protection detail.
– Define ownership of the “master” buried services view in the CDE and set a process for updates after every find.
– Brief supervisors and machine operators on NUAR’s purpose and limits during inductions and daily start-ups.
A UK site scenario: retrofit street works under programme heat
/> A local authority commissions an energy retrofit on a Victorian terraced street, adding heat network laterals and EV charging points. The main contractor has eight weeks between school terms to trench, lay ducts and reinstate the footways. The utility coordinator pulls NUAR data: it shows telecoms ducts hard against the kerb, a water main in the carriageway, and legacy gas services wandering between plots. The QS has carried a modest allowance for utility protection, but the groundworker is priced tight and wants to minimise trial pits to hit productivity. At week one, NUAR helps the team plan crossing points and diversion candidates, and they issue a permit-to-dig with marked safe corridors. By week two, a trial hole reveals the gas service is actually 800 mm off NUAR’s plotted line, clipping a proposed EV feeder route. The PM burns two days re-sequencing, and the commercial team agrees a variation with the client to drop in a short duct diversion with additional protection plates. Without NUAR, that conversation would have started later and cost more calendar days; with NUAR, it started early—but still relied on on-site verification.
Pitfalls and fixes when adopting NUAR
/> The biggest pitfall is assuming NUAR is definitive. It isn’t. Treat it as a planning layer that reduces blind spots, not as a control measure on its own. Another frequent slip is handing NUAR access to one precon lead and leaving site teams to chase screenshots via email. A platform only adds value if the right people can use it when decisions are made—in design workshops, in pre‑start briefings, and at the edge of the trench.
Data stewardship is the next trap. If no one owns the “master” buried services model, your CDE fills up with conflicting layers: NUAR exports here, GPR plots there, and subbie mark-ups nowhere traceable. Name a single custodian—often the utilities coordinator or BIM lead—to reconcile sources and push controlled updates to drawings and permits. Finally, procurement often forgets to specify deliverables from surveys in a way that complements NUAR: if you don’t ask for georeferencing and chainage compatible with NUAR grids, you’ll burn time stitching datasets together when the clock is ticking.
# Common mistakes
/>
– Treating NUAR as a substitute for PAS 128 surveys. It should guide where you look harder, not replace looking.
– Printing NUAR screenshots without scale, legend or date. That kills traceability and weakens permit-to-dig quality.
– Not training supervisors and plant operators on what NUAR is. If they think it’s gospel, they’ll take unsafe shortcuts.
– Ignoring updates mid‑programme. NUAR coverage can improve while you’re on site; if you don’t revisit it, you miss options.
The fixes are simple and practical. Put NUAR into your standard preconstruction checklist with an early export and a coverage note. Write into your utility detection scope that survey outputs must align with NUAR coordinates and layering conventions. Include a five‑minute NUAR briefing in inductions for anyone who digs or directs plant, and refresh it at the weekly coordination meeting. And when you find something different in the ground, update the CDE immediately—treat NUAR as the starter layer that your verified record refines.
Bottom line: NUAR helps you de‑risk earlier, argue for realistic allowances, and tidy up the fragmented “plans request” circus. But it only pays off if it’s owned, integrated and challenged by people who understand both maps and mud.
Before your next excavation, ask three questions: who owns NUAR access and the reconciled buried services view; how will NUAR be verified against PAS 128 and fed into permits; and what changes if NUAR coverage improves mid‑programme. Watch for more asset owners joining, better APIs into CDEs and BIM, and local authorities expecting NUAR evidence in street works dialogues.
FAQ
# Is NUAR mandatory for my project right now?
/> There isn’t a one-size-fits-all requirement across the UK, and adoption is rolling out in phases. Many clients and authorities are starting to expect NUAR to be consulted as part of service avoidance and coordination. It’s smart practice to use it wherever coverage exists, then document how it informed your planning.
# How should NUAR sit alongside PAS 128 surveys?
/> Use NUAR to scope where you need detection and verification, to sequence surveys efficiently, and to brief surveyors. Survey outputs should then be aligned to the same grid and chainage as your NUAR export so the project can reconcile differences quickly. Think of NUAR as the planning baseline and PAS 128 as the evidence that drives permits and RAMS.
# Who should hold NUAR access on a project?
/> Give access to the people who make decisions affecting the ground: utilities coordinators, site engineers, temporary works and the supervisor responsible for permits. Keep a named custodian—often the utilities or BIM lead—who manages the “master” buried services record in the CDE. Avoid bottlenecks by training backups and documenting the login and export process.
# How do I handle discrepancies between NUAR and what we find on site?
/> Assume discrepancies will occur and set a routine to capture them. Mark up the verified location, take geo‑referenced photos, and update the CDE with a dated change note so permits and drawings reflect the new reality. Escalate significant clashes to design and commercial early; a small re‑route agreed on Tuesday beats a late variation claim on Friday.
# Can subcontractors rely on our NUAR exports, or do they need their own access?
/> If subcontractors are directing excavation or proposing routes, they should see the latest data in context, not a stale screenshot. Either provide controlled exports through your CDE with clear dates and legends, or arrange project-level NUAR access for key subcontractors under your information protocols. Make sure responsibilities are spelled out in orders and RAMS so there’s no ambiguity at the trench edge.
