Incident Tracking

Design

• Options
  • Students (default)
  • Team Members
  • Totals
  • List

Business Rules

• Students will be the default view

Export/Print

• We will export and print exactly what is shown on the screen

Design

• This is a graph showing the number of unique students with incidents reported
• Option for:
  • Cumulative
  • Non-Cumulative
• We will show a key based on the filter selections

Business Rules

• Shows the number of unique students with incidents reported within the date range
• By default, the data will be displayed cumulatively

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are running a Non-Cumulative District report, this is what we will export and print.

Design

• We will show one line on the graph
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• Shows the number of unique students in all child accounts the user has access to with incidents reported within the date range.
• This will show if skills, sel, or behavior have been purchased for students in at least 1 child account the user has access to
• Any student with incidents reported at any point within our date range will be counted. If a student had incidents reported during Month 2 of the selected date range but not Month 3, this student will still be counted on the report.
• The Key will show District
• Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique students with incidents reported at all child accounts the user has access to.

Design

• We will show a line on the graph for each region selected
• We will show a line on the graph for the district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least 1 of the selected region's child accounts the user has access to
• Any student with incidents reported at any point within our date range will be counted. If a student had incidents reported during Month 2 of the selected date range but not Month 3, this student will still be counted 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, assuming both Regions have child accounts with the components allocated
• For each region line, we will show the number of unique students in all of the region's child accounts the user has access to with incidents reported within the date range.
• The district total line will show the number of unique students in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each region selected and District Total
• Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique students with incidents reported at all of the selected regions' child accounts the user has access to.

Design

• We will show a line on the graph for each building selected
• We will show a line on the graph for the region or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least 1 of the selected buildings
• Any student with incidents reported at any point within our date range will be counted. If a student had incidents reported during Month 2 of the selected date range but not Month 3, this student will still be counted 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, assuming both Buildings have child accounts with the components allocated
• For each building line, we will show the number of unique students in the building with incidents reported within the date range.
• If the buildings selected belong to the same Region, we will show the Region Total Line on the graph. If the buildings selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  • The region total line will show the number of unique students in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique students in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each building selected and District or Region Total
• Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique students with incidents reported for each building selected.

Design

• We will show a line on the graph for each role selected
• We will show a line on the graph for the building, region, or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains team members with the selected roles
• Any student with incidents reported at any point within our date range will be counted. If a student had incidents reported during Month 2 of the selected date range but not Month 3, this student will still be counted on the report.
• For each role line, we will show the number of unique students assigned to users with that role in all buildings the user has access to with incidents reported within the date range.
• If the roles selected have team members that belong to the same Building, we will show the Building Line on the graph. If the roles selected have team members that belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the roles selected have team members that belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  • The building total line will show the number of unique students in the building who have incidents reported within the date range.
  • The region total line will show the number of unique students in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique students in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each role selected and District, Region, or Building Total
• Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique students with incidents reported for each role selected.

Design

• We will show a line on the graph for each team member selected
• We will show a line on the graph for the building, region, or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains the selected team members
• Any student with incidents reported at any point within our date range will be counted. If a student had incidents reported during Month 2 of the selected date range but not Month 3, this student will still be counted on the report.
• For each team member line, we will show the number of unique students assigned to that team member in all buildings the user has access to with incidents reported within the date range.
• If the team members selected belong to the same Building, we will show the Building Line on the graph. If the team members selected belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the team members selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  
  • The building total line will show the number of unique students in the building who have incidents reported within the date range.
  • The region total line will show the number of unique students in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique students in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each team member selected and District, Region, or Building Total
• Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique students with incidents reported for each team member selected.

Design

• There will be two lines on the graph
  • All selected students will be represented by one line on the graph
  • A district total, region total, or building total line will show on the graph as well
• Options for Cumulative vs Non-Cumulative
• We will show the names of the students selected below the graph.

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains the selected students
• Any student with incidents reported at any point within our date range will be counted. If a student had incidents reported during Month 2 of the selected date range but not Month 3, this student will still be counted on the report.
• For the students line, we will show the number of unique students out of those selected with incidents reported within the date range.
• If the students selected belong to the same Building, we will show the Building Line on the graph. If the students selected belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the students selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  
  • The building total line will show the number of unique students in the building who have incidents reported within the date range.
  • The region total line will show the number of unique students in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique students in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show Students* and District, Region, or Building Total
• Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Student A has incidents reported in January & February and Student B has incidents reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique students with incidents reported out of those selected.

Design

