On the Incidents page, there are six fields that you can control via the Configure page. As seen below, they are:
- Role – was the student in the incident an offender, a victim, a witness, etc.?
- Consequence Type – is the student in the incident going to receive a suspension, detention, behavioral intervention, etc.?
- Time – did the incident occur before school, at lunchtime, between classes, etc.?
- Location – did the incident happen on the bus, in the classroom, in the hall, etc.?
- Type – what type of incident was this: disrespect, fighting, profanity, etc.?
- Subtype* – a further level of detail that pertains to Type.
*Only visible when selecting a Type that has dependent subtypes already set up.
You can find these under the "Culture" heading on the Configure page.
Edit Incident Roles
Editing incident roles is pretty straightforward. Click the link to see what roles already exist, and then you can create new roles or edit existing roles as you see fit. One thing to note is that if you change the name of a role in Schoolrunner, it will affect the export file that Schoolrunner produces. This may in turn affect your import into your SIS!
Edit Consequence Types
What sort of consequences does your school have? Use this page to manage the different types of consequences. You'll notice that there are a few attributes to consequences such as External Name (how the consequence should appear in export files), Auto Daily Attendance (if an existing attendance code should automatically be applied to students who receive the respective consequence), and All Schools (if the consequence should be available at all schools in your network.
Edit Incident Times
Editing incident times is another straightforward task. Just be aware that changing any codes will disrupt imports into your SIS!
Edit Incident Locations
Similar to incident times, editing locations is easy as long as you're careful not to change any existing codes.
Edit Incident Types
Just like editing times and locations, make sure that when you add or edit incident types you don't change currently existing codes. If you want a specific type of incident to have a required role that goes with it, you can configure that as well, which will then be listed next to that incident type on the Incident Types page.
Edit Incident Subtypes
Since incident subtypes are dependent on the incident type, you need to specify which incident a given subtype belongs to whenever you add one. Again, subtypes have their own codes that correlate to those in your SIS, so make sure you don't change any existing codes. Subtype codes are specific to the incident type that a subtype belongs to, so you may see see multiple "01" codes - this is because those subtypes are contained within separate incident types.