Legislative intelligence / 90R
SESSION 2027View project ↗

Government Code § 411.0727: PROCEDURE FOLLOWING SUCCESSFUL COMPLETION OF VETERANS TREATMENT COURT PROGRAM

1 bill in the 90th Legislature would change this section

Part of Government Code Chapter 411, 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. 411.0727. PROCEDURE FOLLOWING SUCCESSFUL COMPLETION OF VETERANS TREATMENT COURT PROGRAM. (a) This section applies only to a person who successfully completes a veterans treatment court program under Chapter 124 or former law.

(b) Notwithstanding any other provision of this subchapter or Subchapter F, a person described by Subsection (a) is entitled to file with the court that placed the person in the veterans treatment court program a petition for an order of nondisclosure of criminal history record information under this section if the person:

(1) satisfies the requirements of this section and Section 411.074;

(2) has never been previously convicted of an offense listed in Article 42A.054(a), Code of Criminal Procedure, or a sexually violent offense, as defined by Article 62.001, Code of Criminal Procedure; and

(3) is not convicted of any felony offense between the date on which the person successfully completed the program and the second anniversary of that date.

(c) Regardless of whether the person was convicted of or placed on deferred adjudication community supervision for the offense for which the person entered the veterans treatment court program or whether the case against the person was dismissed under Section 124.001(b), after notice to the state, an opportunity for a hearing, and a determination that the person is entitled to file the petition and issuance of the order is in the best interest of justice, the court shall issue an order prohibiting criminal justice agencies from disclosing to the public criminal history record information related to the offense for which the person entered the veterans treatment court program.

(d) A person may file with the court that placed the person in the veterans treatment court program a petition for an order of nondisclosure of criminal history record information under this section only on or after the second anniversary of the date the person successfully completed the program.

(e) A person is not entitled to petition the court for an order of nondisclosure of criminal history record information under this section if the person's entry into the veterans treatment court program arose as the result of a conviction of an offense involving the operation of a motor vehicle while intoxicated.

Added by Acts 2017, 85th Leg., R.S., Ch. 889 (H.B. 3069), Sec. 4, eff. September 1, 2017.

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.