• This is a graph showing the number of unique team members reporting incidents
• Option for:
  • Cumulative
  • Non-Cumulative
• We will show a key based on the filter selections

Business Rule

• Shows the number of unique team members who reported incidents within the date range
• By default, the data will be displayed cumulatively

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are running a Non-Cumulative District report, this is what we will export and print.

Design

• We will show one line on the graph
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• Shows the number of unique team members in all child accounts the user has access to who reported incidents within the date range.
• This will show if skills, sel, or behavior have been purchased for students in at least 1 child account the user has access to
• Any team member reporting incidents at any point within our date range will be counted. If a team member had incidents reported during Month 2 of the selected date range but not Month 3, this team member will still be counted on the report.
• The Key will show District
• Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique team members reporting incidents at all child accounts the user has access to.

Design

• We will show a line on the graph for each region selected
• We will show a line on the graph for the district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules.

• This will show if skills, sel, or behavior have been purchased for students in at least 1 child account the user has access to
• Any team member reporting incidents at any point within our date range will be counted. If a team member had incidents reported during Month 2 of the selected date range but not Month 3, this team member will still be counted on the report.
• If a team member belongs to Region 1 during Month 1 of our date range and Region 2 during Month 2 of our date range, the team member will be calculated under Region 1 for Month 1 and Region 2 for Month 2, assuming both Regions have child accounts with the components allocated
• For each region line, we will show the number of unique team members in all of the region's child accounts the user has access to with incidents reported within the date range.
• The district total line will show the number of unique team members in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each region selected and District Total
• Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique team members reporting incidents at all of the selected regions' child accounts the user has access to.

Design

• We will show a line on the graph for each building selected
• We will show a line on the graph for the region or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules.

• This will show if skills, sel, or behavior have been purchased for students in at least 1 of the selected buildings
• Any team member reporting incidents at any point within our date range will be counted. If a team member had incidents reported during Month 2 of the selected date range but not Month 3, this team member will still be counted on the report.
• If a team member belongs to Building 1 during Month 1 of our date range and Building 2 during Month 2 of our date range, the team member will be calculated under Building 1 for Month 1 and Building 2 for Month 2, assuming both Buildings have the components allocated
• For each building line, we will show the number of unique team members in the building with incidents reported within the date range.
• If the buildings selected belong to the same Region, we will show the Region Total Line on the graph. If the buildings selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  • The region total line will show the number of unique team members in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique team members in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each building selected and District or Region Total
• Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique team members reporting incidents at each of the selected buildings.

Design

• We will show a line on the graph for each building selected
• We will show a line on the graph for the building, region, or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules.

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains team members with the selected roles
• Any team member reporting incidents at any point within our date range will be counted. If a team member had incidents reported during Month 2 of the selected date range but not Month 3, this team member will still be counted on the report.
• For each role line, we will show the number of unique team members assigned to that role in all accounts the user has access to with incidents reported within the date range.
• If the roles selected have team members that belong to the same Building, we will show the Building Line on the graph. If the roles selected have team members that belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the roles selected have team members that belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph
  • The building total line will show the number of unique team members in the building who have reported incidents within the date range.
  • The region total line will show the number of unique team members in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique team members in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each role selected and District, Region, or Building Total
• Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique team members reporting incidents assigned to each selected role.

Design

• There will be two lines on the graph
  • All selected team members will be represented by one line on the graph
  • A district total, region total, or building total line will show on the graph as well
• Options for Cumulative vs Non-Cumulative
• We will show the names of the team members selected below the graph.

Business Rules.

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains the team members selected
• Any team member reporting incidents at any point within our date range will be counted. If a team member had incidents reported during Month 2 of the selected date range but not Month 3, this team member will still be counted on the report.
• For the team member line, we will show the number of unique team members out of those selected with incidents reported within the date range.
• If the team members selected belong to the same Building, we will show the Building Line on the graph. If the team members selected belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the team members selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  
  • The building total line will show the number of unique team members in the building who have reported incidents within the date range.
  • The region total line will show the number of unique team members in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique team members in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show Team Members* and District, Region, or Building Total
• Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique team members out of those selected who have reported incidents within the date range.

Design

• We will show a line on the graph for each student selected
• We will show a line on the graph for the building, region, or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules.

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains the students selected
• Any team member reporting incidents at any point within our date range will be counted. If a team member had incidents reported during Month 2 of the selected date range but not Month 3, this team member will still be counted on the report.
• For each student line, we will show the number of unique team members assigned to the selected student with incidents reported within the date range.
• If the students selected belong to the same Building, we will show the Building Line on the graph. If the students selected belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the students selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  
  • The building total line will show the number of unique team members in the building who have reported incidents within the date range.
  • The region total line will show the number of unique team members in all of the region's child accounts the user has access to who have incidents reported within the date range.
  • The district total line will show the number of unique team members in all of the district's child accounts the user has access to who have incidents reported within the date range.
