The Texas context
ERCOT’s September 3, 2026 notice describes conditional Batch Zero classifications and project-specific verification or model-data conditions, including defined routes for certain eligibility disputes. The governor’s August 18 statement describes information sought in the data-center audit. Those are current records to examine with the provider. They should not be rewritten as an enacted blanket ban on every rural campus.
ERCOT September 3, 2026: Batch Zero conditional classifications
Policy status matters
The Texas Legislative Reference Library collects agency documents, executive correspondence and local actions. A public comment, announced policy preference, filed proposal, adopted rule and effective statute carry different weight. The sources reviewed here do not establish a statewide rural-campus prohibition. That is a boundary of this review, not an assurance that a site is protected from future change.
Our view
Put the specific condition next to the next irreversible expenditure. The owner needs to know whether a project record is incomplete, an approval is conditional, a local requirement applies, or a future-policy scenario could change the economics. A generic legislative watch does not tell the team whether to release a transformer order.
A usable policy register
Swipe or scroll to compare all columns.
| Status | Decision treatment | Do not infer |
|---|---|---|
| Effective requirement | Identify applicability and compliance evidence | Compliance from a press statement |
| Project condition | Assign closure and deadline with provider | An unconditional energization date |
| Filed or proposed change | Model scenarios and review milestones | Enactment or a final effective date |
| Political discussion | Record the uncertainty if material | A binding prohibition or exemption |
The owner’s situation
A campus owns rural land and has spent on preliminary design. Its provider forwards a conditional classification while community objections raise questions about water and traffic. The investment committee asks whether annexation would protect the project. Meanwhile, a tenant expects a start date and the procurement team wants a long-lead release. The assignment is to establish the current approval basis and preserve sensible options without treating political uncertainty as either a certain ban or a nonissue.
What we need to establish
Obtain the actual provider notice, submitted ownership and load information, model-data status, land and municipal boundaries, local approval record and applicable deadlines. Ask counsel to distinguish effective requirements, pending proceedings and speculative changes. Create one dated source register linking each material statement to an authority, project action, responsible party and decision date. Check municipal and utility territories separately; changing one boundary does not automatically change the other.
The options we would test
What owners should do
Our proposed execution sequence for this assignment:
Reconcile the public and project records
Compare published requirements with the notice and correspondence for this campus. Identify inconsistencies before communicating an assured date to tenants.
Build the response through accountable parties
Sitebraid coordinates ownership, water, load and development evidence with the provider and specialists. Counsel and qualified engineers retain responsibility for legal and technical positions.
Connect uncertainty to capital gates
Identify which expenditures are recoverable, transferable or stranded if a condition fails. Have the owner decide which risk to retain, and reflect that in tenant and supplier terms.
Maintain the status after submission
A submitted response is not an accepted response. Record receipts, further questions, decisions and changed conditions. Update the campus baseline before releasing the next phase.
How we protect the decision
Do not promise that annexation avoids a future restriction whose final wording does not exist in the record. Do not confuse a local measure with statewide law. Use actual deadlines from the current provider notice, not a date copied from another project. Public advocacy for regional benefits does not substitute for compliance evidence.
What completion looks like
The owner receives a current, sourced approvals position; the assigned conditions are closed or explicitly escalated; and capital releases reflect the remaining uncertainty. A monitoring assignment has an owner, trigger and review cadence. It is not complete merely because an article predicts what the legislature might do.
What we would track
- Project-specific conditions and response deadlines.
- Unaccepted assumptions supporting tenant dates.
- Capital exposed before each material decision.
- Source status and date of the last applicability review.
Respond to the requirements that exist and preserve options for those that may follow.