The UK’s National Underground Asset Register is moving from policy to everyday tool, and site teams are asking a blunt question: how do we make our utility avoidance workflow NUAR-ready so we actually reduce strikes? The answer isn’t a single app or a shiny survey; it’s a practical chain linking desk-based data, detection methods, permits, and on-the-day decisions. Done well, asset information becomes living context for RAMS, the permit-to-dig, and line marking. Done poorly, it’s another file on the server while the ganger follows spray paint laid over guesswork.
TL;DR
/>
– Build a single utility dataset that blends NUAR data (where available), stat plans and PAS 128 outputs, tied to a controlled permit-to-dig.
– Treat NUAR as a starting layer, not a substitute for detection: combine GPR/EML, trial holes and hold points.
– Define roles: a utility coordinator curates data; supervisors brief crews daily; surveyors capture as-builts for closeout.
– Bake location accuracy, date and source metadata into every utility record so it’s shareable and auditable.
– Use checklists, not hope: permit conditions, scan photos, mark-ups and sign-offs all aligned to HSG47 principles.
NUAR in plain English: the site view that matters
/> NUAR is a central service designed to surface underground asset information from multiple owners through one interface. For construction, its value is that it reduces the paper chase and conflicting “stat plan” packs that overwhelm a pre-start meeting. But NUAR is not a magic x-ray. It is an upstream data resource that, when combined with PAS 128 surveys, site detection and methodical supervision, cuts uncertainty and time.
To make a workflow NUAR-ready, standardise three things. First, geo-reference: keep all utility data in a consistent UK coordinate system and tie it to your control network. Second, provenance: record source (NUAR, client records, utility owner extracts, PAS 128 QL level, trial pit), date accessed, and who approved it. Third, accessibility: put it into a GIS or model the team can open on a tablet and print for the gang box, not just a CAD drawing trapped with the engineer.
The site versions of these themes are simple. The permit-to-dig must reference the same layers the supervisor is using in the field. The RAMS must state detection methods and hold points clearly. And when a kerb line shifts or a duct route flexes by half a metre, the change needs to travel back into the dataset within 24 hours, not wait for a distant as-built.
On-site: turning NUAR data and surveys into safer digging
/> A pragmatic NUAR-ready approach starts at pre-construction. The principal contractor nominates a utility coordinator to assemble a single composite map from NUAR (where access is granted), the client’s record drawings and any existing surveys. That dataset is checked by the design lead, then passed to a utility survey subcontractor to scope PAS 128 detection in risk areas. The output is layered into the common data environment and linked to a digital permit-to-dig template.
On site, supervisors receive printed extracts and tablet access. Before any excavation, the team follows HSG47-aligned steps: interpret plans, scan with EML and GPR where appropriate, mark the ground, and hand-dig trial holes to verify and expose. Only then does mechanical excavation commence, with hold points and sign-offs captured in the permit.
Here’s a real UK scenario. A town-centre streetscape scheme is replacing pavements and adding new EV chargers on a night-shift programme. The site manager has delivery windows from 21:00 to 05:30, the council wants lanes reopened by 06:00, and the QS is watching prelims bleed. The utility coordinator has layered NUAR outputs with recent PAS 128 QL-B findings along the charger feeder routes. Mid-week, a late design tweak nudges a kerb line by 300mm to protect trees, dragging a duct route with it. The ganger raises the clash risk because the sprayed marks now ride a suspected gas main. The supervisor pauses, opens the dataset on a tablet, runs a quick EML sweep, and insists on a trial pit at the new kink. The service is 200mm off the record in a pinch-point, but confirmed and protected in time; the EV duct goes in with a protective board, the lane opens on schedule, and the team captures an as-built to feed back into the project record.
That outcome depends on coordination, not luck. The NUAR-informed layer gave context fast; the permit and detection regime enforced reality; and the as-built created a traceable closeout.
Pitfalls and fixes for NUAR-ready utility avoidance
/> The main trap is assuming NUAR will tell you exactly where everything is. It won’t. What it reliably does is consolidate record knowledge so you start from one map, not seven conflicting ones. Your controls are the detection plan, the permit and the supervisor’s judgement.
H3: Common mistakes
– Treating NUAR layers as a replacement for PAS 128 surveys. They complement each other; you still need detection in risk zones.
– Skipping metadata: saving screenshots without date, coordinate system or source. That kills traceability when something moves.
– Over-marking the ground with six colours and no legend. Crews then follow the brightest paint, not the safest route.
– Leaving as-builts to the end of the phase. Memory fades, shifts occur, and the final record becomes a best guess.
Fixes that work focus on roles, hold points and data shape. Give the utility coordinator authority to freeze and tag the dataset for each work area. Put permit conditions in plain English with photos of markings, scan outputs and signatures. Structure the survey scope so detection targets the highest-risk sections first, and add explicit re-scan triggers: design change, unexpected obstructions, or a missed depth tolerance. Lastly, make the as-built a live task: capture exposed services with GNSS/total station and photos before backfill, and push updates to the model overnight.
Checklist for NUAR-ready permits and digs
– Pin a single composite utility map to the work area, tagged with date, source layers and coordinate system.
– Attach detection evidence: EML/GPR screenshots or logs, with operator name, equipment type and time.
– Define hold points: no machine digging until trial holes verify location and depth at crossings and tie-ins.
– Record redlines in the field app with geolocation and brief notes; sync to the CDE by end of shift.
– Capture as-built positions of new ducts and confirmed existing services before backfill, with photos.
– Brief every gang with a short toolbox talk on that night’s utility risks and what to do if findings differ.
– Escalate any deviation over tolerance to the utility coordinator immediately; adjust permits accordingly.
Beyond the core workflow, consider interfaces. Groundworkers, utilities surveyors and electricians often cross over the same trench. Nominate a trench controller per area. Plant operators should see the same live map as the supervisor; a paper-only pack in a cab at 02:00 invites error. Commercially, price in detection and trial holes early and defend them at value-engineering stage—removing them shifts risk back to site and increases strike exposure.
A word on accuracy and coordinates. Urban canyons and tree cover can degrade GNSS; plan for total station tie-in and control points near workfaces. If subbies bring their own scanners or handheld GNSS, agree common control and data export formats up front. Small alignment gaps snowball when you’re threading a 110mm duct between three live services.
NUAR does not remove the need for utility owners’ engagement. Where you hit missing or contradictory data in critical corridors, pick up the phone and ask for clarifications or standby attendance. It’s slower, but cheaper than a strike, a claim and a delayed handover.
The UK market will move quickly as asset owners improve their feeds and NUAR coverage grows. Watch for clients beginning to require NUAR-aligned metadata in as-builts and for digital permits becoming standard in frameworks—teams that can demonstrate that chain end-to-end will be safer and faster.
FAQ
/>
How do we actually get access to NUAR information on a project?
Access routes are controlled and typically require organisational onboarding and user permissions. On many schemes you’ll still rely on the client or designer to supply NUAR extracts alongside utility records. Agree early who will request and maintain access, and set a refresh cadence so you’re not digging on stale data.
# Does NUAR replace a PAS 128 utility survey?
/> No. NUAR aggregates record information from asset owners, which is a starting point. PAS 128 surveys add detection confidence and are still needed where you plan to excavate, especially in congested corridors. Treat NUAR as context and PAS 128 plus trial holes as the verification that drives permits.
# Who owns the utility data we create on site, and can it flow back to NUAR?
/> Ownership usually sits with the client under contract, with the principal contractor responsible for producing accurate as-builts. NUAR’s data supply is primarily from asset owners, so contractor updates generally route back via the client or the utility owner’s processes. Make your outputs NUAR-ready by including clear metadata, coordinates and provenance so they’re usable downstream.
# How do we make subcontractors follow NUAR-ready workflows?
/> Bake the requirements into subcontracts: digital permits, detection evidence, hold points and as-built capture. Induct crews with the live dataset and make supervisors accountable for sign-offs. Audit with spot checks on scan logs and permit packs, and link compliance to payment milestones where appropriate.
# What if GNSS doesn’t work well in our location?
/> Plan for a mixed approach: establish control points and use total stations to tie utility positions into the site grid. Capture photos and sketches with dimensions when visibility or access blocks perfect survey shots. The aim is a traceable, consistent record rather than chasing theoretical centimetres you can’t practically achieve on a night shift.
