Disclose Interconnection Queue Status for GPU Offtake Buyers

Consider a hypothetical industrial site with a 20 MW service history and only 4 MW of current load. The owner markets the remaining 16 MW for GPU offtake. A buyer asks for the utility’s written confirmation that the proposed computing load can be served. The owner produces a preliminary feasibility letter—but no completed system impact study or executed agreement covering the new load.

The issue is not necessarily insufficient power. It is an unsupported claim about availability.

For site owners, interconnection disclosure should turn “unused grid capacity” into a documented sequence of approvals, studies, and obligations. Buyers need to distinguish existing service from proposed capacity before they can assess a credible deployment date.

Name the study stage, not just “interconnection underway”

Utility terminology and processes vary. Use the utility’s exact study names, then explain what each document establishes.

A feasibility study may identify preliminary constraints and possible upgrade needs. A system impact study generally examines network effects in greater detail. A facilities study, where applicable, may refine the equipment, scope, cost estimates, and construction requirements. None should be presented as an unconditional commitment to energize unless the governing documents actually provide that commitment.

For each stage, disclose:

• Status: not requested, submitted, underway, draft received, or final issued.
• Evidence: document title, issuing organization, date, and reference number.
• Scope: requested MW, service voltage, load profile, and operating assumptions.
• Open items: missing inputs, revised models, restudy triggers, or unresolved findings.

An unused service connection is not automatically approved for a materially different load. State whether the utility has reviewed the proposed GPU load—not merely the property’s historical industrial use.

Make queue status traceable and qualified

“Good queue position” is not a useful disclosure. Provide the queue or application identifier, submission date, current stage, and the date that status was last verified.

Also identify which process applies. A large-load service request may follow a different path from a generation interconnection queue. Do not use an unrelated generation queue number as evidence that computing load is approved.

If the utility publishes a position, report it with its source and date. If it does not provide an ordinal position, say so rather than inventing a ranking.

Include any known conditions for retaining the application’s status: deposits, study payments, site-control evidence, milestone deadlines, or acceptance of study results. Explain whether a change in applicant, requested demand, or load characteristics requires utility review.

Queue position is context, not a reservation of deliverable MW or a guaranteed construction slot.

Separate upgrade findings from upgrade commitments

List contingent upgrades identified in studies or utility correspondence: substation work, feeder upgrades, protection changes, metering, customer-side equipment, or third-party easements. For each item, disclose estimated cost ownership, schedule dependency, and whether the estimate is binding.

Do not treat transformer hardware lead time as synonymous with interconnection queue timing; they are related but separate disclosures.

Publish an energization estimate with its assumptions

Give buyers a dated estimate rather than a floating promise. Distinguish three milestones:

• Existing service available under current terms.
• Initial capacity potentially available for a staged deployment.
• Full requested capacity available after all required work.

For each milestone, state the MW, target window, source, and remaining conditions. Specify whether the date is utility-provided, contractor-estimated, or owner-modeled.

A useful disclosure reads: “Owner planning estimate: initial energization in the stated quarter, contingent on final study acceptance, execution of the service agreement, and completion of identified utility work. Utility schedule confirmation pending.”

That is stronger than “power ready next year” because a buyer can see what would change the date. If relevant, distinguish the site’s future energization case from an interim strategy described through bridge-capacity options; the latter does not validate the former.

Give buyers an evidence index, not a document dump

Package a one-page status summary with a dated evidence index. Buyers commonly ask for utility correspondence, study reports, application identifiers, applicable service agreements, upgrade scopes, milestone notices, and confirmation of the proposed load assumptions.

Identify what can be shared immediately, what requires an NDA, and what needs utility consent. Redact sensitive details where appropriate without removing the qualifications that explain capacity availability.

Keep “confirmed,” “conditional,” and “unverified” claims visibly separate. This makes the site’s readiness easier to discuss alongside GPU capacity opportunities, without portraying a pending application as operating capacity.

Have a site with unused interconnect and a partially documented utility path? Schedule a 30-minute conversation with Pacific Intelligent Technologies, Inc. to discuss how you present its status to GPU offtake buyers.

FAQ

Does unused interconnect mean I can offer the full historical MW?

Not automatically. Confirm applicable service rights, current agreements, physical limits, and utility treatment of the proposed load. Present only the capacity your evidence supports when discussing GPU capacity.

Can I market a site before studies are complete?

Yes, provided you disclose the stage and conditions clearly. Position it as a development-stage opportunity, not energized capacity. Keep any bridge-capacity discussion separate from claims about the site’s completion date.

What should I update after a utility review?

Update the verification date, study status, available MW assumptions, upgrade register, and energization estimate together. For broader company context, see Pacific Intelligent Technologies, Inc..