CALPADS error brief · SWDS
SWDS0593
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
22.12 Special Education Status Code 22.13 Non-Participation Reason CodeRecommended correction path
Suggested resolution
CALPADS SWDS correction guide · Fatal input validation
SWDS0593: Missing Non-Participating Reason Code
Non-Participating Reason Code must be populated when Special Education Status code is not equal to 1 (Eligible and Participating)
Official CALPADS rule
Severity: Fatal Type: Input Validation
Fields validated:
- 22.12 Special Education Status Code
- 22.13 Non-Participation Reason Code
Recommended correction path
- 1
Freeze the evidence before editing
Capture the CALPADS submission, rejected row, current ODS SWDS history, local special-education record, SENR history, and relevant meeting/plan documents.
- 2
Confirm the student and ownership
Match SSID, Reporting LEA, Reporting SELPA, local special-education ID, enrollment status, and enrollment dates. Resolve identity before interpreting status.
- 3
Build a dated student timeline
Place enrollment, referral/evaluation, determination, initial entry, status changes, meetings, plans, amendments, services, transfers, and exits in chronological order.
- 4
Determine the exact status event
Identify the documented eligibility determination, initial provision/consent outcome, participation change, transfer, exit, max-age event, or other event that changed the student’s status. Distinguish that event date from the historical Initial Entry Start Date.
- 5
Inspect the four-file chain
Compare SWDS with related MEET, PLAN, and SERV records and their effective dates. Identify missing precursors and conflicting successors.
- 6
Coordinate the responsible team
Include the case manager, school psychologist or assessment lead, special-education administrator, registrar, CALPADS/SELPA data staff, and system owner as applicable.
- 7
Correct the system of record
Change the authoritative special-education or enrollment record first, then regenerate the affected CALPADS files. Avoid a one-off upload edit that will be overwritten.
- 8
Post in dependency-aware order
Ensure qualifying SENR ownership exists; post the supported SWDS status history; then post or reconcile dependent MEET, PLAN, and SERV records for the scenario.
- 9
Verify CALPADS history and reports
Inspect the student’s ODS containers and Reports 16.12, 16.14, 16.22, and 16.23. Confirm the immediate previous and next effective records.
- 10
Check the affected population
Find other students produced by the same local code, date rule, workflow, vendor mapping, or transfer process; document the correction and prevention owner.
Where this correction sits in the reporting cycle
Dates are from the current 2026–27 CDE CALPADS calendar. Verify the official calendar before acting because dates can change.
Before closing the ticket
- Confirm the student’s SWDS history, immediate prior/next status, and qualifying enrollment directly in CALPADS.
- Reconcile related MEET, PLAN, and SERV records with the authoritative IEP/assessment system.
- Review Reports 16.12, 16.14, 16.22, and 16.23 with district special-education and SELPA staff.
- Document the underlying event, source evidence, correction owner, affected population, and prevention step.
Official references and practical support
- Official CALPADS SWDS0593 troubleshooting page
- CALPADS Students with Disabilities Status details
- CDE Special Education File Submission Scenarios
- CALPADS Update Flash 260 — special-education redesign
- CALPADS Update Flash 264 — ownership and secondary enrollment
- CALPADS SELPA and Students with Disabilities report guidance
- Current CALPADS File Specifications, code sets, and valid combinations
- Official CALPADS reporting calendar
IEP, assessment, SIS, and CALPADS support
Begin with the current California/CALPADS documentation supplied by your special-education system and SIS vendors. Ask who owns each SWDS, MEET, PLAN, and SERV field; how SSIDs and enrollment are synchronized; how effective-dated changes are generated; and how rejected or duplicate transactions are corrected. Access may require a customer account.
These directory and third-party support links are informational only and do not indicate ownership, partnership, certification, recommendation, or endorsement by the School Data Leadership Association.


































































