Legislative intelligence / 90R
SESSION 2027View project ↗

Special District Local Laws Code § 3980.0306: APPROVAL BY THE CITY

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 3980, 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. 3980.0306. APPROVAL BY THE CITY. (a) The district must obtain the approval of the city for:

(1) the plans and specifications of an improvement project financed by bonds, notes, or other obligations; and

(2) the plans and specifications of an improvement project related to the use of land owned by the city, an easement granted by the city, or a right-of-way of a street, road, or highway.

(b) City approval may be by an administrative process that does not involve the city's governing body, unless approval of the city's governing body is required by federal, state, or local law, ordinance, or regulation.

(c) Before issuing bonds, the district must:

(1) provide to the city the documents authorizing the bonds;

(2) provide to the city a certification from each developer of property in the district that the developer is in compliance with the terms and conditions of the developer's project agreement with the city; and

(3) certify that the district is in compliance with the terms and conditions of the ordinance or resolution consenting to the creation of the district under Section 3980.0109 and the operating agreement entered into under that section.

(d) The city must complete the city's review of the documents and certifications required by Subsection (c) not later than the 30th day after the date the city receives the documents and certifications. The city may object to the issuance of the bonds if the city determines that:

(1) the district is not in compliance with the terms and conditions of the ordinance or resolution consenting to the creation of the district under Section 3980.0109;

(2) the district is not in compliance with the operating agreement entered into under Section 3980.0109; or

(3) a developer of property in the district is not in compliance with the terms and conditions of a project agreement that applies to the developer.

(e) If the city objects to the district's issuance of bonds, the district must obtain the consent of the city's governing body to the issuance of the bonds. The city's governing body may not unreasonably withhold consent to the issuance of bonds.

(f) Section 375.207, Local Government Code, does not apply to the district.

Added by Acts 2019, 86th Leg., R.S., Ch. 556 (H.B. 4683), Sec. 1, eff. June 10, 2019.

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.