Skip to main content

CALPADS error brief · SIRS

SIRS0704E1

Missing Student Offense (SOFF) Record for student with an Incident Result for a reportable offense
Severity Fatal
Error type CVR
Record type SIRS

Official CALPADS rule

What CALPADS is rejecting

Student Incident Results (SIRS) Record where Incident Results = 100, 110, 200, 300, 400 must have an associated Student Offense (SOFF) Record

Focus fields

Fields validated

SIRS Data 19.05 - School of Attendance 19.07 - SSID 19.13 - Incident ID Local 19.14 - Incident Result Code SOFF Data 20.05 - School of Attendance 20.07 - SSID 20.13 - Incident ID Local

Recommended correction path

Suggested resolution

CALPADS End-of-Year certification correction guide - Fatal CVR validation

SIRS0704E1: Missing Student Offense (SOFF) Record for student with an Incident Result for a reportable offense

Student Incident Results (SIRS) Record where Incident Results = 100, 110, 200, 300, 400 must have an associated Student Offense (SOFF) Record

Official Version 18 validation

Severity: Fatal   Type: CVR

SIRS result 100, 110, 200, 300, or 400 requires an associated SOFF record supported by a reportable offense.

Fields validated: SIRS 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, SIRS result 100, 110, 200, 300, or 400, and the records needed to establish an associated SOFF record supported by a reportable offense.

  2. 2

    Confirm the incident occurred

    Review the authorized incident narrative, occurrence date, participants, and Incident ID Local.

  3. 3

    Confirm the student’s role

    Ensure the SINC, SIRS, or SOFF record belongs to the correct student and school.

  4. 4

    Verify the offense finding

    Use authorized findings to determine whether a reportable/statutory offense exists; do not infer an offense from the result.

  5. 5

    Verify the disciplinary result

    Use the final administrative decision and dates; do not infer a result from the offense.

  6. 6

    Compare cross-file keys

    Match Academic Year, School, Reporting LEA, SSID, and Incident ID Local across SINC, SIRS, and SOFF.

  7. 7

    Correct the authoritative behavior workflow

    Add/repair only supported component records or remove an unsupported orphan.

  8. 8

    Reprocess and reconcile

    Confirm the entire chain and aggregate discipline reports agree.

Before closing the correction

  • The student, school, Reporting LEA, and academic year are correct.
  • SIRS result 100, 110, 200, 300, or 400 is supported by authorized evidence.
  • an associated SOFF record supported by a reportable offense is supported on the relevant date.
  • All connected records and regenerated reports reconcile.

Official references