Approach Texas data center permitting through two separate questions: which approvals apply to the project, and what evidence supports its promised delivery date? Before committing land, capital or customer capacity, keep the environmental-permit position distinct from power, water, construction and connectivity readiness.
For developers, operators and AI infrastructure buyers, the useful unit of analysis is the specific site and phase. A campus-wide megawatt figure or proposed opening date should lead to a document request, not end the conversation.
What the halt does and does not mean
Treat a permitting halt as a question about a named authority, approval type, project and effective period. Do not use that phrase alone to decide whether construction, operation or expansion can proceed. Establish the applicable scope with project counsel, then track the separate conditions for delivering customer-ready capacity.
What changed with Texas data center permitting?
In its September 21, 2026 announcement, the Texas Governor’s Office reported that Governor Greg Abbott had directed the Texas Commission on Environmental Quality to halt permits sought by data centers.
Use that announcement as a trigger to reopen the project’s approvals register. Ask counsel to identify the governing instrument, the approvals relevant to the site and the treatment of each project phase. Distinguish an application being prepared, an application under review, an issued approval and an authorization with outstanding conditions.
The commercial question is narrower than whether Texas is open or closed for development: what can this project support, under which conditions, by which date? Carry that answer into the investment memo, customer proposal and construction schedule.
Why power and water audits matter
For this diligence exercise, make the power and water audit a reconciliation of design assumptions, service commitments and delivery dependencies. Start with the proposed customer load and cooling design—not a general description of the campus.
For power, request the quantity, delivery point, service conditions, phased availability and supporting work schedule. Ask whether the quoted megawatts describe utility supply, total facility demand or IT capacity. Require the project team to explain the relationship rather than comparing unlike figures.
As Bob Generale puts it, “A power agreement is not power at the wall.” Use that distinction to press for evidence behind the delivery promise. A document describing a future commitment should not be presented as a record of completed energization.
For water, request a balance tied to the proposed cooling design and operating assumptions. Identify the source, peak requirements, service commitments, discharge approach where relevant and conditions that could alter the design. Ask the responsible engineer to reconcile those assumptions with the customer phase being sold.
Use the data center power availability guide to extend the power discussion. Keep the resulting evidence attached to the specific site, phase and capacity figure.
ERCOT interconnection vs energized capacity
When a seller describes a project as “ERCOT approved,” ask for the exact document and the milestone it represents. For a project described as ERCOT-connected, request a map of the relevant grid, utility and on-site workstreams, with an owner and completion evidence for each.
Do not accept a single status label in place of that map. Ask what remains between the cited milestone and service to the proposed customer load: studies, agreements, equipment, construction, testing or other project-specific conditions.
Then separate energization evidence from customer acceptance evidence. Request the records supporting the promised service level and the commissioning or acceptance criteria for the contracted space. Keep electrical service, facility readiness and customer availability as separate entries until the documents justify combining them.
How permitting changes site selection and financing risk
Compare candidate sites on the conditions that remain unresolved, not just the most optimistic delivery date. For each site, ask the team to identify the next decision, the party controlling it, the supporting document and the consequence of a delay.
Build the financing case around explicit conditions. Ask the deal team to identify which approvals, service commitments and completion milestones support each funding or revenue assumption. Model a delayed-delivery case alongside the proposed schedule, then have counsel address the associated contractual exposure.
If the first customer phase has supporting evidence but a later expansion depends on an unresolved upgrade, underwrite and describe those phases separately. Do not let the evidence for one phase stand in for the entire campus.
Use the data center site selection checklist to compare physical readiness, then connect those findings to the assumptions in your data center financing structure.
Where fiber and interconnection fit after power
Once the power case is documented, test whether the proposed connectivity serves the intended customers and workloads. Do not let a broad claim such as “fiber nearby” close that workstream.
Request route information, building-entry plans, service availability, delivery responsibilities and the connection path to the networks or destinations the customer needs. Where route diversity is part of the proposal, ask for evidence of the physical paths rather than relying on a carrier count.
Carry the connectivity delivery dates into the same schedule as the electrical and facility milestones. Use the data center fiber connectivity guide to structure the follow-up questions.
Texas Project Readiness Stack
Use the Texas Project Readiness Stack as a diligence sequence:
Permit → Deliverable Power → Water → Utility Interconnection → Site/Civil Readiness → Fiber/Interconnection → Schedule → Customer/Credit
This is a review order, not a statutory approval process or a construction sequence. Investigate dependent workstreams in parallel. At each layer, record the evidence, unresolved condition, responsible owner and date for the next decision.
Use three working labels: documented, conditional and open. “Documented” should identify what the record actually establishes; it should not imply that every downstream dependency is complete. “Conditional” should name the condition. “Open” should have an owner and a next action.
Match each readiness claim to a document
| Diligence item | Evidence required | Responsible party | False-positive signal | Buyer risk |
|---|---|---|---|---|
| Permit position | Project-specific approvals register, issued documents and counsel’s scope assessment | Developer and project counsel | “Permitted” without identifying the approval or phase | Commitment based on the wrong approval scope |
| Deliverable power | Quantity, delivery point, conditions and dated evidence supporting availability | Developer and utility counterpart | Availability letter presented as completed delivery | Capacity commitment ahead of supported service |
| Water and cooling | Design water balance, source documentation and relevant service conditions | Design engineer and water provider | Nearby infrastructure treated as a service commitment | Unresolved cooling assumptions |
| Utility interconnection | Applicable agreements, outstanding work and milestone ownership | Utility counterpart and electrical lead | Application or study described as energization | Unbudgeted work or schedule exposure |
| Site and civil readiness | Site-control documents, access arrangements and engineering readiness assessment | Developer, counsel and civil engineer | Controlled land described as construction-ready | Unresolved access or site-work dependencies |
| Fiber and interconnection | Route, building-entry and service-delivery evidence | Network lead and service providers | Carrier names substituted for route evidence | Connectivity that does not meet the intended use |
| Schedule | Integrated dependencies, accountable owners and acceptance milestones | Project controls lead | Opening date without a dependency schedule | Contract dates disconnected from delivery work |
| Customer and credit | Executed commitments, conditions and counterparty assessment | Commercial lead, finance and counsel | Pipeline interest described as contracted revenue | Funding assumptions unsupported by commitments |
What developers/operators/buyers should verify now
- Developers: Reconcile the approvals register with the current design and phase plan. Assign an owner to every unresolved dependency and connect each to the delivery schedule.
- Operators: Reconcile the capacity being marketed with the service, construction and acceptance evidence. Specify what is available now and what remains conditional.
- Buyers: Request a dated evidence package for the exact site, phase, capacity and service date under discussion. Have your technical and legal teams examine the same package before commitment.
Keep a version-controlled readiness record. When a design, approval, utility milestone or delivery assumption changes, identify which commercial statements and contractual dates must be revisited.
For commercial teams, use the same milestone language in sales decks, investor updates and omnichannel marketing. Separate what is deliverable now from what is planned, and identify the condition behind every future-capacity claim.
What to watch next
Monitor the Texas Governor’s Office for directives, TCEQ for agency materials and applicable project records, and ERCOT for relevant grid-process materials. Pair those sources with direct updates from project counsel and the serving utility.
For each development, ask what changes in your project file. Does it affect an approval, an outstanding condition, a service commitment or the critical path? Record the answer and its supporting document before revising the schedule or sales narrative.
Make the next commitment against the project’s documented position—not against a headline, an application milestone or an undifferentiated campus capacity figure.
Build the launch story around the delivery evidence
Taking a Texas facility to market? Bring the readiness matrix to a conversation about positioning, sales materials and launch communications.
FAQs
Does a Texas data center permitting halt mean every project must stop?
Do not infer a statewide construction or operating prohibition from a permit headline. Have project counsel identify the applicable instrument, authority, approval type, effective period and treatment of the specific site and phase.
Does an ERCOT milestone prove that a site has usable power?
For a buying decision, require separate evidence of the milestone reached, remaining utility work, energization and customer acceptance conditions. Do not treat an application, study or approval label as proof of customer-ready capacity.
What should a buyer request before signing for future capacity?
Request a dated package identifying the site, phase, capacity definition, permit position, power and water commitments, connectivity plan, delivery dependencies and acceptance criteria. Ask counsel to address the consequences if a condition or delivery date changes.
About Bob Generale
Bob Generale is President of Percepture.
