Legislative intelligence / 90R
SESSION 2027View project ↗

Local Government Code § 232.001: PLAT REQUIRED

2 bills in the 90th Legislature would change this section

Part of Local Government Code Chapter 232, 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. 232.001. PLAT REQUIRED. (a) The owner of a tract of land located outside the limits of a municipality must have a plat of the subdivision prepared if the owner divides the tract into two or more parts to lay out:

(1) a subdivision of the tract, including an addition;

(2) lots; or

(3) streets, alleys, squares, parks, or other parts of the tract intended by the owner of the tract to be dedicated to public use.

(a-1) A division of a tract under Subsection (a) includes a division regardless of whether it is made by using a metes and bounds description in a deed of conveyance or in a contract for a deed, by using a contract of sale or other executory contract to convey, or by using any other method.

(b) To be recorded, the plat must:

(1) describe the subdivision by metes and bounds;

(2) locate the subdivision with respect to an original corner of the original survey of which it is a part; and

(3) state the dimensions of the subdivision and of each lot, street, alley, square, park, or other part of the tract intended to be dedicated to public use or for the use of purchasers or owners of lots fronting on or adjacent to the street, alley, square, park, or other part.

(c) The owner or proprietor of the tract or the owner's or proprietor's agent must acknowledge the plat in the manner required for the acknowledgment of deeds.

(d) The plat must be filed and recorded with the county clerk of the county in which the tract is located.

(e) The plat is subject to the filing and recording provisions of Section 12.002, Property Code.

(f) The commissioners court may require a plat application submitted for approval to include a digital map that is compatible with other mapping systems used by the county and that georeferences the subdivision plat and related public infrastructure using the Texas Coordinate Systems adopted under Section 21.071, Natural Resources Code. A digital map required under this subsection may be required only in a format widely used by common geographic information system software. A requirement adopted under this subsection must provide for an exemption from the requirement if the owner of the tract submits with the plat application an acknowledged statement indicating that the digital mapping technology necessary to submit a map that complies with this subsection was not reasonably accessible.

(g) A plat is considered filed on the date the applicant submits the plat, along with a completed plat application and the application fees and other requirements prescribed by or under this subchapter, to:

(1) the commissioners court; or

(2) the county authority responsible for approving plats.

(h) The commissioners court or the county authority responsible for approving plats may not require an analysis, study, document, agreement, or similar requirement to be included in or as part of an application for a plat, development permit, or subdivision of land that is not explicitly required by state law.

Acts 1987, 70th Leg., ch. 1

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.