Skip to main content

CALPADS error brief · SINC

SINC0653E1

Student should not have the same Incident ID in two different schools
Severity Warning
Error type DD
Record type SINC

Official CALPADS rule

What CALPADS is rejecting

The following combination of fields may not be duplicated in more than one record: Academic Year ID, Reporting LEA, SSID, Incident ID Local

Focus fields

Fields validated

SINC Data 18.06 - Academic Year ID 18.07 - SSID 18.13 - Incident ID Local

Recommended correction path

Suggested resolution

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

SINC0653E1: Student should not have the same Incident ID in two different schools

The following combination of fields may not be duplicated in more than one record: Academic Year ID, Reporting LEA, SSID, Incident ID Local

Official Version 18 validation

Severity: Warning   Type: DD

the same Incident ID Local in two schools requires one supported school attribution for the student incident within the Reporting LEA and academic year.

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, the same Incident ID Local in two schools, and the records needed to establish one supported school attribution for the student incident within the Reporting LEA and academic year.

  2. 2

    Reconstruct the incident in the behavior system

    Use original incident documentation, participants, school, occurrence date, and local incident identifier.

  3. 3

    Compare every SINC row

    Check Academic Year, Reporting LEA, School of Attendance, SSID, Incident ID Local, and Incident Occurrence Date character for character.

  4. 4

    Distinguish duplication from multiple participants

    Confirm whether rows represent one student, different students in one event, or an accidental duplicate.

  5. 5

    Choose the supported identifier and school

    Follow the authoritative behavior record; do not renumber or move an incident merely to avoid validation.

  6. 6

    Correct the behavior-system source

    Repair duplicate generation, school attribution, date, or incident-key mapping.

  7. 7

    Rebuild the entire incident chain

    Regenerate SINC, SIRS, and SOFF together and confirm all rows share the supported keys.

Before closing the correction

  • The student, school, Reporting LEA, and academic year are correct.
  • the same Incident ID Local in two schools is supported by authorized evidence.
  • one supported school attribution for the student incident within the Reporting LEA and academic year is supported on the relevant date.
  • All connected records and regenerated reports reconcile.

Official references