Skip to main content
Skip table of contents

Incident Type, Codes, and Subcodes Setup


Set up incident types, codes, and subcodes at the district level.

To create incidents, security groups must have access to Tennessee State Reporting. Refer to System Help in PowerSchool for more information on group-level permissions.

Incident Types

Using incident types, you can control which users can view and enter specific types of incidents.

Navigation: District Setup, then Incident Management, and then Incident Types.

Data Element

Additional Information

[Table]FieldName

Name

The following incident type must not be removed or edited.

  • TN State Reporting

[Incident_LU_Code]Incident_Category

[Incident_LU_Code]Code_Type=incidenttype

Code and Subcode Setup

Code types are used as an organizational tool to categorize incidents. PowerSchool includes 11 system-defined, non-editable code types that provide the basis from which all user-defined incident codes, subcodes, and secondary subcodes are created.

Navigation: District Setup, then Incident Management, and then Code & Subcode Setup.

Data Element

Additional Information

[Table]FieldName

Action Codes

Action codes are used to assign disciplinary action to a behavior.

[Incident_LU_Code]Code_Type=actioncode

[Incident_LU_Code]Incident_Category

Action Subcodes

Action subcodes are used to further define action codes.

[Incident_LU_Sub_Code]Sub_Category

[Incident_LU_Sub_Code]State_Detail_Report_Code

Attribute Codes

Attribute codes are used to describe further details about an incident.

[Incident_LU_Code]Code_Type=attributecode

[Incident_LU_Code]Incident_Category

Behavior Codes

Behavior codes are used to associate a behavior (alcohol, fights, vandalism, etc.) to an offender in an incident.

[Incident_LU_Code]Code_Type=behaviorcode

[Incident_LU_Code]Incident_Category

Behavior Subcodes

Behavior subcodes are used to further define behavior codes.

[Incident_LU_Sub_Code]Sub_Category

[Incident_LU_Sub_Code]State_Detail_Report_Code

Participant Attribute Codes

Participant attribute codes are used to describe detail about a participant.

[Incident_LU_Code]Code_Type=participantattributecode

[Incident_LU_Code]Incident_Category

Location Codes

Location codes are used to identify the location of an incident.

[Incident_LU_Code]Code_Type=locationcode

[Incident_LU_Code]Incident_Category

Location Subcodes

Location subcodes are used to further define location codes.

[Incident_LU_Sub_Code]Sub_Catetory

[Incident_LU_Sub_Code]State_Detail_Report_Code

Object Codes

Object codes are used to describe an item used in the incident.

[Incident_LU_Code]Code_Type=objectcode

[Incident_LU_Code]Incident_Category

Participant Role Codes

The following participant role codes are set up by default and should not be removed.

  • Offender
  • Victim
  • Witness
  • Reporter

N/A

Time Codes

Time codes are used to assign a time of day (during school hours, outside school hours, etc.) to an incident.

[Incident_LU_Code]Code_Type=timecode

[Incident_LU_Code]Incident_Category

Duration Codes

Duration codes are used to assign duration (hours, days, weeks, etc.) to a disciplinary action as the result of a violent behavior in an incident.

[Incident_LU_Code]Code_Type=durationcode

[Incident_LU_Code]Incident_Category

Action Change Codes

Action change codes are used to describe the reasons an action was changed.

[Incident_LU_Code]Code_Type=actionchangecode

[Incident_LU_Code]Incident_Category

Action Attributes

Action attributes are used to describe further details about an action taken in response to an incident.

[Incident_LU_Code]Code_Type=actionattribute

[Incident_LU_Code]Incident_Category

Verify Codes

  1. Click a Code Type.
  2. Review the list of codes. If a code is missing, add the code.
  3. Repeat steps 1 and 2 for all Code Types.

Add Codes

  1. Click a Code Type.
  2. Click the Plus (+) button.
  3. Complete the fields and click Submit.
Use the same process to verify or add subcodes, selecting the appropriate code in step 1 instead of the code type.

Map Codes

If the district has user-created codes and PowerSchool supplied codes are subsequently loaded, it may result in duplicate incident management codes. This code mapping functionality allows user-created codes to be merged with system codes, eliminating duplicates.

Navigation: District Setup, then District Info, then Incident Management Code Mapping.

Data Element

Additional Information

[Table]FieldName

Current Incident Codes (Subcodes)This lists all codes/subcodes used in the district, both user-created and system codes.

[Incident_LU_Code]Code_Type

[Incident_LU_Code]Incident_Category

State Reporting Incident Codes (Subcodes)For each duplicate subcode, choose a code to merge it with from the corresponding pop-up menu.

[Incident_LU_Code]Code_Type

[Incident_LU_Code]Incident_Category

JavaScript errors detected

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

If this problem persists, please contact our support.