CALPADS error brief · MEET
MEET0436F1
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
SWDS 22.11 - Special Education Status Effective Start Date 22.12 - Special Education Status Code MEET 24.13 - Special Education Meeting Date 24.16 - Meeting Activity - Evaluation Type Code 24.17 - Meeting Activity - Plan Review IndicatorRecommended 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
| Record | What it represents | Question to ask |
|---|---|---|
| MEET — 24.xx | A referral, evaluation, plan-review, reevaluation, completed meeting, or pending-meeting event. | What happened, and on what actual event date? |
| SWDS — 22.xx | The student’s effective special education eligibility and participation status history. | What status was effective when the event occurred? |
| PLAN — 23.xx | The 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.16 — Meeting Activity: Evaluation Type Code
- MEET 24.17 — Meeting Activity: Plan Review Indicator
Six questions that resolve this certification finding
| Question | Specific finding | Evidence |
|---|---|---|
| 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? | The effective SWDS history supports an annual plan-review or reevaluation event on the MEET date. | Census-day snapshot and reporting-window logic |
| What is inconsistent? | The MEET record describes an annual plan review or reevaluation, but the effective SWDS history does not show Eligible and Participating status for that event. | 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? | Correct the event classification when the MEET activity was coded incorrectly, or correct/add the evidence-supported SWDS status history when the student was actually Eligible and Participating. | 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 extracts | Refreshed snapshot plus student-level support |
Concrete checks
- Identify exactly what occurred: initial evaluation, reevaluation, annual plan review, or another meeting activity.
- Use 24.17 = Y only when the meeting satisfies the required review of an established plan.
- Review the most recent SWDS status effective on the meeting date—not merely the student’s current status today.
- Do not change status 4 (Not Eligible), or any other nonparticipating status, unless the eligibility record itself is wrong.
- After reconciling MEET and SWDS, confirm the resulting PLAN history accurately represents any plan established or continued by the meeting.
Recommended correction path
- 1
Locate the certification row
Match the SSID, Reporting LEA, meeting date, academic year, and snapshot revision identified by MEET0436F1.
- 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
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
Test the complete rule
Identify exactly what occurred: initial evaluation, reevaluation, annual plan review, or another meeting activity. Use 24.17 = Y only when the meeting satisfies the required review of an established plan. Review the most recent SWDS status effective on the meeting date—not merely the student’s current status today. Do not change status 4 (Not Eligible), or any other nonparticipating status, unless the eligibility record itself is wrong. After reconciling MEET and SWDS, confirm the resulting PLAN history accurately represents any plan established or continued by the meeting.
- 5
Make the supported correction
Correct the event classification when the MEET activity was coded incorrectly, or correct/add the evidence-supported SWDS status history when the student was actually Eligible and Participating. Correct the source system or extract mapping so the next submission does not recreate the discrepancy.
- 6
Regenerate and reconcile
Regenerate the Fall 1 snapshot, verify MEET0436F1 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 MEET0436F1 guidance · CALPADS MEET record guidance · Current certification and real-time reports · SDLA CALPADS report directory







































































