Buried-utility uncertainty is a design problem before it becomes a field problem.
A utility conflict rarely arrives as a single surprise. It begins as an unowned gap: a line that is mapped at the wrong level of confidence, a relocation decision without a due date, or a field change that never returns to the design record. By the time a crew finds it, the job is negotiating access, sequence, cost, and safety at once.
Federal Highway Administration guidance treats Subsurface Utility Engineering (SUE) as a risk-management process—not a one-time locating exercise. The work is to collect the right level of utility information, identify the conflict, decide whether to protect, relocate, or design around it, and keep the stakeholders working from the same record.
TODAY’S DECISION
Make the utility conflict matrix a controlled design deliverable.
For every open conflict, name the affected utility, evidence quality, owner, proposed resolution, required decision, and date that resolution must be reflected in the field package.
THE FIELD CALL: Before the next excavation release, ask: “Which utility assumption still lacks enough evidence for this workfront?” Assign one owner and one next verification step.
Make the matrix live
Separate evidence from assumption. Record what is known, how it was established, and what still needs confirmation. A mark on a plan is not the same as a verified location or an approved relocation.
Connect every conflict to a workfront. Describe the package, area, activity, and sequence affected. That turns a utilities list into an operational schedule input.
Give each decision an owner and a date. “Coordinate with utility” is not a decision. The record needs the party accountable, the required action, the decision deadline, and the trigger that escalates an unresolved item.
Return the result to the field package. When conditions, locations, or sequencing change, the updated answer must reach the team that will build the work—not remain in a meeting note.
Why this matters
FHWA describes SUE as a way to locate and map utilities early enough to manage conflicts through design, construction, and beyond. Its utility-conflict resources make the same operational point: late discoveries create delay, cost, safety exposure, and redesign. The valuable output is not the scan or the spreadsheet by itself; it is a decision record that changes the plan before the crew inherits the uncertainty.
A useful leading measure is simple: at each design or preconstruction gate, count the open conflicts that lack an owner, required evidence level, resolution path, or field-release condition. The goal is not to report a clean spreadsheet. It is to prevent a workfront from being released with an unknown that nobody owns.
Keep the safety boundary clear
Use the matrix to coordinate planning, but do not treat it as a substitute for the applicable one-call, utility-owner, project, and site-safety requirements. Before work starts, the responsible team still needs to follow the controls and verification required for that specific location and activity.
Some teams never seem to stop moving. They're on Attio, the agentic CRM.
It’s your always-on revenue engine: agents and workflows build pipeline, chase every buying signal, and move deals forward alongside your team.
Teams like Parallel, Turbopuffer, and Wordsmith build on Attio. Are you one of them?
Source ledger
FHWA: EDC-8 Subsurface Utility Engineering — SUE methods, quality levels, and conflict-management uses.
FHWA: Subsurface Utility Engineering Program — design-stage utility information, conflict avoidance, and project-delivery impacts.
FHWA SHRP2: Identifying and Managing Utility Conflicts — the Utility Conflict Matrix approach for earlier coordination and resolution.
THE DIG DAILY DOSE — practical decisions for stronger construction teams.