Legislative intelligence / 90R
SESSION 2027View project ↗

Family Code § 85.021: REQUIREMENTS OF ORDER APPLYING TO ANY PARTY

2 bills in the 90th Legislature would change this section

Part of Family Code Chapter 85, 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. 85.021. REQUIREMENTS OF ORDER APPLYING TO ANY PARTY. In a protective order, the court may:

(1) prohibit a party from:

(A) removing a child who is a member of the family or household from:

(i) the possession of a person named in the order; or

(ii) the jurisdiction of the court;

(B) transferring, encumbering, or otherwise disposing of property, other than in the ordinary course of business, that is mutually owned or leased by the parties; or

(C) removing a pet, companion animal, or assistance animal, as defined by Section 121.002, Human Resources Code, from the possession or actual or constructive care of a person named in the order;

(2) grant exclusive possession of a residence to a party and, if appropriate, direct one or more parties to vacate the residence if the residence:

(A) is jointly owned or leased by the party receiving exclusive possession and a party being denied possession;

(B) is owned or leased by the party retaining possession; or

(C) is owned or leased by the party being denied possession and that party has an obligation to support the party or a child of the party granted possession of the residence;

(3) provide for the possession of and access to a child of a party if the person receiving possession of or access to the child is a parent of the child;

(4) require the payment of support for a party or for a child of a party if the person required to make the payment has an obligation to support the other party or the child; or

(5) award to a party the use and possession of specified property that is community property or jointly owned or leased property.

Added by Acts 1997, 75th Leg., ch. 34, Sec. 1, eff. May 5, 1997.

Amended by:

Acts 2011, 82nd Leg., R.S., Ch. 136 (S.B. 279), Sec. 1, eff. September 1, 2011.

Acts 2013, 83rd Leg., R.S., Ch. 543 (S.B. 555), Sec. 1, eff. September 1, 2013.

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.