Skip to main content

CALPADS error brief ยท PLAN

PLAN0347

Missing Special Education Program Type Code
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

If Special Education Plan Type Code = 150 (IFSP) then Special Education Program Type Code must be populated.

Focus fields

Fields validated

23.11 - Special Education Plan Type Code 23.24 - Special Education Program Type Code

Recommended correction path

Suggested resolution

PLAN validation

Severity: Fatal   Type: Input Validation

Fields validated

  • 23.11 Special Education Plan Type Code
  • 23.24 Special Education Program Type Code

IFSP identifies the kind of plan; Program Type describes where or how the infant receives special education instruction and related services. They are related fields, not substitutes.

Plan type controls which fields belong

Plan TypeMeaningConditional-field principle
100Individualized Education Program (IEP)IEP transition indicators and Special Transportation may apply.
150Individualized Family Service Plan (IFSP)Infant Program Type and specified Part C fields may apply.
200Individual Service Plan (ISP)Do not carry IEP- or IFSP-only fields into the record.

Concrete checks

  • Confirm Plan Type 150 is factually correct.
  • Review the current IFSP and service environment.
  • Select the current Program Type code supported by the record.
  • Check whether the source system left 23.24 blank or mapped it to the wrong column.

Recommended correction path

  1. 1

    Preserve the rejected PLAN row

    Capture SSID, Reporting LEA/SELPA, effective date, Plan Type, the failed conditional field, and current PLAN history.

  2. 2

    Verify the governing plan type

    Determine whether this record represents an IEP, IFSP, or ISP. Do not choose a plan type merely to accommodate another field.

  3. 3

    Review the governing documentation

    Use the signed/effective plan, transition documentation, eligibility evidence, and team determinations applicable to this field.

  4. 4

    Determine whether the field belongs

    When the plan type supports the field, verify its evidence-backed value. When it does not, trace why the field was populated.

  5. 5

    Correct the source and mapping

    Populate the supported Program Type when the student truly has an IFSP, or correct Plan Type if 150 was submitted in error. Repair copied-forward defaults and export logic.

  6. 6

    Resubmit and reconcile history

    Confirm acceptance and review connected MEET, SWDS, PLAN, and SERV records for the same effective period.

Official references