Top Layer
Need to show totalDesign
- Line graph showing # of unique students with incidents tracked for the past 90
- days
- Option to view cumulative vs non-cumulative
Second Layer
- Total Incidents - This will display the total # of incidents tracked. This will be the default.
- Team Members - This will display the # of unique team members tracking incidents.
- Students - This will display the # of unique students with incidents tracked.
- data
Business Rules
- The line graph should show number of unique students with incident data tracked
- Default view will be cumulative
- Should be calculated same as for logins
Second Layer
Design
- Three views
- Students
- Team Members
- Totals
- Option for:
- Cumulative
- Non-Cumulative
- Filter by
- District
- Displays one line on the graph
- Region
- A menu of regions will appear
- Search bar
- Regions will be listed alphabetically
- Each region will be represented by a different colored line
- District
- on the graph
- A district total line will show on the graph as well
- There will be a key by the graph
- Building
- There will be a menu of all buildings
- Search bar in the menu
- Buildings will be listed alphabetically
- Each building will be represented by a different colored line
- on the graph
- There will be a
- district/region total line on the graph
- There will be a key by the graph
- Team Member
- A menu of team members will appear
- Search bar
- Team Members will be listed alphabetically by last name
- Each team member will be represented by a different colored line
- on the graph
- A district/region/building total line will show on the graph as well
- There will be a key below the graph
- Student
- A menu of students will appear
- Search bar
- Students will be listed alphabetically by last name
- Each student will be represented by a different colored line on the graph
- A district/region/building total line will show on the graph
- There will be a key
- by the graph
- Total Incidents would show total # of incidents for the team members selected. Each team member will be represented by a different colored line.
- Team Members will not be an option here
- Students would show total # of unique students with incidents tracked by the team members selected. Each team member will be represented by a different colored line.
- Able to select one or multiple students
- Able to select all students - this will be the default
- Only those students assigned to a team member will appear in the list
- Each student will be represented by a different colored line on the graph
- There will be a key below the graph
- If Incident Type was selected, only those incident types will be accounted for on the graph. If building has been selected, only students from those buildings will appear on the graph & in the menu selection. If Team Members were selected, only students assigned to those team members will appear on the graph and in the menu selection.
- Report Types:
- Total Incidents would show total # of incidents for the students selected. Each student will be represented by a different colored line.
- Team Members would show total # of unique team members recording incidents for the students selected. Each student will be represented by a different colored line.
- Students would not be an option here
- Week
- Month
- Year
Third Layer
- Incident View (DEFAULT)
- Need to show total # of incidents recorded in date range specified
- Need to show total # of each incident type recorded in date range specified
- Need to show which students engaged in each incident type
- Actions View
- Need to show total # of actions recorded in date range specified
- Need to show total # of each action type recorded in date range specified
- Need to show which students had each action type recorded
- Team Members View
- Incidents Recorded:
- Need to show list team members recording incidents during the specified date range
- Need to also show for each team member recording: # of incidents recorded, # of students incident data was recorded for, & date of last incident.
- Team members should be ranked in order of # of incidents recorded, with the team member recording the most incidents at the top of the list. If two or more team members have recorded the same # of incidents, the team member with the most recent date of recording should appear first. If two or more team members have the same recording date, the team members in question should be listed alphabetically by last name.
- Add a message stating "Check it out! The following Team Members have recorded incidents from INSERT START DATE to INSERT END DATE. Please take a moment to review the data."
- No Incidents Recorded
- Need to show list of team members who did not record incidents during the specified date range
- Need to show for teach team members: last date incident data was recorded for (If no incidents were ever recorded, the field will read "No Incidents Recorded") and date of last login (If the team member has never logged in, the field will read "Has Not Logged In").
- Team members should be ranked in terms of last recording date, with the team member with the most recent recording date appearing first. If two or more team members have the same last recording date, the team members in question should be ranked in terms of last login date, with the team member logging in most recently appearing first. If two or more team members have the same last login date, the should be listed alphabetically by last name.
- Add a message stating "It looks like the following team members have not recorded incidents from INSERT START DATE to INSERT END DATE."
- Incidents Recorded:
- Students View
- Incidents Recorded
- Need to show list of students with incidents recorded during the specified date range
- Need to also show # of incidents recorded, team members recording incidents, and date of last incident recorded.
- Students should be ranked in order of # of incidents recorded, with the student with the most incidents at the top of the list. If two or more students have the same # of incidents recorded, the student with the most recent incident date should appear first. If two or more students have the same last incident date, the students in question should be listed alphabetically by last name.
- Clicking on a student's name should take you to the individual student incident report.
- Add a message stating "Check it out! The following students have engaged in incidents from INSERT START DATE to INSERT END DATE. Please take a moment to review the data."
- No Incidents Recorded
- Need to show list of students with no incidents recorded during the specified date range
- For each student, also show last date of incidents recorded (If no incidents were ever recorded, the field will read "No Incidents Recorded") and team members assigned to the student.
- Students should be ranked in terms of last incident recorded date, with the student with the most recent date appearing first. If two or more students have the same date, the students should be listed alphabetically by last name.
- Add a message stating "It looks like the following students have not engaged in any incidents from INSERT START DATE to INSERT END DATE."
- Incidents Recorded
- Able to select one or multiple buildings.
- Able to select all buildings - this will be the default.
- Only buildings with access to the Skills, Behavior, or SEL Platforms will show in the list. If a building does not have access to one of these platforms, it will not appear in the list.
- Only those incident types selected will be accounted for on the report.
- Report Types:
- Incidents View will show total # of incidents recorded for the types selected
- Actions View will show the total # of actions recorded for the incident types selected
- Team Members View will show the team members who recorded/did not record the incident types selected
- Students View will show the students who engaged/did not engage in the incident types selected
- Able to select one or multiple buildings.
- Able to select all buildings - this will be the default.
- Only buildings with access to the Skills, Behavior, or SEL Platforms will show in the list. If a building does not have access to one of these platforms, it will not appear in the list.
- Only those buildings selected will be account for on the report.
- Report Types:
- Incidents View will show the # of incidents recorded for the buildings selected
- Actions View will show the # of actions taken for the buildings selected
- Team Members View will show the team members recording/not recording incidents for the buildings selected
- Students View will show the students with incidents recorded/not recorded for the buildings selected
- Able to select one or multiple team members
- Able to select all team members - this will be the default.
- Only team members with access to students will appear in the list. If a team member is not linked to at least one student, they will not appear.
- Only those team members selected will be accounted for on the report.
- Report Types:
- Incidents View will show the incidents recorded for the team members selected
- Actions View will show the actions recorded for the team members selected
- Team Members view will show the report for only the team members selected. If the team members selected did not record any incidents, the view will default to no incidents recorded.
- Students View will show students with incidents recorded/not recorded by the team members selected. If the team members selected did not record any incidents, the view will default to no incidents recorded.
Business Rules
- Three views
- Students will display the number of unique students with incidents reported within the date range (default)
- Team Members will display the number of team members reporting incidents within the date range
- Totals will display the total number of incidents reported within the date range
- Cumulative will be default view
- District View
- If a student was active during Month 2 of the selected date range but not Month 3, this student will still show on the report.
- Region View
- Any region active during the specified date range will appear in the menu
- Able to select from 1-10 regions
- If regions have not been set up for an account, regions will not appear as a filter option
- If a student was active during Month 2 of the selected date range but not Month 3, this student will still show on the report.
- If a student belongs to Region 1 during Month 1 of our date range and Region 2 during Month 2 of our date range, the student will be calculated under Region 1 for Month 1 and Region 2 for Month 2
- If a student belongs to more than one region (multi-account user), this student will be calculated under each region they belong to.
- Building View
- Any building active during the specified date range will appear in the menu
- If regions were previously selected, only show buildings within the selected regions
- Able to select from 1-10 buildings
- If buildings from only 1 region are selected, show the region total line on the graph. If buildings from multiple regions are selected, show the district total line on the graph.
- If a student was active during Month 2 of the selected date range but not Month 3, this student will still show on the report.
- If a student belongs to Building 1 during Month 1 of our date range and Building 2 during Month 2 of our date range, the student will be calculated under Building 1 for Month 1 and Building 2 for Month 2
- If a student belongs to more than one building (multi-account user), this student will be calculated under each building they belong to
- Team Member View
- Any team member active during the specified date range will appear in the menu
- If regions or buildings were previously selected, only show team members within the selected regions/buildings.
- Able to select 1-10 team members.
- If team members from only 1 building are selected, show the building total line on the graph. If team members from only 1 region are selected, show the region total line on the graph. If team members from multiple regions are selected, show the district total line on the graph.
- If a student was active during Month 2 of the selected date range but not Month 3, this student will still show on the report.
- Student View
- Any student active during the specified date range will appear in the menu
- If regions/buildings/team members were previously selected, only show students assigned to the selected regions/buildings/team members.
- Able to select 1-10 students
- If students from only 1 building are selected, show the building total line on the graph. If students from more than 1 building but only 1 region are selected, show the region total line on the graph. If students from more than 1 region are selected, show the district total line on the graph.
- If a student was active during Month 2 of the selected date range but not Month 3, this student will still show on the report.
- District View
Third Layer
Design
Incidents Report
- This is a list view showing:
- Incident Name
- Occurrences
- Students
- There will be a sort feature
- Tabs for each region/building/team member selected
- Filter by:
- District
- Region
- Building
- Team Member
- Student
Business Rules
Incidents Report
- We will show all incidents reported within the date range
- Users will be able to sort by incident name (alphabetically), occurrences, or students.
- By default we will sort by incident name
- Incident name will list the name of the incident
- Occurrences will list the number of times that incident occurred
- Students will list the number of students that incident was reported for.
- Clicking this number will display the students for whom the incident was reported
- Clicking on a student's name will take you to that student's incident report
Actions Report
- This is a list view showing:
- Action Name
- Occurrences
- Students
- There will be a sort feature
- Tabs for each region/building/team member selected
- Filter by:
- District
- Region
- Building
- Team Member
- Student
Actions Report
- We will show all actions reported within the date range
- Users will be able to sort by action name (alphabetically), occurrences, or students.
- By default we will sort by action name
- Action name will list the name of the action
- Occurrences will list the number of times that action was reported
- Students will list the number of students that action was reported for.
- Clicking this number will display the students for whom the action was reported
- Clicking on a student's name will take you to that student's action report
Team Member Report
- This is a list view showing:
- Team Member Name
- Occurrences
- Students
- There will be a sort feature
- Tabs for each region/building/team member selected
- Filter by:
- District
- Region
- Building
- Team Member
- Student
Team Member Report
- We will show all team members with access to incident reporting on this list
- Users will be able to sort by team member name (alphabetically by last name), occurrences, or students.
- By default we will sort by occurrences
- Team Member name will list the name of the team member
- Occurrences will list the number of times the team member reported an incident within the date range
- Students will list the number of students the team member reported incidents for within the date range
- Clicking this number will display the students for whom the incident was reported
- Clicking on a student's name will take you to that student's incident report
Student Report
- This is a list view showing:
- Student Name
- Occurrences
- Student's Team
- There will be a sort feature
- Tabs for each region/building/team member selected
- Filter by:
- District
- Region
- Building
- Team Member
- Student
Student Report
- This will be the default view
- We will show all students
- Users will be able to sort by student name (alphabetically by last name), occurrences, or student's team.
- By default we will sort by occurrences
- Student name will list the name of the student
- Clicking on a student's name will take you to that student's incident report
- Occurrences will list the number of times the student had an incident reported within the date range
- Student's Team will list the number of team members assigned to the student
- Clicking this number will display the team members and roles assigned to the student
RULES
- Role 7 will have access to all incident information across the entire account (all sub-accounts & parent account)
- Role 6 will have access to all incident information across the sub-accounts they are linked to
- Role 5 will have access to all incident information for the sub-account they are linked to
- Custom roles may have access to incident information if admin reports were selected during customization. These roles will have access to all incident information for the sub-accounts they are linked to.
- No other roles will have access to this report.
- Accounts with Skills, Behavior, or SEL Platforms allocated will have access to this report. If an account (or sub-account) does not have access to either the skills, behavior, or SEL platform, this report will not appear.
- All sub-accounts with the aforementioned platforms allocated will appear in this report. If a sub-account does not have one of these platforms allocated, they will not appear in the report.
- All users assigned to the skills, behavior, or sel platform will appear in this report. If a user does not have one of the aforementioned platforms assigned, they will not appear in the report. RITA - Let's discuss. Thinking down the road to MIS integration. Not sure if this will work until account setup is complete though.
- Only students assigned to a classroom or a user will appear in the report. If a student has been added to the platform, but has not been assigned to either a user or a classroom, the student will be excluded from the report