Legislative intelligence / 90R
SESSION 2027View project ↗

Education Code § 29.066: PEIMS REPORTING REQUIREMENTS

3 bills in the 90th Legislature would change this section

Part of Education Code Chapter 29, 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. 29.066. PEIMS REPORTING REQUIREMENTS. (a) A school district that is required to offer bilingual education or special language programs shall include the following information in the district's Public Education Information Management System (PEIMS) report:

(1) demographic information, as determined by the commissioner, on students enrolled in district bilingual education or special language programs;

(2) the number and percentage of students enrolled in each instructional model of a bilingual education or special language program offered by the district; and

(3) the number and percentage of students identified as emergent bilingual students who do not receive specialized instruction.

(b) For purposes of this section, the commissioner shall adopt rules to classify programs under this section as follows:

(1) if the program is a bilingual education program, the program must be classified under the Public Education Information Management System (PEIMS) report as:

(A) transitional bilingual/early exit: a bilingual program that serves students identified as emergent bilingual students in both English and Spanish and transfers a student to English-only instruction not earlier than two or later than five years after the student enrolls in school;

(B) transitional bilingual/late exit: a bilingual program that serves students identified as emergent bilingual students in both English and Spanish and transfers a student to English-only instruction not earlier than six or later than seven years after the student enrolls in school;

(C) dual language immersion/two-way: a biliteracy program that integrates students proficient in English and students identified as emergent bilingual students in both English and Spanish and transfers a student identified as an emergent bilingual student to English-only instruction not earlier than six or later than seven years after the student enrolls in school; or

(D) dual language immersion/one-way: a biliteracy program that serves only students identified as emergent bilingual students in both English and Spanish and transfers a student to English-only instruction not earlier than six or later than seven years after the student enrolls in school; and

(2) if the program is a special language program, the program must be classified under the Public Education Information Management System (PEIMS) report as:

(A) English as a second language/content-based: an English program that serves students identified as emergent bilingual students in English only by providing a full-time teacher certified under Section 29.061(c) to provide supplementary instruction for all content area instruction; or

(B) English as a second language/pull-out: an English program that serves students identified as emergent bilingual students in English only by providing a part-time teacher certified under Section 29.061(c) to provide English language arts instruction exclusively, while the student remains in a mainstream instructional arrangeme

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.