Data center interconnection agreement: the IA clock that binds

A study can say a data-center load is workable. An executed interconnection agreement says the customer and grid owner have put terms on paper — and on what clock. Watt Brief reads an IA, LGIA, or comparable load interconnection agreement as a public-record delta: identity first, then the executed scope, contracted MW, and decision dates that bind. A campus deck that says power is coming is not a row. A filed agreement or docket document with a document ID is.

Four fields before you trust the IA

Open the utility, RTO, ISO, transmission provider, or commission docket. Pull these fields before you treat deliverability as committed:

• Document ID — the agreement number, docket number, queue identity, or filing reference printed on the IA or LGIA packet. That is the identity key with source and event class. We do not invent one because a release said “executed.”
• Agreement packet — the executed IA, LGIA, exhibits, approval order, or redline-to-final sequence that shows who signed and what facilities, service, and conditions are covered. The packet is where the commitment becomes legible.
• Contracted MW — the requested, reserved, deliverable, or staged MW actually stated in the agreement. We keep the packet’s distinction between initial and ultimate service, POI limits, milestones, and contingent upgrades. If the filing only says “hyperscale load,” we do not manufacture a campus number.
• Clock dates — execution, effectiveness, commission approval, security posting, construction notice, milestone, energization, termination, or customer decision dates. A signed cover page without an effective date is not the same row as an IA with a live milestone clock.

Why the IA binds before campus PR

Campus marketing moves when a developer wants a headline. An IA moves when the parties execute terms, a commission docket accepts or approves the filing, or a milestone clock forces a response. For colo and hyperscale site-selection BD, utility large-load teams, and infra PE, the binding fact is not that someone announced a power plan. It is that a named document ID now carries an agreed scope, a dated obligation, and a path toward service.

Execution does not make every future megawatt certain. Agreements can stage service, condition facilities, require security, or terminate after a missed milestone. That is why Watt Brief keeps the exact agreement language and clock rather than flattening “IA signed” into “campus energized.” A new exhibit, approval, amendment, or milestone on a known identity is a delta; a restated announcement is not.

What counts as an IA delta

• IA, LGIA, or comparable load interconnection agreement filed or executed with a document ID and stated MW.
• Commission approval, effectiveness, security posting, or construction authorization issued on that agreement.
• Facilities, network-upgrade, POI, or service exhibit added, replaced, or materially amended.
• Milestone, energization, commercial-operation, customer decision, or termination date issued or moved.
• Contracted or staged MW, service phase, POI, or responsibility table revised in the packet.
• Agreement withdrawn, terminated, superseded, or closed after execution.

None of that is a trade-magazine feature. It is a pointer to the executed packet, exhibit, or docket filing you can open. If the same document ID later gets an approval order or amended MW table, that is a new delta on the same identity — not a duplicate with a restated lede.

What we skip

We skip generic “power secured” press kits that do not attach an IA, LGIA, docket, or agreement reference. We skip unsigned term sheets presented as executed contracts. We skip restated headlines about the same document ID, and we skip inventing agreement numbers, MW, or dates from a rendering or broker slide.

An IA row is not proof that the campus will energize on schedule. It is also not a substitute for a system impact study (SIS), facilities study, transmission service request (TSR), ERCOT Batch Zero verification, permit, county conditional-use permit (CUP), or PUC tariff case. Those are separate identities when the sources are separate, even when they describe the same load. The agreement is the binding record for its own terms and clock — not a license to merge every milestone into one row.

Open the agreement URL or docket. Match the document ID, executed scope, and clock date. If the data-center load is not on that packet, the row is not for you yet.