Legislative intelligence / 90R
SESSION 2027View project ↗

Estates Code § 32.003: JURISDICTION OF CONTESTED PROBATE PROCEEDING IN COUNTY WITH NO STATUTORY PROBATE COURT OR STATUTORY COUNTY COURT

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 Estates Code Chapter 32, 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. 32.003. JURISDICTION OF CONTESTED PROBATE PROCEEDING IN COUNTY WITH NO STATUTORY PROBATE COURT OR STATUTORY COUNTY COURT. (a) In a county in which there is no statutory probate court or county court at law exercising original probate jurisdiction, when a matter in a probate proceeding is contested, the judge of the county court may, on the judge's own motion, or shall, on the motion of any party to the proceeding, according to the motion:

(1) request the assignment of a statutory probate court judge to hear the contested matter, as provided by Section 25.0022, Government Code; or

(2) transfer the contested matter to the district court, which may then hear the contested matter as if originally filed in the district court.

(b) If a party to a probate proceeding files a motion for the assignment of a statutory probate court judge to hear a contested matter in the proceeding before the judge of the county court transfers the contested matter to a district court under this section, the county judge shall grant the motion for the assignment of a statutory probate court judge and may not transfer the matter to the district court unless the party withdraws the motion.

(b-1) If a judge of a county court requests the assignment of a statutory probate court judge to hear a contested matter in a probate proceeding on the judge's own motion or on the motion of a party to the proceeding as provided by this section, the judge may request that the statutory probate court judge be assigned to the entire proceeding on the judge's own motion or on the motion of a party.

(c) A party to a probate proceeding may file a motion for the assignment of a statutory probate court judge under this section before a matter in the proceeding becomes contested, and the motion is given effect as a motion for assignment of a statutory probate court judge under Subsection (a) if the matter later becomes contested.

(d) Notwithstanding any other law, a transfer of a contested matter in a probate proceeding to a district court under any authority other than the authority provided by this section:

(1) is disregarded for purposes of this section; and

(2) does not defeat the right of a party to the proceeding to have the matter assigned to a statutory probate court judge in accordance with this section.

(e) A statutory probate court judge assigned to a contested matter in a probate proceeding or to the entire proceeding under this section has the jurisdiction and authority granted to a statutory probate court by this subtitle. A statutory probate court judge assigned to hear only the contested matter in a probate proceeding shall, on resolution of the matter, including any appeal of the matter, return the matter to the county court for further proceedings not inconsistent with the orders of the statutory probate court or court of appeals, as applicable. A statutory probate court judge assigned to the entire probate proceeding as provided by Subsection (b-1) shall, on resolut

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.