Checklist | Create Behavior | Data Tracking | MTSS Suite

UI:

User sees navigation tab and selects Data Settings.

• User sees timeline.

• To learn more about measurement types, User clicks on or hovers over information icon.

• User clicks on Checklist to select it.

• To Save and exit the modal, user clicks Save and exit button.

• To Continue to next slide, User clicks on Continue button.

• To go back to the previous slide, user clicks on Go back button.

Business Rules:

• Users with permission to Edit Settings (Behavior Support) and access to Behavior Support OR MTSS Interventions (all tools or Behavior Tracking enabled) will be able to create Behaviors to track.

• If user has saved the behavior tracking once, it is a draft and shows the draft tag at the top until reaching the done screen.

• Clicking on the timeline labels or circles takes the User to that section for the collection method they selected.

  • Users can move between sections if they have selected a measurement tool

  • Completing the section turns the circle blue with checkmark

  • If the user does not complete a section, then the circle will not be filled-in in blue with checkmark.

  • If the user leaves a section incomplete, they will not be able to track behaviors.

• If the Users clicks on Checklist, the remaining timeline items follow the parameters for Checklist. (See Data Collection: Checklist in Figma)

Buttons:

• Clicking Go Back button takes the User to Behavior Definition screen.

• Clicking Continue saves the work to this screen and takes the User to Baseline for Checklist

• Clicking Save and exit saves the work as a Draft and closes the modal.

UI:

• User sees timeline.

UI: Select No

• To select No, the User clicks on down arrow in selection field and selects No or leaves it as the default state.

• To Save and Record baseline in Data Express, user clicks on Record baseline button.

• To go back to previous screen (Select data type), User selects Go Back button.

Select Yes:

• To select Yes, the User clicks on down arrow in selection field and selects Yes.

• To select start and end dates for baseline data collection, User selects start and end dates from the calendar.

• To record the average % of opportunities per day, the User selects from drop down or types in a number.

• To return to previous screen, User clicks on Save & Go Back button.

• To advance to the next section, User clicks on Save & Continue Button.

Business Rules:

• If User has selected a tool, then Select tool will be filled in with blue and white checkmark in timeline.

• If User has selected a tool, then Record Baseline is outlined in blue in timeline.

• Default setting for Baseline selection is No.

• Selecting Save & Go Back takes User to previous screen. (Select measurement tool)

• If User Selects No, then Record baseline button is shown. (See Frequency Section 2 Baseline for further explanation)

  • If the User selects Checklist, they are taken to Checklist in data express.

  • Selecting Go Back button takes User to Select Type screen.

• If User Selects Yes for baseline data:

  • Calendar appears when User clicks on Start and End date.

    • Selections appear as MM/DD/YYYY in start and end fields.

  • Average field appears.

    • Drop down contains increments of 5 in descending order from 100 to 0 or User can type in any number 0-100

    • User click selects from drop down or custom types a number from 0-100.

  • Selecting Save & Continue button takes Users to Set Goal section.

  • Selecting Save & Go Back button takes User to Select Measurement Tool screen.

UI:

• User sees timeline and success message.

• User sees completed summary view.

Business Rules:

• If User completes Baseline in Data express and returns to Create Behavior Tracking, the Timeline shows completion of Recorded Baseline with filled-in blue circle and white checkmark and success message.

• If the User completed checklist in Data express, they see summary view.

UI:

• User sees timeline.

Set Goal:

• To edit the goal the User selects choices from drop downs

• To edit the Customized goal Statement the User clicks inside the Goal definition text box and enters additional information before and/or after the hard coded sentence.

• To go back to previous slide, User clicks on Go back button.

• To continue to track objectives, User clicks on Continue.

• To save and exit the modal, the user clicks on Save and exit.

Business Rules: (copy of old specs)

• Users must select a goal.

• We will show a default mastery criteria based on the account settings.

• The format of the mastery criteria is dependent on the data collection type

• The goal sentence is based on the data collection type. It will be formatted as:

  • Increase: STUDENT NAME will increase BEHAVIOR NAME to INSERT MASTERY CRITERIA.

  • Decrease: STUDENT NAME will decrease BEHAVIOR NAME to INSERT MASTERY CRITERIA.

  • Checklist only has Increase.

• If the user updates the mastery criteria, the hard-coded goal definition sentence will update as well.

• The mastery criteria will populate a hard-coded sentence in the goal definition box. This sentence cannot be edited. However, custom text may be entered before and/or after this sentence.

Timeline:

• Timeline has Select Tool and Record Baseline colored in blue with white check mark.

• Set Goal in Timeline is outlined in blue.

Buttons:

• Go Back takes user to Baseline selection for Duration.

