Legislative intelligence / 90R
SESSION 2027View project ↗

Education Code § 29.912: RURAL PATHWAY EXCELLENCE PARTNERSHIP (R-PEP) PROGRAM

6 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.912. RURAL PATHWAY EXCELLENCE PARTNERSHIP (R-PEP) PROGRAM. (a) In this section, "program" means the Rural Pathway Excellence Partnership (R-PEP) program.

(b) The commissioner shall establish and administer the Rural Pathway Excellence Partnership (R-PEP) program to incentivize and support multidistrict, cross-sector, rural college and career pathway partnerships that expand opportunities for underserved students to succeed in school and life while promoting economic development in rural areas.

(b-1) The commissioner shall ensure that agency employees assigned to administer the program have experience with or training in the procedures relating to a school district contracting to partner to operate a district campus under Section 11.174.

(c) The program must enable an eligible school district that has fewer than 1,600 students in average daily attendance to partner with at least one other school district located within a distance of 100 miles to offer a broader array of robust college and career pathways. Each partnership must:

(1) offer college and career pathways that align with regional labor market projections for high-wage, high-demand careers; and

(2) be managed by a coordinating entity that:

(A) has or will have at the time students are served under the partnership the capacity to effectively coordinate the partnership;

(B) has entered into a performance agreement approved by the board of trustees of each partnering school district that confers on the coordinating entity the same authority with respect to pathways offered under the partnership provided to an entity that contracts to operate a district campus under Section 11.174;

(C) is an eligible entity as defined by Section 12.101(a); and

(D) has on the entity's governing board as either voting or ex officio members, or has on an advisory body, representatives of each partnering school district and members of regional higher education and workforce organizations.

(c-1) A school district that has participated in the program may continue to participate in the program regardless of the number of students in average daily attendance in the district for the current school year.

(d) The performance agreement described by Subsection (c)(2)(B) must:

(1) include ambitious and measurable performance goals and progress measures tied to current college, career, and military readiness outcomes and longitudinal postsecondary completion and employment-related outcomes;

(2) allocate responsibilities for accessing and managing progress and outcome information and annually publish that information on the Internet website of each partnering district and the coordinating entity;

(3) authorize the coordinating entity to optimize the value of each college and career pathway offered through the partnership by:

(A) determining scheduling;

(B) adding or removing a pathway;

(C) selecting and assigning pathway-specific personnel;

(D) developing and exercising final approval of pathway bud

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.