• The Key will show the name of each selected student and District, Region, or Building Total
• Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Member A reported incidents  in January & February and Team Member B reported incidents in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all unique team members assigned to each selected student who have reported incidents within the date range.

Design

• This is a graph showing the total number of incidents recorded
• Option for:
  • Cumulative
  • Non-Cumulative
• We will show a key based on the filter selections

Business Rules

Business Rules

• Shows the number of incidents reported within the date range
• By default, the data will be displayed cumulatively

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are running a Non-Cumulative District report, this is what we will export and print.

Design

• We will show one line on the graph
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• Shows the number of incidents reported for students in all child accounts the user has access to within the date range.
• This will show if skills, sel, or behavior have been purchased for students in at least 1 child account the user has access to
• The Key will show District
• Cumulative
  • If Student A has 1 incident reported in January & February and Student B has 1 incident reported in February and March, we would show
    •  January 1, February 3, March 4
• Non-Cumulative
  • If Student A has 1 incident reported in January & February and Student B has 1 incident reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all incidents reported at all child accounts the user has access to within the date range.

Design

• We will show a line on the graph for each region selected
• We will show a line on the graph for the district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least 1 child account the user has access to
• For each region line, we will show the number of incidents reported in all of the region's child accounts the user has access to within the date range.
• The district total line will show the number of incidents reported in all of the district's child accounts the user has access to within the date range.
• The Key will show the name of each region selected and District Total
• Cumulative
  • If Student A has 1 incident reported in January & February and Student B has 1 incident reported in February and March, we would show
    •  January 1, February 3, March 4
• Non-Cumulative
  • If Student A has 1 incident reported in January & February and Student B has 1 incident reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all incidents reported at all child accounts the user has access to for each region selected within the date range.

Design

• We will show a line on the graph for each building selected
• We will show a line on the graph for the region or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least 1 of the selected buildings
• For each building line, we will show the number of incidents reported in the building within the date range.
• If the buildings selected belong to the same Region, we will show the Region Total Line on the graph. If the buildings selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  • The region total line will show the number of incidents reported in all of the region's child accounts the user has access to within the date range.
  • The district total line will show the number of incidents reported in all of the district's child accounts the user has access to within the date range.
• The Key will show the name of each building selected and District or Region Total
• Cumulative
  • If Student A has 1 incident reported in January & February and Student B has 1 incident reported in February and March, we would show
    •  January 1, February 3, March 4
• Non-Cumulative
  • If Student A has 1 incident reported in January & February and Student B has 1 incident reported in February and March, we would show
    
    • January 1, February 2, March 1

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all incidents reported at each selected building within the date range.

Design

• We will show a line on the graph for each role selected
• We will show a line on the graph for the building, region, or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains team members with the selected roles
• For each role line, we will show the number of incidents reported by users with the selected role in all accounts the user has access to within the date range.
• If the roles selected have team members that belong to the same Building, we will show the Building Line on the graph. If the roles selected have team members that belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the roles selected have team members that belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  • The building total line will show the number of incidents reported in the building within the date range.
  • The region total line will show the number of incidents reported in all of the region's child accounts the user has access to within the date range.
  • The district total line will show the number of incidents reported in all of the district's child accounts the user has access to within the date range.
• The Key will show the name of each role selected and District, Region, or Building Total
• Cumulative
  • If Team Members assigned to Role A have 1 incident reported in January & February and none in March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Members assigned to Role A have 1 incident reported in January & February and none in March, we would show
    
    • January 1, February 1, March 0

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all incidents reported by users with each selected role within the date range.

Design

• We will show a line on the graph for each team member selected
• We will show a line on the graph for the building, region, or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains the selected team members
• For each team member line, we will show the number of incidents reported by the selected team member in all accounts the user has access to within the date range.
• If the team members selected belong to the same Building, we will show the Building Line on the graph. If the team members selected belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the team members selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  
  • The building total line will show the number of incidents reported in the building within the date range.
  • The region total line will show the number of incidents reported in all of the region's child accounts the user has access to within the date range.
  • The district total line will show the number of incidents reported in all of the district's child accounts the user has access to within the date range.
