Legislative intelligence / 90R
SESSION 2027View project ↗

Property Code § 27.007: DISCLOSURE STATEMENT REQUIRED

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Property Code Chapter 27, 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. 27.007. DISCLOSURE STATEMENT REQUIRED. (a) A written contract subject to this chapter, other than a contract between a developer of a condominium and a contractor for the construction or repair of a residence or appurtenance to a residence in a condominium, must contain in the contract a notice printed or typed in 10-point boldface type or the computer equivalent that reads substantially similar to the following:

"This contract is subject to Chapter 27 of the Texas Property Code. The provisions of that chapter may affect your right to recover damages arising from a construction defect. If you have a complaint concerning a construction defect and that defect has not been corrected as may be required by law or by contract, you must provide the notice required by Chapter 27 of the Texas Property Code to the contractor by certified mail, return receipt requested, not later than the 60th day before the date you file suit to recover damages in a court of law or initiate arbitration. The notice must refer to Chapter 27 of the Texas Property Code and must describe the construction defect. If requested by the contractor, you must provide the contractor an opportunity to inspect and cure the defect as provided by Section 27.004 of the Texas Property Code."

(b) If a contract does not contain the notice required by this section, the claimant may recover from the contractor a civil penalty of $500 in addition to any other remedy provided by this chapter.

(c) Repealed by Acts 2023, 88th Leg., R.S., Ch. 291 (S.B. 1768), Sec. 13(4), eff. May 29, 2023, and Ch. 441 (H.B. 2022), Sec. 8(3), eff. September 1, 2023.

Added by Acts 1999, 76th Leg., ch. 189, Sec. 8, eff. Sept. 1, 2000. Amended by Acts 2003, 78th Leg., ch. 458, Sec. 2.06, eff. Sept. 1, 2003.

Amended by:

Acts 2007, 80th Leg., R.S., Ch. 750 (H.B. 3147), Sec. 2, eff. September 1, 2007.

Acts 2007, 80th Leg., R.S., Ch. 843 (H.B. 1038), Sec. 4, eff. September 1, 2007.

Acts 2023, 88th Leg., R.S., Ch. 291 (S.B. 1768), Sec. 13(4), eff. May 29, 2023.

Acts 2023, 88th Leg., R.S., Ch. 441 (H.B. 2022), Sec. 8(3), eff. September 1, 2023.

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.