CALPADS error brief · PLAN
PLAN0673F1
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
SWDS Data
22.04 - Reporting LEA
22.11 - Special Education Status Effective Start Date
22.12 - Special Education Status Code
PLAN Data
23.04 - Reporting LEA
23.06 - SSID
23.12 - Special Education Plan Effective Start Date
Recommended correction path
Suggested resolution
“Missing” can mean absent, mistimed, mismatched, or superseded
A record may exist in the SEDS or CALPADS ODS and still fail the relationship because the SSID, Reporting LEA, Reporting SELPA, plan type/reason, or effective dates do not line up. Diagnose the complete history before adding another record.
Special education records to check
The table identifies related records. Use their effective dates to establish what happened for this student. After parental consent, CDE recommends reporting a pending initial evaluation in MEET. A referral alone does not establish SWDS eligibility or participation. CDE special education reporting FAQ.
| Record or snapshot | Record family | What it establishes | This page |
|---|---|---|---|
| Enrollment | SENR 1.xx | Where and when the student is enrolled | Confirm relationship and date |
| SWDS status | SWDS 22.xx | Eligibility and participation over time | Rule focus |
| MEET | MEET 24.xx | Referral, evaluation, meeting, or pending event | Confirm relationship and date |
| PLAN | PLAN 23.xx | The operative IEP, IFSP, ISP, setting, and plan facts | Confirm relationship and date |
| SERV | SERV 25.xx | Services reported under the plan | Confirm relationship and date |
| Fall 1 snapshot | Certification | The relationships effective for the reporting rule | Confirm relationship and date |
Fields and records evaluated
- PLAN 23.06 — SSID
- PLAN 23.12 — Plan Effective Start Date
- SWDS 22.06 — SSID
- SWDS 22.11/22.12 — Status Effective Date and Status
Six questions that resolve this certification finding
| Question | Specific finding | Evidence |
|---|---|---|
| What passed? | Individual source transactions may have posted successfully. | Submission detail and ODS history |
| What did Fall 1 expect? | A new PLAN event is connected to some statewide special education status history. | Snapshot relationship logic |
| What is absent or inconsistent? | No SWDS record exists for the SSID, or identity/date/transmission problems prevent CALPADS from finding it. | Student-level certification detail |
| Who owns correction? | Special education staff and the SEDS own SWDS, MEET, PLAN, and SERV facts; enrollment staff and the SIS own SENR; the CALPADS/SELPA process reconciles identifiers, LEA/SELPA ownership, and effective dates. | SIS, SEDS, and authoritative records |
| What must change? | Add/correct the actual SWDS status event, or correct/delete an unsupported PLAN. The status code must reflect the real outcome; this existence rule does not automatically require code 1. | Add, replace, delete, sequence, or service request |
| 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 support |
Recommended correction path
- 1
Locate the exact snapshot row
Match the SSID, Reporting LEA/SELPA, operative dates, and snapshot revision identified by PLAN0673F1.
- 2
Build one effective-date timeline
Place SENR, every SWDS status, MEET, PLAN, and SERV record in chronological order before editing anything.
- 3
Test identifiers and ownership
Compare SSID, Reporting LEA, Reporting SELPA, school, local IDs, and MID history as applicable.
- 4
Verify authoritative evidence
Confirm 23.12 falls from July 1 through Census Day. Search SWDS history across Reporting LEAs. Check rejected or omitted SEDS transactions. Verify SSID/MID history. Special education staff and the SEDS own SWDS, MEET, PLAN, and SERV facts; enrollment staff and the SIS own SENR; the CALPADS/SELPA process reconciles identifiers, LEA/SELPA ownership, and effective dates.
- 5
Make the supported correction
Add/correct the actual SWDS status event, or correct/delete an unsupported PLAN. The status code must reflect the real outcome; this existence rule does not automatically require code 1. Repair the owning source/export so the discrepancy is not recreated.
- 6
Regenerate and reconcile
Regenerate Fall 1, verify PLAN0673F1 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. Aggregate and student-level histories must agree.
Official PLAN0673F1 guidance · CALPADS PLAN guidance · Certification reports · SDLA report directory