CALPADS error brief · PLAN
PLAN0399
Official CALPADS rule
What CALPADS is rejecting
Infant Regional Center Services Eligibility Indicator must be populated if Disability 1 Code is 220, 230, 250, 270, or 300 and Student is on an IFSP Plan (Education Plan =150)
Focus fields
Fields validated
23.11 - Special Education Plan Type Code 23.15 - Disability 1 Code 23.19 - Infant Regional Center Services Eligibility IndicatorRecommended correction path
Suggested resolution
PLAN validation
Severity: Fatal Type: Input Validation
Fields validated
- 23.11 Special Education Plan Type Code
- 23.15 Disability 1 Code
- 23.19 Infant Regional Center Services Eligibility Indicator
Required does not mean automatically Y. The field reports Y or N from the student’s documented eligibility circumstance; do not infer eligibility solely from disability or IFSP participation.
Plan type controls which fields belong
| Plan Type | Meaning | Conditional-field principle |
|---|---|---|
| 100 | Individualized Education Program (IEP) | IEP transition indicators and Special Transportation may apply. |
| 150 | Individualized Family Service Plan (IFSP) | Infant Program Type and specified Part C fields may apply. |
| 200 | Individual Service Plan (ISP) | Do not carry IEP- or IFSP-only fields into the record. |
Concrete checks
- Confirm Plan Type 150 and the primary disability code.
- Verify whether the student is eligible for Regional Center services.
- Use authorized documentation rather than assumption.
- Check whether the source application collected the value but the extract omitted it.
Recommended correction path
- 1
Preserve the rejected PLAN row
Capture SSID, Reporting LEA/SELPA, effective date, Plan Type, the failed conditional field, and current PLAN history.
- 2
Verify the governing plan type
Determine whether this record represents an IEP, IFSP, or ISP. Do not choose a plan type merely to accommodate another field.
- 3
Review the governing documentation
Use the signed/effective plan, transition documentation, eligibility evidence, and team determinations applicable to this field.
- 4
Determine whether the field belongs
When the plan type supports the field, verify its evidence-backed value. When it does not, trace why the field was populated.
- 5
Correct the source and mapping
Populate the documented Y/N eligibility indicator, or correct the plan/disability field that incorrectly triggered the rule. Repair copied-forward defaults and export logic.
- 6
Resubmit and reconcile history
Confirm acceptance and review connected MEET, SWDS, PLAN, and SERV records for the same effective period.







































































