CALPADS error brief ยท SOFF
SOFF0502
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
20.06 Academic Year ID 20.07 SSID 20.13 Incident ID Local 18.06 Academic Year ID 18.07 SSID 18.13 Incident ID Local 18.15 Statutory Offense IndicatorRecommended correction path
Suggested resolution
CALPADS SOFF correction guide - Fatal data discrepancy
SOFF0502: Invalid Incident ID
The Incident ID and Academic Year Combination must match an existing SINC Incident ID and SINC Academic Year ID combination for the same Student where Statutory Offense is indicated
Official Version 18 rule
Severity: Fatal Type: Data Discrepancy
Fields validated:
- 20.06 Academic Year ID
The Incident ID and Academic Year Combination must match an existing SINC Incident ID and SINC Academic Year ID combination for the same Student where Statutory Offense is indicated
Follow the behavior incident from evidence to CALPADS
SINC - incident and student
- Evidence
- Incident report, date, school, student, statutory/support facts
- Role
- Anchors the incident
SIRS - result
- Evidence
- Authorized action, authority, duration, and modification
- Role
- Documents what resulted for the student
SOFF - offense
- Evidence
- Supported reportable offense and weapon category when applicable
- Role
- Documents the qualifying infraction
Recommended correction path
- 1
Preserve the rejected evidence
Save the submission ID, rejected SOFF row, error details, and an accepted comparison before changing any source record.
- 2
Reconstruct the documented event
Match the student, school, academic year, Incident ID Local, incident date, offense findings, and result documentation in the behavior management system and supporting records.
- 3
Verify the incident timeline
Use the date the event actually occurred. Reconcile it to the academic year and the student's enrollment dates; do not backdate, forward-date, or move an event merely to clear validation.
- 4
Correct the source workflow
Update the behavior management system, SIS, or controlled crosswalk that produced the error. Document the correction owner and retain the source evidence.
- 5
Rebuild the complete incident chain
Generate a small corrected set and reconcile SINC, SIRS, and SOFF by School of Attendance, Academic Year ID, Incident ID Local, and student. Submit in the required sequence and confirm acceptance.
- 6
Check for systemic impact
Review other records produced by the same rule, default, code crosswalk, or vendor extract so the next full submission does not recreate the error.
Before closing the correction
- Confirm the accepted row describes the documented student behavior incident.
- Confirm school, academic year, Incident ID Local, SSID, and enrollment align.
- Confirm offense and result values are supported, not inferred or manufactured.
- Reconcile the complete SINC-SIRS-SOFF chain and other records from the same workflow.
Official references and practical support
Incident evidence checklist
- Original incident report and authorized findings
- Student identity, School of Attendance, and enrollment on the incident date
- Academic year and stable Incident ID Local
- Offense documentation and weapon facts when applicable
- Authorized result, authority, served duration, and modification
- Special-education supports or interim-setting documentation when applicable
- Rejected extract row, source-system record ID, and accepted post-correction evidence