The Utility Coordination Field Guide for 2026

If you have run more than a handful of urban construction projects in the last three years, you already know the punchline: utility coordination is now the single largest driver of schedule risk on most jobs. Not weather. Not labor. Not inspection backlogs. Subsurface conflicts and joint-trench sequencing failures account for more lost days than any other category we instrument, and the trend has accelerated as fiber and small-cell density has filled the urban right-of-way to capacity.

This guide is the working version of how we run utility coordination across active programs. It is written for owners, program managers, and senior PMs who already understand that utility risk is a design problem first and a construction problem second. For the full service description, our Utility Coordination service page covers scope, deliverables, and pricing structure in detail.

The shape of the problem in 2026

Three structural changes have made utility coordination harder than it was even five years ago. First, the density of subsurface infrastructure in major urban corridors has roughly doubled since 2019, driven by fiber buildouts, small-cell deployments, and EV-charging service expansions. Second, the underlying utility records, especially for gas and legacy water mains, have aged out of reliability faster than they have been updated. Third, one-call systems are operating at sustained capacity in every top-fifty metro, which means the locate ticket you submit today is not the same instrument it was a decade ago.

We went deep on the macro picture in Utility Coordination Is Eating Construction Schedules. The short version: the chance that a given urban project will encounter at least one undocumented subsurface conflict is now north of eighty percent. The question is no longer whether you will hit something. It is whether you will find it during design or during excavation.

“By the time a backhoe finds a utility, the cheapest version of the answer is already gone. The work is to find it months earlier.”

The principle: pull the discovery left

The operating principle behind everything that follows is simple. The cost of resolving a utility conflict scales roughly with the phase you discover it in. A conflict surfaced during design review costs hours. The same conflict surfaced during permit review costs weeks. The same conflict surfaced during excavation costs the entire week the trench is open, plus the demobilization, plus the rebooking of every downstream trade.

Every practice in this guide is, in some form, an attempt to pull the discovery left. The earlier the conflict is on the timeline, the cheaper it is to fix. Everything else is detail.

Step one: build the composite before you commit to a design

Before a design team is asked to make irreversible alignment decisions, somebody needs to produce a composite drawing that reconciles every available utility record for the corridor. That means pulling as-builts from each owner, requesting record drawings from the franchise providers, submitting design-stage one-call tickets, and overlaying the results on a single base map. It is not glamorous work and it is the single highest-leverage hour in the project.

The composite is rarely complete on the first pass. The point is not completeness, it is to surface the gaps early enough that the team can scope a quality-level-A or quality-level-B subsurface utility engineering investigation against the right segments rather than blanket-surveying the whole corridor. Targeted SUE is dramatically cheaper than comprehensive SUE, and it is only possible if the composite tells you where to point the equipment.

Step two: run the joint-trench sequencing meeting before the permit

Joint-trench failures almost always trace back to a sequencing meeting that either did not happen or happened too late. The meeting is the moment where electric, gas, telecom, CATV, and any wet-utility owners with adjacent work agree on the trench schedule, the conduit handoff, the proof-of-grade requirements, and who is responsible for which inspections.

Held before permit submission, the meeting takes two hours and produces a sequencing document that becomes part of the submittal. Held after permit issuance, the same meeting takes three weeks of back-and-forth because every utility now has a customer commitment on its calendar that did not exist a month ago. The cost differential is enormous and the leverage is almost entirely in the calendar.

Step three: lock the outage windows early

For any project that requires an outage on an active service, the outage window is the gating constraint. Treat it that way. Identify the affected ratepayers, the critical loads, and the notification requirements in the first thirty days of the project, not in the last thirty days before cut-over. Hospitals, data centers, traffic-signal grids, and large commercial tenants typically require thirty to sixty days of formal notice and may impose blackout periods that compress your usable schedule by weeks.

The teams that do this well treat the outage calendar as a contract, not a coordination call. We hold the calendar inside the platform alongside every other project artifact, which means the GC, the owners, and the agency are all looking at the same window. When somebody asks for a shift, the impact is modeled before the answer is given.

Step four: package each utility submittal the way that utility wants it

Every utility has a preferred submittal format, a preferred clearance standard, and a preferred way of receiving design questions. Most of these are documented in the utility's design manual. Almost none of them are followed by the design teams submitting work into them, which is why redline cycles routinely run two or three rounds longer than they should.

The fix is a per-utility submittal checklist maintained at the program level and applied to every package. It is the same principle as the program-wide submittal standard we describe in The External PM Playbook for Multi-Site Rollouts, narrowed to the utility-coordination workstream. The investment pays back inside the first two submittals.

Step five: instrument the corridor

Every interaction with every utility, the call, the email, the field meeting, the redline, the field change, belongs in the corridor's record. Not in somebody's inbox. Not in a notebook. In the platform, attributable and timestamped. The cost of not doing this is that six months into the program, when a utility owner asks why a conduit was placed where it was, nobody can produce the conversation that produced the decision.

Inside PermitPilot, this happens automatically because every coordination event passes through the platform. We described the agent-level mechanics in Inside the Agent Control Center, but the principle is independent of the tool: if it is not in the system, it did not happen, and you will lose a week of schedule arguing about it later.

Where this connects to the permitting workstream

Utility coordination and permitting are different workstreams that fail in the same place. A permit that ignores a utility conflict will not be issued. A permit that is issued without resolving the conflict will produce a stop-work order during construction. The model we run on multi-site programs, described in detail in The External PM Playbook, treats utility coordination as a first-class parallel workstream with its own named lead and its own weekly status reporting into the same executive brief.

The cost of pretending these workstreams are separate is that one of them eventually surprises the other. The cost of integrating them is roughly zero, once the model is in place.

What good looks like by the end of design

A well-coordinated corridor reaches the end of design review with four artifacts in hand: a composite conflict drawing with every resolved and pending issue marked, a contact matrix with named escalation contacts for every affected utility, a corridor master schedule with locked sequencing and outage windows, and a per-utility submittal checklist that has already produced one clean redline cycle for each owner. If any of those is missing, the project is carrying utility risk it does not need to carry.

If you want a senior coordinator to read your corridor and tell you where the gaps are, send us the plan set and we will respond inside one business day. If you want to see how our team runs the workstream end to end, the Utility Coordination service overview and the PermitPilot™ service overview are the right places to start.

Appendix: free working artifacts

Two artifacts compress most of the practice in this guide into something a coordinator can put on a desk Monday morning. The Multi-Site Permit Readiness Checklist includes a utility-coordination section keyed to the four steps above, and the Submittal Package Template ships with the per-utility checklist already in the close-out tab. Both are free behind a one-field email gate and are designed to be edited inside your own program.

If you want to see how this guide sits inside a broader operating model, the External PM Playbook for Multi-Site Rollouts describes the program-level frame, and Utility Coordination Is Eating Construction Schedules covers the underlying market shift driving the urgency.