Skip to main content

CALPADS error brief · PLAN

PLAN0443

Invalid SELPA for Reporting LEA
Severity
FATAL error - Must be corrected in order to post the record and/or certify the data.
Error type PLAN - Special Education Plan
Record type PLAN

Official CALPADS rule

What CALPADS is rejecting

SELPA must be a valid Entity Code and have an active reporting relationship with the Reporting LEA.

Focus fields

Fields validated

23.04 - Reporting LEA 23.09 - Reporting SELPA 23.12 -Special Education Plan Effective Start Date

Recommended correction path

Suggested resolution

PLAN validation

Severity: Fatal   Type: Input Validation

Fields validated

  • 23.04 Reporting LEA
  • 23.09 Reporting SELPA
  • 23.12 Special Education Plan Effective Start Date

A currently valid SELPA code can still fail when it was not the Reporting LEA’s SELPA for this effective date. CALPADS evaluates PLAN records dated July 1, 2019 or later.

Do not collapse four different organizations into one

RoleWhat it describesDiagnostic caution
Reporting LEAThe LEA reporting the PLAN record.Not automatically the DSEA.
Reporting SELPAThe SELPA with the active reporting relationship.The relationship is effective-dated.
DSEAThe district or qualifying charter accountable for ensuring services.Not automatically the district of service or attendance.
School/placementWhere education or services occur.Location does not alone establish accountability.

Concrete checks

  • Verify both organizational codes literally.
  • Confirm the relationship effective on 23.12—not merely today.
  • Review reorganizations, charter membership changes, and historical corrections.
  • Do not move an accurate plan date to match a later SELPA relationship.

Recommended correction path

  1. 1

    Preserve the rejected record

    Capture SSID, LEA/SELPA, DSEA, plan type, effective date, transition fields, and existing PLAN history as applicable.

  2. 2

    Confirm the exact student and plan

    Match the record to the governing IFSP, IEP, or ISP and its effective period.

  3. 3

    Establish the authoritative relationship

    Use membership/accountability records or the child’s IFSP transition evidence rather than defaults or assumptions.

  4. 4

    Build the effective-date timeline

    Place organizational relationships or birth, IFSP, transition plan, conference, and Part B events in order.

  5. 5

    Correct the owning source

    Correct the inaccurate LEA, SELPA, or effective date from authoritative records. If all are correct, coordinate the missing or incorrect organizational relationship with the SELPA and CALPADS support. Repair recurring crosswalk or copied-forward logic.

  6. 6

    Resubmit and reconcile

    Confirm acceptance and review connected SENR, SWDS, MEET, PLAN, SERV, SELPA, and DSEA history.

Official references