Legislative intelligence / 90R
SESSION 2027View project ↗

Property Code § 53.160: SUMMARY MOTION TO REMOVE INVALID OR UNENFORCEABLE LIEN

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.160. SUMMARY MOTION TO REMOVE INVALID OR UNENFORCEABLE LIEN. (a) In a suit brought to foreclose a lien or to declare a claim or lien invalid or unenforceable, a party objecting to the validity or enforceability of the claim or lien may file a motion to remove the claim or lien. The motion must be verified and state the legal and factual basis for objecting to the validity or enforceability of the claim or lien. The motion may be accompanied by supporting affidavits.

(b) The grounds for objecting to the validity or enforceability of the claim or lien for purposes of the motion are limited to the following:

(1) notice of claim was not timely furnished to the owner or original contractor as required by Section 53.056 or 53.057;

(2) an affidavit claiming a lien failed to comply with Section 53.054 or was not filed as required by Section 53.052;

(3) notice of the filed affidavit was not furnished to the owner or original contractor as required by Section 53.055;

(4) the deadlines for perfecting a lien claim for retainage under this chapter have expired and the owner complied with the requirements of Section 53.101 and paid the retainage and all other funds owed to the original contractor before:

(A) the claimant perfected the lien claim; and

(B) the owner received a notice of the claim as required by this chapter;

(5) all funds subject to the notice of a claim to the owner and a notice regarding the retainage have been deposited in the registry of the court and the owner has no additional liability to the claimant;

(6) when the lien affidavit was filed on homestead property:

(A) no contract was executed or filed as required by Section 53.254;

(B) the affidavit claiming a lien failed to contain the notice as required by Section 53.254; or

(C) the notice of the claim failed to include the statement required by Section 53.254; and

(7) the claimant executed a valid and enforceable waiver or release of the claim or lien claimed in the affidavit.

(c) The claimant is not required to file a response. The claimant and any other party that has appeared in the proceeding must be notified by at least 30 days before the date of the hearing on the motion. A motion may not be heard before the 30th day after the date the claimant answers or appears in the proceeding. The claimant must be allowed expedited discovery regarding information relevant to the issues listed under Subsection (b).

(d) At the hearing on the motion, the burden is on:

(1) the claimant to prove that the notice of claim and affidavit of lien were furnished to the owner and original contractor as required by this chapter; and

(2) the movant to establish that the lien should be removed for any other ground authorized by this section.

(e) The court shall promptly determine a motion to remove a claim or lien under this section. If the court determines that the movant is not entitled to remove the lien, the court shall enter an order denying the motion. If the court determines

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.