CALPADS error brief · PLAN
PLAN0714F1
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
SINF Data
02.18 - Student Birth Date
PLAN Data
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 | Confirm relationship and date |
| 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 | Rule focus |
| 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
- SINF 2.18 — Student Birth Date
- PLAN 23.06 — SSID
- PLAN 23.12 — Plan Effective Start Date
- Census enrollment at the PLAN Reporting LEA
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 possible chronology in which birth precedes every special education plan event. | Snapshot relationship logic |
| What is absent or inconsistent? | The effective birth date is later than the PLAN start date, usually because of an incorrect year, identity match, migrated placeholder, or wrong PLAN date. | 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? | Correct the evidence-supported SINF birth date or PLAN event. Do not move a valid birth date merely to clear the discrepancy. | 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 PLAN0714F1.
- 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
Compare all eight digits. Verify SSID and student identity. Distinguish PLAN effective date from meeting, amendment, upload, or initial-entry date. Check century/year defaults and migration values. 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
Correct the evidence-supported SINF birth date or PLAN event. Do not move a valid birth date merely to clear the discrepancy. Repair the owning source/export so the discrepancy is not recreated.
- 6
Regenerate and reconcile
Regenerate Fall 1, verify PLAN0714F1 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 PLAN0714F1 guidance · CALPADS PLAN guidance · Certification reports · SDLA report directory