Utility Readiness Advisory · 4–8 Weeks
Before you sign, a utility gap is a negotiation.
After you sign, it's a capital expense.
That is the whole argument for running this work early.
Right now, more than one party wants your project. The utility has a business development motive. The community has a council that can appropriate. The state has a discretionary fund. A missing second feed, an undersized main, a substation that needs an upgrade — every one of those is currently a problem that other people have reasons to help solve, and a term you can put in writing before you commit.
Four weeks after the LOI, the same finding is an invoice. The leverage is gone, the schedule is yours, and the contribution-in-aid-of-construction is a line in your capital budget that nobody forecast. The findings don't change based on when you look. What changes is who pays for them.
Three Engagements Touch the Grid
Which of these is your question?
Utility Readiness Advisory
Corporate side, one project. Can this site — or these three candidate sites — serve my requirement by my date, across power, gas, water, wastewater, and telecom? What does it cost to close the gap, and who should pay?
Data Center Advisory
Corporate and developer side, large load. Power-first strategy for a campus where the energization date is the project schedule, extending into behind-the-meter generation, tariff and PPA structure, and campus phasing.
Regional Utilities Study
Community and utility side. A substation-by-substation read on what an entire region can serve, built for utility ED teams and EDOs preparing for industrial load growth.
If you're not sure, the fit call sorts it in twenty minutes. We'd rather scope you into the smaller engagement than the larger one.
Why This Keeps Happening
The utility answered your question correctly
You asked whether there's capacity. There is. The letter is accurate, the person who wrote it was being helpful, and nobody misled you. But a capacity letter is a snapshot of headroom under normal conditions. Your project needs deliverable service, at your peak, with your redundancy requirement, energized by your date, at a cost somebody has agreed to bear. Each of those is a separate question, and a letter confirming the first says nothing about the other four.
The gaps cluster in predictable places.
Load margin read at nameplate, not under contingency
A substation with comfortable headroom at normal configuration can have none under N-1. If your operation can't take an outage, the number that matters is the one that survives losing a transformer or a feeder — and that's rarely the number in the letter.
"Dual feed" describes several different things
Two feeders off the same substation bus is not the redundancy a critical process needs. Service from two separate substations is. These get discussed interchangeably during courtship and distinguished during engineering — and the second feed is frequently the largest unbudgeted number in the whole project.
Everything except power gets a paragraph
Gas capacity is discussed without distinguishing firm from interruptible transport. Water gets confirmed against process demand when it's usually fire flow that fails. Wastewater capacity gets confirmed hydraulically while the organic loading triggers a pretreatment requirement and a permit modification nobody scheduled.
The schedule is set by procurement, not engineering
Long-lead equipment has been the binding constraint on industrial energization dates for several years running. If the transformer quote runs longer than your construction schedule, no amount of utility goodwill fixes it — and that is a fact you want in Week 3, not after the ground is broken.
Four Phases, One Rule
Specify. Test. Cost. Position.
The rule: nothing enters the report as available capacity unless it carries a source and a date — a utility document, a tariff, a capital plan, or a named conversation with the person accountable for the answer. Sourced, derived, and pending figures stay distinguished throughout.
Service Requirement Definition
The specification the utility should have been given in the first place.
Electrical demand at connected, peak, and coincident load, with the growth case; power quality and redundancy requirement, and what an outage actually costs your process. Gas demand and required delivery pressure, with a firm versus interruptible determination. Water: process demand, plus the fire-flow requirement your building code and insurer will impose, which is often the larger number. Wastewater: hydraulic volume, organic and constituent loading, and anything that triggers pretreatment. Telecom: bandwidth, route diversity, and latency if it's operationally relevant. Then the in-service date you're actually holding.
A written service requirement specification per utility, in the form each utility needs to answer precisely.
Capacity & Deliverability Testing
The phase that produces the verdict.
Electric: substation load margin at your demand under contingency; feeder configuration and capacity on the specific circuit serving the site; dual-feed feasibility — source substations, physical route, transfer scheme, and what it costs; long-lead equipment procurement and current quoted lead times; interconnection queue position and study timeline where applicable; applicable tariff and large-load rate provisions. Gas: upstream capacity, delivery pressure under design conditions, firm versus interruptible transport, curtailment exposure on peak days. Water: source and treatment capacity, distribution pressure and pressure zone, and fire-flow availability tested at the parcel — the failure most often discovered late. Wastewater: plant hydraulic and organic headroom, pretreatment requirements, industrial user permit path, and discharge permit modification timeline. Telecom: diverse physical route count and validated route maps rather than a coverage claim.
A pass / conditional / fail verdict per utility per site, with the binding constraint named and a defensible in-service date for each.
Gap Costing & Schedule Reconciliation
What it costs to close, who should pay, and whether the date survives.
Every conditional finding gets costed and scheduled: the upgrade or extension required, the utility's line extension policy and contribution-in-aid-of-construction methodology, whether any portion is refundable against revenue credits, the design and construction sequence, and the permitting the work itself will require. Then we reconcile against your in-service date — including the dependencies most schedules miss, like the fact that a permit modification can't start until a design exists and a design can't start until a load is committed.
A costed gap register per site, a critical-path schedule to energization and service, and a written risk register.
Leverage & Negotiation Positioning
Findings converted into terms, while you still hold the position.
This is the phase that distinguishes early diligence from late diligence. Each gap becomes a specific ask, benchmarked against what comparable projects have obtained: infrastructure cost-sharing on the substation, main, or extension; written timeline commitments with milestone dates rather than assurances; rate structure and demand charge treatment; capacity reservation and what it takes to hold it; and LOI or purchase agreement language conditioned on utility milestones so the risk sits with the party that controls it. We support you at the table or negotiate alongside your team.
A prioritized ask list with benchmark support, recommended agreement conditions, and negotiation support through commitment.
Why It Matters Who's Asking
We're not selling you the fix
No engineering, construction, or equipment margin
We don't design the substation, build the main, or sell the transformer, and we take no fee from the firms that do. When we tell you an upgrade is required, it's because service can't be delivered without it — not because we're quoting it. We'll tell you who does that work well and take nothing for the introduction.
No transaction commission, no incentive contingency
No brokerage or land commission, and no percentage of captured incentives. Our fee doesn't change based on which site you pick or whether you proceed at all. 'None of these three works on your date' is an available conclusion, and it's sometimes the most valuable one.
We've been the party writing the capacity letter
Hyphen has an economic development practice, and it's the reason this engagement works. We've assembled the utility confirmations, sat with the utility deciding what it could commit to in writing, and taken infrastructure cost-sharing through council approval. We know which claims in a letter are load-bearing, what's held in reserve, and what a community can concede that costs it nothing politically.
We ask the utility the second question
Not whether capacity exists. Whether it can be delivered, to this parcel, at this load, with this redundancy, by this date — and who pays. Utilities answer that question well when someone asks it precisely. Most projects never do.
Case Study
One finalist eliminated in Week 3, before the client spent a day on a site visit
Community eliminated before travel, diligence spend, or executive attention.
On a $75M advanced manufacturing search, we confirmed power deliverability with each finalist utility rather than accepting nameplate capacity. One community's capital improvement plan wouldn't support the client's load for thirty-plus months — a finding that removed it from consideration before a single site visit was scheduled.
Two other finalist sites carried shovel-ready claims concealing rezoning or remediation that would have added six to twelve months. Neither risk was disclosed in the RFI responses. The recommended community was the only finalist whose utility could confirm delivery inside the construction timeline.
The constraint wasn't power. It was 1,200 feet of roadway geometry.
A private industrial developer had utilities in place and no permittable highway access. Everyone was working the funding. The actual constraint was a geometry problem at the intersection — and solving it required a different sequence entirely.
Sequencing the infrastructure question correctly is the same discipline whether the constraint is a substation, a main extension, or a roadway. Identify the binding constraint first. Then figure out who has a reason to help solve it.
How We Work
Structured to fit inside a live decision
Weeks, not quarters
Four to eight weeks is fast enough to run before an LOI, which is the entire point. A schedule note worth stating: utility response times are partly outside our control. Where a formal capacity confirmation has its own queue, we'll tell you in Week 1 and give you the interim read rather than holding the deliverable.
Fixed fee, never hourly
You know the number before we start, and it doesn't move when scope clarifies.
Principal-led
The person on your first call is the person in the utility meetings. These conversations go better when the person asking has sat on the other side of the table, and that isn't a skill you can hand to an analyst.
Confidentiality by default
Searches and diligence run under a project code with your identity withheld until you choose to disclose it. On utility questions this materially changes the answer you get.
Every figure traced
If a capacity number came from a marketing packet or a community claim, it's labeled as a claim until confirmed against a utility document or a named conversation.
You own everything
The requirement specifications, the capacity workbooks, the gap register, the correspondence record. If the project phases up in three years, the baseline is yours.
Fit
This engagement fits a specific situation
It's built for you if:
- You're approaching an LOI, purchase agreement, or board commitment on a site and the utility assumptions haven't been independently tested.
- Your process has a redundancy requirement, an unusual demand profile, or constituents that could complicate discharge.
- You have two or three candidate sites and need a defensible basis for eliminating one.
- Your in-service date is tight enough that a thirty-month upgrade would be fatal.
- Somebody has handed you a capacity letter and you don't know what it doesn't say.
An honest note on where it doesn't fit:
If your project is a hyperscale or AI campus where the interconnection process governs the entire schedule, this engagement is the wrong shape — that's Data Center Advisory, and the difference is real, not a packaging distinction.
If you want a region-wide read for a community or utility rather than a project-specific one, that's Regional Utilities Study.
If the site is chosen, committed, and you need the interconnection application or utility coordination engineered and filed, that's an engineer of record; we're happy to tell you who's good.
And if your utility relationships are strong, your load is modest, and the service is already in the ground at the parcel line — you may not need us. Say so on the fit call and we'll tell you that.
Often Paired With
Frequently combined
Corporate Site Search
Where this work sits as the diligence phase inside a full multi-market search.
Incentive Package Analysis
Infrastructure cost-sharing is often the most valuable term in the package, and Phase Four hands you the ask.
Data Center Advisory
For large-load projects where power drives the entire schedule.
Regional Utilities Study
For the community or utility on the other side of this conversation.
Further Reading
Data Center Site Selection: What Actually Matters When Billions Are on the Line
Everyone has a checklist. Power. Land. Fiber. Tax incentives. But if you've spent any time in data center site selection at scale, you know the checklist is the easy part. The hard part is what the spreadsheet doesn't tell you.
IncentivesStop Comparing Incentive Packages by Face Value
The conventional approach to evaluating economic development incentives — comparing total dollar values — is the wrong analysis. Here's a better framework built around timing, deliverability, and risk.
Site SelectionYou're Not Going to See the Arch. You're Going to See the Substation.
The reality of work travel in site selection: FAM tours, site visits, and why boots-on-the-ground still closes the gap between what a community says it is and what it actually is.
Start Here
The cheapest week to run this is the week before you commit
Twenty minutes, no cost. Tell us the site or sites, the load across each utility, and the in-service date you're holding. We'll tell you which assumptions look soft, whether four weeks or eight is the right scope, and whether you need this at all.
Or email [email protected]