End of Year Errors
WBLR — Work-Based Learning
WBLR errors involve student participation in reportable work-based learning activities. These validations may examine activity types, dates, hours, locations, and completion indicators. Confirm that the activity meets CALPADS reporting requirements, occurred within the applicable academic period, and is associated with the correct student, school, and program.
PLAN — Special Education Plan
PLAN errors involve Individualized Education Program and other special education plan information. These validations examine plan dates, eligibility, services, settings, and related required fields. Verify that the plan reflects the student’s current special education record and that it aligns with associated meeting, service, and student-with-disabilities data.
SOFF - Student Offense
SOFF errors involve offenses associated with a reported student incident. These validations check offense codes, weapon or substance information, and relationships to the correct incident and student. Confirm that each offense accurately describes the event and is linked to the corresponding SINC and SIRS records without duplication or conflicting values.
STAS - Student Attendance
STAS errors concern summarized attendance and absence information reported for students. They may identify invalid instructional-day totals, inconsistent attendance counts, missing expected records, or values that conflict with enrollment dates. Compare CALPADS data with the local attendance system and verify that totals cover only the student’s eligible enrollment period.
SWDS — Students with Disabilities
SWDS errors involve a student’s special education eligibility and status information. These validations check disability, eligibility, entry, exit, and related status fields. Review the student’s special education history and ensure SWDS records align with the applicable meeting, plan, service, enrollment, and postsecondary records.
MEET — Special Education Meetings
MEET errors involve special education meeting records, including meeting dates, purposes, outcomes, and required timelines. Confirm that each meeting is associated with the correct student and that its dates and values are consistent with related special education plans and services. Resolve missing, invalid, or conflicting meeting information before resubmission.
SCTE - Student Career Tech Ed
SCTE errors involve student participation and completion in Career Technical Education pathways. These validations may examine pathway codes, completion status, academic year, school, and related student enrollment information. Confirm that the reported pathway and completion data agree with local CTE records and the student’s participation during the reporting period.
Certification Error - EOY 1,2,3,4
End-of-Year certification errors apply to the EOY 1, EOY 2, EOY 3, and EOY 4 submissions. They identify incomplete, inconsistent, or unexpected year-end data involving courses, programs, discipline, attendance, career technical education, and special education. Review the specified certification report and correct the underlying records before final approval.
SIRS — Student Incident Results
SIRS errors involve the disciplinary or administrative results assigned to a student following a reported incident. They may concern result codes, dates, durations, instructional support, removals, or related special education requirements. Verify that every result is connected to the correct student and incident and accurately reflects the action taken.
LEAP — LEA Educational Program
LEAP errors involve programs administered or reported at the local educational agency level. These validations check program identifiers, dates, participation information, and other required values. Review the relevant program definition and confirm that each LEAP record accurately represents the program offered by the LEA during the reported period.
SINC - Student Incident
SINC errors involve incidents associated with student discipline reporting. These validations may examine incident identifiers, dates, locations, authorities, and relationships among students involved in the same event. Confirm that each incident is reported once, uses valid codes, and connects correctly to its related offense and result records.


































