• The Key will show the name of each team member selected and District, Region, or Building Total
• Cumulative
  • If Team Member A has 1 reported incident in January & February and none in March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Team Member A has 1 reported incident in January & February and none in March, we would show
    
    • January 1, February 1, March 0

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all incidents reported by each selected team member within the date range.

Design

• We will show a line on the graph for each student selected
• We will show a line on the graph for the building, region, or district total
• Option for:
  • Cumulative
  • Non-Cumulative

Business Rules

• This will show if skills, sel, or behavior have been purchased for students in at least one of the accounts the user has access to that contains the selected students
• For each student line, we will show the number of incidents reported for the selected student within the date range.
• If the students selected belong to the same Building, we will show the Building Line on the graph. If the students selected belong to more than 1 building but the same Region, we will show the Region Total Line on the graph. If the students selected belong to more than 1 region or if regions do not exist, we will show the District Total Line on the graph.
  
  • The building total line will show the number of incidents reported in the building within the date range.
  • The region total line will show the number of incidents reported in all of the region's child accounts the user has access to within the date range.
  • The district total line will show the number of incidents reported in all of the district's child accounts the user has access to within the date range.
• The Key will show the name of each student selected and District, Region, or Building Total
• Cumulative
  • If Student A has 1 incident reported in January & February and none in March, we would show
    •  January 1, February 2, March 2
• Non-Cumulative
  • If Student A has 1 incident reported in January & February and none in March, we would show
    
    • January 1, February 1, March 0

Export/Print

• We will export and print exactly what is shown on screen. Meaning, if we are looking at a cumulative graph, we will export and print the cumulative view of all incidents reported for each selected student within the date range.

Design

Report options are:

• Incidents
• Actions
• Students
• Team Members

Business Rules

• Default is Incidents

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Incidents Report, this is the view we will export and print

Design

• This is a list view showing:
  • Incident Name
  • Occurrences
  • Students
• There will be a sort feature
• Tabs for each region/building/role/team member/student selected

Business Rules

• 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Students, this is the view we will export and print.

Design

• All incidents will display in one report
• This is a list view showing:
  • Incident Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• We will show all incidents reported in all child accounts the user has access to within the date range
  • Each incident recorded for the district will appear. For example, if 20 incidents of hitting occurred for 15 students, we would show Hitting-20-15
• 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
  • 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.

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Students, this is the view we will export and print.

Design

• There will be a separate tab for each region selected.
• This is a list view showing:
  • Incident Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each region tab, we will show all incidents reported in all of the region's child accounts the user has access to 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
  • 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 incidents for the student will be calculated under Region 1 for Month 1 and Region 2 for Month 2

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Region A tab and filter by Students, this is the view we will export and print.

Design

• There will be a separate tab for each building selected.
• This is a list view showing:
  • Incident Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each building tab, we will show all incidents reported in all that building 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
  • 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Building A tab and filter by Students, this is the view we will export and print.

Design

• There will be a separate tab for each role selected.
• This is a list view showing:
  • Incident Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each role tab, we will show all incidents reported by users assigned to that role in all accounts the user has access to 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
  • 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.

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Role A tab and filter by Students, this is the view we will export and print.

Design

• There will be a separate tab for each team member selected.
• This is a list view showing:
  • Incident Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each team member tab, we will show all incidents reported by that team member 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
  • 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.

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Team Member A tab and filter by Students, this is the view we will export and print.

Design

• There will be a separate tab for each student selected.
• This is a list view showing:
  • Incident Name
  • Occurrences
• There will be a sort feature

Business Rules

• For each student tab, we will show all incidents reported for that student 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Student A tab and filter by Occurrences, this is the view we will export and print.

Design

• This is a list view showing:
  • Action Name
  • Occurrences
  • Students
• There will be a sort feature
• Tabs for each region/building/role/team member/student selected

Business Rules

• 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Occurrences, this is the view we will export and print.

Design

• All actions will display in one report
• This is a list view showing:
  • Action Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• We will show all actions reported in all child accounts the user has access to 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Occurrences, this is the view we will export and print.

Design

• Each region selected will have a separate tab
• This is a list view showing:
  • Action Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each region tab, we will show all actions reported in all of the region's child accounts the user has access to 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
  • 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 incidents for the student will be calculated under Region 1 for Month 1 and Region 2 for Month 2

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Region A tab and filter by Occurrences, this is the view we will export and print.

Design

• Each building selected will have a separate tab
• This is a list view showing:
  • Action Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each building tab, we will show all actions reported in the building 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
  • 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 incidents for the student will be calculated under Building 1 for Month 1 and Building 2 for Month 2

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Building A tab and filter by Occurrences, this is the view we will export and print.

