Legislative intelligence / 90R
SESSION 2027View project ↗

Special District Local Laws Code § 8303.102: STRATEGIC PARTNERSHIP; CONTINUATION OF DISTRICT AFTER ANNEXATION BY MUNICIPALITY

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 8303, 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. 8303.102. STRATEGIC PARTNERSHIP; CONTINUATION OF DISTRICT AFTER ANNEXATION BY MUNICIPALITY. (a) The district may continue to exist as a limited district after full-purpose annexation by a municipality if the district and the annexing municipality state the terms of the limited district's existence in a strategic partnership agreement.

(b) A strategic partnership agreement between the district and an annexing municipality may:

(1) authorize the conversion of the district to a limited district upon full-purpose annexation and may permit the limited district to continue to exist and provide services for a fixed term or an indefinite term, on conditions that are mutually agreeable to the district and the annexing municipality;

(2) contain a pledge of user fee revenues, tax proceeds from taxes levied within constitutional limits, miscellaneous revenues, and other funds under the control of a party, to cover that party's pecuniary obligations under the agreement;

(3) continue in effect for a fixed term or an indefinite term, as may be agreed upon by the district and the annexing municipality; and

(4) contain other provisions relating to annexation or services, including enforcement provisions, as may be agreed upon by the district and the annexing municipality.

(c) An agreement described in this section shall be valid, binding, and enforceable in accordance with its terms. To achieve this purpose:

(1) this section controls over any other laws, rules, regulations, charter provisions, or ordinances, including any contrary provision of Section 43.0751, Local Government Code; and

(2) if the district and an annexing municipality enter into such an agreement, sovereign immunity is waived for each party for the purpose of adjudicating claims based on the agreement, including claims for money damages, declaratory judgment, and other remedies, subject to the terms and conditions of this section.

(d) The total amount of money awarded in an adjudication described by Subsection (c)(2) is limited to direct damages, excluding consequential damages, exemplary damages, or damages for unabsorbed office overhead, plus reasonable and necessary attorney's fees that are equitable and just, plus interest as allowed by law, including interest as calculated under Chapter 2251, Government Code. This section does not waive a defense or a limitation on damages available to a party to such an agreement other than a bar against suit based on sovereign immunity.

(e) An agreement described in this section is not a joint enterprise for liability purposes. This section does not waive sovereign immunity to suit for a cause of action for a negligent or intentional tort or for a cause of action brought by any person or entity that is not a party to an agreement described in this section.

(f) In this section:

(1) "Sovereign immunity" includes immunities commonly referred to as "sovereign immunity" or "governmental immunity" and encompasses both immunity from suit and immu

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.