Skip to main content

CALPADS error brief · SWDS

SWDS0605F1

Missing Meeting Record for active Student with Disabilities
Severity Fatal
Error type CDD
Record type SWDS

Official CALPADS rule

What CALPADS is rejecting

A student with an SWDS record indicating an evaluation must have at least one MEET Record at the same Reporting LEA

Focus fields

Fields validated

SENR Data 1.04 - Reporting LEA 1.22 Enrollment Start Date 1.25 Enrollment Exit Date SWDS Data 22.04 - Reporting LEA 22.11 - Special Education Status Effective Start Date 22.12 - Special Education Status Code MEET Data 24.04 - Reporting LEA

Recommended correction path

Suggested resolution

Status is not the same as enrollment, a meeting, a plan, or a service

Eligibility answers whether the student qualifies. Participation answers whether the student is receiving special education under the reported status. MEET records an event. PLAN records the operative education plan. SERV records services. Each relationship depends on its own effective date.

The history CALPADS is trying to reconstruct

Enrollment → SWDS status → MEET → PLAN → SERV → Fall 1 snapshot

StageRecord familyWhat it establishesThis page
1. EnrollmentSENR 1.xxWhere and when the student is enrolledStart with the enrollment context
2. SWDS statusSWDS 22.xxEligibility and participation over timeReconcile the effective relationship
3. MEETMEET 24.xxReferral, evaluation, meeting, or pending eventRule focus
4. PLANPLAN 23.xxOperative IEP, IFSP, ISP, or other planReconcile the effective relationship
5. SERVSERV 25.xxServices delivered under the planReconcile the effective relationship
6. Fall 1 snapshotCertificationThe census-day relationship CALPADS evaluatesReconcile the effective relationship

Fields and records evaluated

  • SENR 1.04 — Reporting LEA
  • SENR 1.22/1.25 — Enrollment Dates
  • SWDS 22.04 — Reporting LEA
  • SWDS 22.11 — Status Effective Start Date
  • SWDS 22.12 — Status Code
  • MEET 24.04 — Reporting LEA
  • MEET 24.13/24.14 — Meeting or Pending Date

Six questions that resolve this certification finding

QuestionSpecific findingEvidence
What passed?The individual SENR, SWDS, MEET, PLAN, or SERV transactions may each have posted successfully.Submission detail and ODS history
What did Fall 1 expect?The status outcome is traceable to the meeting/evaluation event reported by the responsible LEA.Census-day snapshot logic
What is inconsistent?The SWDS status exists, but no MEET record is found at that same Reporting LEA.Student-level certification detail
Who owns correction?Special education staff and the SEDS own eligibility, participation, meeting, plan, and service facts; enrollment staff and the SIS own SENR; the CALPADS/SELPA reporting process reconciles the effective histories.SIS, SEDS, and authoritative special education records
What must change?Submit the missing supported MEET event at the eligibility-determining LEA, or correct the SWDS/MEET Reporting LEA, identity, activity, or effective date that prevents the relationship.Supported add, replace, delete, service request, or sequencing action
What proves resolution?1.0 Certification Errors; 16.12 Students with Disabilities Education Plan by Primary Disability; 16.14 Students with Disabilities Plan Student List; 16.15 Students with Disabilities Services; 16.16 Students with Disabilities Services Student List; 16.17 Students with Disabilities Annual Comparison; applicable SELPA reportsRefreshed snapshot and student-level evidence

Concrete checks

  • Match 22.04 to 24.04; a MEET from another LEA does not satisfy this particular rule.
  • Locate the evaluation or meeting that produced the SWDS determination.
  • Check rejected MEET submissions and SEDS export filters.
  • Do not invent a meeting date; use the IEP/IFSP/ISP team record or pending-event evidence.

Recommended correction path

  1. 1

    Locate the exact snapshot row

    Match the SSID, Reporting LEA, census context, and snapshot revision identified by SWDS0605F1.

  2. 2

    Build one effective-date history

    Place SENR enrollment dates, every SWDS status event, MEET dates, PLAN effective dates, and SERV dates on one timeline.

  3. 3

    Verify the authoritative evidence

    Use the SEDS, IEP/IFSP/ISP documents, evaluation records, SIS, and identity records. Special education staff and the SEDS own eligibility, participation, meeting, plan, and service facts; enrollment staff and the SIS own SENR; the CALPADS/SELPA reporting process reconciles the effective histories.

  4. 4

    Test this rule—not a neighboring rule

    Match 22.04 to 24.04; a MEET from another LEA does not satisfy this particular rule. Locate the evaluation or meeting that produced the SWDS determination. Check rejected MEET submissions and SEDS export filters. Do not invent a meeting date; use the IEP/IFSP/ISP team record or pending-event evidence.

  5. 5

    Make the supported correction

    Submit the missing supported MEET event at the eligibility-determining LEA, or correct the SWDS/MEET Reporting LEA, identity, activity, or effective date that prevents the relationship. Repair the source system or extract mapping so the next submission does not recreate the discrepancy.

  6. 6

    Regenerate and reconcile

    Regenerate Fall 1, verify SWDS0605F1 clears, and reconcile 1.0 Certification Errors; 16.12 Students with Disabilities Education Plan by Primary Disability; 16.14 Students with Disabilities Plan Student List; 16.15 Students with Disabilities Services; 16.16 Students with Disabilities Services Student List; 16.17 Students with Disabilities Annual Comparison; applicable SELPA reports. Confirm the aggregate and student-level histories agree.

Official SWDS0605F1 guidance · CALPADS SWDS record guidance · Current certification and real-time reports · SDLA CALPADS report directory