CALPADS error brief · PLAN
PLAN0633
Official CALPADS rule
What CALPADS is rejecting
Special Education Plans 300, 700, 800,and 900 are invalid for the PLAN file
Focus fields
Fields validated
23.01 - Record Type Code 23.11 - Special Education Plan Type CodeRecommended correction path
Suggested resolution
PLAN validation
Severity: Fatal Type: Input Validation
Fields validated
- 23.01 Record Type Code
- 23.11 Special Education Plan Type Code
Those legacy codes represented pending, eligible without a plan, or not eligible circumstances and ended after 2022–23. Current PLAN types are 100 IEP, 150 IFSP, and 200 ISP.
Why the retired values should not be “translated” automatically
| Retired code | Former meaning | Current diagnostic question |
|---|---|---|
| 300 | Pending | Does the event belong in MEET pending history or another current status structure? |
| 700 | Eligible—parent declined FAPE/private placement | What current SWDS/MEET/PLAN history accurately represents the circumstance? |
| 800 | Eligible—no plan for other reasons | Is there actually an effective plan, or should this not be a PLAN record? |
| 900 | Not Eligible | Does the eligibility outcome belong in MEET rather than PLAN? |
Official wording inconsistency: the PLAN0633 rule lists 300, 700, 800, and 900, while its explanatory paragraph omits 800. Version 18 confirms that all four are retired.
Concrete checks
- Confirm the event belongs in PLAN rather than SWDS or MEET.
- Review whether a legacy code remained in the SEDS crosswalk.
- Verify the student’s current effective plan.
- Do not translate a retired no-plan status into an active plan type without evidence.
Recommended correction path
- 1
Preserve the rejected version
Capture SSID, LEA/SELPA, effective date, plan type, disability, support, setting, participation, and current PLAN history.
- 2
Verify student and plan
Confirm the record belongs to the intended student and governing IEP, IFSP, or ISP.
- 3
Review authoritative determinations
Use eligibility, plan, placement, participation, and program documentation—not assumptions based on services or classroom.
- 4
Check the current matrix
Validate each code individually, then verify the required combination and effective period.
- 5
Correct the owning source
Use 100, 150, or 200 only when an effective IEP, IFSP, or ISP exists. Route pending, non-participating, or not-eligible facts through the current appropriate record structure. Repair crosswalks, defaults, or copied-forward values.
- 6
Resubmit and reconcile
Confirm acceptance and review connected SWDS, MEET, PLAN, SERV, and reporting results.







































































