Description: School and district administrators should be able to see all incident and action details for individual students as well as aggregated patterns. School and district administrators should be able to also see previous year patterns in order to intervene early and/or note whether a behavior pattern is new or continuing from previous years. (This kind of multi-year data can be used to provide evidence for RtI/MTSS interventions, testing for special education placement, etc.)
Users prefer to have data in one place; being able to get discipline data from the SWIS application via API would enable this. Not so much for reporting but for use by school staff in terms of deciding where to allocate personnel resources, do interventions, etc.
Actor: Mainly school and district administrators. Teachers probably do not need to see aggregated data but should be able to see the discipline records of their own students (depending on district policy).
Current State: Districts that do not use SWIS are limited in what they can see in terms of detailed discipline data. Experienced SIS users may be able to run reports to get these details, but most school-level do not have this level of expertise.
Future State: Future state would allow school and district staff (mainly administrators) to see patterns in discipline data by type of offense, action taken, person reporting, and location and time of incident. In addition, users would be able to see patterns of total incidents as well as total offenders (who may have more than one incident).
Criteria | Description |
---|
Actions | |
Change Enabled | |
Data Required | |
Systems Used | |
Expand |
---|
title | Click here for additional notes... |
---|
|
| User story | NOTES | Discipline | Need to see text of incident and action code (not just numerical code) | Use case needs a bit more detail and definition. Mainly: - What is the essential question. I'm not really sure how to word an EQ, but here is a first attempt: "What are the existing patterns of behavior (incident) and discipline (action) within districts (by school, grade level, demographic, individual student), including patterns by reporting staff member, and what changes in district/building policy and practice, including interventions, will help reduce the most persistent/frequent behavior (and discipline) issues?
- Who are the actors?
- Mainly school and district administrators. Teachers probably do not need to see aggregated data but should be able to see the discipline records of their own students (depending on district policy).
- Do all actors need the same info for discipline?
- No, see above #2. School and district administrators should be able to see all incident and action details for individual students as well as aggregated patterns. School and district administrators should be able to also see previous year patterns in order to intervene early and/or note whether a behavior pattern is new or continuing from previous years. (This kind of multi-year data can be used to provide evidence for RtI/MTSS interventions, testing for special education placement, etc.)
- Current vs. Future state
- Current: Districts that do not use SWIS are limited in what they can see in terms of detailed discipline data. Experienced SIS users may be able to run reports to get these details, but most school-level do not have this level of expertise. Future state would allow school and district staff (mainly administrators) to see patterns in discipline data by type of offense, action taken, person reporting, and location and time of incident. In addition, users would be able to see patterns of total incidents as well as total offenders (who may have more than one incident).
- Not familiar with PBIS/SWIS applications, but similar to attendance if other systems have/provide this information what would be the value add for a reporting offering?
- Answer: users prefer to have data in one place; being able to get discipline data from the SWIS application via API would enable this. Not so much for reporting but for use by school staff in terms of deciding where to allocate personnel resources, do interventions, etc.
| Discipline | Need to be able to see and filter by discipline details (location, time of day, who reported it, etc.) | Discipline | Need to be able to break these down by the categories that schools use (i.e. not state-reported and non-state-reported) | Discipline | Need to have a total offense count instead of only separate and mutually exclusive categories | Discipline | Need to break out in-school and out-of-school suspensions | Discipline | In general, it would be great to be able to sync with PBIS/SWIS applications |
|
.Description: School and district administrators should be able to see all incident and action details for individual students as well as aggregated patterns. School and district administrators should be able to also see previous year patterns in order to intervene early and/or note whether a behavior pattern is new or continuing from previous years (This kind of multi-year data can be used to provide evidence for RtI/MTSS interventions, testing for special education placement, etc.)Users prefer to have data in one place; being able to get discipline data from the SWIS application via API would enable this. Not so much for reporting but for use by school staff in terms of deciding where to allocate personnel resources, do interventions, etc.
Actor: Mainly school and district administrators. Teachers probably do not need to see aggregated data but should be able to see the discipline records of their own students (depending on district policy).
Current State: Districts that do not use SWIS are limited in what they can see in terms of detailed discipline data. Experienced SIS users may be able to run reports to get these details, but most school-level do not have this level of expertise.
Future State: Future state would allow school and district staff (mainly administrators) to see patterns in discipline data by type of offense, action taken, person reporting, and location and time of incident. In addition, users would be able to see patterns of total incidents as well as total offenders (who may have more than one incident).
Criteria | Description |
---|
Actions | Change Enabled | Data Required | Systems Used