CALPADS error brief · PLAN
PLAN0368E1
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
2.06 SSID 2.18 Student Birth Date 23.06 SSID 23.12 Special Education Plan Effective Start Date 23.17 Disability 2 CodeRecommended correction path
Suggested resolution
CALPADS EOY 1 certification correction guide - Fatal CDD validation
PLAN0368E1: Invalid Student Age for Established Medical Disability 2 Code
If Disability Code 2 is equal to 281, then Student Age must be at least 3 years, but less than 6 years.
Official Version 18 validation
Severity: Fatal Type: CDD
Disability 2 Code 281 requires at least 3 and younger than 6. Student age is evaluated using the effective SINF birth date and the date specified by the Version 18 validation.
Fields validated: 2.06 SSID
Recommended correction path
- 1
Preserve the failed comparison
Save SSID, birth date, Plan Effective Start Date, plan type, setting/disability/reason fields, and the operative source document.
- 2
Confirm identity and birth date
Use the authorized student-demographic process; correct SINF only when supported by evidence.
- 3
Calculate completed age
Use the exact date basis in the official rule. Account for whether the birthday has occurred; do not subtract years alone.
- 4
Verify the operative plan fact
Have special-education staff confirm the secondary disability determination and the student’s completed age on the Plan Effective Start Date from the signed plan and effective-dated system history.
- 5
Review lifecycle boundaries
Determine whether a later plan should have replaced an earlier age-limited value and whether status, meetings, and services align.
- 6
Correct the supported source
Repair only the fact shown to be wrong—birth date, plan date, plan type, setting, disability, reason, or mapping.
- 7
Reprocess and reconcile
Confirm the validation clears and PLAN, SINF, SWDS, MEET, SERV, and enrollment remain coherent.
Before closing the correction
- The student identity and effective dates are verified.
- Every demographic, plan, status, setting, service, and transition value is supported by its authoritative record.
- Cross-file keys and effective-date relationships reconcile.
- The local source or repeatable extract is corrected before certification.







































































