CALPADS error brief · MEET
MEET0601
Official CALPADS rule
What CALPADS is rejecting
Evaluation Outcome Code is required if Special Education Meeting Date is populated and Meeting Activity - Evaluation Type Code is Populated
Focus fields
Fields validated
24.13 - Special Education Meeting Date 24.16 - Meeting Activity - Evaluation Type Code 24.18 - Evaluation Outcome CodeRecommended correction path
Suggested resolution
Official rule in plain language
Severity: Fatal Type: Input Validation
Fields validated
- 24.13 Special Education Meeting Date
- 24.16 Evaluation Type Code
- 24.18 Evaluation Outcome Code
Initial evaluations end in Eligible (20) or Not Eligible (25). Reevaluations end in Continued Eligibility (50) or No Longer Eligible (55). Pending events do not yet have a completed outcome.
Describe what occurred—not merely that a meeting existed
Version 18 evaluation/outcome pairs
| Evaluation type | Allowed outcome | Meaning |
|---|---|---|
| 10 Initial Part B | 20 or 25 | Eligible or Not Eligible |
| 15 Initial Part C | 20 or 25 | Eligible or Not Eligible |
| 40 Reevaluation | 50 or 55 | Continued Eligibility or No Longer Eligible |
| Blank | Blank | No evaluation activity/outcome |
Concrete checks
- Confirm the meeting occurred and 24.13 is accurate.
- Verify the signed eligibility determination.
- Do not infer the outcome from the student’s later status alone.
- Use the outcome compatible with the evaluation type.
Recommended correction path
- 1
Preserve the rejected row
Capture submission ID, SSID, Reporting LEA/SELPA, Academic Year, all MEET dates, activity indicators, outcome, delay, and the ODS history.
- 2
Identify the event state
Determine whether the activity was pending or completed and whether it involved an initial evaluation, reevaluation, plan review, or combination permitted by Version 18.
- 3
Build the chronology
Place referral, consent, pending checkpoints, meeting, determination, delay, SWDS, and PLAN events in order.
- 4
Verify governing evidence
Use signed meeting/evaluation records, procedural documentation, the SEDS, and the current code/combination definitions. Do not infer an outcome or delay reason.
- 5
Correct the source and mapping
Populate the supported completed outcome. If the event is pending or no evaluation occurred, correct the Meeting Date or Evaluation Type instead of inventing an outcome. Repair any recurring export rule.
- 6
Resubmit and reconcile
Confirm acceptance, inspect the complete MEET history, and review connected SWDS/PLAN records and affected reporting results.







































































