Legislative intelligence / 90R
SESSION 2027View project ↗

Family Code § 55.67: PROCEEDINGS IN JUVENILE COURT FOR CHILD FOUND UNFIT TO PROCEED OR LACKING RESPONSIBILITY FOR CONDUCT DUE TO INTELLECTUAL DISABILITY

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 Family Code Chapter 55, 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. 55.67. PROCEEDINGS IN JUVENILE COURT FOR CHILD FOUND UNFIT TO PROCEED OR LACKING RESPONSIBILITY FOR CONDUCT DUE TO INTELLECTUAL DISABILITY. (a) If the juvenile court initiates proceedings under Section 55.40(1) or 55.59(1), the prosecuting attorney may file with the juvenile court an application for an interdisciplinary team report and recommendation that the child is in need of long-term placement in a residential care facility, under Section 593.041, Health and Safety Code. The juvenile court shall:

(1) set a date for a hearing and provide notice as required by Sections 593.047 and 593.048, Health and Safety Code; and

(2) conduct the hearing in accordance with Sections 593.049-593.056, Health and Safety Code.

(b) After conducting a hearing under this section and with consideration given to the least restrictive appropriate setting for services for the child and to the parent's, managing conservator's, or guardian's availability and willingness to participate in the services for the child, the juvenile court may order residential intellectual disability services for the child if the criteria under Section 55.06 are satisfied.

(c) On receipt of the court's order, the Health and Human Services Commission shall identify a residential care facility and admit the child to the identified facility.

(d) If the child is currently detained in a juvenile detention facility, the juvenile court shall:

(1) order the child released from detention to the child's home or another appropriate place;

(2) order the child detained or placed in an appropriate facility other than a juvenile detention facility; or

(3) conduct a detention hearing and, if the court makes findings under Section 54.01 to support further detention of the child, order the child to remain in the juvenile detention facility subject to further detention orders of the court.

Added by Acts 1999, 76th Leg., ch. 1477, Sec. 14, eff. Sept. 1, 1999. Amended by Acts 2001, 77th Leg., ch. 1297, Sec. 30, eff. Sept. 1, 2001.

Amended by:

Acts 2015, 84th Leg., R.S., Ch. 1 (S.B. 219), Sec. 1.012, eff. April 2, 2015.

Transferred, redesignated and amended from Family Code, Section 55.41 by Acts 2023, 88th Leg., R.S., Ch. 1166 (S.B. 1585), Sec. 20, eff. September 1, 2023.

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.