School Discipline

The School Discipline collection contains school level information for (1) the counts of students disciplined based on the type of incident (behavior), (2) the demographics of the student(s) disciplined and (3) the counts of students that brought or possessed a firearm for each school. The data from the School Discipline collection is used to populate the Civil Rights Data Collection (CRDC) for LEAs which occurs every other year.

For questions or support, please email 

General Resources

Visit the Data Submissions Library for:

  • Data Submissions Handbook
  • Data Submissions Calendar
  • Troubleshooting Errors

Important Announcements

All Training and resources will be posted by April 18th, 2024

The School and SPED Discipline Collections have been merged into one interchange for the 23-24 school year, although the snapshots remain separate.  The collection has changed significantly since last year with data now being collected by Student rather than aggregate.  See the updated resources below as they become available. 

5/13 – IC update 2415.10 has corrected the SASID and Gender issues on the file extract, however the SPED Program Code is still reporting only two zeros instead of the necessary four.  This will continue to cause an error on each record unless manually updated.  Reach out to IC to submit a ticket in order to correct this issue.  

4/29 – PowerSchool also has file Extract issues.  The SPED Removal Type, Removal Reason, Mechanically Restrained, and Transferred to Alternative School are all populating blank when the file should reflect those as zero-filled.  Also, Behavior Code 11 – Bullying is automatically providing a zero filled Resulting Action, similar to a CRDC Behavior Code.  This in incorrect per CDE and should be pulling a valid code. Ensure you submit a ticket to PowerSchool for quicker corrections.

4/19 – Infinite Campus has officially released the Discipline Interchange Action file for the Discipline Collection.  Several districts are reporting issues with the extract, including the LASID populating in the SASID field and not all incidents are being reported.  Also, a potential of incorrect Gender and SPED Program Type Coding.  Upon review, it seems that most CSI schools may be impacted by these issues.  If you find that your school is impacted, it is recommended to submit a ticket to IC support.

Also, CSI has noticed that the the mapping is off in Inifinite Campus in terms of Resolution Coding.  It appears to still be mapping to last years codes.  You will need to go to the Discipline Setup and adjust the State Reporting Field that each Resolution Type is currently mapping to.  

4/15 – Infinite Campus Rx Pack 2411.11, set to be released on 4/16, should contain the new Discipline Interchange Extract.

4/5 – PowerSchool has released the new Discipline Action Interchange file but Infinite Campus has not.




File Layouts

File layouts provide guidance on the valid coding and definitions for each data element being collected and includes notes specific to CSI schools.

  • Discipline Action File Layout [pdf]

Submissions Training

All school submissions contacts should review relevant training prior to starting the data collection.

Data Validation Resources

Data validation resources should be utilized prior to submitting initial files to CSI and throughout the collection to ensure data is comprehensive and accurate. Regularly using the data validation resources will reduce the number of updates needed at the end of the collection after receiving the Summary Report.

  • Discipline Record Checker [xlsx]

Systems Resources

Infinite Campus

  • Infinite Campus File Extract Guidance [docx]
  • Infinite Campus Discipline Action Crosswalk [xlsx]
  • Infinite Campus Discipline Quick Entry Training [slides]


  • PowerSchool File Extraction Guidance [docx]
  • PowerSchool Discipline Action Crosswalk [xlsx]
  • PowerSchool Discipline Quick Entry Training [slides]
Translate »