Utility coordination, SUE review support, and conflict intelligence

A clearer way to review surface and subsurface conflicts before design is locked.

SubSync Maps helps engineering teams bring GPR, utility GIS, 811 history, CAD alignments, floodplain context, wetlands, soils, and field notes into one review package built for constructability conversations.

Discuss a pilot partnership See the review workflow
Inputs
CAD, GIS, GPR, 811, as-builts
Outputs
Map view, conflict cards, CSV, PDF
Use case
Design review before field surprises

Greenville Utility Corridor · Review Package

Conceptual product view showing combined surface overlays, subsurface utilities, exact conflict markers, and review cards.

For civil design teamsSubdivision, corridor, site, and municipal utility reviews.

For SUE workflowsQuality-level aware review support, not a replacement for the engineer-of-record.

For owner coordinationConflict matrices, review notes, and exports built for project meetings.

The problem engineers already know

Utility risk is usually discovered across too many files, too late in the design cycle.

Plans, GIS layers, 811 history, marked utilities, record drawings, field notes, wetlands, floodplain limits, and soils rarely arrive in the same coordinate system or the same review format. SubSync Maps is being built to make that review legible before the project team is arguing from screenshots, PDFs, and half-updated spreadsheets.

The goal is not to replace professional judgment. The goal is to give the project engineer a sharper first pass: what crosses, what is close, what needs field verification, what can likely be designed around, and what should be elevated before a coordination meeting.

Surface plus subsurface context

A review workspace for the constraints that actually change designs.

01

Utility conflict intelligence

Compare proposed alignments against existing gas, water, sanitary, storm, fiber, electric, abandoned lines, and GPR indications. Conflict cards capture severity, geometry basis, clearance logic, confidence, and reviewer disposition.

02

Surface review overlays

Bring floodplain, wetland, soil, contour, and public infrastructure context into the same map so drainage, environmental, and utility review conversations happen in one place.

03

ASCE 38-informed framing

Track source confidence and quality-level context with cautious language that supports engineering review without pretending software can stamp a deliverable.

04

Meeting-ready exports

Generate a concise PDF, Markdown summary, and conflict matrix CSV that can support internal design review, owner coordination, and follow-up field verification.

How a pilot review would run

Built around the way engineering teams already coordinate utilities.

  1. 1

    Collect the project package

    Upload CAD, GIS, GPR exports, as-builts, 811 ticket history, field notes, and available surface constraint layers.

  2. 2

    Normalize and classify layers

    Identify proposed versus existing utilities, utility type, confidence, source, and whether a layer is exact geometry or AOI review context.

  3. 3

    Run conflict detection

    Flag crossings, proximity issues, vertical-clearance concerns, GPR uncertainty zones, and surface review items that need engineering judgment.

  4. 4

    Review and disposition

    Move each item through statuses such as valid concern, needs field verification, accepted risk, false positive, or resolved.

  5. 5

    Export the coordination package

    Leave the meeting with a map exhibit, conflict matrix, source notes, methodology, and next-action list for the project team.

Designed for engineering firms

Partnership-first software for firms that already understand the field reality.

We are looking to partner with engineering firms that want to help shape SubSync Maps around real project conditions, not abstract demo data. The best pilots are corridors, municipal utility upgrades, commercial sites, campus projects, and land development jobs where utility coordination already consumes senior review time.

  • Review proposed utility alignments against existing records and field indications.
  • Separate exact geometric conflicts from surface or AOI review items.
  • Document reviewer notes in a format your design team can actually use.
  • Build toward a shared utility database useful to 811, counties, municipalities, and infrastructure owners.

Pilot partnership

Bring us one real project. We will help turn scattered utility information into a review package your engineers can critique.

SubSync Maps is being developed with engineering partners, not in isolation. We want the uncomfortable feedback: missing fields, wrong assumptions, bad layer names, export gaps, and the review steps that matter before a PE is willing to rely on the package.

Start a pilot conversation Review the product view