Skip to main content

CALPADS error brief · MEET

MEET0624F1

Missing Special Education Status Record
Severity Fatal
Error type CDD
Record type MEET

Official CALPADS rule

What CALPADS is rejecting

If a non-Pending Meeting exists for the SSID, there should be at least one SWDS Status record

Focus fields

Fields validated

SWDS Data 22.12 - Special Education Status Code MEET Data 24.13 - Special Education Meeting Date

Recommended correction path

Suggested resolution

MEET is an event—not the student’s status or plan

A MEET record says that a special education event occurred or remains pending. SWDS identifies the student’s status over time, and PLAN identifies the operative education plan. A valid correction must reconcile all three histories; changing whichever code clears the screen can damage the student’s longitudinal record.

The special education lifecycle

RecordWhat it representsQuestion to ask
MEET — 24.xxA referral, evaluation, plan-review, reevaluation, completed meeting, or pending-meeting event.What happened, and on what actual event date?
SWDS — 22.xxThe student’s effective special education eligibility and participation status history.What status was effective when the event occurred?
PLAN — 23.xxThe education plan under which services are offered or delivered.What plan became or remained operative after the event?

Fields and records evaluated

  • SWDS 22.11 — Special Education Status Effective Start Date
  • SWDS 22.12 — Special Education Status Code
  • MEET 24.13 — Special Education Meeting Date
  • MEET 24.14 — Pending As Of Date

Six questions that resolve this certification finding

QuestionSpecific findingEvidence
What passed?The individual MEET, SWDS, SINF, or PLAN transactions may each have posted successfully.Submission detail and ODS history
What did Fall 1 expect?A completed special education meeting event is connected to a status history that records the student’s resulting or relevant special education status.Census-day snapshot and reporting-window logic
What is inconsistent?CALPADS finds a completed MEET event in the reporting window but no SWDS status record for the student across Reporting LEAs.Student-level certification detail
Who owns correction?Special education staff establish the referral, meeting, eligibility, and plan facts; the SEDS owns the source records; the CALPADS/SELPA reporting process verifies the MEET, SWDS, and PLAN histories selected for Fall 1.SEDS, IEP/IFSP/ISP documentation, and CALPADS history
What must change?Add the supported SWDS status event, or correct/delete the MEET record if it belongs to the wrong student, represents a pending event, or contains an incorrect meeting date.Evidence-supported add, replace, delete, 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; applicable SELPA reports and local SEDS extractsRefreshed snapshot plus student-level support

Concrete checks

  • Confirm that 24.13 contains an actual completed meeting date between July 1 and Census Day.
  • Distinguish a completed MEET record from a pending record, which uses 24.14 Pending As Of Date instead of 24.13.
  • Search the student’s statewide SWDS history; this rule allows the qualifying SWDS record to have been submitted by another Reporting LEA.
  • Determine the actual outcome before assigning the SWDS code—Eligible and Participating is not the only possible evaluation result.
  • Check SSID, Reporting LEA, and SEDS-to-CALPADS transmission history for a missing or rejected SWDS transaction.

Recommended correction path

  1. 1

    Locate the certification row

    Match the SSID, Reporting LEA, meeting date, academic year, and snapshot revision identified by MEET0624F1.

  2. 2

    Reconstruct the lifecycle

    Read MEET as the event, SWDS as the status history, and PLAN as the operative plan. Place every effective date on one timeline before editing any record.

  3. 3

    Check the authoritative evidence

    Compare the IEP/IFSP/ISP documents, referral and consent records, SEDS history, and student identity data. Special education staff establish the referral, meeting, eligibility, and plan facts; the SEDS owns the source records; the CALPADS/SELPA reporting process verifies the MEET, SWDS, and PLAN histories selected for Fall 1.

  4. 4

    Test the complete rule

    Confirm that 24.13 contains an actual completed meeting date between July 1 and Census Day. Distinguish a completed MEET record from a pending record, which uses 24.14 Pending As Of Date instead of 24.13. Search the student’s statewide SWDS history; this rule allows the qualifying SWDS record to have been submitted by another Reporting LEA. Determine the actual outcome before assigning the SWDS code—Eligible and Participating is not the only possible evaluation result. Check SSID, Reporting LEA, and SEDS-to-CALPADS transmission history for a missing or rejected SWDS transaction.

  5. 5

    Make the supported correction

    Add the supported SWDS status event, or correct/delete the MEET record if it belongs to the wrong student, represents a pending event, or contains an incorrect meeting date. Correct the source system or extract mapping so the next submission does not recreate the discrepancy.

  6. 6

    Regenerate and reconcile

    Regenerate the Fall 1 snapshot, verify MEET0624F1 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; applicable SELPA reports and local SEDS extracts. Confirm the aggregate result and student-level history agree.

Official MEET0624F1 guidance · CALPADS MEET record guidance · Current certification and real-time reports · SDLA CALPADS report directory