Skip to content

Earlier work (2025–2026). GridVision now focuses on data-center site advancement and cross-gate coordination for controlled sites in Northern Virginia. The interconnection-queue research below is kept for reference and retains the vocabulary of the period in which it was written; it is not a current product.

Interconnection diligence guide

Interconnection Due Diligence Checklist for Energy Developers

Before a team relies on an interconnection record, its working file should show what is supported, what is assumed, and what remains unknown.

GridVision AI ResearchPublished Updated

6

record groups

4

source classes

1

traceable working file

The six evidence groups

Decision and alternatives

Name the project, decision owner, deadline, candidate POIs, and the pathways being compared.

Project evidence

Record market, utility territory, requested capacity, target date, site control, permitting status, and queue identifier.

Network model

Record topology source, model version, ratings, base-case injections, exact POI mapping, units, and as-of dates.

Queue evidence

Capture the source, request status, study milestone, retrieval time, coverage limits, and any unavailable fields.

Schedule and commercial assumptions

Separate supplied estimates from verified commitments. Record dependencies, exclusions, and what could change the date or cost.

Unknowns and next diligence

List the evidence that could change the comparison and assign the next question to its source owner.

A queue position is not a complete project record

A queue record can be useful evidence, but it does not by itself establish deliverable capacity, a final upgrade scope, a commercial-operation date, or a management recommendation. Keep source, retrieval time, version, and coverage visible. If a required field is missing, record the gap instead of filling it with a plausible value.

Keep formal utility determinations, engineering studies, and governing tariffs in their original role. A source-tracing checklist does not replace or extend them.

How to use the checklist

  1. Freeze the review date and source cutoff. Label later facts as updates instead of silently mixing versions.
  2. For every material claim, store the source, retrieval time, market, project identifier, and the exact field or passage supporting it.
  3. Keep facts, project inputs, assumptions, and unknowns in separate columns. A missing value is a diligence task, not permission to estimate.
  4. Use the same boundary when comparing records: requested MW, POI, target date, operating profile, upgrade scope, and stated commercial assumptions.
  5. End with an owner and next action for every unknown that could change a documented project condition or next gate.

Why process context matters

FERC Order No. 2023 introduced a first-ready, first-served cluster-study framework with site-control and financial requirements, study deadlines, affected-system procedures, and storage modeling provisions. The exact process still depends on the applicable transmission provider and tariff. PJM, for example, separates application and study agreements across its current platforms. Treat the governing tariff and current provider documents as the controlling source for a live project.

Authoritative starting points

Sources were checked September 2026. Process rules and queue data can change; verify the current tariff, provider portal, and study documents before relying on a project conclusion.

Related guides and public records

Have a controlled site and a next gate?

The public form collects contact details only. Do not send site or transaction documents.

Request a qualification conversation →

GridVision provides data-center site advancement and cross-gate coordination in Northern Virginia.