Legislative intelligence / 90R
SESSION 2027View project ↗

Health and Safety Code § 775.014: CREATION OF DISTRICT THAT INCLUDES MUNICIPAL 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 Health and Safety Code Chapter 775, 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. 775.014. CREATION OF DISTRICT THAT INCLUDES MUNICIPAL TERRITORY. (a) Before a district may be created that contains territory in a municipality's limits or extraterritorial jurisdiction, a written request to be included in the district must be presented to the municipality's governing body after the petition is filed under Section 775.015. Except as provided by Subsection (c), that territory may not be included in the district unless the municipality's governing body gives its written consent on or before the 60th day after the date on which the municipality receives the request.

(b) If the municipality's governing body does not consent to inclusion within the 60-day period prescribed by Subsection (a), a majority of the qualified voters and the owners of at least 50 percent of the territory in the municipality's limits or extraterritorial jurisdiction that would have been included in the district may petition the governing body to make fire control and emergency medical and ambulance services available. The petition must be submitted to the governing body not later than the 90th day after the date on which the municipality receives the request under Subsection (a).

(c) If the municipality's governing body refuses or fails to act on the petition requesting fire protection and emergency medical and ambulance services within six months after the date on which the petition submitted under Subsection (b) is received, the governing body's refusal or failure to act constitutes consent for the territory that is the subject of the petition to be included in the proposed district.

(d) If the proposed district will include territory designated by a municipality as an industrial district under Section 42.044, Local Government Code, consent to include the industrial district must be obtained from the municipality's governing body in the same manner provided by this section for obtaining consent to include territory within the limits or extraterritorial jurisdiction of a municipality.

(e) If the municipality's governing body consents to inclusion of territory within its limits or extraterritorial jurisdiction, or in an industrial district, the territory may be included in the district in the same manner as other territory is included under this chapter.

(f) A governing body's consent to include territory in the district and to initiate proceedings to create a district as prescribed by this chapter expires six months after the date on which the consent is given.

(g) This section does not apply if the proposed district contains territory in the unincorporated area of a county with a population of 3.3 million or more.

Without reference to the amendment of this subsection, this subsection was repealed by Acts 2023, 88th Leg., R.S., Ch. 298 (S.B. 1794), Sec. 7(1), eff. March 1, 2024.

(h) The governing body of a municipality with a population of more than one million may negotiate with the commissioners court of a county with a population of less than

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.