What a utility response establishes—and what remains unresolved
How to distinguish preliminary capacity feedback, study results, cost estimates and service agreements when assessing a project.
A favorable utility response is useful only in the context of the project it describes and the conditions attached to it. An indication that capacity appears available, an engineering finding and an accepted service agreement answer different questions. None should be treated as interchangeable evidence of capacity, cost and delivery timing.
Read the response by its purpose
- Preliminary inquiry: asks whether a location and proposed load warrant further investigation. It can identify the next step without reserving capacity.
- Formal application: supplies the information the utility requires to process the request. Submission alone does not establish feasibility or a delivery date.
- Engineering study: evaluates the proposed connection and identifies relevant constraints or system changes within its stated scope.
- Cost estimate: describes anticipated charges for specified work, subject to the estimate's validity period and conditions.
- Service agreement: records the parties' obligations. Read the conditions, dependencies and timing provisions rather than inferring a guarantee from the document's title.
These are useful distinctions, not a universal sequence. Utilities can combine steps, use different names or require further studies as the project changes.
Will-serve and ability-to-serve letters
These letters communicate a utility's position on serving a described project. Their significance depends on their wording: a letter may confirm service territory or express conditional willingness to serve without allocating a defined amount of capacity. Establish the load and location it covers, outstanding studies or upgrades, and any expiry or other conditions. Do not insert the letter into a fixed sequence or assume every utility issues one.
What published examples establish
This table compares process documents, not available capacity. It contains no per-record utility values. Metric labels prevent the process examples from being mistaken for comparable MW observations. The examples below identify the document and its limits. Older publications are dated evidence of a process, not confirmation that the same terms govern a new request today.
| Utility and source | What it establishes | What remains to confirm | Capacity-data context |
|---|---|---|---|
| National Grid, New York Service delivery process, September 2024 | Preliminary feedback can change with system loading. Formal reservation does not occur before a work request reaches engineering. | Whether this project's capacity has been reserved, with what scope and conditions. Reaching a stage is not evidence of the project's specific allocation. | Metric type: electrification_headroom; unit: MW. Not comparable: yes. Capacity records: not shown; no utility-reported source date in this table. Use archive source dates when reviewing National Grid records. |
| Central Hudson, New York Undated service delivery process, hosted by NY State Homes and Community Renewal | The study examines required system changes; off-site work can entail customer contributions and additional time. | The scope, cost responsibility and schedule for the actual project. A study duration is not an energization schedule. | Metric type: load_serving_headroom; unit: MW. Not comparable: yes here, because this is process evidence rather than a capacity observation. No utility-reported source date in this table; the document date is separate. |
| Con Edison, New York Project Center User Guide, Rev. 6, February 15, 2022, pp. 48–49 | The guide describes a 180-day estimate validity period and 30 days to begin payment after acceptance. | The terms of a new estimate and any agreement. The guide does not turn an estimate into a final-cost or energization guarantee. | Metric type: EV hosting capacity (ev_hosting_capacity); unit: MW. Not comparable: yes. Con Edison substation records have no utility-reported source date. The February 2022 date belongs to the process guide, not a capacity assessment. |
Keep four questions separate
Assessment: can the system accommodate the proposed load under the studied conditions? Reservation: has capacity been allocated to this project? Cost: what work and charges does the estimate cover, and what can change? Delivery: what obligations, milestones and dependencies govern service availability?
A response can resolve one of these while leaving the others open. Record each separately in site diligence so that a positive feasibility finding does not become an unsupported assumption about the construction schedule.
Questions for the next utility exchange
- Which location, load, operating profile and service date does this response cover?
- Which studies, approvals, payments or works remain outstanding?
- Has capacity been reserved? If so, what amount, conditions and expiry apply?
- How long do the findings and estimate remain valid, and what costs are excluded?
- What timing is committed, what is indicative, and what dependencies could change it?
- What must be revisited if the project load, design or requested date changes?
Weighing a list of sites? Send up to ten addresses and I'll send back a free written brief. ash@substationcapacity.com