• Continue takes user to Track behaviors for Duration.

• Save and exits, saves the behavior tracking as a draft and exits the modal.

UI:

• User sees timeline.

Select No

• If the User does not want to track objectives, the User selects No from drop down or leaves it as the default.

• To go back to previous slide, User clicks on Go back button.

• To continue to track objectives, User clicks on Continue.

• To save and exit the modal, the user clicks on Save and exit.

Select Yes

• To track objectives, the User selects Yes.

Selecting Yes shows the goal the User set in Goal Selection section.

Selecting Yes opens 3 objectives fields.

• To select mastery criteria for each of the objectives, the User selects from the drop down fields.

• To customize objective definition, the User clicks inside text field and types.

• To remove an objective, the user clicks on the x next to the objective.

• To add a new objective, the User clicks on +Add new objective.

Business Rules:

• Timeline has Select Tool, Record Baseline, Set Goal colored in blue with white check mark and Track objectives outlined in blue.

• Track objectives field contains:

  • No

  • Yes

  • Tracking objectives is optional.

• Default selection is No.

• Selecting Save & Go Back button goes to Goal Selection screen for Checklist.

• Selecting Save & Continue goes to Set Self-Monitoring Screen for Checklist.

Select Yes to track objectives:

• 3 objectives will appear as the default.

• If the User clicks the X next to an objective, the objective is removed.

• If the User clicks on +Add new objective, a field for a new objective will appear.

• For each objective, the user must enter a mastery criteria.

• If a User does not create mastery criteria, then the objective cannot be used for behavior tracking.

• The objective definition box will include a hard-coded sentence based on the mastery criteria. The user may not change this sentence, but may add custom text before and/or after this sentence.

• If objectives are selected, the user must include at least 1 objective.

• Checklist only has increase behavior as an option.

• Increase Behavior

  • The mastery criteria must increase for each objective. Meaning, the criteria for objective 1 cannot be higher than the criteria for objective 2.

  • The mastery criteria for the last objective must be equal to the mastery criteria for the goal.

  • By default, each objective criteria will be evenly distributed in an increasing fashion from the first objective to the last. For example, if my goal is to increase time on task to 30 minutes & I have included 3 objectives, my first objective will be to increase to 10 minutes, my second objective will be to increase to 20 minutes, & my 3rd objective will be to increase to 30 minutes.

  • This logic will continue & the mastery criteria will update as I add and remove objectives.

  • Once I begin editing the mastery criteria for any objective, the system will no longer update the criteria for any other objective.

• Decrease Behavior

  • The mastery criteria must decrease for each objective. Meaning, the criteria for objective 1 cannot be lower than the criteria for objective 2.

  • The mastery criteria for the last objective must be equal to the mastery criteria for the goal.

  • By default, each objective criteria will be evenly distributed in increments of 10 in a decreasing fashion from the first objective to the last. For example, if my goal is to decrease tantrums to 0 minutes & I have included 3 objectives, my first objective will be to decrease to 20 minutes, my second objective will be to decrease to 10 minutes, & my 3rd objective will be to decrease to 0 minutes.

  • This logic will continue & the mastery criteria will update as I add and remove objectives.

  • Once I begin editing the mastery criteria for any objective, the system will no longer update the criteria for any other objective.

• The format of the mastery criteria is dependent on the data collection type

• The objective definition sentence is based on the data collection type. It will be formatted as:

  • Increase: STUDENT NAME will increase BEHAVIOR NAME to INSERT MASTERY CRITERIA.

  • Decrease: STUDENT NAME will decrease BEHAVIOR NAME to INSERT MASTERY CRITERIA.

• If the user updates the mastery criteria, the hard-coded objective definition sentence will update as well.

• If User clicks on +Add new objective, an additional objective section is added.

• User can have up to 5 objectives.

• Additional objectives follow same rules for increase and decrease behavior.

UI:

• User sees Done screen with Success message.

Business Rules:

• Timeline includes blue fill-in with white checkmarks for all items.

• If the User has successfully completed all the previous for checklist, then they will see the Success message.

• See Section 6 Done from Frequency for functionality of buttons.

Active Status (See: View/Edit Behavior Tracking)

• If the User has completed all parts of creating Behavior tracking and has recorded data, Print data sheets, Record Data, View Data, Change status are active buttons.

  • Print Data sheets button

    • If User set up behavior tracking for Checklist with Objectives and selects Print Data sheets, they are taken to Print Data sheets.

    • If User sets up behavior tracking for Checklist without Objectives and selects Print Data sheets, they are taken to Print Data Sheets.

  • Record Data button

    • If User sets up behavior tracking forChecklist and selects Record Data button, they are taken to Data express.

• View Data button takes user to view data for checklist.