Skip to main content
Stand-up comedian: Quick! Think of something funny to say about CALPADS. Good luck!

CALPADS error brief · PLAN

PLAN0627F1

Invalid Special Education Plan Reason Code based on Previous Education Plan Code
Severity Fatal
Error type CDD
Record type PLAN

Official CALPADS rule

What CALPADS is rejecting

Education Plan Code must be the same as the preceding plan when using Special Education Plan Reason Code 4

Focus fields

Fields validated

SWDS Data

22.11 - Special Education Status Effective Start Date

22.12 - Special Education Status Code

PLAN Data

23.11 - Special Education Plan Type Code

23.13 - Reason For Plan Record Code

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 snapshotRecord familyWhat it establishesThis page
EnrollmentSENR 1.xxWhere and when the student is enrolledConfirm relationship and date
SWDS statusSWDS 22.xx Eligibility and participation over timeConfirm relationship and date
MEETMEET 24.xxReferral, evaluation, meeting, or pending eventConfirm relationship and date
PLANPLAN 23.xxThe operative IEP, IFSP, ISP, setting, and plan factsRule focus
SERVSERV 25.xxServices reported under the planConfirm relationship and date
Fall 1 snapshotCertificationThe relationships effective for the reporting ruleConfirm relationship and date

Fields and records evaluated

  • SWDS 22.11/22.12 — Status Effective Date and Status
  • PLAN 23.11 — Plan Type Code
  • PLAN 23.12 — Plan Effective Start Date
  • PLAN 23.13 — Reason for Plan Record Code 4
  • Immediately preceding PLAN record

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?Reason 4 continues the plan-type relationship permitted by the current valid-code rule.Snapshot relationship logic
What is absent or inconsistent?The current PLAN uses reason 4 but changes plan type, or CALPADS is selecting a different preceding record than the SEDS expects. 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 unsupported reason code or plan type, or repair the missing/mistimed preceding PLAN record. Preserve the actual historical sequence.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 PLAN0627F1.

  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

    Sort every PLAN by 23.12 before comparing types. Identify the immediately preceding record—not the oldest or latest upload. Verify reason 4 in the current CALPADS code set. Check same-day duplicates before diagnosing the sequence. 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

    Correct the unsupported reason code or plan type, or repair the missing/mistimed preceding PLAN record. Preserve the actual historical sequence. Repair the owning source/export so the discrepancy is not recreated.

  6. 6

    Regenerate and reconcile

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