Legislative intelligence / 90R
SESSION 2027View project ↗

Government Code § 403.0246: LOCAL DEVELOPMENT AGREEMENT DATABASE

2 bills in the 90th Legislature would change this section

Part of Government Code Chapter 403, 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. 403.0246. LOCAL DEVELOPMENT AGREEMENT DATABASE. (a) In this section:

(1) "Business day" means a day other than a Saturday, Sunday, or state or national holiday.

(2) "Local development agreement" means:

(A) an agreement entered into by a municipality under Section 380.001 or 380.002, Local Government Code;

(B) an agreement entered into by a county under Section 381.004, Local Government Code;

(C) an agreement entered into by a local government under Chapter 312, Tax Code; or

(D) any other agreement to grant or otherwise commit public money or other resources for economic development purposes by a local government under Chapter 380 or 381, Local Government Code.

(3) "Local government" includes:

(A) a municipality;

(B) a county;

(C) a county industrial commission under Section 381.001, Local Government Code; or

(D) a board of development under Section 381.002, Local Government Code.

(b) The comptroller shall create and make accessible on the Internet a consolidated searchable data tool, to be known as the Local Development Agreement Database, that contains information regarding all local development agreements in this state.

(c) For each local development agreement described by Subsection (b), the database must include:

(1) the name of the local government that entered into the agreement;

(2) a numerical code assigned to the local government by the comptroller;

(3) the address of the local government's administrative offices and public contact information;

(4) the name of the appropriate officer or other person representing the local government and that person's contact information;

(5) the name and contact information of any entity or the entity's agent that entered into the agreement with the local government, including the business address and any assumed names of the entity;

(6) the date on which the agreement went into effect and the date and terms on which the agreement expires;

(7) the focus or scope of the agreement;

(8) an electronic copy of the agreement;

(9) the name and contact information of the individual reporting the information to the comptroller;

(10) the total monetary value of the agreement; and

(11) the source of the money used or type of tax implicated by the agreement, including a sales and use tax, ad valorem tax, or hotel occupancy tax.

(d) The comptroller may consult with the appropriate officer of, or other person representing, each local government that enters into a local development agreement to obtain the information necessary to operate and update the database.

(e) The comptroller shall enter into the database for access by the public the information described by Subsection (c) not later than the 15th business day after the date the comptroller receives the information from the providing local government. The information, including a copy of the agreement, must remain accessible to the public through the database during the period the agreement is in effect.

(f) The comptroller may not

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.