Skip to main content

CALPADS error brief · STAS

STAS0744E1

Missing Suspension Data at the same Reporting LEA for a student who was reported as absent due to either out-of-school suspension or in-school suspension
Severity Warning
Error type DD
Record type STAS

Official CALPADS rule

What CALPADS is rejecting

Students who are reported as having suspensions (in-school or out-of-school) in the absence summary file must have associated Incident data at the same Reporting LEA

Focus fields

Fields validated

STAS Data 13.05 - School of Attendance 13.06 - Academic Year ID 13.07 - SSID 13.14 - Hourly Attendance School Type Indicator 13.17 - Days Absent Out-of-School Suspension 13.18 - Days Absent In-School Suspension SINC Data 18.05 - School of Attendance 18.06 - Academic Year ID 18.07 - SSID 18.14 - Incident Occurrence Date SIRS Data 19.05 - School of Attendance 19.06 - Academic Year ID 19.07 - SSID 19.14 - Incident Result Code

Recommended correction path

Suggested resolution

CALPADS End-of-Year certification correction guide - Warning DD validation

STAS0744E1: Missing Suspension Data at the same Reporting LEA for a student who was reported as absent due to either out-of-school suspension or in-school suspension

Students who are reported as having suspensions (in-school or out-of-school) in the absence summary file must have associated Incident data at the same Reporting LEA

Official Version 18 validation

Severity: Warning   Type: DD

STAS in-school or out-of-school suspension absence requires associated incident data at the same Reporting LEA.

Fields validated: STAS Data

Recommended correction path

  1. 1

    Preserve the failed cross-file evidence

    Save student, school, Reporting LEA, academic year, Incident ID Local where applicable, all relevant dates, STAS in-school or out-of-school suspension absence, and the records needed to establish associated incident data at the same Reporting LEA.

  2. 2

    Verify the attendance coding

    Review each in-school/out-of-school suspension absence date and daily attendance detail.

  3. 3

    Locate the behavior incident

    Search by student, school/LEA, date, and Incident ID Local.

  4. 4

    Confirm the final suspension result

    Use the authorized discipline decision; do not create a suspension because attendance used a suspension code.

  5. 5

    Compare reporting keys and dates

    Reconcile STAS with SINC/SIRS/SOFF, SENR, Reporting LEA, school, and academic year.

  6. 6

    Correct the unsupported side

    Repair attendance reason or behavior records only from evidence.

  7. 7

    Repair the system bridge

    Trace behavior-to-attendance integration, date aggregation, and LEA/school mapping.

  8. 8

    Reprocess and reconcile

    Confirm suspension days and incident results match without double counting.

Before closing the correction

  • The student, school, Reporting LEA, and academic year are correct.
  • STAS in-school or out-of-school suspension absence is supported by authorized evidence.
  • associated incident data at the same Reporting LEA is supported on the relevant date.
  • All connected records and regenerated reports reconcile.

Official references