Skip to main content
Skip table of contents

Incident Setup

On this page:


Introduction

State reportable incidents must be created at the school level via Special Functions. Non-state reportable incidents may be created at the student, school, or district level.

Incident Rules

Use the following rules when creating incidents.

State reportable incidents must be associated with the incident type SDFS Reportable.

Offender

At least one student must be assigned the role of offender for each incident.

At least one behavior must be defined for each offender. After you create a behavior, you must drag the behavior to the participant to associate the two elements.

At least one action must be assigned to each violent behavior assigned to an offender. After you create an action, 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 behaviors.

Attribute

At least one attribute must be associated with each incident involving a violent behavior. Attributes indicate if the incident was violent and involved physical injury. Attributes are associated to the incident itself, i.e. it is not necessary to drag the attribute to an offender or behavior.

Back to Top

Setup Elements

The following data elements are required for discipline incidents. Incident types, as well as incident codes and subcodes, must be set up at the district level prior to creating discipline incidents. See District Setup for more information.

Data Element

Additional Information

[Table]FieldName

Used in these Reports

Defining 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. Review additional information about incident management.

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 Setup

School

The current school name appears. State reportable incidents must be created at the school level.

[Incident]School_Number

Required Setup

Incident Type

Choose the Idaho incident types from the pop-up menu: SDFS Reportable.

[Incident_LU_Code]Code_Type=incidenttypecode

[Incident_LU_Code]Incident_Category

Required Setup

Incident Date

Enter the date and time that the incident occurred.

[Incident]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

Required Setup

Time Frame Comment

If applicable, enter a comment regarding the time frame.

[Incident_Detail]Lookup_Code_Desc

Optional Setup

Title

Enter a title for the incident.

[Incident]Incident_Title

Not Required

Description

Enter a description of the incident.

[Incident]Incident_Detail_Desc

Not Required

Location

Choose the location where the incident occurred from the pop-up menu.

[Incident_LU_Code]Code_Type=locationcode

[Incident_LU_Code]Incident_Category

Required Setup

Location Subcode

Choose the location subcode from the pop-up menu.

[Incident_LU_Sub_Code]Sub_Catetory

[Incident_LU_Sub_Code]State_Detail_Report_Code

Required based on the Location Code

Location Description

If applicable, enter the description of the location of the incident.

[Incident]Location_Details

Optional Setup

Prepared By

Not Required

N/A

Not Required

Financial Impact

Not Required

N/A

Not Required

Created By

The system-generated record of the person logged into PowerSchool who recorded the incident.

[Incident]Created_By

System Generated

Created On

The system-generated date and time that the incident was recorded in PowerSchool.

[Incident]Created_TS

System Generated

Use the following steps to add participants to the incident.

  1. Click the plus (+) next to Participants. The Search for Student, Staff, or Other Participants dialog appears.
  2. Enter criteria for the search and click Search. The Results section is populated with matching participants.
  3. Highlight the appropriate participant in the search results and click Add.

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 Idaho.

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:

  • Reporter
  • Victim
  • Offender
  • Witness

Note: In order to assign more than one role, click the plus (+) next to Select Role(s).

[Incident_Person_Role]Role_Incident_Detail_ID

Required Setup

Use these steps to add a non-student/non-staff participant to the incident.

  1. Click the plus (+) next to Participants. The Search for Student, Staff, or Other Participants dialog appears.
  2. 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

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:

  • Reporter
  • Victim
  • Offender
  • Witness

Note: In order to assign more than one role, click the plus (+) next to Select pRole(s).

[Incident_Person_Role]Role_Incident_Detail_ID

Required Setup

Use these steps to add a disciplinary action to the incident.

  1. Click the plus (+) next to Incident Elements. The Incident Elements dialog appears.
  2. 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 pop-up menu: Expelled, Suspended from school or Convicted.

Note: At least one action must be assigned to each violent behavior.

[Incident_LU_Code]Code_Type=actioncode

[Incident_LU_Code]Incident_Category

Required Setup

Action Subcode

Choose the action subcode from the pop-up menu. Subcodes are required for Expelled and Suspended from school.

[Incident_LU_Sub_Code]Sub_Catetory

[Incident_LU_Sub_Code]State_Detail_Report_Code

Required Setup

Duration Code

Choose the duration of the disciplinary action from the pop-up menu.

[Incident_Detail]LU_Code_ID

[Incident_LU_Code]Code_Type=durationcode

Required Setup

Use these steps to add behavior to the incident.

  1. Click the plus (+) next to Incident Elements. The Incident Elements dialog appears.
  2. 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 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

Behavior Subcode

If available, choose a behavior subcode from the pop-up menu.

[Incident_LU_Sub_Code]Sub_Catetory

[Incident_LU_Sub_Code]State_Detail_Report_Code

Required Setup

Behavior Code Comment

If appropriate, enter a comment regarding the behavior.

[Incident_Detail]Lookup_Code_Desc

Required Setup

This section defines whether a violent incident involved physical injury.

  1. Click the plus (+) next to Incident Elements. The Incident Elements dialog appears.
  2. Click Add Attribute. The Add Attribute dialog appears.

Attribute Code

Select the checkbox for Violent Incident without Physical Injury or Violent Incident with Physical Injury, if applicable (do not select both checkboxes).

Note: At least one attribute code must be associated with each incident involving a violent behavior.

[Incident_LU_Code]Code_Type=attributecode

[Incident_LU_Code]Incident_Category

Required Setup

Attribute Comment

Enter a comment related to the attribute code, if applicable.

[Incident_Detail]Lookup_Code_Desc

Optional Setup

Back to Top

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.