Student Incident Results Records (SIRS)

Introduction

Student Incident Results records are used to submit discipline action information. Multiple student offense records may be associated with a single incident. This extract is formatted in a delimited text file. Student Discipline records may be submitted independently of other records; however, a student enrollment record must exist for the student in the incident. The Student Incident Results report uses the Replacement processing method.

All Student Incident Results records must be submitted for each incident reported in Student Incident records.

For information about setting up discipline data, see CALPADS Discipline Quick Entry.

Selection Criteria

The extract includes student discipline incidents based on the following criteria:

There must be a corresponding Student Incident Record (SINC) as determined by Incident ID Local, Academic Year, and School of Attendance.
The incident must have at least one reportable action.

The California Department of Education (CDE) has added a new grade level of ‘TK’ that districts must use when reporting Transitional Kindergarten students to CALPADS. This new grade level will be effective starting with the 2023-2024 school year.

To support this functionality, PowerSchool has updated all California state reporting pages and reports to honor the grade level mappings as defined by each district.

The grade level is reported as mapped in all CA-specific reports once you meet the following criteria:

You are on PS Version 23.1 or higher
LTK Pref is enabled
While running the report, the selected school year is 23-24 or higher.

LTK Grade Level Mapping - valid values:

Grade 0 = KN
Grades -1 and below = TK, PS, IN
Grades >12 = AD

Report Input

This report is run at the District and School level.

For help with navigation and running the report, see How to Find and Generate a Report.

Field	Description
Select Schools	If run at the district level, choose one of the following: Select Multiple Schools - Select schools to include in the report. To select a single school, click that school. To select multiple schools, use Ctrl+Click and select each school to be included. Select schools to include in the report All Schools - Run the report for the entire district. If run at the school level, the report includes all records associated with the current school that meet the selection criteria. To change the current school, click School at the top of the page and choose the appropriate school from the list.
Select Students	Indicate which students to include in the report by selecting one of the following options: The selected [number] students only - Run the report for students in the current selection. All students - Run the report for all students in the current school or district that meet the selection criteria. Notes: If running the report for a single student, or group of students, select the students prior to running the report.
Report Period Start Date	Enter the report start date. PowerSchool recommends using the first day of the current school year, as defined in the Years & Terms, as the start date.
Report Period End Date	Enter the report end date. PowerSchool recommends using the last day of the school year so that all discipline incidents are captured in the extract for the full academic year.
School Group Note: This overrides the Use selection above.	Choose a group of schools to override the above "Use" parameter indicating District-Wide vs.Current School Only. The extract includes student records associated with the selected schools that meet the selection criteria. Note: This parameter is optional. The “School Group“ Report parameter will only be available when the sub-district functionality is not enabled.

Report Output

Each of the fields displayed in the output of the report is described below. See Understanding the Report Output Table for a definition of each column in the table.

Operational Keys: School of Attendance, Academic Year ID, Incident ID Local

Processing Method: Replacement

A separate record is generated for each action.

