CALPADS error brief · SWDS
SWDS0662F1
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
23.06 - SSID 23.12 - Special Education Plan Effective Start DateRecommended correction path
Suggested resolution
Status is not the same as enrollment, a meeting, a plan, or a service
Eligibility answers whether the student qualifies. Participation answers whether the student is receiving special education under the reported status. MEET records an event. PLAN records the operative education plan. SERV records services. Each relationship depends on its own effective date.
The history CALPADS is trying to reconstruct
Enrollment → SWDS status → MEET → PLAN → SERV → Fall 1 snapshot
| Stage | Record family | What it establishes | This page |
|---|---|---|---|
| 1. Enrollment | SENR 1.xx | Where and when the student is enrolled | Start with the enrollment context |
| 2. SWDS status | SWDS 22.xx | Eligibility and participation over time | Rule focus |
| 3. MEET | MEET 24.xx | Referral, evaluation, meeting, or pending event | Reconcile the effective relationship |
| 4. PLAN | PLAN 23.xx | Operative IEP, IFSP, ISP, or other plan | Reconcile the effective relationship |
| 5. SERV | SERV 25.xx | Services delivered under the plan | Reconcile the effective relationship |
| 6. Fall 1 snapshot | Certification | The census-day relationship CALPADS evaluates | Reconcile the effective relationship |
Fields and records evaluated
- SWDS 22.06 — SSID
- SWDS 22.11 — Special Education Status Effective Start Date
- SWDS 22.12 — Special Education Status Code
- MID merge history, when applicable
Six questions that resolve this certification finding
| Question | Specific finding | Evidence |
|---|---|---|
| What passed? | The individual SENR, SWDS, MEET, PLAN, or SERV transactions may each have posted successfully. | Submission detail and ODS history |
| What did Fall 1 expect? | One unambiguous status event per SSID and effective date. | Census-day snapshot logic |
| What is inconsistent? | Two or more SWDS records share the same SSID and effective date but carry conflicting status codes—often after two SSIDs are merged. | Student-level certification detail |
| Who owns correction? | Special education staff and the SEDS own eligibility, participation, meeting, plan, and service facts; enrollment staff and the SIS own SENR; the CALPADS/SELPA reporting process reconciles the effective histories. | SIS, SEDS, and authoritative special education records |
| What must change? | Determine the historically correct status event. Because the conflict may be a post-MID ODS condition that the LEA cannot safely resolve through an ordinary upload, preserve evidence and submit the CALPADS service request identified by the official guidance. | Supported add, replace, delete, service request, or sequencing action |
| What proves resolution? | 1.0 Certification Errors; 16.12 Students with Disabilities Education Plan by Primary Disability; 16.14 Students with Disabilities Plan Student List; 16.15 Students with Disabilities Services; 16.16 Students with Disabilities Services Student List; 16.17 Students with Disabilities Annual Comparison; applicable SELPA reports | Refreshed snapshot and student-level evidence |
Concrete checks
- Compare SSID, 22.11, 22.12, Reporting LEA, and source student identifiers.
- Review MID merge history and both predecessor SSIDs.
- Do not delete an apparently duplicate record until its origin and status outcome are understood.
- Attach the conflicting ODS rows, SEDS evidence, merge information, and intended status to the service request.
Recommended correction path
- 1
Locate the exact snapshot row
Match the SSID, Reporting LEA, census context, and snapshot revision identified by SWDS0662F1.
- 2
Build one effective-date history
Place SENR enrollment dates, every SWDS status event, MEET dates, PLAN effective dates, and SERV dates on one timeline.
- 3
Verify the authoritative evidence
Use the SEDS, IEP/IFSP/ISP documents, evaluation records, SIS, and identity records. Special education staff and the SEDS own eligibility, participation, meeting, plan, and service facts; enrollment staff and the SIS own SENR; the CALPADS/SELPA reporting process reconciles the effective histories.
- 4
Test this rule—not a neighboring rule
Compare SSID, 22.11, 22.12, Reporting LEA, and source student identifiers. Review MID merge history and both predecessor SSIDs. Do not delete an apparently duplicate record until its origin and status outcome are understood. Attach the conflicting ODS rows, SEDS evidence, merge information, and intended status to the service request.
- 5
Make the supported correction
Determine the historically correct status event. Because the conflict may be a post-MID ODS condition that the LEA cannot safely resolve through an ordinary upload, preserve evidence and submit the CALPADS service request identified by the official guidance. Repair the source system or extract mapping so the next submission does not recreate the discrepancy.
- 6
Regenerate and reconcile
Regenerate Fall 1, verify SWDS0662F1 clears, and reconcile 1.0 Certification Errors; 16.12 Students with Disabilities Education Plan by Primary Disability; 16.14 Students with Disabilities Plan Student List; 16.15 Students with Disabilities Services; 16.16 Students with Disabilities Services Student List; 16.17 Students with Disabilities Annual Comparison; applicable SELPA reports. Confirm the aggregate and student-level histories agree.
Official SWDS0662F1 guidance · CALPADS SWDS record guidance · Current certification and real-time reports · SDLA CALPADS report directory