Legislative intelligence / 90R
SESSION 2027View project ↗

Special District Local Laws Code § 6904.052: ANNEXATION OF TERRITORY

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Special District Local Laws Code Chapter 6904, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 6904.052. ANNEXATION OF TERRITORY. (a) Territory may be annexed to the district as provided by this section or by Section 6904.053.

(b) The board may annex territory or a municipality under this section only if a petition requesting annexation is signed by 50 voters of the territory or municipality to be annexed, or a majority of the registered voters of that territory or municipality, whichever is fewer, and is filed with the board. The petition must describe the territory to be annexed by metes and bounds, or otherwise, except that if the territory is the same as that contained in the boundaries of a municipality, the petition is sufficient if it states that the territory to be annexed is the territory contained in the municipal boundaries.

(c) If the board determines that the petition complies with Subsection (b), that the annexation would be in the best interest of the territory or municipality and the district, and that the district will be able to supply water or other services to the territory or municipality, the board shall:

(1) adopt a resolution stating the conditions, if any, under which the territory or municipality may be annexed to the district; and

(2) set a time and place to hold a hearing on the question of whether the territory or municipality to be annexed will benefit from:

(A) the improvements, works, or facilities owned or operated or contemplated to be owned or operated by the district; or

(B) the other functions of the district.

(d) At least 10 days before the date of the hearing, notice of the adoption of the resolution stating the time and place of the hearing shall be published one time in a newspaper of general circulation in the territory or municipality to be annexed. The notice must describe the territory in the same manner in which Subsection (b) requires the petition to describe the territory.

(e) Any interested person may appear at the hearing and offer evidence for or against the annexation.

(f) The hearing may proceed in the order and under the rules prescribed by the board and may be recessed from time to time.

(g) If, at the conclusion of the hearing, the board finds that the property in the territory or municipality will benefit from the present or contemplated improvements, works, or facilities of the district, the board shall adopt a resolution making a finding of the benefit and calling an election in the territory or municipality to be annexed.

(h) In calling an election on the proposition for annexation of the territory or municipality, the board may include, as part of the same proposition or as a separate proposition, a proposition for:

(1) the territory to assume its part of the tax-supported bonds of the district then outstanding and those bonds previously voted but not yet sold; and

(2) an ad valorem tax to be imposed on taxable property on the territory along with the tax in the rest of the district for the payment of the bonds.

(i) If a majority of the votes cast at the electi

The section continues: whole chapter.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.