Field #	Data Element	Description	[Table]FieldName	Max Length	Field Type	O/U	Required
19.01	Record Type Code	The type of data record being submitted.	Always SIRS	4	CS	N/A	Y
19.02	Transaction Type Code	The action taken when the data record is submitted. CALPADS processes the following Transaction Type Codes: Blank: Add or update the record D: Delete the current record R: Replace the record	This value is calculated based on the updatable fields and operational keys.	1	CS	N/A	N
19.03	Local Record ID	A local use field to provide the system record identifier for a submitted record in any CALPADS file format. This field is calculated by concatenating internal ID fields. The values for the internal fields may be separated by periods.	Discipline records: [Incident]Incident_ID [Incident]Student_Number [psrw_ParticipantBehaviorCode]ID	255	CS	U	N
19.04	Reporting LEA	The district number; a unique identifier for the LEA responsible for obtaining and maintaining a student's SSID by way of an enrollment record in the CALPADS. State Business Rules: The seven-digit county district (CD) code must be reported if the reporting LEA is a district or county office. The school (S) code must be reported if the reporting LEA is an independently reporting charter school.	[Prefs]Name=districtnumber [Prefs]Value	7	CS	N/A	Y
19.05	School of Attendance	The seven-digit school code for the school that is associated with the incident. The report locates the School of Attendance for a student based on the school associated with the incident. Each school is assigned a seven-digit School Number, which is used as the School of Attendance value. State Business Rules: If the student attends an independently reporting charter school, the school number (S) must be submitted. If the student attends an NPS school, the School of Attendance must be 0000001.	[PSRW_Incident]School_Number [Schools]ID [S_CA_SCH_X]StateSchoolNumber	7	CS	O	Y
19.06	Academic Year ID	The period during which school is in regular session and provides a required number of days of instruction (175 days in California). Extracted in the format CCYY-CCYY, such as 2008-2009.	[Terms]FirstDay [Terms]LastDay The report extracts the last four digits of the date value stored in both the FirstDay and LastDay fields.	9	CS	O	Y
19.07	SSID	The unique identifier for the student assigned by the first California district in which the student is enrolled. State Business Rules: Must be a valid CALPADS SSID.	[Students]State_StudentNumber	10	CS	N/A	Y
19.08	Local Student ID	A unique identifier assigned to the student by an LEA. State Business Rules: Updates to this field must be made through the SSID Enrollment extract.	[Students]Student_Number	15	CS	N/A	Y
19.09	Student Legal First Name	The first name given to the student after birth or through legal action. State Business Rules: Updates to this field must be made through the Student Information extract. Note: If populated, the student's legal name overrides the student's preferred name.	[StudentCoreFields]PSCore_Legal_First_Name [Students]First_Name	30	CS	N/A	Y
19.10	Student Legal Last Name	The last name given to the student after birth or through legal action. State Business Rules: Updates to this field must be made through the Student Information extract. Note: If populated, the student's legal name overrides the student's preferred name.	[StudentCoreFields]PSCore_Legal_Last_Name [Students]Last_Name	50	CS	N/A	Y
19.11	Student Birth Date	The student’s birth date, extracted in the format CCYYMMDD, e.g. 20081025. State Business Rules: Updates to this field must be made through the Student Information extract.	[Students]DOB	8	DT	N/A	Y
19.12	Student Gender Code	The student’s gender. State Business Rules: Updates to this field must be made through the Student Information extract. Notes: If populated, the student's legal gender overrides the student's preferred gender. If the student's preferred gender is X, the student's legal gender must be M or F.	[StudentCoreFields]PSCore_Legal_Gender [Students]Gender	1	CS	N/A	Y
19.13	Incident ID Local	The unique identifier for the incident. A disciplinary incident is one or more student offenses that occur on the same date at the same time. This value is used to track the incident throughout multiple student records. In Incident Management, this value is system generated. State Business Rules: This value must be unique for the incident per Academic Year and school.	[Incident]Incident_ID	20	CS	N/A	Y
19.14	Incident Result Code	The disciplinary action taken against the student for the incident. State Business Rules: If an Incident Result Modification Code is reported, then the Incident Result Code must be 200 (Expulsion). If the Incident Result Code equals 300, then no other SIRS record with the same Academic Year ID, School of Attendance, SSID, and Incident ID Local may exist where Incident Result Code = 100 (out-of-school suspension), 110 (in-school suspension, or 200 (expulsion).	[Incident_LU_Code]State_Aggregate_RPT_Code	3	CS	N/A	Y
19.15	Incident Result Authority Code	The agency that authorizes any disciplinary action taken against the student. In Incident Management, this is the Action Authority Code.	[Incident_LU_Code]Code_Type=actionattribute [Incident_LU_Code]State_Aggregate_RPT_Code [Incident_LU_Sub_Code]State_Detail_Report_Code	2	CS	N/A	Yes, if the student has an active SPED Plan on the date of the incident and the Incident Result Code is not equal to 300 or 400.
19.16	Incident Result Duration Days	The length of the disciplinary action. In Incident Management, this is the Actual Duration. The value is calculated incrementally, which allows for increments of less than one day. Format: ###.## The duration for incidents with an action code of 300 is reported as '0'. State Business Rules: If Incident Result Duration Days = 0, then Incident Result Action Modification Code must = 100 (Enforcement Suspended) or 200 (Shortened). If Incident Result Code is equal to 300 (No Action), 400 (Other Means of Correction), seclusion, or restraint, then Incident Result Duration Days must either not be populated or equal to zero.	[Incident_Action]Duration_Actual	3	CS	N/A	Yes, if the Action Taken Code is not equal to 300, 400, seclusion, or restraint.
19.17	Incident Result Modification Code	The code describing a modification made to a disciplinary action order, such as shortening the term of the suspension or expulsion. In Incident Management, this is the Action Change Code and subcode. State Business Rules: This field is only required if the disciplinary action is 200 (expulsion). If Incident Result Duration Days = 0, then Incident Result Action Modification Code must = 100 (Enforcement Suspended) or 200 (Shortened).	[Incident_LU_Code]Code_Type=Actionchange [Incident_LU_Code]State_Aggregate_RPT_Code [Incident_LU_Sub_Code]State_Detail_Report_Code	3	CS	N/A	Yes, if the Disciplinary Action is 200 (Expulsion).