Legislative intelligence / 90R
SESSION 2027View project ↗

HB 338: Relating to reimbursement of infrastructure costs incurred by a developer of attainable housing developments by certain municipalities and counties.

Session
90th Texas Legislature, Regular Session
Status
Filed
Filed
Nov 9, 2026
Most recent action
11/09/2026 H Filed
Authors
Raymond
Official subjects
City Government--General; County Government--General; Housing--General

AI summary (not official): Lets certain municipalities and counties reimburse developers for infrastructure costs tied to qualifying attainable housing developments.

Topics: Housing & property, Local government. From AI review or caption rules.

Laws this bill changes

Bill text (Introduced)

90R2995 DRS-D

By: Raymond H.B. No. 338

A BILL TO BE ENTITLED

AN ACT

relating to reimbursement of infrastructure costs incurred by a developer of attainable housing developments by certain municipalities and counties.

BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF TEXAS:

SECTION 1.

Subtitle C, Title 12, Local Government Code, is amended by adding Chapter 396 to read as follows: CHAPTER 396. ATTAINABLE HOUSING DEVELOPMENT INFRASTRUCTURE FOR CERTAIN MUNICIPALITIES AND COUNTIES

Sec. 396.001. DEFINITIONS. In this chapter:

(1) "Attainable housing development" means a residential development consisting of at least seven acres that is developed or renovated to provide at least 50 single-family offsite residences.

(2) "Infrastructure" means:

(A) a facility for water, wastewater, electricity, broadband Internet service, or another utility; and

(B) a street, road, highway, or bridge.

(3) "Single-family offsite residence" means a housing unit governed by Chapter 1201, Occupations Code.

(4) "Tax year" has the meaning assigned by Section 1.04, Tax Code.

Sec. 396.002. APPLICABILITY. This chapter applies only to:

(1) a county with a population of 2.5 million or more but less than 4 million;

(2) a county with a population of 190,000 or more that is adjacent to a county described by Subdivision (1);

(3) a county that:

(A) is adjacent to the Texas-Mexico border;

(B) has a population of less than 300,000; and

(C) contains a municipality with a population of 200,000 or more; and

(4) a municipality wholly or partly located in a county described by Subdivision (1), (2), or (3).

Sec. 396.003. ELIGIBILITY FOR INFRASTRUCTURE COST REIMBURSEMENT. (a) A developer is eligible for reimbursement under this chapter for a cost incurred to build infrastructure related to an attainable housing development if:

(1) the developer directly or indirectly incurred the cost of building or financing the construction, maintenance, or renovation of the infrastructure or connection of the infrastructure to the development;

(2) a municipality or county would have built or financed the infrastructure had the infrastructure not been built by the developer;

(3) at least 80 percent of the lots in the development accommodate a single-family offsite residence that is at least 1,000 square feet and not more than 2,500 square feet in area;

(4) the development is connected to:

(A) a public water system; and

(B) a sewer system as defined by Section 26.001, Water Code;

(5) the development is governed by a property owners' association agreement or land lease agreement that includes restrictive covenants relating to the maintenance of the common areas and grounds of the development and enforcement of community regulations;

(6) the developer offers units in the development to veterans or active duty members of the military, first responders, or employees of a school district; and

(7) the developer complies with Federal Housing Administration tenant site lease protections required by:

(A) a municipality in which the development is wholly or partly located; and

The text continues: full text of HB 338.

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.