Creating Discipline Incidents

Introduction

The following data elements are required for discipline incidents. Discipline incidents are created at the student, school, or district level. For KIAS, create all incidents at the school level via the Special Functions navigation below.

The Kansas State Reporting incident type, as well as Kansas-specific incident codes and subcodes, must be set up at the district level prior to creating discipline incidents. For more information on code values, see the Appendix.

Data Element	Additional Information	[Table]FieldName	Length	Used in these Reports
Editing Incident Details Start Page > Special Functions > Incident Management > Edit/Create New Incident > Incident Detail Note: Security groups must be granted access to Incident Types in order to create incidents. Refer to System Help in PowerSchool for more information on how to set up group level permissions.
Incident Description
Incident ID	This field is view-only. The ID is populated automatically when the incident is first submitted.	[Incident]Incident_ID	15	KIAS
School	Choose the appropriate school. Note: For KIAS, create all incidents at the school level.	[Incident]School_Number	4	KIAS
Incident Type	Choose Kansas State Reporting^ as the incident type.	[Incident_LU_Code]Code_Type=incidenttypecode [Incident_LU_Code]Incident_Category=Kansas State Reporting	N/A	KIAS
Incident Date	Enter the date and time that the incident occurred.	[Incident]Incident_TS	10	KIAS
Time Frame	Choose the time frame that the incident took place. Valid values: 100 – During School 200 – Outside School Hours	[Incident_Detail]LU_Code_ID – Associates a time code to the incident. [Incident_LU_Code]Code_Type=timecode [Incident_LU_Code]Incident_Category	4	KIAS
Time Frame (second pop-up menu)	Choose the specific time of the school day that the incident occurred.	[Incident_Detail]LU_Subode_ID	4	KIAS
Time Frame Comment	Enter notes regarding the time frame.	[Incident_Detail]Lookup_Code_Desc	255	KIAS
Title	Enter the title of the incident.	[Incident]Incident_Title	255	KIAS
Description	Enter the description of the incident.	[Incident]Incident_Detail_Desc	N/A	KIAS
Location Location Group	Choose the location where the incident occurred. Valid values: 100 – On Campus 200 – Off Campus	[Incident_Detail]LU_Code_ID – Associates a location code to the incident. [Incident_LU_Code]Code_Type=locationcode	4	KIAS
Location (second pop-up menu)	Choose a specific location where the incident occurred.	[Incident_Detail]LU_Subode_ID	4	KIAS
Location Description	Enter the description of the location of the incident.	[Incident]Location_Details	255	KIAS
Building Discipline Incidents
Adding Students or Staff Members Incident Builder: Participants: Add Student or Staff Member Follow the steps below to add a student or staff participant to the incident. Click the Plus (+) button next to Participants. The Search for Student, Staff, or Other Participants dialog appears. Enter criteria for the search and click Search. The Results section is populated with matching participants. Highlight the appropriate participant in the search results and click Add.
Name School Grade (Level) Gender Type	The full name, school, grade level, gender and type (student or staff member) of the participant. The identity of the participant is saved in PowerSchool. The name, school, grade level, gender, and type data are referenced from the student or staff member record.	[Incident_Person_Role]StudentID [Incident_Person_Role]TeacherID	N/A	KIAS
Attributes	See Incident Builder: Participants: Update Participant Attributes below.	See below	N/A	N/A
Role	Choose the role that best describes the participant’s involvement in the incident. Valid values: Reporter Victim Offender Witness For the Reporter, Victim and Offender roles, choose the appropriate sub-value. Note: In order to assign more than one role, click the Plus (+) sign next to Select Role(s). For example, a participant can be reported as both the reporter and the victim.	[Incident_Person_Role]Role_Incident_Detail_ID	1	KIAS
Adding Other Participants Incident Builder: Participants: Add Other Participant Follow the steps below to add an Other Participant to the incident. Click the Plus (+) button next to Participants. The Search for Student, Staff, or Other Participants dialog appears. Click Create Other. The Add Other Participant dialog appears.
Mark Person as Unknown	Select the checkbox if the person is unknown.	[Incident_Other_Person]Is_Unknown	N/A	Not Required
First, Middle, Last	Enter the first, middle, and last names of the participant, if available.	[Incident_Other_Person]First_Name [Incident_Other_Person]Middle_Name [Incident_Other_Person]Last_Name	255	KIAS
Position	Enter the position of the participant, if available.	[Incident_Other_Person]Position	N/A	Not Required
Age	Enter the age of the participant, if available.	[Incident_Other_Person]Age	255	KIAS
Gender	Enter the gender of the participant, if available.	[Incident_Other_Person]Gender	255	KIAS
Attributes	See Incident Builder: Participants: Update Participant Attributes below.	See below	N/A	N/A
Role	Choose the role that best describes the participant’s involvement in the incident. Valid values: Reporter Victim Offender Witness For the Reporter, Victim and Offender roles, choose the appropriate sub-value. Note: In order to assign more than one role, click the Plus (+) sign next to Select Role(s).	[Incident_Person_Role]Role_Incident_Detail_ID	1	KIAS
Adding Participant Attributes Incident Builder: Participants: Update Participant Attributes Click the Pencil icon next to the name of an offender or victim to add/update participant attributes. For Other Participants, click Add after opening their record to access the attributes. Note: Participant attributes must only be associated offenders and victims in the incident.
Attributes: GFSA Modification	Click the plus (+) in the Attributes section to add GFSA Modification. Choose Yes or No from the second pop-up menu to indicate if an expulsion length was shortened or changed to a suspension by the superintendent under the case-by-case modification provisions of Section 4141(b)(1) of the Gun-Free Schools Act. Note: This field is required if the Offender Type is 10.	[Incident_Detail]Incident_Code_ID [Incident_Detail]Incident_Sub_Code_ID	1	KIAS
Attributes Code Comment GFSA Modification	If you select Yes for GFSA Modification, then a comment is mandatory.	[Incident_Detail]Lookup_Code_Desc	255	KIAS
Attributes: IDEA Disability	Click the plus (+) in the Attributes section to add IDEA Disability. Choose Yes or No from the second pop-up menu to indicate if the student had an IEP for disability as defined in IDEA at the time of the incident. Note: This field is required if the Offender Type is 1 or 2.	[Incident_Detail]Incident_Code_ID [Incident_Detail]Incident_Sub_Code_ID	1	KIAS
Attributes: Disability Manifest	Click the plus (+) in the Attributes section to add Disability Manifest. Choose Yes or No from the second pop-up menu to indicate if the incident was a manifestation of the student’s disability. Note: This field is required IDEA Disability is 1.	[Incident_Detail]Incident_Code_ID [Incident_Detail]Incident_Sub_Code_ID	1	KIAS
Attributes: Zero Tolerance	Click the plus (+) in the Attributes section to add Zero Tolerance. Choose Yes or No from the second pop-up menu to indicate if the disciplinary action was pursued only as a result of the school zero tolerance policy.	[Incident_Detail]Incident_Code_ID [Incident_Detail]Incident_Sub_Code_ID	1	KIAS
Attributes: Motivation	Click the plus (+) in the Attributes section to add Motivation. Choose the appropriate value to indicate the offender’s motivation for the incident.	[Incident_Detail]Incident_Code_ID [Incident_Detail]Incident_Sub_Code_ID	2	KIAS
Attributes Code Comment Motivation	Optionally, enter a comment if the Motivation is Other.	[Incident_Detail]Lookup_Code_Desc	255	KIAS
Attributes: Victim Injury	Click the plus (+) in the Attributes section to add Victim Injury. Choose the appropriate value to indicate if the victim sustained an injury as a result of the incident. Valid values: 1 – No Injury 2 – Minor Injury 3 – Major Injury	[Incident_Detail]Incident_Code_ID [Incident_Detail]Incident_Sub_Code_ID	1	KIAS
Adding Actions Incident Builder: Incident Elements: Add Action
Action Code	Choose the action code.	[Incident_Action]Action_Incident_Detail_ID [Incident_Detail]LU_Code_ID – Associates an action code to the incident. [Incident_LU_Code]Code_Type=actioncode	4	KIAS
Action Code Comment	Enter details regarding the action taken. Note: This field is required if Action Taken is 710, 770, 810, 850, 860, 870, or 999.	[Incident_Detail]Lookup_Code_Desc		KIAS
Action Taken Detail	Enter comments regarding the action taken. Note: This field is required if Action Taken is 710 or 999.	[Incident_Action]Action_Resolved_Desc	255	KIAS
Duration Code	Choose School Days. Choose the appropriate number of school days for a suspension or expulsion, if applicable. Length in School Days is required if Action Taken is if 450, 510, 515, 520, 525, 550, 555, 560, or 565. Note: The report refers first to the Actual Duration field, then to the Assigned Duration field. If both of those fields are blank, then the report refers to the Duration Code and subcode values.	[Incident_Action]Action_Incident_Detail_ID [Incident_Detail]LU_Code_ID – Associates a duration code to the incident. [Incident_LU_Code]Code_Type=durationcode	6	KIAS
Assigned Duration	Enter the assigned length of the disciplinary action. Note: The report refers to the Actual Duration field first. If neither of these fields is populated, the report refers to the Duration Code and subcode.	[Incident_Action]Duration_Assigned	6	KIAS
Actual Duration	Enter the actual length of the disciplinary action. Note: If this field is not populated, the report refers to Assigned Duration.	[Incident_Action]Duration_Actual	6	KIAS
Adding Objects Incident Builder: Incident Elements: Add Object
Object Code	Choose W2-Weapons.	[Incident_Object]Object_Incident_Detail_ID – Associates an object code to the incident. [Incident_Detail]LU_Code_ID [Incident_LU_Code]Code_Type=objectcode	N/A	Required Setup
Object Subcode	Choose the appropriate weapon. Note: This field is required if the Incident Type Group is 1200. Valid values: 100 – Handgun 200 – Rifles/Shotgun 300 – Other Firearm 400 – Firearm component or attachment 500 – Explosive/Destructive Device 600 – Substance used as a Weapon 700 – Knife/Cutting Instrument 999 – Other Weapon	[Incident_Detail]LU_Sub_Code_ID – Associates an object subcode to the incident	4	KIAS
Description	Enter a description of the weapon if the Type of Weapon is 999 (Other Weapon).	[Incident_Object]Object_Desc	255	KIAS
Adding Behaviors Incident Builder: Incident Elements: Add Behavior
Behavior Code	Choose the behavior code.	[Incident_Detail]LU_Code_ID – Associates a behavior code to the incident [Incident_LU_Code]Code_Type=behaviorcode	4	KIAS
Behavior Subcode	Choose the behavior subcode.	[Incident_Detail]LU_Sub_Code_ID – Associates a behavior subcode to the incident	4	KIAS
Behavior Code Comment	Enter a description if 9999 is selected for Incident Type Group or if 1099, 1299, 2099, 2199, 2399, 2599, 3399, 4499, or 5199 is selected for Incident Type Classifier.	[Incident_Detail]Lookup_Code_Desc	255	KIAS
Primary Behavior	Select the Primary Behavior checkbox for the most severe offense (even if there is only one behavior in the incident). Note: If the incident has multiple behaviors, the most egregious behavior should be checked as the Primary Behavior.	[Incident_Detail]Primary_Indicator	30
Allegation	Select the Allegation checkbox to indicate that the behavior has not been proven. An allegation is a claim or assertion of wrongdoing, typically made without proof.	[Incident_Detail]Allegation_Indicator	1

Back to Top

Introduction

Editing Incident Details

Building Discipline Incidents

Adding Students or Staff Members

Adding Other Participants

Adding Participant Attributes

Adding Actions

Adding Objects

Adding Behaviors