Skip to main content

CALPADS error brief · SWDS

SWDS0353

Invalid Special Education Status Effective Start Date for Special Education Initial Entry Start Date
Severity Fatal
Error type Input Validation
Record type SWDS

Official CALPADS rule

What CALPADS is rejecting

Special Education Status Effective Start Date for Eligible and Participating Student must be equal to or greater than Special Education Initial Entry Start Date

Focus fields

Fields validated

22.10 Special Education Initial Entry Start Date 22.11 Special Education Status Effective Start Date 22.12 Special Education Status Code

Recommended correction path

Suggested resolution

Official rule in plain language

Severity: Fatal   Type: Input Validation

Fields validated

  • 22.10 Special Education Initial Entry Start Date
  • 22.11 Special Education Status Effective Start Date
  • 22.12 Special Education Status Code

Initial Entry is the durable historical anchor. Status Effective Start Date begins the particular Eligible and Participating status segment being reported. For Status 1, 22.11 must be the same as or later than 22.10.

One student, one effective-dated history

1 · Initial entry22.10 anchors the student’s first entry into special education.
2 · Status becomes effective22.11 begins a documented status segment; 22.12 identifies that status.
3 · Applicable academic year22.05 is derived from the Status Effective Start Date.
4 · Subsequent status historyAdd a new effective row only when a real status event changes the history.

Key distinction: Initial Entry is normally a once-established historical anchor. Status Start Dates may recur as the student’s documented status changes. Neither is the upload date.

Valid, invalid, and diagnostic examples

ResultExampleWhy
ValidInitial Entry 20230915; Status Start 20230915Initial status begins on the entry date.
ValidInitial Entry 20230915; later Status Start 20260820A supported later status segment follows the historical anchor.
InvalidInitial Entry 20230915; Status Start 20230901The status begins before the student entered special education.

Concrete checks

  • Compare all eight digits; transposed months, days, or years can reverse the sequence.
  • Confirm that 22.10 was not incorrectly replaced with a current IEP, transfer, enrollment, or reentry date.
  • Confirm that 22.11 reflects the documented status event, not the upload date.
  • Review adjacent SWDS rows before changing either date; an apparently wrong date may belong to a different status segment.

Recommended correction path

  1. 1

    Preserve the rejected row

    Capture the submission ID, SSID, Reporting LEA and SELPA, Academic Year, Initial Entry Date, Status Start Date, Status Code, and adjacent SWDS history.

  2. 2

    Verify identity and enrollment context

    Match the student and confirm the qualifying SENR history before interpreting the special education chronology.

  3. 3

    Build the four-stage timeline

    Place initial entry, each status event, its academic year, and subsequent status rows in chronological order. Add MEET, PLAN, and SERV dates when they help identify the underlying event.

  4. 4

    Verify the authoritative event

    Use the special education system, signed evaluation/eligibility/consent records, transfer evidence, and CALPADS ODS history. Do not infer the date from the file upload.

  5. 5

    Correct the source and mapping

    Correct the unsupported date in the authoritative special education system. Preserve a valid historical Initial Entry Start Date and repair the status event when that is the value placed before it. Repair any repeatable extract rule so the next file preserves the same truth.

  6. 6

    Resubmit and reconcile

    Confirm acceptance, inspect the complete SWDS history in CALPADS, and review related MEET, PLAN, SERV, Fall 1, and EOY 1 results for unintended chronology effects.

Official references