Legislative intelligence / 90R
SESSION 2027View project ↗

Water Code § 49.181: AUTHORITY OF COMMISSION OVER ISSUANCE OF DISTRICT BONDS

1 bill in the 90th Legislature would change this section

Part of Water Code Chapter 49, 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. 49.181. AUTHORITY OF COMMISSION OVER ISSUANCE OF DISTRICT BONDS. (a) A district may not issue bonds to finance a project for which the commission has adopted rules requiring review and approval unless the commission determines that the project is feasible and issues an order approving the issuance of the bonds. This section does not apply to:

(1) refunding bonds if the commission issued an order approving the issuance of the bonds or notes that originally financed the project;

(2) refunding bonds that are issued by a district under an agreement between the district and a municipality allowing the issuance of the district's bonds to refund bonds issued by the municipality to pay the cost of financing facilities;

(3) bonds issued to and approved by:

(A) the Farmers Home Administration;

(B) the United States Department of Agriculture;

(C) the North American Development Bank;

(D) the Texas Water Development Board; or

(E) a federally chartered instrumentality of the United States authorized under 12 U.S.C. Section 2128(f) to finance such a project, provided that the district that issues the bonds is located wholly in a county that:

(i) does not contain a municipality that has a population of more than 750,000; and

(ii) is not adjacent to a county described by Subparagraph (i);

(4) refunding bonds issued to refund bonds described by Subdivision (3); or

(5) bonds issued by a public utility agency created under Chapter 572, Local Government Code, any of the public entities participating in which are districts if at least one of those districts is a district described by Subsection (h)(1)(E).

(b) A district may submit to the commission a written application for investigation of feasibility. An engineer's report describing the project, including the data, profiles, maps, plans, and specifications prepared in connection with the report, must be submitted with the application.

(c) The executive director shall examine the application and the report and shall inspect the project area. The district shall, on request, supply the executive director with additional data and information necessary for an investigation of the application, the engineer's report, and the project.

(d) The executive director shall prepare a written report on the project and include suggestions, if any, for changes or improvements in the project. The executive director shall retain a copy of the report and send a copy of the report to both the commission and the district.

(e) The commission shall consider the application, the engineer's report, the executive director's report, and any other evidence allowed by commission rule to be considered in determining the feasibility of the project.

(f) The commission shall determine whether the project to be financed by the bonds is feasible and issue an order either approving or disapproving, as appropriate, the issuance of the bonds. If the commission determines that an application for the approval of bonds complies with the

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.