Design

• Each role selected will have a separate tab
• This is a list view showing:
  • Action Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each role tab, we will show all actions reported by users with the selected role in all accounts the user has access to 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Role A tab and filter by Occurrences, this is the view we will export and print.

Design

• Each team member selected will have a separate tab
• This is a list view showing:
  • Action Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each team member tab, we will show all actions reported by that team member in all accounts the user has access to 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Team Member A tab and filter by Occurrences, this is the view we will export and print.

Design

• Each student selected will have a separate tab
• This is a list view showing:
  • Action Name
  • Occurrences
• There will be a sort feature

Business Rules

• For each student tab, we will show all actions reported for that student 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Student A tab and filter by Occurrences, this is the view we will export and print.

• This is a list view showing:
  • Team Member Name
  • Occurrences
  • Students
• There will be a sort feature
• Tabs for each region/building/student selected

• We will show all team members who have reported incidents during the selected date range 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Occurrences, this is the view we will export and print.

Design

• All team members reporting incidents will appear on one report
• This is a list view showing:
  • Team Member Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• We will show all team members in the district and all of the district's child accounts the user has access to who have reported incidents during the selected date range 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
  • If a team member was active during Month 2 of the selected date range but not Month 3, this team member will still show on the report.
• 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Occurrences, this is the view we will export and print.

Design

• Each region selected will have a separate tab
• This is a list view showing:
  • Team Member Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each region tab, we will show all team members in the region and all of the region's child accounts the user has access to who have reported incidents during the selected date range on this list
• If a team member belongs to Region 1 during Month 1 of our date range and Region 2 during Month 2 of our date range, the team member will be calculated under Region 1 for Month 1 and Region 2 for Month 2
• If a team member belongs to more than 1 region (multi-account team member), the team member will show under each region she belongs to
• 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
  • If a team member was active during Month 2 of the selected date range but not Month 3, this team member will still show on the report.
• 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Region A tab and filter by Occurrences, this is the view we will export and print.

Design

• Each building selected will have a separate tab
• This is a list view showing:
  • Team Member Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each building tab, we will show all team members in the building who have reported incidents during the selected date range on this list
• If a team member belongs to Building 1 during Month 1 of our date range and Building 2 during Month 2 of our date range, the team member will be calculated under Building 1 for Month 1 and Building 2 for Month 2
• If a team member belongs to more than 1 building (multi-account team member), the team member will show under each building she belongs to
• 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
  • If a team member was active during Month 2 of the selected date range but not Month 3, this team member will still show on the report.
• 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Building A tab and filter by Occurrences, this is the view we will export and print.

Design

• Each role selected will have a separate tab
• This is a list view showing:
  • Team Member Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• For each role tab, we will show all team members assigned to that role in all accounts the user has access to who have reported incidents during the selected date range on this list
• Any team member assigned to a selected role at any point within our date range will show.
• 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
  • If a team member was active during Month 2 of the selected date range but not Month 3, this team member will still show on the report.
• 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Role A tab and filter by Occurrences, this is the view we will export and print.

Design

• All selected team members will appear on the same report
• This is a list view showing:
  • Team Member Name
  • Occurrences
  • Students
• There will be a sort feature

Business Rules

• We will show all team members selected
• 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
  • If a team member was active during Month 2 of the selected date range but not Month 3, this team member will still show on the report.
• Occurrences will list the number of times the team member reported an incident within the date range
  • If the team member has not recorded any incidents, we will show 0
• 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
  • If the team member has not recorded any incidents, we will show 0

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Occurrences, this is the view we will export and print.

Design

• Each student selected will have a separate tab
• This is a list view showing:
  • Team Member Name
  • Occurrences
• There will be a sort feature

Business Rules

• For each student tab, we will show all team members assigned to that student who have recorded incidents for that student within the date range
• Users will be able to sort by team member name (alphabetically by last name) or occurrences
• By default we will sort by occurrences
• Team Member name will list the name of the team member
  • If a team member was active during Month 2 of the selected date range but not Month 3, this team member will still show on the report.
• Occurrences will list the number of times the team member reported an incident within the date range

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we are on the Student A tab and filter by Occurrences, this is the view we will export and print.

• This is a list view showing:
  • Student Name
  • Occurrences
  • Student's Team
• There will be a sort feature
• Tabs for each region/building/role/team member selected

• 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

Export/Print

• We will export and print exactly what is shown on the screen. Meaning, if we filter by Occurrences, this is the view we will export and print.

Design

• This is a list view showing:
  • Student Name
  • Occurrences
  • Student's Team
• There will be a sort feature