The National Underground Asset Register (NUAR) is moving from pilot to wider use across the UK. For contractors, it promises faster, clearer utility information before breaking ground. But it also introduces new access controls, roles, and record-keeping that need to mesh with existing permit-to-dig, HSG47 practices and programme pressures. Getting the access steps right now will save clashes later when the platform becomes the default way to see buried assets.
TL;DR
/>
– NUAR is a controlled-access map of underground assets; contractors need project-based authority and named users to view data.
– Treat NUAR as one input to safe digging; pair it with surveys, trial holes and standard HSG47-aligned controls.
– Build NUAR into your pre-construction workflow: letters of authority, user provisioning, data capture, and permit packs.
– Expect patchy coverage early on; keep existing utility search routes running in parallel until confidence is high.
NUAR in plain English: who can use it and what you’ll actually see
/> NUAR is a government-backed digital map bringing together underground utility records from participating asset owners. It is not a public map; access is granted to eligible organisations and named individuals with a legitimate need linked to real work. For most contractors, that means being appointed on a project and holding a letter of authority from the client or relevant asset owner before getting a login.
Once in, users can view a location in a web map and switch on layers for buried assets such as water, gas, power and telecoms. You can expect to see extents, alignment and attribute notes where provided by the owner, plus a timestamp on when each dataset was last updated. The platform carries caveats about accuracy and usage; it is an aid to planning, not a dig ticket in itself. You can typically print or export what you view for inclusion in method statements and site packs, but usage is subject to terms.
Coverage is growing as owners onboard. Until it’s comprehensive in your patch, keep running your usual utility queries with the relevant statutory undertakers and existing search portals. NUAR will sit alongside those processes for a while. Treat it as a strong new source, but not the only one.
Site-side workflow to access NUAR data and fold it into permits
/> Start with eligibility. Confirm with your client that NUAR can be used on the project and secure a letter of authority that clearly names your organisation and the project scope. Nominate an internal admin (often in pre-construction or engineering) to request organisation access, set up named users, and define how project data will be stored and controlled.
Define the area of interest by work package or chainage rather than a huge polygon that captures more than you need. Pull the latest NUAR view close to design freeze and again ahead of mobilisation, so you’re not working off stale layers. File the outputs in your common data environment with versioning, dates and initials. If a utility dataset looks thin, flag it early with the designer and the client.
Cross-reference NUAR results with your existing utility enquiries. If an owner isn’t yet visible in NUAR for your area, raise separate searches and factor that into programme risk. Align the combined utility information to your risk assessment and method statement, including the choice of detection methods (electromagnetic locator, GPR), trial holes and any vacuum excavation. Feed the outcome into temporary works design and traffic management so the team isn’t discovering constraints at night in live carriageways.
On site, give the supervisor and ganger a simplified plan that strips back clutter but keeps the essential layers, depth notes if present, and a clear permit boundary. Use pre-start briefings to confirm last-seen version dates. Capture discrepancies: if a duct bank runs off-line versus the plan, record it, adapt the method safely, and feed that back to the project team for design decisions and NUAR notes where appropriate.
# Scenario: night works on a town-centre drainage upgrade
/> A civils contractor is delivering a drainage connection on a busy high street with night-only windows. The PM secures a letter of authority from the local authority and utility co-signoff for NUAR access. The engineer logs in, defines a 120-metre area around the works, and sees dense telecoms and a medium pressure gas main clipping the excavation. The job’s method is revised to add two trial pits at the entry and exit points and to switch to vacuum excavation across the gas corridor. A last-minute change to the traffic management plan nudges the route of a temporary footway; the supervisor checks the NUAR layers again and picks up a private LV service close to the kerb. The discovery avoids a rushed diversion and keeps the shift within the roadspace booking. The site team closes the loop by updating the permit pack with photos, marked-up plans and the NUAR view date.
# Pre-dig NUAR access checklist
/>
– Secure a letter of authority from the client or asset owner naming your organisation and project.
– Nominate an internal NUAR admin and define user roles, retention rules and version control.
– Draw tight areas of interest; pull fresh NUAR views near design freeze and again pre-start.
– Cross-check NUAR against other search routes; chase owners not yet visible on the map.
– Embed NUAR outputs into RAMS, temporary works and traffic management plans.
– Brief supervisors with simplified, dated plans and an escalation route for discrepancies.
– Record field findings against the plan and store them with the permit-to-dig pack.
Pitfalls and fixes while NUAR beds in
/> Early-adopter teams report two realities: NUAR can remove days of back-and-forth with utility owners, and coverage still varies by region and asset class. That mix creates risk if the site leans on NUAR as the only truth. Build your process around two tracks: use NUAR wherever possible, and maintain your existing searches and verification.
Commercially, NUAR access isn’t a one-off task. Organisations need to manage leavers and joiners, expired letters of authority and who owns the audit trail when a subcontract package starts. Close coordination with planners and traffic teams is vital; if your NUAR snapshot is updated after a roadspace booking is fixed, make sure that change is surfaced fast to the person holding the notice.
# Common mistakes
/>
– Treating a NUAR printout as a permit to dig. It’s a planning tool and must feed into HSG47-aligned controls.
– Pulling one NUAR view at tender and never refreshing it. Data currency matters when streetworks dates slide.
– Overdrawing huge project extents that drown the team in irrelevant layers. Smaller, task-based windows keep clarity.
– Ignoring private services from buildings. NUAR helps with mains and networks, but laterals and private cables still need on-site proving.
# Practical fixes that hold up on live jobs
/>
– Lock NUAR into the pre-start gate: no permit pack is “complete” without a dated NUAR view or a written note explaining why it wasn’t available.
– Push ownership to the right roles: pre-construction for letters of authority and account setup; engineering for data interpretation; supervisors for on-site verification and feedback.
– Time-stamp everything: the plan given to the ganger must carry the NUAR view date alongside the permit validity dates.
– Capture learning: where the team finds mismatches, build a short feedback loop to design and planning so repeat shifts get steadily safer and faster.
The direction of travel is clear: as more asset owners onboard, NUAR will become the primary starting point for underground information. Two practical questions for your next project meeting: who owns NUAR user provisioning on our jobs, how often will we refresh views, and how are we proving what we found on site against what the map showed?
FAQ
# Who in a contracting business should apply for NUAR access?
/> Typically an organisation-level admin in pre-construction, engineering, or digital delivery takes the lead. They handle the onboarding, add named users, and ensure each project has the right letter of authority before anyone views data. Site supervisors and engineers then use the outputs as part of permit packs and briefings.
# Is NUAR a replacement for our current utility searches and scanning?
/> Not yet. Treat NUAR as an additional, authoritative source that improves planning, but keep your existing search routes and on-site detection methods. HSG47-aligned controls, including competent scanning and trial holes where risks warrant it, remain essential.
# Can subcontractors get NUAR access, or must it go through the principal contractor?
/> Access usually reflects who holds the appointment and letter of authority for the work. In many cases, the principal contractor manages access and shares outputs within the permit process; in others, specialist subcontractors may be named and onboarded directly. Clarify this at procurement so there’s no delay when works start.
# What should go into the permit-to-dig pack when using NUAR?
/> Include a dated NUAR view for the immediate work area, the list of other utility enquiries made, your detection strategy, and any trial hole requirements. Add simplified plans for the supervisor, escalation contacts, and a way to record what was found versus what was expected. Keep all versions in your project’s data environment for audit.
# How often should we refresh NUAR data during a programme?
/> Refresh when significant programme dates shift, when the design changes, and before each mobilisation window on streetworks. If your project is long-running or in a utility-dense area, schedule periodic refreshes so you’re not relying on stale views. Always mark the view date on site plans and permits.
