Skip to main content

CALPADS error brief · SOFF

SOFF0510

Missing Removal to Interim Alternative Setting Reason Code
Severity Warning
Error type Data Discrepancy
Record type SOFF

Official CALPADS rule

What CALPADS is rejecting

If student has an Active SPED Plan at the same Reporting LEA AND Student Offense Code in ('100', '103', '105', '200', '400', '401', '500',' 503', '505', '600') then associated SINC Removal to Interim Alternative Setting Reason Code should be populated

Focus fields

Fields validated

14.04 Reporting LEA 14.08 SSID 14.27 Special Education Initial Entry Start Date 14.46 Special Education Program Exit Date 20.04 Reporting LEA 20.07 SSID 18.14 Incident Occurrence Date 20.14 Student Offense Code 18.17 Removal to Interim Alternative Setting Reason Code

Recommended correction path

Suggested resolution

CALPADS SOFF correction guide · Warning data discrepancy

SOFF0510: Missing Removal to Interim Alternative Setting Reason Code

If student has an Active SPED Plan
at the same Reporting LEA
AND Student Offense Code in ('100', '103', '105', '200', '400', '401', '500',' 503', '505', '600') then associated SINC
Removal to Interim Alternative Setting Reason Code should be populated

Official CALPADS rule

Severity: Warning   Type: Data Discrepancy

Fields validated:

  • 14.04 Reporting LEA
  • 14.08 SSID
  • 14.27 Special Education Initial Entry Start Date
  • 14.46 Special Education Program Exit Date
  • 20.04 Reporting LEA
  • 20.07 SSID
  • 18.14 Incident Occurrence Date
  • 20.14 Student Offense Code
  • 18.17 Removal to Interim Alternative Setting Reason Code

Recommended correction path

  1. 1

    Assemble the incident chain

    Place the local discipline record, SINC row, SIRS row or rows, SOFF row or rows, enrollment history, and CALPADS posted records side by side.

  2. 2

    Compare the shared keys

    Match School of Attendance, SSID, Academic Year ID, and Incident ID Local exactly. Confirm the SINC Statutory Offense Indicator supports a SOFF child record.

  3. 3

    Check posting order

    Post or correct the parent SINC record before its SOFF child. Confirm that the intended SINC record exists in the ODS rather than only in a rejected batch.

  4. 4

    Coordinate safeguards

    For students with disabilities, involve the special education case manager and SELPA data lead before changing interim-alternative-setting information or plan dates.

  5. 5

    Reconcile the full incident

    Post the correction, inspect the linked incident in CALPADS, compare discipline reports with the local source, and check other children of the same Incident ID.

Where this correction sits in the 2026–27 calendar

Capture throughout the yearKeep incident IDs, offenses, results, statutory-offense decisions, weapon details, and special-education safeguards aligned while evidence is fresh.
EOY 1 submission window opens; Student Incidents are part of the consolidated EOY 1 collection.
CDE’s recommended date for reaching zero EOY 1 errors.
EOY 1 amendment window closes; required SELPA approval must be complete.

Dates are from the current CDE CALPADS 2026–27 calendar. Verify the official calendar before acting because dates can change.

Before closing the ticket

  • Confirm the corrected SOFF record under the intended student and Incident ID Local in CALPADS.
  • Reconcile the related SINC parent and every applicable SIRS/SOFF child record.
  • Document whether the defect arose in source evidence, coding, translation, enrollment, configuration, or extract logic.
  • Check other incidents affected by the same local rule before EOY 1 certification.

Official references and practical support

SIS, discipline, and extract support

Begin with your vendor’s current California/CALPADS documentation. Incident models, local offense codes, weapon mappings, and SINC/SIRS/SOFF extract paths vary by product and configuration. Inclusion is not an endorsement; some resources require customer access.