The National Underground Asset Register is moving from concept to everyday tool, giving contractors a single window into buried utility records. Used alone, it won’t keep a bucket or auger out of harm’s way. Paired with PAS 128 utility detection and verification, it can reshape how pre-construction planning, permits to dig, and day-to-day setting out actually happen, reducing rework and keeping programme risk within reach.
TL;DR
/>
– NUAR centralises utility records; PAS 128 gives site-verified confidence. Use both to inform designs, method statements and permits to dig.
– Start pairing at tender: use NUAR for scope and risk pricing, then commission PAS 128 surveys to the right level before design freeze.
– Push both datasets into the CDE with clear version control, coordinate systems and extents so groundworks and traffic management work to the same truth.
– Revisit NUAR updates and re-survey critical corridors when designs shift or stakeholders change; don’t let stale data drive excavations.
– Keep evidence: survey deliverables, clash assessments, on-site verification and change logs. It protects the programme and the commercial position.
NUAR and PAS 128 in plain English
/> NUAR is a national platform that aggregates digital plans from asset owners into one map. It helps you see who has plant where, compare alignments, and get a quick handle on routes that may clash with your works. It is powerful for planning, but it is not a permit to break ground. Records can be incomplete, imprecise or out of date.
PAS 128 sets out how to survey for underground utilities using graduated levels of effort and confidence. At one end, it covers desktop collation and reconnaissance; at the other, detection using tools like electromagnetic locating and ground-penetrating radar, plus verification by exposing services. The output gives you a defined level of positional certainty, attribution of service type where possible, and a format for drawings and data. It’s the ground truth you need to turn NUAR’s big picture into safe, buildable detail.
When you combine the two, you move from “likely location” to “confirmed location,” and you do it where it matters. Use NUAR to target survey effort, and PAS 128 to prove the corridor you intend to excavate, drill or pile.
How pairing works from tender to trench on a UK programme
/> Begin at tender. Pull NUAR data to understand the density of services, interfaces with third parties and likely diversion pressure. That informs prelims (traffic management, suction excavation, survey allowances), design risk registers and early stakeholder engagement. As designs firm up, commission a PAS 128 survey to a level proportionate to risk across work zones, not just the footprint.
Push both datasets into your CDE, aligned to the same coordinate system and survey grid. The BIM/geomatics lead should structure layers so site engineers, temporary works, and groundworks supervisors can interrogate and export clean sets to GNSS or total stations. Build the utility model into clash checks with drainage runs, piling mats, duct banks and crane bases. Do a focused verification in the week before breaking ground in high-risk corridors; conditions and usage change.
Scenario: A civils team is upgrading a town-centre public realm with new kerb lines, ducting and a foul connection. The planner has a tight road-opening window and night works only. NUAR shows a cluster of telecoms and a gas main along one kerb; desktop mapping suggests enough room for the foul run. A PAS 128 detection survey confirms the gas main sits 400 mm off the expected line and a redundant telecoms duct is actually live. A late tweak shifts the duct route to the carriageway, and a handful of vacuum-excavated trial holes verify depths where the crossing is tight. The permit to dig is issued against the verified model, and the groundworks subbie receives a simple, dated utility pack synced to the CDE.
# Pre-excavation pairing checklist
/>
– Obtain the latest NUAR extract for the exact work extents and adjoining tie-ins; note known poor data areas from asset owners.
– Commission PAS 128 surveys with defined corridor widths, target locations and confidence levels aligned to risk and method.
– Fix the project coordinate system and datum for all utility data; document it in the model and on printed plans.
– Attribute each utility in the combined model with source, date and confidence so site teams know what they are looking at.
– Schedule verification (trial holes, suction excavations) at clashes, crossings and plant locations like crane pads and sheet piles.
– Embed utility constraints in RAMS, permits to dig and daily briefings; include no-go zones and tolerances for hand-digging.
– Log changes: if design shifts or a stakeholder updates records, record the delta and issue a controlled revision to all affected trades.
Pitfalls and fixes when combining NUAR and PAS 128
/> Data currency is the first trap. NUAR pulls from asset owners who update on different cycles, and PAS 128 outputs can age fast on busy streets. Fix by date-stamping all layers, setting review points before major milestones, and refreshing the most sensitive corridors.
Another trap is misalignment. Utility records might be drawn to historic grids or local assumptions. If your PAS 128 survey and NUAR extract aren’t sitting on the same coordinate system, your supposed clearance could be fiction. Fix by making geomatics sign-off a formal gate before any setting out.
Detection blind spots are real. GPR struggles in clays and under saturated ground, and electromagnetic locating needs live metallic conductors. Don’t assume invisibility means absence. Fix by increasing verification density where conditions are poor and switching techniques where appropriate.
Finally, over-scoping or under-scoping the survey wastes money or invites risk. You don’t need Type A verification across the whole site, but you do need it at pinch points. Fix by using NUAR to target and phase your PAS 128 effort, then escalate only where the build demands it.
# Common mistakes
/>
– Treating NUAR polylines as safe dig lines. They are a planning aid, not a substitute for detection and verification.
– Issuing multi-source utility drawings without a clear legend and confidence labelling. Crews can’t make safe choices if they can’t read the risk.
– Freezing design before the PAS 128 deliverable is coordinated into the model. That bakes in clashes and late-night RFIs.
– Ignoring service owner engagement. If you don’t talk to them early, permissions, shut-offs and standby requests will capsize your programme.
What to watch next? Expect tighter data standards from asset owners feeding NUAR, wider adoption of handheld and vehicle-mounted GPR, and more clients insisting on auditable utility QA trails. For now, the winning move is simple: use NUAR to see the field and PAS 128 to prove the line before you cut into it.
FAQ
/>
Do we still need a PAS 128 survey if NUAR is available?
Yes. NUAR is a powerful planning tool, but it isn’t a verified record of exact positions or depths. A PAS 128 survey brings measured confidence to the specific corridors you will excavate or drill. Use NUAR to focus where you spend survey money, not to replace it.
# Who owns and can share NUAR data on a project?
/> Access to NUAR is controlled, and use is typically limited to defined project purposes. Clarify in appointments who will request access, store extracts and distribute them within the team. Keep sharing within your CDE with access controls, and avoid re-publishing outside agreed channels.
# How do we handle subcontractors using different utility models?
/> Set the project utility model and drawing set as the single source of truth, with versions and dates clearly marked. Include the model in subcontracts, RAMS requirements and permit-to-dig procedures. If a subbie brings their own data, fold it into coordination formally and reissue, rather than running parallel plans on site.
# What QA evidence should we retain to defend programme and safety decisions?
/> Keep the NUAR extract dates, PAS 128 scope and deliverables, verification photos, trial hole logs, and method statements tied to specific utility constraints. Store change logs and revised drawings showing who approved what and when. This record helps with audits, claims and lessons learned.
# How often should we refresh NUAR data and surveys during delivery?
/> Refresh when your workfront moves, when design changes affect corridors, or when asset owners advise updates. For long programmes or high-risk streets, plan periodic checks and targeted re-surveys rather than blanket repeats. Tie refresh points to gates like permit renewals, traffic management switches or major deliveries.
