Discipline Incidents Setup
Introduction
The following data elements are required for discipline incidents. Discipline incidents are created at the school or district level, or at the student level. See District Setup > District Information > Incident Management.
See Incident Management Quick Entry for more information.
Note: This documentation is specific to the Incident Management on PowerSchool versions 6.0.1 and later.
Incident Elements
Use the following rules when creating incidents.
State reportable incidents must be associated with the incident type NM State Reporting. |
At least one offender must be defined for each incident. Multiple offenders per incident are allowed. |
At least one behavior (infraction) must be defined for each offender. Multiple behaviors are allowed per offender; however one of the behaviors must be the primary behavior. While there may be multiple behaviors per incident, only one can be marked as the primary behavior. Note: Once you have selected a behavior in the incident elements portion of the page, the behavior MUST be dragged to the offender to link the elements correctly. Once this is done, the behavior will still appear under “incident elements”. |
At least one action (response) (only the most serious deemed by the District) must be associated with each primary behavior. 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. |
Objects are NOT necessary for New Mexico state reporting. If the District chooses to define/use object codes, they must be associated with each offender. Objects are used to define the weapon used by an offender. Note: After you create an object, you must drag the object to the participant to associate the two elements. After the object is associated with the participant, it also remains under the Incident Elements heading. |
It is not necessary to define victims to report an incident, but if a victim is defined, the victim subcode must be selected (student, teacher, administrator, etc.). |
Location codes are NOT necessary for New Mexico state reporting. Location codes can be set up and used, but they will not be reported in the New Mexico Discipline domain extracts. |
Witnesses are not reported. |
Reporters are not reported. |
Incident attributes are mandatory for New Mexico state reporting. Select the checkboxes to all attributes that apply to the incident. |
Defining Incident Details
Use the following steps to create New Mexico discipline incidents for reporting in the discipline domain extracts (Student Infraction and Student Infraction Response).
Data Element | Additional Information | [Table]FieldName | Required/Optional |
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. | |||
Describing the Incident | |||
Incident ID | This field is view-only. The ID is populated automatically when the incident is first submitted. | [Incident]Incident_ID | Required Setup |
School | Choose a school or the district from the pop-up menu. Note: This option is only available if the incident is created at the district. | [Incident]School_Number | Required Setup |
Incident Type | Choose NM State Reporting from the pop-up menu. | [Incident_LU_Code]Incident_Category = NM State Reporting [Incident_LU_Code]Code_Type=incidenttype | Required Setup |
Incident Date | Enter the date and time the incident occurred. | [Incident]TS | Required Setup |
Time Frame | Choose the time frame that the incident took place from the pop-up menu. | [Incident_LU_Code]Code_Type=timecode [Incident_LU_Code]Incident_Category | Optional Setup |
Title | Enter a title for the incident. | [Incident]Incident_Title | Required Setup |
Description | Enter a description of the incident. | [Incident]Incident_Detail_Desc | Required Setup |
Location | Choose the location where the incident occurred from the pop-up menu. | [Incident_LU_Code]Code_Type=locationcode [Incident_LU_Code]Incident_Category | Optional Setup |
Location Description | If applicable, enter the description of the location of the incident. | [Incident]Location_Details | Not Required |
Prepared by | Not Required | N/A | Not Required |
Financial Impact ($) | Not Required | N/A | Not Required |
Adding Student and Staff ParticipantsUse the following steps to add participants to the incident.
| |||
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 Setup |
Attributes | This field refers to participant attribute codes, which are not used for New Mexico. | N/A | Not Required |
Role | Choose the role that best describes the participant’s involvement in the incident. Each incident must be associated with at least one offender. Valid values:
Note: In order to assign more than one role, click the Plus (+) button next to Select Role(s). Note: If Victim is selected, the Victim subcode is required. | [Incident_Person_Role]Role_Incident_Detail_ID | Required Setup |
Adding Other ParticipantsUse these steps to add a non-student/non-staff participant to the incident.
| |||
Mark Person as Unknown | Select the checkbox if the person is unknown. | [Incident_Other_Person]Is_Unknown | 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 | Required Setup |
Position | Not Required | [Incident_Other_Person]Position | Not Required |
Age | Not Required | [Incident_Other_Person]Age | Not Required |
Gender | Enter the gender of the participant, if available. | [Incident_Other_Person]Gender | Required Setup |
Role | Choose the role that best describes the participant’s involvement in the incident. Each incident must be associated with at least one offender. Valid values:
Note: In order to assign more than one role, click the Plus (+) button next to Select Role(s). Note: If Victim is selected, the Victim subcode is required. | [Incident_Person_Role]Role_Incident_Detail_ID | Required Setup |
Adding Discipline ActionsUse these steps to add a disciplinary action to the incident.
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 an action code from the pop-up menu. Note: At least one action (only the most serious deemed by the District) must be assigned to each primary behavior. | [Incident_LU_Code]Code_Type=actioncode [Incident_LU_Code]Incident_Category | Required Setup |
Action Date Range (Begin Date, End Date) | Enter the dates that the discipline action was effective. | [Incident_Action]Action_Plan_Begin_Dt [Incident_Action]Action_Plan_End_Dt | Optional Setup |
Action Taken Detail | Enter a comment of the action taken. | N/A | Not Required |
Actual Resolution Date | Enter the date that the discipline action was resolved. | N/A | Not Required |
Duration Code | Choose the duration from pop-up menu. | [Incident_LU_Code]Code_Type=durationcode [Incident_LU_Code]Incident_Category | Required Setup |
Assigned Duration | Enter a comment of the assigned duration. | N/A | Required Setup |
Actual Duration | Enter the actual length of the disciplinary action. | [Incident_Action]Duration_Actual | Required Setup |
Duration Notes | Enter a comment regarding the duration, if applicable. | N/A | Not Required |
Action Change Reason | Enter a comment of the reason for the action change, if applicable. | N/A | Not Required |
Action Change Code | Choose the action change code from the pop-up menu, if applicable. | [Incident_LU_Code]Code_Type=actionchangecode [Incident_LU_Code]Incident_Category | Not Required |
Adding ObjectsUse these steps to add an object to the incident.
Note: After you create an object, you must drag the behavior to the participant to associate the two elements. | |||
Object Code | Choose the object from the pop-up menu. | [Incident_LU_Code]Code_Type=durationcode | Not Required |
Description | Enter a description of the object. | [Incident_Object]Object_Desc | Not Required |
Quantity | Enter the quantity of the object used in the incident. | [Incident_Object]Object_Quantity | Not Required |
Adding BehaviorsUse these steps to add behavior to the incident.
Note: After you create a behavior for a participant, you must drag the behavior to the offender to associate the two elements. | |||
Behavior Code | Choose the behavior code from the pop-up menu. Note: At least one behavior must be defined for each offender. | [Incident_LU_Code]Code_Type=behaviorcode [Incident_LU_Code]Incident_Category | Required Setup |
Primary Behavior (Most Severe Offense Code) | Select the checkbox to indicate that this is the Most Severe Offense. This indicator is required when there is more than one behavior in an incident. Note: When a behavior is marked as primary, the behavior icon updates to reflect the change. | [Incident_LU_Code]Code_Type=behaviorcode [Incident_Detail]Primary_Indicator | Required Setup |
Adding Incident AttributesThis section defines whether a violent incident involved physical injury.
| |||
Attribute Code | Select the checkboxes to all attributes that apply to the incident. Note: Incident attributes are mandatory for New Mexico state reporting. | [Incident_LU_Code]Code_Type=attributecode [Incident_LU_Code]Incident_Category | Required Setup |