Discipline Incident Setup

The following data elements are required for discipline incidents. Discipline incidents are created at the student or school level. It is recommended to create all incidents at the school level via the Special Functions navigation below.

Incident types, as well as 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.

The following rules apply to each type of person associated with an incident.

Type of Person	Rule
Offender
	At least one offender must be defined for each incident.
	At least one violation (behavior) must be defined for each offender. Note: After you create a behavior for a participant, you must drag the behavior to the participant to associate the two elements.
	One violation (behavior) must be marked as the primary violation in the incident. If a primary violation is not selected, then the report derives the primary violation.
	At least one action must be associated with each violation (behavior) assigned to an offender. Note: After you create an action in response to a behavior, you must drag the action to the behavior to associate the two elements. After the action is associated with the behavior, it no longer appears under the Incident Elements heading.
Victim
	Victims are not required for incidents.
	Victims must not have any associated behaviors.
	Victims must have at least one associated action to be reported.
Witness
	Witnesses are not required for incidents.
	Witnesses must not have any associated behaviors.
	Witnesses do not have state-reportable actions.
Reporter
	At least one reporter must be defined for each incident.
	Reporters must not have any associated actions or violations (behaviors).

Although the Participant Types are a required element in Incident Management. The discipline data that fulfills all the publishing criteria will get published even if one participant type is filled in. Districts are not required to enter every Participant Type.

