Skip to main content

CALPADS error brief · PLAN

PLAN0620F1

Missing Eligible and Participating Status Record for a Plan record
Severity Fatal
Error type CDD
Record type PLAN

Official CALPADS rule

What CALPADS is rejecting

Plan records need to have an effective Eligible and Participating Status on the Plan Effective start date

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.

The lifecycle CALPADS is reconstructing

Enrollment → SWDS status → MEET → PLAN → SERV → Fall 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 timeRule focus
3. MEETMEET 24.xxReferral, evaluation, meeting, or pending eventConfirm relationship and date
4. PLANPLAN 23.xxThe operative IEP, IFSP, ISP, setting, and plan factsConfirm relationship and date
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

  • SENR 1.23 — Enrollment Status 10, 30, or 50
  • SWDS 22.04 — Reporting LEA
  • SWDS 22.11/22.12 — Status Effective Date and Status Code 1
  • PLAN 23.04 — Reporting LEA
  • PLAN 23.12 — Plan Effective Start Date

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?The PLAN is nested within a same-LEA period of eligibility and participation.Snapshot relationship logic
What is absent or inconsistent?SWDS is missing, begins too late, changed before Census Day, uses another LEA, or the PLAN/enrollment is wrong.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?Submit or correct the evidence-supported SWDS history, or correct the inaccurate PLAN/SENR relationship. Never create code 1 merely because a PLAN exists.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 PLAN0620F1.

  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 SWDS status on the PLAN effective date and on Census Day. Match SWDS 22.04 to PLAN 23.04. Verify the latest status event, not only that code 1 appears somewhere in history. Confirm the operative PLAN and qualifying census enrollment. 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

    Submit or correct the evidence-supported SWDS history, or correct the inaccurate PLAN/SENR relationship. Never create code 1 merely because a PLAN exists. Repair the owning source/export so the discrepancy is not recreated.

  6. 6

    Regenerate and reconcile

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