Skip to main content

CALPADS error brief · SWDS

SWDS0648

Duplicate SWDS Status Effective Start Date
Severity Fatal
Error type Input Validation
Record type SWDS

Official CALPADS rule

What CALPADS is rejecting

Student has an existing SWDS record with the same Special Education Status Effective Start Date

Focus fields

Fields validated

22.11 Special Education Status Effective Start Date

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

A duplicate date may be a repeated file row, an attempted update to an existing ODS record, or two local events collapsed onto one date. These scenarios require different corrections.

How CALPADS reads the SWDS history

Documented eventEligibility, participation, enrollment, consent, exit, or other supported change.
Status Code1 Participating · 2 Not Participating · 3 Not Enrolled · 4 Not Eligible.
Reason requirementBlank for Status 1; valid effective reason required for Status 2, 3, or 4.
Next genuine changeAdd another row only when the documented state changes.

Concrete checks

  • Search both the current file and CALPADS ODS for the same SSID and 22.11.
  • Compare Reporting LEA/SELPA, Academic Year, Initial Entry Date, Status, and Reason.
  • Inspect immediate prior and next SWDS rows before deleting either record.
  • Correct duplicate-generation logic, transaction type, or date mapping in the source system.

Recommended correction path

  1. 1

    Preserve the rejected row

    Capture submission ID, SSID, Reporting LEA and SELPA, Academic Year, Status Start Date, Status, Reason, and the complete ODS SWDS history.

  2. 2

    Confirm identity, ownership, and period

    Verify the student, qualifying SENR context, reporting organizations, and effective academic year before interpreting the status event.

  3. 3

    Reconstruct the event

    Use eligibility, consent, plan, enrollment, exit, transfer, and service evidence to determine what actually changed and when.

  4. 4

    Compare the whole SWDS history

    Review the immediately previous and next status records as well as connected MEET, PLAN, and SERV dates. Do not treat the rejected row in isolation.

  5. 5

    Correct the authoritative source

    Preserve one authoritative status event for the date. Suppress an exact duplicate, properly update an existing record, or correct the unsupported date when two genuinely different events were mistakenly assigned the same effective date. Repair any repeatable source-to-CALPADS mapping.

  6. 6

    Resubmit and verify

    Confirm acceptance, reread the full ODS history, and review Reports 16.22 and 16.23 plus affected Fall 1 or EOY 1 results.

Official references