1. Incident Management and Dropout Data Updates-Edtech
Evie Coakley
Student Information Systems
March 1, 2016

2. SCDE Updates
Incident Management

3. IM-What’s New for 2015-16 School Year
New Action Code
EXO-Expulsion Overturned
New Discipline Code
031 District Medication Violation
New Behavior Code Sub codes
Harassment
HNO – Due to National Origin of Victim
HSO – Due to Sexual Orientation of Victim
Bullying
BNO – Due to National Origin of Victim
BSO – Due to Sexual Orientation of Victim

4. Incident Management Coding
All SUX-Pending Expulsion should be resolved before the 180th day reporting.
All SPC-Pending Parent Conference should be resolved and updated before the 180th day reporting.
When coding 789 Weapons you must code a sub code and action taken. (Subcodes 780,781, 782, 783, 784, 785, & 786)

5. Incident Management Coding 101
Reminder: Behavior Code must be dragged and dropped on the top of the participant’s name. The Action Code must be dragged and dropped on the top of the behavior.
Offender Name Behavior (must be dragged and dropped on Participants name) Action (must be dragged and dropped on the behavior)
Additional Behavior (must be dragged and dropped on Participants name) Action(must be dragged and dropped on the behavior.
The incident below was coded using Chrome.

6. Properly Coded Incident-

7. Incident Management Coding
Weapon Coding-Adding Object

8. Incident Management Coding
Do not use students names in the title or Suns ID.
Toy bullets, toy guns, toy cap guns, toy pellet guns should be coded as 789 Weapons-OBJ Misc. Objects. Do not code as 781,782, & 783.
BB Guns should be coded as 789 as Other Weapons-sub code Other Weapon-sub code 780-Other Weapons.
783-Other Firearms – examples- devices designed to expel a projectile, grenade, explosive
780-Other Weapons- examples- razor blade, ice pick, Chinese star, chain, brass knuckle, billy club, stun gun, mace, tear gas

9. Incident Management Coding
Do not add additional codes to Incident Management System. Align your district's codes to the available codes in the system.
No student should have 12 incidents in one day coded.
Incidents must be coded with attributes for each student.
Tardies are not considered Truancy. The tardy code of 180 should be used for excessive tardies.

10. Reviewing Incident Reports in ADT
During the school year the Incident reports will be posted in ADT or Secure SFTP Server at 45th day, 90th day, 135th day and 180th day.
Districts should review data to ensure that incident totals are correctly reported.
Districts should review all incidents reported as Homicides and Kidnapping to ensure this information is coded correctly.
Updated IM Reports are available. Reports must be download by your school district PowerSchool Contact.
Staff Referral Report
Discipline By Behavior
Discipline Frequency Report

11. Discipline Data for Reporting
Reports should be reviewed for the following errors:
Error Code         
Error Message
1000
Duration code missing.  All expulsions require a duration code (Refer to IM Guide page 21).
1010
Behavior code missing.  All incidents require at least one behavior code. (Note: Make sure that you dragged and dropped the behavior code on top of the participant) (Refer to IM Guide page 8).
1020
More than one student per Truancy incident.  Create a separate incident for each truant student.
1030
Physical Injury code missing. Participant Attributes is missing (Refer to IM Guide page 15).
1040
All pending expulsions should be updated to the final outcome (e.g., Expulsion, Alternative School, OSS, Overturn Expulsion or other outcome (Refer to IM Guide page 28-30).
1050
All incidents require some type of action.
1060
Missing Weapon Object from a '789' Weapon incident (Refer to IM Guide page 22).
1070 
Warning - Please confirm Homicide and Kidnapping incidents. Double check the coding to ensure for accuracy.

12. Reviewing Incident Data Reports- Report with Errors

13. Reviewing Incident Data Reports Report without Errors

14. What’s New with Data Validation?
Error Reports delivered in PowerSchool directly to the school
Instant Feedback with Error Corrections
Direct Link to the incident

15. Level Data Validation Reports

16. Level Data Validation Reports

17. Level Data Validation Reports

18. Level Data Validation Tips
Make sure you click on the incident link to make updates
Review the incident for additional errors such as:
Missing Action Codes
Missing Object Codes
Missing Duration Code
Pending Expulsion (no final outcome)
Make sure you click the submit button to update changes made to the incident
Make sure you reload the tab once corrections are made to update the totals

19. IM Resources
safety/discipline-related-reports/incident- management-training/
PowerSchool Incident Management User Training and Reference Guide
Incident Management Frequently Asked Questions

20. Questions??????

21. Business Services Department
Contact Information
Evie Coakley
GCSD
Business Services Department
2018 Church Street
Georgetown, SC
Phone:
Fax: