Legislative intelligence / 90R
SESSION 2027View project ↗

Property Code § 53.106: AFFIDAVIT OF COMPLETION

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 53, 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. 53.106. AFFIDAVIT OF COMPLETION. (a) An owner may file with the county clerk of the county in which the property is located an affidavit of completion. The affidavit must contain:

(1) the name and address of the owner;

(2) the name and address of the original contractor;

(3) a description, legally sufficient for identification, of the real property on which the improvements are located;

(4) a description of the improvements furnished under the original contract;

(5) a statement that the improvements under the original contract have been completed and the date of completion; and

(6) a conspicuous statement that a claimant may not have a lien on retained funds unless the claimant files an affidavit claiming a lien in the time and manner required by this chapter.

(b) A copy of the affidavit must be sent to the original contractor and to each claimant who sends a notice to the owner under Section 53.056 or 53.057 not later than the third day after the date the affidavit is filed or the 10th day after the date the owner receives the notice of lien liability, whichever is later.

(c) A copy of the affidavit must also be sent to each person who furnishes labor or materials for the property and who furnishes the owner with a written request for the copy. The owner must furnish the copy to the person not later than the date the affidavit is filed or the 10th day after the date the request is received, whichever is later.

(d) An affidavit filed under this section is prima facie evidence of the date the work under the original contract is completed for purposes of this chapter. If the affidavit is filed after the 10th day after the date of completion, the date of completion for purposes of this subchapter is the date the affidavit is filed. This subsection does not apply to a person to whom the affidavit was not sent as required by this section.

(e) Repealed by Acts 1999, 76th Leg., ch. 889, Sec. 12, eff. Sept. 1, 1999.

Added by Acts 1989, 71st Leg., ch. 1138, Sec. 18, eff. Sept. 1, 1989. Amended by Acts 1997, 75th Leg., ch. 526, Sec. 14, eff. Sept. 1, 1997; Acts 1999, 76th Leg., ch. 889, Sec. 12, eff. Sept. 1, 1999.

Amended by:

Acts 2011, 82nd Leg., R.S., Ch. 499 (H.B. 1390), Sec. 5, eff. September 1, 2011.

Acts 2021, 87th Leg., R.S., Ch. 690 (H.B. 2237), Sec. 19, eff. January 1, 2022.

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.