Skip to main content

CALPADS error brief · SOFF

SOFF0711E1

Missing Student Incident (SINC) Record for Student with Student Offense Record (SOFF)
Severity Fatal
Error type CDD
Record type SOFF

Official CALPADS rule

What CALPADS is rejecting

Student Offense (SOFF) Records must have an associated Student Incident (SINC) Record

Focus fields

Fields validated

SINC Data 18.05 - School of Attendance 18.06 - Academic Year ID 18.07 - SSID 18.13 - Incident ID Local SOFF Data 20.05 - School of Attendance 20.06 - Academic Year ID 20.07 - SSID 20.13 - Incident ID Local

Recommended correction path

Suggested resolution

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

SOFF0711E1: Missing Student Incident (SINC) Record for Student with Student Offense Record (SOFF)

Student Offense (SOFF) Records must have an associated Student Incident (SINC) Record

Official Version 18 validation

Severity: Fatal   Type: CDD

a SOFF offense requires an associated SINC record for the same incident key.

Fields validated: SINC 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, a SOFF offense, and the records needed to establish an associated SINC record for the same incident key.

  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.
  • a SOFF offense is supported by authorized evidence.
  • an associated SINC record for the same incident key is supported on the relevant date.
  • All connected records and regenerated reports reconcile.

Official references