Skip to main content

CALPADS error brief · SWDS

SWDS0517

Special Education Status Start Date must be less than or equal to current date
Severity Fatal
Error type Input Validation
Record type SWDS

Official CALPADS rule

What CALPADS is rejecting

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

Focus fields

Fields validated

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.11 Special Education Status Effective Start Date
  • 22.12 Special Education Status Code

The current CALPADS resolution supplies an important qualifier that the short title omits: SWDS0517 applies to statuses not equal to 1. It does not prohibit every future Status 1 record; SWDS0665 governs that limited exception.

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
ValidStatus other than 1; Start Date today or earlier The status event has occurred.
InvalidStatus other than 1; Start Date tomorrowNon-Status-1 events cannot be future-dated.
Separate ruleStatus 1; future Start DateEvaluate SWDS0665 and the six-month limit; verify the planned effective date is authoritative.

Concrete checks

  • Read both 22.11 and 22.12; the date rule changes only for Status Code 1.
  • Distinguish an actual status change from a planned meeting, projected plan, or data-entry reminder.
  • Check for date transposition, default dates, and extract timezone/run-date logic.
  • Do not change the status code merely to gain access to the Status 1 future-date allowance.

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

    For a non-Status-1 row, submit the actual effective date after the event occurs or correct the mistaken future value. For Status 1, verify the record under SWDS0665 rather than applying this general prohibition. 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