Skip to main content

CALPADS error brief · SWDS

SWDS0355

Special Education Initial Entry Start Date is greater than current date
Severity Fatal
Error type Input Validation
Record type SWDS

Official CALPADS rule

What CALPADS is rejecting

Special Education Initial Entry Start Date must be less than or equal to current date.

Focus fields

Fields validated

22.10 Special Education Initial Entry Start Date

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

Do not confuse a planned meeting, anticipated consent, proposed service date, or future enrollment with Initial Entry. Report 22.10 only after the qualifying initial-entry event has occurred.

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
ValidToday 20260829; Initial Entry 20260829 or earlierThe historical event is not future-dated.
InvalidToday 20260829; Initial Entry 20260915The reported entry event has not occurred.
Common cause20260809 entered as 20260908A month/day transposition creates a future date.

Concrete checks

  • Compare the value with the signed consent and initial-provision evidence.
  • Check century, year, month, day, and source-to-extract field mapping.
  • Confirm a scheduled initial IEP or projected start date was not exported into 22.10.
  • If the event is genuinely future, leave the student out of Status 1 until the reportable event occurs and the complete record is supported.

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

    Replace a typographical, mapping, or source-record error with the actual historical date. Do not wait for an invented date to pass or backdate an event that has not occurred. 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