A city can support a data center campus without controlling its water connection, electrical delivery, or off-site access. The developer’s task is to turn overlapping boundaries into a coordinated delivery plan: who has authority, who owns the asset, who pays, and what must happen before the first phase can operate.
This is the technical companion to When annexation reduces risk for a Texas data center campus. That article evaluates the jurisdiction decision and political exposure. This one explains the evidence needed to make the selected route executable.
The campus problem
Consider an illustrative campus outside city limits. Municipal records place it within an extraterritorial jurisdiction, or ETJ. A separate retail public utility holds the water certificate of convenience and necessity, or CCN. The city is discussing annexation, but the proposed water main crosses another owner’s land and requires a county-road crossing. Electrical service follows a separate provider process.
The tenant asks whether municipal support means the phase has a service date. It does not. Before answering, the team must resolve four different questions: who may authorize service, whether capacity is available, who will build the extension, and whether the route can legally be used. A city letter can answer one question without answering the other three.
The hidden constraint is often outside the parcel and outside the negotiating counterparty’s control.
One drawing, separate layers of authority
Chapter 42 addresses Texas municipal ETJs, while Chapter 43 governs annexation procedures. ETJ status is not incorporation and should not be treated as full city zoning authority. Obtain the current boundary record and have counsel confirm which municipal and county requirements apply to the specific parcel and proposed work. Do not infer today’s position from an undated brokerage map.[1][2]
Water and sewer certification require a separate review. Water Code Section 13.247 addresses certificated service within municipalities, and Section 13.255 provides a conditional municipal single-certification process with important limits. Annexation is not an automatic transfer of another provider’s service rights. Any proposed change needs its own applicable agreement, regulatory process, and delivery analysis.[3]
Those legal distinctions explain why the development team needs separate evidence layers:
Swipe or scroll to compare all columns.
| Layer | Record to obtain | Question that remains open |
|---|---|---|
| Ownership and access | Survey, title commitments, recorded easements, and relevant restrictions | Does the project control the entire construction and operating route? |
| City limits and ETJ | Current municipal records and counsel-confirmed applicability | Which approvals apply to each on-site and off-site component? |
| Water and sewer certification | Current CCN records, orders, and provider confirmation | Can the authorized provider supply the required volume, pressure, quality, and discharge arrangement? |
| Electric service | Provider-confirmed service route and project-specific application record | What capacity, network work, study results, and operating conditions support the phase? |
| Roads and drainage | Ownership, jurisdiction, crossing requirements, and outfall rights | Can the route be built and maintained without an unresolved third-party consent? |
| Districts and shared infrastructure | Enabling authority, asset ownership, funding commitments, and operating responsibilities | Who carries costs or obligations if later phases do not proceed? |
The map should label unverified lines and missing documents. A precise-looking GIS drawing can still be based on preliminary data. Distinguish screening information from surveyed rights, regulatory records, and executed agreements.
The connection point is where separate scopes collide
Suppose the water provider’s scope ends at a meter near the property line. The campus design assumes a different elevation, pressure, flow, and commissioning date. The city has agreed to improve the road, but the improvement would conflict with the main’s proposed alignment. Each organization may be progressing its own scope while the campus still lacks an operable interface.
Resolve that interface before authorizing incompatible work. Define the physical connection point, design basis, testing requirements, acceptance responsibilities, and asset handoff. Identify who signs off when two contractors meet, who operates the connecting asset, and who pays if one party’s requirement changes.
For cooling and water planning, do not combine average consumption, peak-day use, instantaneous demand, storage, fire protection, and wastewater into a single daily figure. Have the design team and providers establish the applicable requirements separately. A letter that addresses only annual volume does not establish that every operating condition can be supported.
Electrical service needs the same discipline. Provider discussions, a study submission, conditional process eligibility, and an accepted service commitment are different evidence states. Record the actual state and remaining conditions instead of assigning all four the label “power secured.”
Solutions and their tradeoffs
Keep the incumbent provider and close the delivery gap
This can be the simplest route when service authority is clear and the unresolved issue is a main, treatment expansion, connection, or funding arrangement. Separate provider-authorized service from the commercial and construction agreement needed to deliver it.
The tradeoff is that the campus may fund substantial enabling work before occupancy. Define ownership, reimbursement conditions, operating charges, oversizing, and the consequences of a delayed second phase. Do not make the first tenant’s opening depend on uncommitted future customers paying for the extension.
Pursue a coordinated alternative where legally available
A city or other provider may offer a better physical solution, but proximity is not authority. Have counsel and the affected providers identify the available certification, transfer, or contractual route before making its economics the base case. A technical proposal is not an approved service-area change.[3]
Test the transition as carefully as the destination. Who supplies the first phase if the alternative is delayed? Who owns the interim assets? Could a temporary solution become a stranded cost? Maintain a dated incumbent-provider case until the alternative has enough evidence to replace it.
Change the connection, corridor, or initial phase
If the issue is the extension’s physical route rather than provider authority, moving the connection or reducing the initial demand may be more effective than changing jurisdiction. Compare easements, crossings, storage, equipment, and tenant consequences under the same design basis.
A smaller phase is useful only if it can operate within an accepted service arrangement and preserves a viable expansion path. Do not describe a theoretical reduction in demand as an approved temporary operating limit.
Resolve the critical path before buying the whole solution
In the illustrative campus, assume the provider can describe an expansion but has not committed its funding. The crossing consent and the final cooling basis are also open. The sensible next expenditure may be a coordinated route study, provider-supported design basis, and negotiation brief, not a major equipment deposit predicated on a promised service date.
Use a dependency record to determine the release sequence:
Swipe or scroll to compare all columns.
| Open dependency | Evidence that would resolve it | Commitment to hold until resolved |
|---|---|---|
| Service authority | Applicable provider record and any required approval or agreement | An unconditional promise that another provider will serve |
| Capacity and operating basis | Accepted demand assumptions, provider-supported analysis, and stated operating conditions | Final equipment sizing or tenant service commitments based on unsupported capacity |
| Off-site route | Sufficient property rights, crossing approvals, and coordinated alignment | Construction release across land or infrastructure the project cannot yet use |
| Funding and asset ownership | Agreed scope, payment responsibilities, ownership, and delivery obligations | Assuming reimbursement or later-phase contributions are secured |
| Acceptance and operation | Test criteria, inspection responsibilities, handoff, and operating arrangements | Treating physical construction alone as service readiness |
Some investigation and design work must proceed before every condition is closed. The objective is not to stop all spending. It is to keep each authorization proportionate to the evidence obtained and to avoid irreversible commitments based on a different party’s unresolved decision.
Putting the analysis to work
Sitebraid would assemble an authority-and-interface record with the owner, counsel, surveyors, engineers, providers, and public counterparts. The owner should be able to trace each service promise from the tenant requirement to the relevant approval, asset, payment, and acceptance test.
For every dependency, record:
- The responsible organization and the person or body with decision authority.
- The source document, date, version, and whether it is preliminary, conditional, or executed.
- The parcel, asset, phase, and operating assumption covered.
- The unresolved prerequisite, latest useful decision date, and downstream effect of delay.
- The available fallback and its cost, approvals, and effect on later phases.
Keep a change log when tenant demand, cooling, pad locations, or service dates move. A revised master plan may change the route, responsible jurisdiction, and infrastructure size simultaneously. Update the underlying provider and approval record, not only the presentation drawing.
The result the owner should require
The output is not simply a boundary map. It is a dated delivery record showing who approves, serves, funds, owns, and operates each required system, with agreed interfaces and clearly identified unresolved conditions.
At the assessment stage, the owner receives a recommended next commitment and the evidence required to advance. At an execution stage, the agreed scope must establish the specified approvals, rights, agreements, and release prerequisites. Neither stage should imply that Sitebraid substitutes for a regulator, provider, surveyor, engineer, or legal adviser.
The practical test is simple: if one responsible party says no or delivers late, can the owner identify the affected phase, the cost, and a credible next move? If not, the interface remains unresolved even when the map looks complete.
Connect the decision to the work
- Decide whether to annex: When annexation reduces risk for a Texas data center campus compares jurisdiction routes, political exposure, and financial tradeoffs.
- Resolve the approvals and development interfaces: Entitlements & community explains the development scope; Entitlements stalled describes the active blockage.
- Commission the site-specific decision package: Site selection & assessment connects mapped constraints, infrastructure alternatives, capacity scenarios, phased costs, and the next capital commitment.
The shared position across these pages is that annexation can reduce selected local risks through enforceable, funded arrangements. It does not automatically protect a campus against statewide law or independent utility constraints.
Sources and scope
Public sources reviewed September 11, 2026. This is development analysis, not legal advice. The campus example and proposed process are illustrative, not a claimed client assignment. Counsel and the responsible authorities must determine parcel-specific applicability and available procedures; engineers and providers must establish technical capacity and service requirements.