Subsurface Utility Engineering: US Design Teams’ Provider Comparison

Compare Penhall, Bess Utility Solutions and 4Sight by their stated coverage, investigation methods and design deliverables—not locate marks alone. Their descriptions below are vendor claims, not independently verified qualifications. [4][5][6]

Compare the evidence each provider offers

Penhall

• Stated footprint: Markets utility mapping across the United States. [4]
• Investigation methods: Lists ground-penetrating radar (GPR), electromagnetic locating and vacuum excavation. [4]
• Design deliverables: Advertises CAD DWG/DXF or PDF plans, georeferenced data, BIM-compatible models, and depth measurements and photographs where utilities are exposed. [4]

Bess Utility Solutions

• Stated footprint: Lists offices in Hayward, Fresno, Ontario, Orange and Sacramento, California, plus Phoenix, Arizona—office locations rather than a confirmed project-service boundary. [5]
• Investigation methods: Describes QL-B electromagnetic/GPR investigation, QL-A vacuum excavation and GNSS positioning. [5]
• Design deliverables: Describes CAD/GIS/BIM integration and documentation of assumptions and limitations. [5]

4Sight Utility Engineers

• Stated footprint: Lists headquarters in Whitby, Ontario, Canada, and an office in Philadelphia, Pennsylvania; coverage for a particular US project remains to be confirmed. [6]
• Investigation methods: Lists records research, surface correlation, geophysical designation, multi-channel GPR and test holes/vacuum excavation. [6]
• Design deliverables: Says deliverables may include record summaries, mapped utilities, field-designation results, test-hole documentation, CAD-ready data and quality-level communication. [6]

Separate agency requirements from vendor advice

Hawaii Department of Transportation’s procedure applies to Hawaii highway projects and uses CI/ASCE 38-02; these providers reference ASCE 38-22. [2][4][5][6] Identify the applicable owner or agency requirements and referenced standard edition before turning a service description into a specification.

HDOT allows quality levels to vary by phase, work type and location. [2] Bess calls QL-B the minimum for design work; that is vendor advice, not an interchangeable statement of HDOT’s requirements or a national mandate. [2][5] Likewise, treat Penhall’s “QL-A is required” language as vendor guidance, and treat Penhall’s accuracy statements and Bess’s ROI figures as marketing claims rather than independently established results. [4][5]

These vendor pages do not substitute for the ASCE 38-22 text; verify tolerances and contractual effects against the standard and agency specifications. [4][5][6] Keep additional commissioned evidence distinct from agency obligations.

Choose information quality for each design decision

Scope evidence by location and design question rather than assigning one quality level everywhere. HDOT’s procedure separates four kinds of evidence: [2]

• QL-D: Records and verbal recollections.
• QL-C: Surveyed visible features correlated with records.
• QL-B: Geophysical horizontal designation tied to project control.
• QL-A: Exposed, measured horizontal and vertical positions at specific points. [2]

Commissioning example: Request horizontal evidence for preliminary conflict screening, then targeted exposure where a crossing’s vertical relationship controls the design. This illustrates HDOT’s staged approach, not a universal minimum. [2]

Use HDOT’s work-type chart in the original document for project minimums. [2]

Specify deliverables and unresolved uncertainty

Build each location-specific scope entry around the design question, required evidence, requested quality level, utility ownership/status, assumptions, unresolved uncertainty, deliverable and escalation trigger. This combines HDOT’s investigation framework with practical conflict-data guidance. [2][3]

• Specify a utility record integrated into base plans/CADD, plus a query-capable data handover where needed. [2]
• Agree test-hole locations with the designer before fieldwork; request written logs, depths and mapped QL-A points. These deliverables follow HDOT’s model, not a national mandate. [2]
• Require depiction of unknown-function, unknown-status and unknown-ownership lines at a quality level commensurate with the task. Do not treat any level as proof that all unknown utilities are absent. [2]

Keep this design-evidence commission separate from public locate notices and excavation execution. The Dig Daily Dose’s practical guidance cautions that conflict documentation does not replace applicable one-call, utility-owner, project or site-safety obligations. [3]

Assign responsibility for conflicts and design changes

The Dig Daily Dose’s commentary—not a contract standard—recommends linking each open conflict to its utility, evidence quality, owner, proposed resolution, required decision and field-package update deadline. [3] Include package, area, activity, accountable party, next action and escalation trigger; distinguish evidence from assumptions and return location, condition or sequencing changes to the field package. [3]

Name who interprets findings, approves design revisions, coordinates with utility owners, and updates the conflict matrix and issued files. HDOT provides an agency-specific model: conflict workshops and ongoing interpretation, with resolution support addressing alternatives, tasks, costs, durations and responsibilities. [2]

Define acceptance around usable evidence and documented open decisions—not a promise that every conflict is resolved or unknown utility eliminated. Keep unresolved items visible and assigned. [2][3]

Verify the proposed team

Use FHWA’s provider-selection guidance to request evidence tied to the proposed team: [1]

• Technical delivery: Examples demonstrating designating, locating and data-management competence, capacity to perform the scope, surveying to project control, and transfer into the agency’s CADD system or plans. [1]
• Accountability: Personnel responsible for the work and deliverable certification; engineer/surveyor employment and registration consistent with applicable state requirements; and a project manager who has been involved in managing at least one SUE contract and has sufficient availability. [1]
• Resources and protection: Staffing, concurrent-project capacity, financial capacity, suitable detection, nondestructive-exposure and survey equipment, compatible software, errors-and-omissions protection, and agency-specified insurance. [1]

What to confirm with each provider

The cited Penhall, Bess Utility Solutions and 4Sight pages do not establish provider-specific state licensing, certified staff rosters, references or audited performance, and do not state prices or the commercial terms below. [4][5][6]

• Coverage and qualifications: Project-specific availability, state licensing, proposed staff, references and evidence of comparable work.
• Price: Rate cards, minimum project value, quote validity and payment terms. Request the same breakdown for records review, designation, surveying, test holes, data delivery, conflict workshops, revisions and additional mobilizations.
• Contract: Duration, cancellation terms, warranties, service-level commitments and provider-specific insurance limits.
• Changes and support: Quantities and assumptions affecting price, additional-authorization triggers, approval responsibilities, included interpretation and revision support, and turnaround commitments.

HDOT allows requested conflict-resolution support on a time-and-material basis—an agency-specific example of why support pricing should be explicit, not a presumed term for these providers. [2]

Choose against the commission: verify coverage and the proposed team, agree decision-specific evidence and acceptance criteria, then compare actual quotes and contract language. Select for demonstrated ability to deliver the agreed evidence and support, with remaining uncertainty and responsibilities documented. [1][2][3]

References

1. Selecting a Provider – Subsurface Utility Engineering – Utility Program – Design – Federal Highway Administration (dot.gov)
2. HDOT SUE Procedures enclosure (hawaii.gov)
3. Treat Utility Conflict Data as a Design Deliverable (thedigdailydose.com)
4. Subsurface Utility Mapping for Construction | Penhall (penhall.com)
5. Utility Locating & ASCE 38-22: What Engineers Must Know (bessutilitysolutions.com, 2026)
6. ASCE 38 Standards – 4Sight Utility Engineers (4sightue.com)