Building a Utility Conflict Matrix from Civil and MEP Drawings

What Drawing Data Feeds the Matrix

A UCM populated from incomplete or misread drawing data produces conflict classifications that are wrong at the source. Resolution decisions built on that matrix carry the same error downstream into the schedule and the budget. The following drawing types contain the raw conflict data, and each requires specific extraction, not a general pass.

Civil Plan and Profile Sheets

Plan and profile sheet pairs are the primary source for horizontal and vertical utility positions. The plan view shows horizontal alignment and utility crossing locations. The profile view shows invert elevations, cover depths, pipe diameter, and the vertical relationship between crossing utilities.

From the profile sheet, extract the following fields at every crossing station: utility type, size, material, top-of-pipe elevation, invert elevation, cover depth, and crossing station number. Profile sheets frequently show proposed grading that changes the finished grade elevation. Compare existing utility elevations against proposed grade, not existing grade, or your cover depth calculations will be wrong before the matrix is started.

Quality level designations from ASCE 38-22 (Standard Guidelines for Investigating and Documenting Existing Utilities) apply directly here. A utility shown at Quality Level D, meaning it is based on record drawings only, carries far lower elevation confidence than a utility located at Quality Level B through geophysical methods. That confidence difference must be reflected in the conflict severity score, not ignored.

MEP Riser Diagrams and Underground Site Plans

For building projects with underground MEP service connections, the utility coordinator must overlay the MEP engineer's underground site plan against the civil grading and utility plan. The specific services to trace are domestic water service, sanitary sewer lateral, storm drain tie-in, gas service, electrical duct bank, and telecommunications conduit.

Riser diagrams give invert elevations at the building connection point. Work backward from that elevation using the civil profile to determine whether each MEP service crosses any existing utility at an insufficient vertical clearance. The standard industry benchmark is 12 inches minimum vertical clearance between pressure mains and gravity systems, though local utility accommodation policies govern and must be confirmed before populating the matrix.

For more on how MEP vs structural conflicts are identified and documented across disciplines, that article addresses the cross-discipline coordination layer in detail.

Existing Utility Records and SUE Data

Utility owner record drawings and subsurface utility engineering (SUE) data form the input layer. Civil and MEP drawings are the design layer. Conflicts emerge at the intersection of the two. Obtain utility owner record drawings for all utilities within the project corridor before beginning matrix population.

Where potholing or vacuum excavation data is available from a subsurface utility engineering investigation, use the potholed elevation rather than the record drawing elevation. On older infrastructure, these frequently differ by 12 inches or more, which changes the conflict classification from "indeterminate" to "confirmed" or changes the severity tier entirely.

Reading Crossings: Identifying Vertical vs. Horizontal Conflicts

The distinction between a vertical conflict and a horizontal conflict determines the resolution strategy. Vertical means insufficient clearance between crossing utilities. Horizontal means utilities running parallel at inadequate separation, or a proposed utility placed within a recorded easement or right-of-way (ROW) occupied by an existing facility. Mixing these two types in the matrix produces incorrect remediation assignments and wrong responsible-party designations.

Vertical Conflict Identification from Profile Views

At every crossing station, compare the proposed utility's top-of-pipe elevation against the existing utility's invert elevation. The gap between those two values is the available vertical clearance. If that gap is less than the applicable minimum, typically 12 inches for water over sewer, 18 inches in some jurisdictions for gas crossings, log the record as a vertical conflict.

When profile data for an existing utility is unavailable, do not leave the conflict status cell blank. Record the status as "Indeterminate, pending field verification" and assign a SUE or potholing action to the utility coordinator. A blank cell is indistinguishable from a reviewed-and-cleared crossing to anyone opening the matrix later.

Horizontal Conflict Identification from Plan Views

Horizontal conflicts take three forms: parallel encroachment, where a proposed main runs within the minimum separation distance of an existing main; right-of-way conflicts, where a proposed installation encroaches on a recorded utility easement; and angular conflicts, where a crossing geometry makes the installation infeasible for open-cut or trenchless construction.

Annotate plan sheets with applicable separation requirements before populating the matrix. This prevents the matrix from being filled from memory rather than from measured drawing data, which is a common source of classification errors on large corridor projects.

