Skip to main content

CALPADS error brief · PLAN

PLAN0663F1

Two or More Special Education Plans must not be Effective on the same Date
Severity Fatal
Error type CDD
Record type PLAN

Official CALPADS rule

What CALPADS is rejecting

The following combination of fields may not be duplicated in more than one record: SSID, Special Education Plan Effective Start Date SSIDs must only have one PLAN record per Special Education Plan Effective Start Date

Focus fields

Fields validated

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.

The lifecycle CALPADS is reconstructing

EnrollmentSWDS statusMEETPLANSERVFall 1 snapshot

StageRecord familyWhat it establishesThis page
1. EnrollmentSENR 1.xxWhere and when the student is enrolledConfirm relationship and date
2. SWDS statusSWDS 22.xxEligibility and participation over timeConfirm relationship and date
3. MEETMEET 24.xxReferral, evaluation, meeting, or pending eventConfirm relationship and date
4. PLANPLAN 23.xx The operative IEP, IFSP, ISP, setting, and plan factsRule focus
5. SERVSERV 25.xxServices reported under the planConfirm relationship and date
6. Fall 1 snapshotCertificationThe relationships effective for the reporting ruleConfirm relationship and date

Fields and records evaluated

  • PLAN 23.06 — SSID
  • PLAN 23.12 — Plan Effective Start Date
  • All PLAN values and source record identifiers
  • MID merge history when applicable

Six questions that resolve this certification finding

QuestionSpecific findingEvidence
What passed?Individual source transactions may have posted successfully.Submission detail and ODS history
What did Fall 1 expect?One unambiguous plan event per SSID and effective date.Snapshot relationship logic
What is absent or inconsistent?Duplicate operational keys exist, often because two predecessor SSIDs were combined through an MID merge.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?Determine the historically correct PLAN event. Remove/replace only a proven duplicate; if the conflict is a post-MID ODS condition the LEA cannot safely repair, preserve evidence and request CALPADS assistance. 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 reportsRefreshed snapshot and student support

Recommended correction path

  1. 1

    Locate the exact snapshot row

    Match the SSID, Reporting LEA/SELPA, operative dates, and snapshot revision identified by PLAN0663F1.

  2. 2

    Build one effective-date timeline

    Place SENR, every SWDS status, MEET, PLAN, and SERV record in chronological order before editing anything.

  3. 3

    Test identifiers and ownership

    Compare SSID, Reporting LEA, Reporting SELPA, school, local IDs, and MID history as applicable.

  4. 4

    Verify authoritative evidence

    Compare every field in both PLAN records. Trace local student IDs and predecessor SSIDs. Review MID merge timing. Do not delete whichever record is easiest to access. 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. 5

    Make the supported correction

    Determine the historically correct PLAN event. Remove/replace only a proven duplicate; if the conflict is a post-MID ODS condition the LEA cannot safely repair, preserve evidence and request CALPADS assistance. Repair the owning source/export so the discrepancy is not recreated.

  6. 6

    Regenerate and reconcile

    Regenerate Fall 1, verify PLAN0663F1 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 PLAN0663F1 guidance · CALPADS PLAN guidance · Certification reports · SDLA report directory