This lesson provides answers to common questions related to Student Incident extract for use in creating a SINC upload to CALPADS.
What is SINC?
SINC refers to the Student Incident file. This is 1 of 3 new discipline files for EOY CALPADS Submission.
Student Incident (SINC) file is how LEAs report all incidents: (1) resulting in the use of physical restraint, mechanical restraint, or seclusion; and (2) in which a statutory offense is committed.
For details on how to enter discipline data in Illuminate to populate this file, please see below.
SINC should be the first discipline extract run, followed by the SIRS, then the SOFF.
Illuminate added new Consequence codes to all ISI client databases in the Summer of 2019. Codes added were 400, 501, 502, 700, and 800. For questions around which code to use and when, please reach out to CALPADS.
For data to generate into the SINC Extract, LEAS must create Major Behavior Incidents overlapping a student's enrollment entry/exit dates.
For each incident, LEAs will submit one or more Student Incident records, which include the SSID(s) of the student(s).
The SINC Extract will:
- Get All Major Behavior Incidents:
- within the selected academic year
- within the selected start date and end date selected.
- within the selected Site
- with Consequences that are State Mapped in Code Management
New Statutory Offense Indicator Column
SINC file will include a new column: Statutory Offense Indicator.
This is an indicator of whether or not the incident involved one or more students committing at least one reportable offense persuant to Education Code 48900/48915.
If Y, then SIRS and SOFF record(s) must be submitted for the incident and students involved.
If N, then only SIRS record(s) must be submitted for the incident.
Offense equates to Violation in the Major Behavior Incident. Just like Consequences, Violations must also be State Mapped in Code Management.
Validation Logs should be reviewed, as they will cross check valid code combinations and identify missing or incorrect data entry.
Database Team limitation: If there is data missing or incorrect for behavior incidents, this must be corrected manually per incident in Illuminate.
Generating File for Submission:
Where to Start
- Click on Reports
- Under Admin, select State Reporting
- Once on the State Reporting Tools page, select CALPADS Student Incident (SINC) File
Please note that the order seen on the above screenshot may be different than the order of reports, extracts, and tools available in your list.
- Validation Logs: These are logs predicting potential errors with the SINC submission. A validation log will automatically be created each time the "Generate Report" button is selected and will show a date and timestamp. Validations reference the logic mentioned in the Data Entry area of this document.
- View as Standard Report: This option will let you run the report like you would any custom/prebuilt report in Illuminate.
- Academic Year: Even though Postsecondary refers to students who were enrolled/graduated in the previous year, this extract should be run for the current year.
- Start Date/End Date: Enter the Start and End Dates for the academic year.
- Generate Report: Clicking this will run the tool to show data for the site, academic year, and Fall 2 selection.
- Download Options: The results can be downloaded as Excel, PDF, Tab Delimited, or More formats.
Downloading SINC for CALPADS Submission
Once you've generated data, select More and then click on the radial option next to CALPADS for the appropriate format to submit and then click Download.
Of the 3 new discipline files, the SINC should be submitted to CALPADS first, followed by the SIRS and then SOFF.
Every SINC record will have at least one corresponding SIRS record. A SINC may have multiple SIRS.
For questions on how you should report student data or which codes to use, contact CALPADS.