The full drawing coordination process for cross-discipline conflict identification is covered separately, this section focuses specifically on the UCM population workflow.

Conflict Matrix Column Structure Aligned with SHRP2 R15B

The FHWA SHRP2 R15B framework and state DOT master worksheets use a standard column set, but neither document explains the data logic behind each field. The following breakdown specifies what a correct entry looks like in each column group.

• Conflict ID and Sheet Reference. Every record must carry a unique identifier tied to the plan sheet number and station where the conflict appears. The ID must be traceable back to a specific sheet and detail callout without a separate explanation. Anyone on the project team should be able to locate the conflict from the ID alone.
• Utility Owner. Record the legal owner of the existing utility, not the operator or designer. This field has direct reimbursement implications under 23 CFR Part 645. Use the utility owner's legal entity name, not a common name, so that relocation cost responsibility can be accurately assigned during the utility relocation coordination process.
• Utility Type, Size, and Material. These three fields together determine relocation difficulty and cost. A 36-inch prestressed concrete cylinder pipe (PCCP) water main conflicts differently than a 6-inch ductile iron main. The material field also governs trenchless feasibility assessments for conflicts where redesign is the proposed resolution.
• Conflict Type. Assign one primary type per record: vertical, horizontal, or ROW/easement. If a crossing has both a vertical clearance issue and an easement problem, create two records with a cross-reference note in each. Do not collapse two conflict types into one record.
• Conflict Status. Use controlled vocabulary only: Confirmed, Indeterminate, Resolved, Relocated. Free-text status entries make the matrix unusable as a management tool across project phases. Everyone reading the matrix must draw the same meaning from every status field.
• Resolution Action and Responsible Party. State the required action, redesign, relocation, pothole and verify, or waiver request, and name the owner of that action. Embed this assignment in the matrix itself, as addressed in the RACI section below.

Scoring and Prioritizing Conflicts

A large matrix without a consistent scoring method becomes a flat list where a minor clearance issue at a low-traffic crossing ranks identically to a conflict involving a high-pressure transmission main under a critical structure. Project managers cannot triage from a flat list. The following three-tier conflict severity classification provides an immediately applicable framework.

• High severity. The conflict involves a high-consequence utility: a transmission main, high-pressure gas line, high-voltage duct bank, or critical fiber trunk. Resolution requires physical utility relocation rather than a redesign adjustment. Or the conflict intersects a controlling project milestone. Flag all high-severity conflicts to the critical path method (CPM) schedule manager at the time of classification.
• Medium severity. Resolution requires utility owner coordination for redesign or minor relocation, but work can proceed in parallel with design development. The conflict does not affect the critical path under current schedule assumptions, but must be resolved before construction documents are finalized.
• Low severity. The conflict requires potholing or field verification but does not require relocation. Resolution is achievable through subsurface utility engineering investigation or a minor design adjustment without utility owner involvement.

Severity classification carries reimbursement implications. Whether a conflict is categorized as requiring relocation, and whether the affected utility is within its prior rights in the ROW, directly determines who funds the relocation under 23 CFR Part 645. The FHWA Program Guide on Utility Relocations, Adjustments, and Reimbursements specifies the reimbursability criteria. This is a legal and financial consequence of the classification decision, not only a tracking exercise.

RACI: Who Owns Each Matrix Action

A UCM with no assigned owner for each conflict resolution action is a documentation artifact, not a management tool. Embed the responsible party assignment directly in the matrix. A separate RACI chart stored in a different file will become disconnected from the matrix over time.

• DOT/Agency Project Manager. Approves conflict severity classifications, authorizes utility owner coordination, and owns CPM schedule impacts from unresolved conflicts.
• Utility Coordinator. Populates and maintains the matrix, conducts utility owner coordination, tracks resolution status, and escalates indeterminate conflicts that require SUE investigation.
• Design Engineer (Civil/MEP engineer of record). Provides redesign options for conflicts resolvable through alignment change. Confirms that proposed redesigns do not introduce new underground utility conflicts elsewhere in the corridor.
• Utility Owner. Confirms existing utility data, approves relocation scope, and provides a relocation schedule for CPM integration.

