Skip to main content

CALPADS error brief · PLAN

PLAN0673E1

Missing SWDS Record for a student with a Plan record
Severity Fatal
Error type CDD
Record type PLAN

Official CALPADS rule

What CALPADS is rejecting

Students with Plan records need to have at least one SWDS Record

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

CALPADS EOY 1 certification correction guide - Fatal CDD validation

PLAN0673E1: Missing SWDS Record for a student with a Plan record

Students with Plan records need to have at least one SWDS Record

Official Version 18 validation

Severity: Fatal   Type: CDD

A student with a PLAN record in the reporting period must have at least one SWDS record, regardless of Reporting LEA.

Fields validated: SWDS Data

Recommended correction path

  1. 1

    Save both searches

    Capture the PLAN record and the CALPADS SWDS search across all reporting LEAs.

  2. 2

    Confirm identity

    Verify SSID and local special-education identifiers so a cross-system mismatch is not mistaken for absence.

  3. 3

    Validate the PLAN

    Confirm the plan exists, belongs to the student, and has the supported effective date.

  4. 4

    Locate status evidence

    Review eligibility, participation, transfer, and exit history and determine which LEA owns the supported SWDS record.

  5. 5

    Correct the right record

    Submit missing SWDS only from authoritative status evidence; otherwise correct or remove an unsupported PLAN record.

  6. 6

    Reprocess without duplication

    Confirm at least one supported SWDS record joins to the student and no duplicate status was invented locally.

Before closing the correction

  • The student identity and effective dates are verified.
  • Every demographic, plan, status, setting, service, and transition value is supported by its authoritative record.
  • Cross-file keys and effective-date relationships reconcile.
  • The local source or repeatable extract is corrected before certification.

Official references