AB 1636 lets the Cerritos Community College District and geographically co‑located K–12 partners exchange a narrowly defined set of personally identifiable student information so the college can create community college student records that smooth enrollment into district courses. The bill directs the California Community Colleges Chancellor’s Office to produce a standard form that lists the exact data elements and to develop a secure transmission method; it limits use of the shared data to creating the student record and requires written consent.
The measure sets concrete deadlines for the state work (form and transmission method), authorizes district-level agreements to begin in late 2027, requires a legislative report on outcomes, and includes a built‑in repeal date. For operational teams and privacy officers, the bill is a focused pilot: it can lower enrollment friction for certain students but also forces agencies to align IT, consent workflows, and compliance without dedicated funding or a long-term statutory framework.
At a Glance
What It Does
The bill directs the Chancellor’s Office to define the specific PII fields needed to create a college student record and to approve a standardized form and transmission method. It authorizes the Cerritos governing board to sign data‑sharing agreements with qualifying local educational agencies so the K–12 partner can provide that limited PII for the narrow purpose of precreating a community college enrollment record.
Who It Affects
Directly affected parties include Cerritos Community College District administrators and enrollment systems, partnering school districts or county offices located in the district’s service area, the Chancellor’s Office (for standards and transmission), and students or their parents/guardians whose records will be shared. Vendors that run OpenCCC/CCCApply or local SIS systems will also need to adapt.
Why It Matters
This is an operational pilot bridging K–12 and community college record systems that could increase dual‑enrollment and reduce enrollment friction, while centralizing the state's role in defining data elements and transmission standards. It also tests a template for local data sharing with privacy guardrails — but only for a fixed period, which shapes how much investment stakeholders will make.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill starts by defining key terms and limiting the program to the Cerritos Community College District and partnering local educational agencies that have an authorized formal partnership and sit inside the district’s service area. That geographic and partnership gate narrows who can participate and keeps the effort local rather than statewide.
Next, the Chancellor’s Office must produce two things: a standardized form that lists the personally identifiable fields required to build a college student record, and a method for the district to compile and transmit that PII to the Chancellor’s Office. The transmission method must meet applicable state and federal privacy laws and may reuse existing system capabilities — the text explicitly contemplates leveraging current batch processing and registration systems rather than building a bespoke integration.Beginning September 30, 2027, the Cerritos governing board may enter data‑sharing agreements with eligible LEAs.
Those agreements must limit the exchange to the fields on the Chancellor’s form and require the LEA to obtain express written consent from the student (if 18 or older) or the student’s parent/guardian. The district then compiles the received PII and sends it to the Chancellor’s Office via the approved method so the state system can create the community college student record used for enrollment.To close the loop, the bill requires the district, working with the Chancellor’s Office, to report to the Legislature by January 1, 2031 on whether the pilot accomplished its goal of providing seamless enrollment.
The entire provision is temporary: it sunsets and is repealed on January 1, 2032. Operationally, implementing the pilot will require mapping PII fields between K–12 and community college systems, designing consent collection and storage workflows, and deciding how to leverage batch processing without triggering data quality or security problems.
The Five Things You Need to Know
The Chancellor’s Office must develop or approve a standardized form identifying the PII needed to create a community college student record by February 1, 2027.
The Chancellor’s Office must develop a transmission method — which may reuse existing system capabilities — by September 1, 2027, and the district must use that method to send compiled PII.
Cerritos CCD may begin entering data‑sharing agreements with eligible local educational agencies on or after September 30, 2027; agreements are limited to agencies inside the district service area with an authorized partnership.
A data‑sharing agreement must require express written consent from the student if age 18 or older, or from the student’s parent or guardian if the student is a minor, before transmitting the listed PII.
The pilot must produce a joint report to the Legislature by January 1, 2031, and the statutory authority for these exchanges automatically repeals on January 1, 2032.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions and scope
Subdivision (a) sets narrow definitions: it makes the Chancellor’s Office, Cerritos Community College District, and a 'partnering local educational agency' the operative players and restricts partnering LEAs to those both authorized by statute to partner and physically located inside the district’s service area. That geographic and legal filter confines who can participate and reduces the chances the program will be treated as a broad statewide mandate.
Standardized form and required PII (state role)
This provision tasks the Chancellor’s Office with developing or approving a single form that enumerates the personally identifiable student information needed to create a community college student record. It also requires the Chancellor’s Office to identify, in the process of designing the transmission method, which specific data elements are required. Practically, this centralizes data‑field decisions at the state level so that all participating partners will share the same minimum dataset, facilitating matching and reducing unnecessary data transfer — but it also means the state decides what counts as 'necessary' PII.
Transmission method and privacy compliance
The Chancellor’s Office, in collaboration with the district, must devise the method by which the district compiles and sends PII to the Chancellor’s Office; that method must comply with state and federal privacy laws and may lean on existing system capabilities. This explicitly contemplates pragmatic reuse of batch processing or current registration flows, which lowers build cost but raises questions about whether legacy systems have sufficient security, audit trails, and matching logic for this new use.
Data‑sharing agreements, consent, and batching
The statute allows the district to enter into data‑sharing agreements with eligible LEAs starting on a set date and confines the shared data to the elements on the Chancellor’s form. Agreements must require express written consent from the student or parent/guardian before transfer. Once received, the district must compile and transmit the information to the Chancellor’s Office via the approved method, using batch processes that leverage existing capabilities (the bill cites noncredit registration as an example). This combination of contractual requirements and a defined technical flow provides an implementable path, but puts the mechanics of consent collection and batch matching squarely on LEAs and the district.
Reporting and sunset
The district and Chancellor’s Office must submit a report to the Legislature by January 1, 2031 assessing whether the program achieved seamless enrollment for participating students. The statute automatically repeals on January 1, 2032. Those deadlines frame the policy as a time‑limited pilot rather than a permanent integration, shaping how much investment stakeholders will commit and setting a concrete evaluation point for policymakers.
This bill is one of many.
Codify tracks hundreds of bills on Education across all five countries.
Explore Education in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Participating high school and K–12 students in the district service area — they gain a lower‑friction path to enroll in community college courses because a student record can be precreated using data supplied by their LEA.
- Cerritos Community College District administrative teams — the district stands to streamline enrollment workflows, reduce manual data entry, and potentially increase dual‑enrollment and early‑college participation.
- Partnering local educational agencies with formal partnerships — school districts and county offices that participate can present a clearer college pathway to students without each student completing a separate college application flow.
- California Community Colleges Chancellor’s Office — gains a standardized data dictionary for the limited purpose, improving data consistency and giving the system a tested method for K–12 to CC transitions that could inform future policy.
Who Bears the Cost
- Partnering local educational agencies — they must collect and document express written consent, map SIS fields to the Chancellor’s form, and establish secure transfer processes, all of which create administrative and IT costs.
- Cerritos Community College District — must modify registration and batch processing workflows, implement matching and identity resolution, maintain compliance controls, and absorb integration and ongoing operational costs.
- Chancellor’s Office — must design, approve, and oversee the standardized form and transmission method and handle additional intake of PII and oversight responsibilities without any dedicated funding in the bill.
- Students and parents — although they benefit from streamlined enrollment, they assume increased exposure of PII and must navigate consent choices; any breach or data‑quality error could affect students’ records.
Key Issues
The Core Tension
The central dilemma is between lowering administrative barriers to college enrollment for individual students (and improving transition rates) and increasing the volume and movement of sensitive student PII across agencies and systems; the bill solves access problems by shifting operational and privacy risks onto districts, LEAs, and the Chancellor’s Office without a parallel funding or liability framework.
The bill threads a narrow needle: it advances enrollment access by enabling precreation of college records but does so by expanding cross‑sector transfer of personally identifiable student information. The statute centralizes the decision about which data elements are 'required' at the Chancellor’s Office, but it does not spell out retention periods, breach notification responsibilities, or liability allocations between LEAs, the district, the Chancellor’s Office, and vendors.
Those implementation details matter for both legal compliance (FERPA, state privacy law, and any contractual obligations) and operational risk.
Operationally, the reliance on existing system capabilities and batch processing lowers initial costs but raises matching, duplication, and security questions. Legacy batch jobs are not always designed for cross‑agency identity resolution; mismatches could create duplicate or misattributed college records.
The consent requirement is explicit (written consent from adult students or parents/guardians), but the bill does not set standards for how consent is recorded, stored, or audited — practical gaps that could expose districts or LEAs to disputes. Finally, the statute’s sunset constrains long‑term planning: stakeholders may be reluctant to invest in durable integrations for a pilot that legally ends in 2032 unless the pilot demonstrates clear returns quickly.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.