Data Element	Additional Information	[Table]FieldName	Required for Incident Setup	Gets published for the State
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.
Incident Description
Incident ID	This field is view-only and appears for existing incidents. The ID is populated automatically when the incident is first submitted.	[Incident]Incident_ID	Required	Yes
School	Choose a school from the pop-up menu. The School must not be excluded from state reporting for the discipline data to get published. Note: This option is only available if the incident is created at the District.	[Incident]School_Number	Required	Yes
Incident Type	State Reportable^ Incident Type has to be selected for the incident to get published to the State.	[Incident_LU_Code]Code_Type=incidenttypecode [Incident_LU_Code]Incident_Category	Required	Yes
Incident Date	Click the Calendar icon to open the calendar menu. Use the Arrow icons to select a different month. Click the date the incident occurred. Use the Time pop-up menus to enter the time the incident occurred.	[Incident]Incident_TS	Required	Yes
Time Frame Time of Day	Choose the time frame that the incident took place from the pop-up menu. Preloaded values: After School Hours Before School Hours During School Hours Non-School Day	[Incident_Detail]LU_Code_ID – Associates a time code to the incident. [Incident_LU_Code]Code_Type=timecode [Incident_Detail]_LU_SUB_CODE]	Optional	No
Title	Incident Title will not get published to the State but it is required for creating a new incident record.	[Incident]Incident_Title	Required	No
Description	Enter the description of the incident.	[Incident]Incident_Detail_Desc	Optional	No
Location	We have preloaded some of the Location Codes for Districts to use.	[Incident_Detail]LU_Code_ID – Associates a location code to the incident. [Incident_LU_Code]Code_Type=locationcode [Incident_LU_Code]Incident_Category	Optional	No
Location Description	Enter the description of the location of the incident.	[Incident]Location_Details	Optional	No
Prepared By	Not Required	N/A	Not Required	No
Financial Impact Cost	Enter the cost incurred as a result of the incident.	[Incident]Financial_Impact	Optional	No
Created By	Not Required The system-generated record of the person logged into PowerSchool who recorded the incident.	[Incident]Created_By	Not Required	No
Incident Builder: Participants: Add Student(s) This section defines the Person portion. Click the Plus (+) button next to Participants. The Search for Student dialog appears. Clicking on Search will give a dropdown for all the active students. Enter the 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 Referring to Individual First Name Referring to Individual Last Name	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	Required	Student - Yes Staff - No
Role	Choose the role that best describes the participant’s involvement in the incident. Valid values: Reporter Victim Offender Witness 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	Required	No
Incident Builder: Participants: Add Other Participant This section defines the Person portion. 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	Not Required	No
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	Required	Yes
Role	Choose the role that best describes the participant’s involvement in the incident. Valid values: Reporter Victim Offender Witness 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	Required	No
Incident Elements: Add Action This section defines the Action portion. Click the Plus (+) button next to Incident Elements. The Incident Elements dialog appears. Click Add Action. The Add Action dialog appears. Note: After you create an action in response to a behavior, you must drag the action to the behavior to associate the two elements. After the action is associated with the behavior, it no longer appears under the Incident Elements heading.
Action Code	Choose the action code from the dropdown menu. Valid values: In-School Suspension Out-of-School Suspension Expulsion	[Incident_Action]Action_Incident_Detail_ID [Incident_Detail]LU_Code_ID – Associates an action code to the incident. [Incident_LU_Code]Code_Type=actioncode [Incident_Person_Action]Incident_Person_Detail_ID – Associates an action code to a behavior and a participant.	Required	Yes
Action Service Code	Choose the action service from the dropdown menu. See the Appendix for valid values.	[Incident_Action]Action_Incident_Detail_ID [Incident_Detail]LU_Sub_Code_ID – Associates an action subcode to the incident.	Required	Yes
Action Date Range: Begin Date & End Date Assigned Action Start Date Assigned Action End Date	Enter the begin and end date of the Action.	[Incident_Action]Action_Plan_Begin_DT [Incident_Action]Action_Plan_End_DT	Required Optional	Yes (Action Begin Date is required)
Action Taken Detail	Enter additional comments for “Other Action” and	[Incident_Action]Action_Resolved_Desc	Optional	No
Assigned Duration Number of Removal / Reassignment Days	Enter the assigned length of the disciplinary action.	[Incident_Action]Duration_Assigned	Required	Yes
Actual Resolution Date	Enter the date that the consequence for the behavior was decided.	[Incident_Action]Action_Actual_Resolved_DT	Optional	Yes
Student Arrest	Choose the required Student Arrest Code Valid Values: (1) ON School Campus (2) OFF School Campus	[Incident_Action_Attribute]	Optional	Yes
Student Arrest Reason	Choose the required Student Arrest Reason See the Appendix for valid values.	[Incident_Action_Attribute]	Optional	Yes
Interim Alternative Education	Choose the required Interim Alternative Education Value. Valid Value: Yes No	[Incident_Action_Attribute]	Optional	Yes
Incident Elements: Add Behavior This section defines the Behavior portion. Click the Plus (+) button next to Incident Elements. The Incident Elements dialog appears. Click Add Behavior. The Add Behavior dialog appears. Note: After you create a behavior for a participant, you must drag the behavior to the participant to associate the two elements.
Behavior Code	Choose the behavior code from the dropdown menu. See the Appendix for valid values.	[Incident_Detail]LU_Code_ID – Associates a behavior code to the incident. [Incident_LU_Code]Code_Type=behaviorcode [Incident_Person_Detail]Incident_Person_Role_ID – Associates a behavior code to a participant.	Required	Yes
Primary Behavior	Select the checkbox to indicate that this is the primary behavior for this incident.	[Incident_Detail]Primary_Indicator	Optional	No
Incident Elements: Add Attribute This section defines whether the Incident Record is related to any Criminal Gang-Related Event. Click the Plus (+) button next to Incident Elements. The Incident Elements dialog appears. Click Add Attribute. The Add Attribute dialog appears.
Attribute Code Criminal Gang-Related Event	Select the checkboxes for Criminal Gang Related Event, if applicable: Valid Values: (0) - N/A not gang-related (default, publish when no action code returned) This code has not been displayed in the Attribute section because this gets selected by default (1) - Investigation Disposed of Internally (2) - Case Referred to Local Law Enforcement	[Incident_Detail]LU_Code_ID – Associates an attribute code to the incident. [Incident_LU_Code]Code_Type=attributecode [Incident_LU_Code]Incident_Category	Optional	Yes

All of the codes that are pre-loaded with the ^ (carrot) symbol at the end can be published up to the State.