Utility searches on UK projects are shifting. For years, the default workflow has been LSBUD enquiries plus direct emails to utilities. Now the National Underground Asset Register (NUAR) is being phased in, promising a consolidated map of buried assets from participating owners. Site teams are asking what actually changes for programme, risk and the permit-to-dig.
TL;DR
/>
– LSBUD routes enquiries to registered asset owners, who reply with their own plans; NUAR aims to show multiple owners’ assets on a single map.
– In the near term, treat NUAR as an additional source, not a replacement: coverage is growing but not complete, and utility consents still sit with the asset owner.
– Your permit-to-dig and CAT & Genny workflow stays essential; neither NUAR nor LSBUD removes the need for on-site detection and trial holes.
– Expect better early-stage planning from NUAR’s consolidated view, but maintain LSBUD and direct contacts for formal records and approvals.
– Update procurement, RAMS and CDE protocols to manage two data sources, versions and expiry dates without confusion.
Plain-English: NUAR, LSBUD and the gap they fill
/>
– LSBUD (LinesearchbeforeUdig) is an enquiry service: you submit a dig location and it notifies participating utility owners. Those owners then send you their plans or instructions. Coverage is broad but not universal, and replies arrive separately to your inbox or portal.
– NUAR (National Underground Asset Register) is a central digital map intended to show underground assets from multiple owners in one place. It is being rolled out in phases. The goal is a consistent view for planning and safer digs, with secure access and data sharing agreements in the background.
– Key difference: LSBUD orchestrates communication with owners; NUAR aggregates and displays data from owners who feed it. LSBUD’s output is a set of owner-issued plans and directions; NUAR’s output is a composite map for situational awareness and planning.
– What doesn’t change: on-site verification with CAT & Genny, vacuum excavation or trial holes, and any owner-specific requirements for permits and proximity working. Neither tool replaces competent supervision or safe systems of work.
On-site workflow: from enquiry to shovel
/>
– Early design and tender: Use NUAR (where available) to get a quick multi-utility picture that informs design optioneering, buildability, and pricing. This helps pre-empt service clashes or diversion scope before design freeze. Still run LSBUD enquiries to capture owner-issued conditions that could materially affect cost and programme.
– Pre-construction: Collate LSBUD responses, any direct utility replies, and NUAR outputs into the CDE. Publish a utilities register noting source, date, coverage, and key constraints. Align with your permit-to-dig process so supervisors understand which documents are advisory (NUAR) and which are owner-issued (LSBUD responses and direct plans).
– Site mobilisation: Brief gangs using the combined utilities plan. Mark anticipated corridors and high-risk zones on the ground. Confirm control measures from RAMS: plant type limits, hand-dig extents, standby supervision, exclusion zones, and temporary works for trial holes.
– Day-of-dig: Validate with CAT & Genny and trial holes before mechanised excavation. Record as-built deviations and feed back into the CDE with clear attribution (observed vs documented). Where NUAR shows a service that isn’t in LSBUD responses—or vice versa—treat it as a red flag and escalate to the PC’s utilities coordinator for resolution before proceeding.
A live UK scenario: congested high street drainage connection
/> A civils crew is delivering a new drainage connection for a mixed-use block on a tight high street. The programme is squeezed by night-time traffic management windows and a planned concrete pour in three days. The PM asks the utilities coordinator for a clear go/no-go on excavation depth and route. NUAR shows multiple comms ducts and a low-voltage cable cluster that aren’t on the architect’s drawings. LSBUD enquiries return separate plans: the water company imposes hand-dig within 3 m of its main; one fibre operator doesn’t respond within the expected window. The site engineer updates the trench route and books a vacuum excavator for initial potholing. On the night, the crew locates an unrecorded spur not present in any dataset, adjusts the trench edge and logs coordinates. The pour goes ahead, but only after a short delay to amend RAMS and secure standby supervision for the remainder of the dig.
Pitfalls and practical fixes
/>
– Assuming NUAR is complete: Coverage is expanding but not universal. Fix: treat NUAR as planning intelligence and confirm with LSBUD, direct owner checks, and on-site verification.
– Version confusion: Screenshots and plan PDFs proliferate. Fix: store source-tagged files in the CDE with dates, owner, and scope polygons; expire them on a set cycle and re-run checks before critical digs.
– Over-reliance on PDFs: Static plans can be misread on site. Fix: take GIS extracts aligned to your grid, produce clear snapshots for briefings, and pair them with on-ground markings and competent supervision.
– Delayed coordination: Utilities risk sits across design, pre-con, and delivery. Fix: appoint a utilities coordinator, run a weekly clash review during enabling works, and log unresolved gaps with clear hold points.
# Common mistakes
/>
– Treating NUAR as a permit to dig. It is not an approval; it’s a planning tool that must be backed by owner instructions and site validation.
– Believing LSBUD covers every owner. Some networks aren’t on LSBUD; always check local knowledge and consider direct enquiries where critical.
– Ignoring data currency. Out-of-date plans can miss diversions or new connections; build plan refreshes into your short-term lookahead.
– Skipping trial holes because the map looks clean. Underground reality is messy; potholing remains a reliable way to avoid cable strikes.
Quick checklist for PMs and site engineers
/>
– Define which stages will use NUAR for planning and which will rely on LSBUD or direct owner plans for permits and RAMS.
– Capture all responses and NUAR views in the CDE with unique IDs, dates, and coverage notes; include a map of what’s not covered.
– Set hold points: no mechanised dig until CAT & Genny, potholing, and sign-off by a competent supervisor are complete.
– Agree with supply chain who pays for searches, potholing, and standby protection; write it into subcontracts and pre-start minutes.
– Build utilities risks into the programme: traffic management windows, plant limitations, standby supervision, and potential rework.
– Train supervisors on interpreting multi-source plans and reconciling discrepancies, with a simple escalation flow for conflicts.
What changes for UK sites in practice
/>
– Planning clarity improves: NUAR’s consolidated view can expose multi-utility conflicts earlier, supporting design tweaks before cost and time pile up. LSBUD remains your route to owner-specific constraints and conditions; keep running it alongside NUAR until coverage and processes mature.
– Permit-to-dig stays the spine: Your permit should list sources used, their dates, and any unresolved gaps. Treat any inconsistency between NUAR, LSBUD replies, and field evidence as a stop-and-think moment, not a footnote.
– Procurement and records tighten: Specifications should require supply chain access to both systems where available, define data handling in the CDE, and mandate refresh cycles before intrusive works.
The direction of travel is clear: better data at planning stage, the same disciplined verification before you break ground. Watch for NUAR coverage growth, API integrations into common CDEs, and clearer guidance from asset owners on how NUAR sits with their own consent processes.
FAQ
# Will NUAR replace LSBUD on my project?
/> Not yet. NUAR’s intent is to provide a consolidated map, but formal owner instructions and permits typically still flow via LSBUD or direct engagement. Treat NUAR as a planning layer and keep LSBUD in your workflow until coverage and owner processes align.
# Do I still need CAT & Genny and trial holes if I’ve used NUAR and LSBUD?
/> Yes. Both tools provide documents and maps, not ground truth. On-site detection and controlled excavation remain essential to manage strike risk and confirm depth, location and alignment before mechanised digging.
# How should I manage data in the CDE when sources differ?
/> Store each source with clear metadata: provider (NUAR, LSBUD, owner), date received, coverage area, and any stated limitations. Use a simple naming convention and set expiry reminders so plans are refreshed before critical activities. When sources conflict, escalate and hold the activity until resolved.
# Does NUAR include private or on-plot services?
/> NUAR focuses on assets from participating network owners. Private laterals, on-plot diversions and temporary site services may not be included. Keep as-built records from previous phases, scan where practical, and verify during potholing.
# What should I write into subcontracts regarding utilities searches?
/> State which searches are required at each stage, who initiates them, and how costs are handled. Require attendance at utilities coordination meetings, adoption of the permit-to-dig process, and timely sharing of as-built and trial hole records. Make sure RAMS reference the latest agreed plans and specify hold points where information is incomplete.
