CALPADS error brief ยท IVR
IVR0612
Official CALPADS rule
What CALPADS is rejecting
Student has an existing record with the same Special Education Plan Effective Start Date
Focus fields
Fields validated
23.04 - Reporting LEA 23.06 - SSID 23.09 - Reporting SELPA 23.12 - Special Education Plan Effective Start DateRecommended correction path
Suggested resolution
Read the complete validation
CALPADS rule: Student has an existing record with the same Special Education Plan Effective Start Date
Fields involved:
- 23.04 - Reporting LEA
- 23.06 - SSID
- 23.09 - Reporting SELPA
- 23.12 - Special Education Plan Effective Start Date
Coordinate the correction
Recommended correction path
- Identify the exact student and plan iteration. Match SSID, Reporting LEA, Reporting SELPA, plan type, and Plan Effective Start Date before editing.
- Confirm the documented value. Compare every validated field with the authoritative source and the current CALPADS rule.
- Locate the true point of failure. Determine whether the issue is in source documentation, IEP/SEDS entry, SIS data, mapping, extract logic, or an existing CALPADS record.
- Correct the owning system. Use the authorized local process; do not overwrite accurate program information merely to make the transaction post.
- Regenerate and verify. Confirm the accepted effective-dated PLAN record, review connected records, and check whether the same mapping affected other students.
Official CALPADS guidance
Understanding the Error: The submitted file contains two or more PLAN records for a student that has the same Special Education Plan Effective Date or already in CALPADS ODS. A student should only have 1 PLAN record for a student per Special Education Plan Effective Start Date.
Suggested Resolution: Verify that the fields listed in the Fields Validated column are correct in the submitted file.
Official IVR0612 troubleshooting page | PLAN online-maintenance guidance | CALPADS system documentation
Cross-team correction support
Begin with: the authoritative plan history and the PLAN operational-key fields.
Coordinate: CALPADS coordinator, special education data steward, case-management owner, and extract support.
Then verify: prior PLAN iterations, SWDS status, MEET events, SERV records, and records generated by the same extract.


































