Integrating the Matrix into the Project Schedule

Utility conflicts are a leading cause of highway construction delay. An unresolved high-severity conflict that is not reflected in the CPM schedule as a predecessor to construction mobilization will cause a field stop. The matrix output must feed directly into the schedule, not sit in a separate coordination file.

At the time of matrix population, assign a target resolution date to every high-severity conflict. Create a CPM predecessor activity for construction in the affected station range, tied to that resolution date. Review matrix status weekly during design development. Update the CPM whenever a conflict status changes from "Confirmed" to "Resolved" or escalates to a higher severity tier.

The SHRP2 R15B research report addresses schedule integration directly. Reference that document by name when briefing the CPM scheduler on how utility conflict resolution dates become schedule predecessors, the FHWA program page is the stable entry point for accessing that research.

For discipline-specific issues related to civil drainage coordination that often intersect with utility conflict scheduling, that article addresses storm drain and grading coordination separately.

How InspectMind Reviews Civil and MEP Documents for Utility Conflicts

Civil and MEP drawing sets with underground utility crossings contain the exact coordination gaps the UCM is designed to catch. Those gaps are only visible when drawings are reviewed across disciplines simultaneously, not in silos. AI civil drawing review from InspectMind processes the full document set at once, cross-referencing civil plan and profile sheets against MEP underground site plans and utility schedules.

The review flags coordinate conflicts, missing clearance callouts, and inconsistencies between utility records and design drawings. Issues are returned with sheet references and location callouts, giving the utility coordinator a starting point for matrix population rather than a cold drawing set. Reviews start from $50 per upload, no per-user fees. Five or more issues found or a full refund.

For a broader look at how construction document conflict detection works across full document sets, that page covers the underlying methodology.

Frequently Asked Questions

What is a utility conflict matrix and how does it differ from a utility conflict log?

A utility conflict matrix is a structured document that records every identified underground utility conflict with a fixed set of fields: conflict ID, utility owner, type, size, material, conflict type, severity, status, and resolution action. A utility conflict log is typically a simpler chronological list of issues without the structured fields needed for severity scoring or RACI assignment. The matrix is a management tool. The log is a record-keeping artifact.

How do you determine conflict severity when the existing utility elevation is unknown?

When no verified elevation is available, record the conflict status as "Indeterminate, pending field verification" and classify severity as High if the utility type is high-consequence. Assign a potholing or SUE investigation action immediately. Do not defer the severity decision until field data arrives. An unclassified conflict cannot be scheduled for resolution.

Which party is responsible for utility relocation costs when a conflict is identified during design?

Cost responsibility is governed by 23 CFR Part 645 and depends on whether the affected utility holds prior rights in the ROW. A utility installed under permit that predates the highway ROW acquisition typically has compensable rights, meaning the agency funds relocation. A utility installed within the ROW without prior rights is typically relocated at the utility owner's expense. The legal entity name in the Utility Owner field of the matrix is the starting point for that determination.

How does a utility conflict matrix connect to the project CPM schedule?

Every high-severity conflict should generate a CPM predecessor activity in the affected station range, with the conflict resolution date as the constraint. Construction cannot mobilize in that range until the predecessor is cleared. The matrix owner reviews status weekly and updates the CPM when conflict status changes.

What ASCE quality level designation is required before a conflict can be classified as confirmed?

Per ASCE 38-22 ASCE 38 standard for quality levels in subsurface utility engineering, Quality Level B, achieved through geophysical location methods, is generally the minimum required to confirm a conflict as "Confirmed" in the matrix. Quality Level D, based on record drawings only, supports an "Indeterminate" classification. Quality Level A, achieved through actual excavation or potholing, provides the highest confidence and should be used before finalizing high-severity conflict resolution strategies.

At what project phase should the utility conflict matrix be first populated?

The first pass at matrix population should occur during design phase utility review, once utility owner record drawings have been obtained and the civil plan and profile sheets show a committed horizontal and vertical alignment. Waiting until construction documents are finalized means conflicts that require physical relocation will be on the critical path with no design-phase resolution window remaining.