Legislative intelligence / 90R
SESSION 2027View project ↗

Government Code § 2206.053: VOTE ON USE OF EMINENT DOMAIN

1 bill in the 90th Legislature would change this section

Part of Government Code Chapter 2206, 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. 2206.053. VOTE ON USE OF EMINENT DOMAIN. (a) Before a governmental entity initiates a condemnation proceeding by filing a petition under Section 21.012, Property Code, the governmental entity must:

(1) authorize the initiation of the condemnation proceeding at a public meeting by a record vote; and

(2) include in the notice for the public meeting as required by Subchapter C, Chapter 551, in addition to other information as required by that subchapter, the consideration of the use of eminent domain to condemn property as an agenda item.

(b) A single ordinance, resolution, or order may be adopted for all units of property to be condemned if:

(1) the motion required by Subsection (e) indicates that the first record vote applies to all units of property to be condemned; and

(2) the minutes of the governmental entity reflect that the first vote applies to all of those units.

(c) If more than one member of the governing body objects to adopting a single ordinance, resolution, or order by a record vote for all units of property for which condemnation proceedings are to be initiated, a separate record vote must be taken for each unit of property.

(d) For the purposes of Subsections (a) and (c), if two or more units of real property are owned by the same person, the governmental entity may treat those units of property as one unit of property.

(e) The motion to adopt an ordinance, resolution, or order authorizing the initiation of condemnation proceedings under Chapter 21, Property Code, must be made in a form substantially similar to the following: "I move that the (name of governmental entity) authorize the use of the power of eminent domain to acquire (describe the property) for (describe the public use)." The description of the property required by this subsection is sufficient if the description of the location of and interest in the property that the governmental entity seeks to acquire is substantially similar to the description that is or could properly be used in a petition to condemn the property under Section 21.012, Property Code.

(f) If a project for a public use described by Section 2206.001(c)(3) will require a governmental entity to acquire multiple tracts or units of property to construct facilities connecting one location to another location, the governing body of the governmental entity may adopt a single ordinance, resolution, or order by a record vote that delegates the authority to initiate condemnation proceedings to the chief administrative official of the governmental entity.

(g) An ordinance, resolution, or order adopted under Subsection (f) is not required to identify specific properties that the governmental entity will acquire. The ordinance, resolution, or order must identify the general area to be covered by the project or the general route that will be used by the governmental entity for the project in a way that provides property owners in and around the area or along the route reasonable notice that the own

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.