Behavior | Cut Scores | Settings | MTSS Report
- Felicia Mizgorski
- Tara Chiatovich
- Mary DelPiano
We need to have a way for the highest level admin to make Tier selections for Behavior. There are two options: Behavior Incidents is integrated over from another entity or the client is using Rethink Incidents.
Behavior Tab-Client without Incident’s Component
User Story:
As a district level administrator who is not using RethinkEd’s Incident reporting, I need to define the tier level criteria for behavior incidents so that cut offs can be used to create the three tier levels.
UI:
The user will see tabs for ELA, Math, Behavior, SEL, and Attendance
The user clicks the Behavior tab.
Acceptance Criteria:
Mapping: See Powerschool Integration
Under Account Setup > Account Settings, we will add a section for MTSS Dashboard.
We will default to the ELA Tab being selected.
Given a client has not included one or more of the content areas in Jrich settings, then we will not include that tab for setting selections and default the landing to the next content area which they do have.
Dashboard
Given I am an admin user at an account where MTSS Dashboard has been allocated, I will see the Dashboard Settings in Account Setup
Given I am an admin user at an account where MTSS Dashboard has not been allocated, I will not see the Dashboard Settings in Account Setup
Given I am a user who clicks MTSS Dashboard, I will see tabs for ELA, Math, Behavior, SEL, and Attendance.
Given I am a user at an account where SEL/Wellness/Life Skills and Wellness has been allocated, I will see the SEL/Wellness/Life Skills and Wellness tab.
The title of this tab will change based on the state.
Given I am a user at an account where SEL/Wellness/Life Skills and Wellness has NOT been allocated, I will NOT see the SEL/Wellness/Life Skills and Wellness tab.
User Story:
As a district level administrator who is not using RethinkEd’s Incident reporting, I need to customize the tier level criteria for behavior incidents so that our district’s policies for incident tracking are upheld.
UI:
To make the screens editable, user clicks on the Edit button contained within that box.
To change the ranges for the number of behavior incidents, user clicks in desired box and makes a selection.
Acceptance Criteria:
Mapping: For more information please see Behavior Mapping | Powerschool
Incident ranges for all tier levels must be both mutually exclusive and all inclusive.
All students will fit into a tier group with the selections made.
The default setting are Tier 1: 0 to 1, Tier 2: 2-5, Tier 3: 6
Given user has not edited the settings, then the default settings are applied.
Given no edits have been made to settings and the first update has come through integration, then the default settings are applied.
Given use has edited prior to the first updates from integration, then the user’s edits are applied.
The settings applied either through default or custom edited are in place for the full school year.
How Set Up Works:
Users must enter range selections in order: Tier 1, Tier 2, Tier 3
If user clicks inside a box to set the ranges (low or high) in Tier 2 before setting the ranges in Tier 1, then they will see an error message.
Error message reads: Please set the incident ranges in order beginning with Tier 1.
The low end of Tier 1 is set to 0 and not editable by the user.
The high end of Tier 1 is set by the user and that determines what the low end of Tier 2 will be.
Given a user has set the high end of Tier 1 to X, then the low end of Tier 2 will be set to X+1 for the user.
The high end entry for Tier 1 is a number greater than 0 and less than 10.
Given user selects Save and all selections are not mutually exclusive and also all inclusive, then user sees error message: Please adjust you selections so that all all ranges of incident frequencies fit into a Tier category.
The high end of Tier 2 is set by the user and that determines the low end of Tier 3.
Given the user sets the high end of Tier 2 to 5, then the low end of Tier 3 is automatically set to 6.
There is no high end for tier 3.
Behavior Tab-Client with Incidents Component
User Story:
As a district level administrator who is using RethinkEd’s Incident reporting, I need to define the tier level criteria for behavior incidents so that cut offs can be used to create the three tier levels.
UI:
The user will see tabs for ELA, Math, Behavior, SEL, and Attendance
The user clicks the Behavior tab.
Acceptance Criteria:
Given client has our Incident Component and also Powerschool integration, we will use our Incidents Component for Behavior and Powerschool integration for Attendance.
Under Account Setup > Account Settings, we will add a section for MTSS Dashboard.
We will default to the ELA Tab being selected.
Given a client has not included one or more of the content areas in Jrich settings, then we will not include that tab for setting selections and default the landing to the next content area which they do have.
Dashboard
Given I am an admin user at an account where MTSS Dashboard has been allocated, I will see the Dashboard Settings in Account Setup
Given I am an admin user at an account where MTSS Dashboard has not been allocated, I will not see the Dashboard Settings in Account Setup
Given I am a user who clicks MTSS Dashboard, I will see tabs for ELA, Math, Behavior, SEL, and Attendance.
Given I am a user at an account where SEL/Wellness/Life Skills and Wellness has been allocated, I will see the SEL/Wellness/Life Skills and Wellness tab.
The title of this tab will change based on the state.
Given I am a user at an account where SEL/Wellness/Life Skills and Wellness has NOT been allocated, I will NOT see the SEL/Wellness/Life Skills and Wellness tab.
User Story:
As a district level administrator who is using RethinkEd’s Incident reporting, I need to customize the tier level criteria for behavior incidents so that our district’s policies for incident tracking are upheld.
UI:
To make the screens editable, user clicks on the Edit button contained within that box.
To change the ranges for the number of behavior incidents for Major and Minor, user clicks in desired box and makes a selection.
To save changes, user clicks save and sees the Admin who edited and the date they edited the settings.
Incident Settings
To get major/minor and de-escalation strategies information included for MTSS Dashboard, user must turn on the features in Incident Settings.
Acceptance Criteria:
We use the data collected in the Incident Report to count the number of Major and Minor Incidents.
We will use the status: Approved to count the incidents.
Given an incident report has been Approved, then it will count.
Given an incident report is in the Draft, Pending Approval, ChangesAreRequested, and/or Denied Status, then it will not be counted.
Given user has Incident Component and has both category and de-escalation checked, then we will show the information in the Student view. (See: Behavior | Student View | MTSS Dashboard)
Incident ranges for all tier levels must be both mutually exclusive and all inclusive.
All students will fit into a tier group with the selections made.
The default setting are Tier 1: 0 to 1 Major Incidents or 0 to 3 Minor incidents, Tier 2: 2-5 Major Incidents or 4 to 10 Minor Incidents, Tier 3: 6 or more Major Incidents or 11 or more Minor Incidents.
Given user has not edited the settings, then the default settings are applied.
Given no edits have been made to settings and the first update has come through our system, then the default settings are applied.
Given use has edited prior to the first updates from our system, then the user’s edits are applied.
The settings applied either through default or custom edited are in place for the full school year.
How Set Up Works:
Users must enter range selections in order: Tier 1, Tier 2, Tier 3
If user clicks inside a box to set the ranges (low or high) in Tier 2 before setting the ranges in Tier 1, then they will see an error message.
Error message reads: Please set the incident ranges in order beginning with Tier 1.
The low end of Tier 1 is set to 0 for both Major and Minor Incidents and not editable by the user.
The high end of Tier 1 is set by the user and that determines what the low end of Tier 2 will be for both major and Minor.
Given a user has set the high end of Tier 1 to X for Major Incidents, then the low end of Tier 2 for Major incidents will be set to X+1 for the user.
Given a user has set the high end of Tier 1 to Y for Minor Incidents, then the low end of Tier 2 for Minor incidents will be set to Y+1 for the user.
The high end of Tier 2 for major and minor incidents is set by the user and that determines the low end of Tier 3 for major and minor incidents.
Given the user sets the high end of Tier 2 to 5 for Major incidents, then the low end of Tier 3 for Major incidents is automatically set to 6.
Given the user sets the high end of Tier 2 to 10 for minor incidents, then the low end of Tier 3 for minor incidents is automatically set to 11.
There is no high end for tier 3 for either major or minor incidents. .
Admin Name and Date
If the user clicks Save after making edits to the settings, then they will see the Edit, ADMIN name, Date, in the bottom right corner of the edited section.
Return Student to Tier 1--Still working on this
User Story
As a district level administrator who is using either RethinkEd’s Incident reporting or an integrated account, I need to select a time period for when a student can be returned to Tier 1 so that they will not remain as a Tier 2 or Tier 3 student when no further incident reports have been recorded.
UI
To select a period of weeks that must pass before a student can be returned to Tier 1, the user clicks on the drop down and selects a number.
Acceptance Criteria
Drop Down
Contains the numbers 1 through 36
Minimum = 1
Maximum= 36
Maximum Length = 2
Drop down is a single select.
Default is 9.
How it works:
The option to custom enter a selection expires when the first incident is reported.
Given highest level admin user has not custom entered a selection prior to the first incident being reported, then the default value of 9 weeks is applied.
The selection entered (custom or default) is applied to the full school year.
All students are reset to Tier 1 for the beginning of the next school year--consulting with Tracey and waiting on a response.
See: Behavior | Student View | MTSS Dashboard for the appearance and application of this functionality.
See also all areas of the graph for Behavior beginning with Overview | MTSS Dashboard Report
Given a student is returned to Tier 1 for behavior, they are moved to the count and graphic representation for Tier 1 and no longer counted in Tier 2 or Tier 3 where they were previously located.