Service clashes
Check service clashes before work reaches site
Compare the proposed works with the service information you actually have.
Project Prime · Practical checklist
Bring the records into one view
Use the current design, survey, utility records, DBYD information and known service levels. Record the revision and source of each file so the project team can see what was checked.
Separate a clash from an unknown
A confirmed level conflict needs design review. A service with no reliable depth or alignment needs investigation. Do not present incomplete records as certainty.
Give the team a decision list
Return marked-up views and a short clash register showing the location, affected design element, available evidence and the next question. Service locating, potholing and engineering approval remain separate project tasks.
General preparation notes. Confirm the requirements, methods and approvals for your project with the responsible team.
Discuss this task