SB 399 adds Education Code section 46600.5 and requires every California school district to keep a record of all interdistrict transfer requests and the disposition of those requests. The statute lists both aggregate counts (granted, denied, withdrawn; transfers in and out) and a set of pupil-level data points — race, ethnicity, gender, self-reported socioeconomic status, free or reduced-price meals eligibility, foster or homeless status, district of residence, English learner and special education classification, and the self-reported reason for the transfer request.
Districts must submit the collected information for the current school year to the State Superintendent by June 30 each year; the Superintendent is required to post the data on the department website by August 1, and may supply templates and guidance. The bill creates new compliance duties for districts and triggers the state-mandated local program process for potential reimbursement.
At a Glance
What It Does
Requires districts to maintain records of every interdistrict transfer request and specified disposition details, collect a defined set of pupil-level demographic and status data, submit that information annually to the State Superintendent, and have it posted publicly by the Department of Education. The Superintendent can issue a reporting template and procedural guidance.
Who It Affects
All California public school districts (including their enrollment/data teams and compliance officers), county offices of education that support small districts, the California Department of Education (for aggregation and posting), and families and advocates who track transfer patterns and equity.
Why It Matters
It creates a routine, statewide data feed about student mobility across district lines that policymakers, researchers, and civil-rights monitors can use to detect access or equity issues, while also imposing operational and privacy duties on districts.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 399 requires districts to treat interdistrict transfer requests as a reportable data flow rather than a purely local administrative matter. Each district must log every request and its outcome, and collect both simple counts (granted, denied, withdrawn; transfers in/out) and a set of pupil-level fields.
Those pupil-level fields include basic demographics, indicators of economic need (free/reduced-price meals and a self-reported socioeconomic field), custodial status flags (foster or homeless), English learner and special education classification (tied to Education Code section 56026), the pupil’s district of residence, and the applicant’s self-reported reason for seeking the transfer.
The bill sets a firm annual cadence: districts submit that year’s data to the State Superintendent by June 30, and the Department of Education posts the submitted information on its website by August 1. The Superintendent may offer a template and guidance on collection and reporting procedures, but the statute leaves the technical format and level of aggregation to the Superintendent’s specification.
The reference to "current school year" means districts will need to decide how to align admission dates, late approvals, and withdrawals with the reporting snapshot.Operationally, districts will have to adapt intake and recordkeeping so reasons for denials are documented and pupil-level fields are captured in a way that supports later aggregation. Small districts and those with limited student information systems will likely need process changes or vendor help to add the new fields and extract them for submission.
Finally, SB 399 invokes the state-mandated local program framework: if the Commission on State Mandates finds this imposes reimbursable costs, reimbursement flows under the Government Code provisions cited in the bill.
The Five Things You Need to Know
Section 46600.5(a) requires districts to keep records of all interdistrict transfer requests and their dispositions, including counts of requests granted, denied, or withdrawn and the reasons for any denials.
Districts must collect pupil-level fields for transferred pupils: race, ethnicity, gender, self-reported socioeconomic status, free/reduced-price meals eligibility, foster youth status, homeless status, district of residence, and the self-reported reason for the transfer.
For pupils transferred in or out, districts must report whether those pupils are English learners or have exceptional needs as defined in Education Code section 56026.
Districts must submit the compiled data for the current school year to the State Superintendent by June 30 annually; the Superintendent must post the submitted data on the Department of Education website by August 1 and may provide a reporting template.
The bill makes the requirements a potential state-mandated local program: if the Commission on State Mandates finds costs, state reimbursement is required under the cited Government Code provisions.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
What districts must record
Subdivision (a) lists the substantive recordkeeping obligations. Districts must capture both aggregate counts (requests granted, denied, withdrawn; transfers in and out) and pupil-level fields for each transferred pupil. The pupil-level items are extensive — demographics, program eligibility (FRPM), foster/homeless status, EL and special education flags (referencing Section 56026), district of residence, and a self-reported reason for the transfer. Practically, this requires districts to add or map these fields into their student information systems and to ensure denials are logged with stated reasons.
Annual submission to the Superintendent
Subdivision (b) imposes a yearly reporting duty: districts must submit the information maintained under subdivision (a) for the current school year to the State Superintendent by June 30. The submission must follow a manner specified by the Superintendent, which creates flexibility but also means districts may need to adapt to an unknown format until guidance is released. "Current school year" places emphasis on aligning district intake and approval timelines with the reporting snapshot.
State posting and optional template/guidance
Subdivision (c) requires the Superintendent to post the submitted data on the department’s internet site by August 1 and authorizes the Superintendent to provide a template and guidance. The posting requirement creates a public transparency obligation for the Department of Education; the statutory authorization for templates means the Department can standardize formats and reduce district variance, but the law does not prescribe the level of aggregation or redaction to be applied before public release.
State-mandated local program and reimbursement
Section 2 ties the bill to the state-mandated local program process: if the Commission on State Mandates finds the law imposes reimbursable costs, reimbursements follow the Government Code process cited. The provision protects districts only to the extent the Commission makes a favorable finding; the bill leaves unresolved the timing and sufficiency of any reimbursement relative to districts’ upfront expenses.
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
- Parents, guardians and student advocates — gain public information about transfer patterns and reasons, which supports transparency around access, enrollment pressures, and possible inequities across districts.
- State and local policymakers and researchers — receive standardized, statewide data to analyze mobility, segregation trends, and the effectiveness of transfer policies.
- Receiving and sending districts — can use reported transfer counts and pupil attributes to plan staffing, programing, and resource allocation more accurately if data are timely and reliable.
- Civil-rights and equity monitors — obtain a new evidentiary basis to investigate patterns of denial by reason or demographics, improving oversight capacity.
Who Bears the Cost
- School districts (especially small and rural districts) — must upgrade intake processes and student data systems, train staff to capture new fields, and allocate time to compile and submit datasets by the June 30 deadline.
- County offices of education and district IT vendors — will likely face increased demand for technical support, system configuration, and data extraction services, producing direct contract or staffing costs.
- California Department of Education (CDE) — must create templates, process incoming data from hundreds of districts, apply any necessary aggregation or redaction, and host public posting, adding workload to an already busy data team.
- Students and families — face increased collection of sensitive status markers (foster, homeless, socioeconomics) that raises privacy and data-security stakes, especially if public posting is at a granular level.
Key Issues
The Core Tension
The central dilemma is transparency versus privacy and capacity: SB 399 demands public, pupil-level insight into interdistrict mobility to surface equity issues, but doing so requires collecting and publishing sensitive student attributes and places material operational burdens on districts and the Department without clear, guaranteed funding or detailed privacy safeguards.
SB 399 advances transparency but leaves several practical questions unanswered that could complicate implementation. The statute requires detailed pupil-level fields including sensitive flags (foster, homeless, socioeconomic) and a "self-reported reason" for transfers, but it does not set standards for how districts must collect or verify that information, nor does it specify retention periods or minimum anonymization before public posting.
That gap forces districts and the Department of Education to make consequential choices about data quality, parental consent, and identifiability.
The bill also risks duplication with existing federal- and state-level student reporting systems (for example, CALPADS), creating potential inefficiencies unless the Superintendent aligns the required submission format with existing feeds. The June 30 submission date may not align with local transfer decision calendars or midyear movements, producing reporting edge cases (late approvals, retroactive withdrawals).
Finally, while the bill references the state-mandated local program reimbursement process, there is no immediate funding mechanism: districts must shoulder up-front costs until and unless the Commission orders reimbursement, and the statute does not define audits, penalties for noncompliance, or the granularity of public posting.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.