1. For Discipline Clerks and Assistant Principals Incident
Management Training
2. Incident Management (IM) Training Session 1 Overview of
reporting requirements Session 2 Data entry methodology Session 3
Data Validation
3. Incident Management (IM) IM Report Dependencies Federal and
SC State Data Submissions Session 1 Overview of reporting
requirements
4. Incident Management (IM) All discipline data must be
reported in the Incident Management (IM) System for the 2014-15
school year. It is critical that all data entered be reviewed and
verified for accuracy.
5. Federal Reporting Requirements: EdFacts Incident Management
(IM)
6. Federal Reporting Requirements: UMIRS Uniform Management
Information Reporting System (UMIRS) is a data collection system
required by No Child Left Behind. Incident Management (IM)
7. South Carolina public school or charter school will be
considered persistently dangerous if its conditions expose students
to injury from violent criminal offenses for a period of three
consecutive years. ~USDE Federal Reporting Requirements:
Persistently Dangerous Schools (PDS) Incident Management (IM)
8. SC State Reporting Requirements Guns Free Act Counts of
incidences of gun possession: Student/School Expulsion and
Suspension Out-of-School Suspensions or Expulsions for Violent
and/or Criminal Offenses Incident Management (IM)
9. Data Entry Methodology Incident Management Training Session
2
10. Incident Management (IM) Data Entry Methodology Tour of
Incident Management System in PowerSchool Data Entry Common Errors
Session 2 Data Entry Methodology
11. Incident Management System in PowerSchool Embedded,
Narrated Video of IM data entry
12. Common Coding Errors If the incident does not have an
element under the offender the incident is improperly coded
Incident Management (IM)
13. Actions must be associated with the Behavior for the
removal and duration to generate on reports and the IM Query.
Common Coding Errors Incident Management (IM)
14. Missing Weapon Object from a '789' Weapon incident 789
Weapons (Objects) Sub-codes for Weapons 780- Other Weapons 781-
Handguns 782- Rifles/Shotguns 783- Other Firearms 784-Knife
Blade> 2 inches (State) 785- Knife Blade>2.5 inches (Federal)
Action Taken Common Coding Errors Incident Management (IM)
15. Data Entry Practice Exercise Incident Management (IM)
(Login to the PowerSchoolTraining server to complete the following)
A physical altercation involving 2 students occurred at Apple Grove
High School. Enter the appropriate incident, participant, behavior
and action codes into PowerSchools Incident Management system.
Details are outlined in Practice1.pdf.
16. Golden Rules of IM Coding All incidents coded must have 1.
an Offender associated with the incident. 2. a Behavior associated
with the offender. 3. an Action associated with the behavior.
Incident Management (IM)
17. 1. All expulsions/suspensions require a duration code 2.
SUX-Pending Expulsions must have a resolution coded prior to the
180th day. Incident Management (IM)
18. Toy bullets, toy guns should be coded as 789 Weapons-OBJ
Misc. Objects. Do not code as 781,782, & 783. Specific Weapons
Coding Incident Management (IM)
19. 783-Other Firearms examples- devices designed to expel a
projectile, grenade, explosive Specific Weapons Coding Incident
Management (IM)
20. 780-Other Weapons- examples- razor blade, ice pick, Chinese
star, chain, brass knuckle, billy club, stun gun, mace, tear gas
Specific Weapons Coding Incident Management (IM)
21. Validating IM Data Review Game Incident Management Training
Session 3
22. Incident Management (IM) Data Validation Validating IM Data
Review of Concepts Session 3 Data Validation
23. Validating IM Data After each of the districts 45th day,
90th day, 135th day and 180th day, validate Incident Management
incident counts. Use PowerSchool internal reports, SCDE reports,
and the IM Data query tool to check data accuracy.
24. Incident Management PowerSchool Reports
25. System Report-Discipline Summary Report System Tab
26. Review Game
27. Incident Management Resources Barbara Solomon,
[email protected] Connie Graham, [email protected] SCDE
Student Intervention Services:
http://ed.sc.gov/agency/ac/Student-Intervention- Services/
PowerSchool Incident Management User Training and Reference Guide
(August 2014) (1.5 Mb PDF)
