CALPADS error brief · SENR
SENR0606
Official CALPADS rule
What CALPADS is rejecting
Enrolled Eligible and Participating Students should have a current Education Plan
Focus fields
Fields validated
23.04 - Reporting LEA
23.12 - Special Education Plan Effective Start Date
Recommended correction path
Suggested resolution
Read the complete validation
CALPADS rule: Enrolled Eligible and Participating Students should have a current Education Plan
Fields involved:
- <p>23.04 - Reporting LEA<br>23.12 - Special Education Plan Effective Start Date</p>
How this record moves through CALPADS
Upload reminder: A file can upload successfully while individual records reject. Correct the source or extract when the next file would reproduce the error.
Choose the diagnostic pathway
- Enrollment dates and chronology
- When did the student actually begin attending?
- Is the enrollment still open, or should it have an exit?
- Does another enrollment overlap or continue this record?
- Do the SIS and CALPADS histories tell the same story?
- SSID and student identity
- Does the student have the correct SSID?
- Does the local record point to a retired or replaced SSID?
- Are staff reviewing the intended student before changing enrollment history?
- LEA, school, and enrollment ownership
- Which LEA and school own the enrollment?
- Is the school authorized under the Reporting LEA?
- Is the enrollment primary, secondary, short-term, or non-ADA?
- Enrollment exit and completion
- Is the enrollment still open?
- When and why did the student leave?
- Did the student complete school?
- Was another enrollment expected?
- Do Exit Reason and Completion Status describe the same event?
- E150 and continuing enrollment
- Was E150 used for a midyear update rather than a departure?
- Was the continuing enrollment created for the next calendar day?
- Did grade, transfer status, or geographic residence actually change?
- SIS, extract, and CALPADS reconciliation
- Is the authoritative SIS record correct?
- Did the extract transform or omit a value?
- Does CALPADS contain an older or conflicting enrollment?
- Will the next extract reproduce the error?
- Downstream student-record effects
- Does SINF overlap the qualifying enrollment?
- Could SPRG or SELA depend on these dates?
- Could the change affect attendance, assessment, course, cohort, dropout, or special-education reporting?
Read the enrollment sequence
- Prior recordLocate existing enrollment.
- New eventConfirm actual attendance date.
- ChronologyCompare starts, exits, and status.
- Source correctionRepair the inaccurate record.
- ODS verificationConfirm a coherent sequence.
Primary participants for this error
- CALPADS coordinator
- Registrar or enrollment staff
- School-site office staff
- Attendance staff
- SIS system owner
- Extract, integration, or vendor support
Compare three versions of the record
- What actually occurred.
- What the authoritative SIS contains.
- What the SENR file and CALPADS ODS contain.
The correction belongs where those versions first diverge.
Recommended correction path
Identify the exact enrollment
Match SSID, Reporting LEA, School of Attendance, start date, enrollment status, grade, and any exit information.
Reconstruct what occurred
Use enrollment, attendance, transfer, withdrawal, or completion documentation rather than inferring the answer from the validation.
Compare SIS, extract, and ODS
Locate the first point where the authoritative history and transmitted or stored values diverge.
Confirm the complete rule
Review every validated field, current code combinations, and any connected enrollment records.
Correct the owning system
Use the authorized local process and avoid a CALPADS-only edit that the next extract will overwrite.
Verify acceptance and downstream meaning
Confirm the complete enrollment history and review SINF, SPRG, SELA, attendance, assessment, cohort, and special-education effects as applicable.
Official CALPADS guidance
Understanding the Error:
When a student is on an Education plan and transfers to a new LEA, a new Special Education Plan (PLAN) record must be submitted at the new LEA with a PLAN Effective Start Date prior to Census Day.
NOTE: The Reporting LEA for SWDS record does not need to be the same as the Reporting LEA in the SENR record that overlaps census day.
Suggested Resolution:
1) Verify if the student has not exited the program. If they have exited, post a Student with Disabilities (SWDS) record reflecting the proper eligibility status.
2) Verify the student enrollment start and exit Date at the LEA.
3) Adopt the existing PLAN from the prior LEA using your student's enrollment start date as the PLAN Effective Start Date or submit a new PLAN record for the student with a date prior to Census Day.
Before closing the issue
- Confirm SENR0606 no longer appears for the intended enrollment.
- Verify the complete accepted enrollment history in CALPADS.
- Document source evidence, owner, correction location, and broader extract impact.
- Review downstream student records and reports affected by the correction.
Official SENR0606 troubleshooting page | SENR guidance | Fall 1 Reporting Roadmap
What SENR does—and does not do
SENR answers enrollment and SSID-context questions such as:
- Does this student have an SSID?
- Which LEA and school own this enrollment record?
- When did the enrollment begin?
- Is it primary, secondary, or short-term?
- What grade level applies to this enrollment?
- Is the enrollment still open?
- If it ended, when and why did the student leave?
- Did the student complete school?
- Was the student transferred, retained, promoted, or updated through an E150 enrollment transition?
- What is the student’s district of geographic residence?
SENR participant directory
Engage the roles needed for the specific student, enrollment event, ownership question, or system issue.
- CALPADS coordinator
- Registrar or enrollment staff
- School-site office staff
- Attendance staff
- Counselor or student-records staff
- Graduation or cohort-data staff
- District student-services administrator
- Charter or alternative-education program staff
- Special education data staff
- SIS system owner
- Extract, integration, or vendor support


































































