Overview
This is the creation process in setting up a Check-In/Check-Out (CICO) tool for a student, designed to monitor target behaviors. Users must define the behaviors for tracking, either from the behavior bank or by creating new behaviors. Additionally, the user can interact with action buttons to print data sheets, record or view data, and manage the status of the tool.
Figma
Feature
Project 223101: MTSS | Check In/Check Out
User Story
As a user, I need to create a Check-In/Check-Out tool for a student by selecting or entering target behaviors, so that I can effectively track and manage the student's progress on the defined behaviors.
UI Description
Page Heading: "Create Check-In, Check-Out Tool"
Student Name Display: The student's first and last name is shown below the heading to ensure the user knows which student they are configuring the tool for.
Step Indicator:
Current Step displays as dark grey in the indicator. The indicator displays the other step as light grey.
Behaviors pill container (current step)
Data Settings pill container
Behaviors Screen:
Users must enter at least one target behavior and has the option to enter up to three target behaviors.
Display dropdown menu input fields with labels
Target Behavior #1
Required Field
Target Behavior #2 (Optional)
Optional Field
Target Behavior #3 (Optional)
Optional Field
Dropdown menu input field values:
Search bar at the top of the dropdown menu to search for behaviors
For each target behavior, a dropdown allows the user to select from the existing behavior bank or choose "Other" to enter a new behavior.
Behaviors included in the Student Behavior Bank and Admin Settings Behavior Bank
Custom input field displays as text input field with ‘Other’ as placeholder text that the user types over.
Behavior descriptions are text fields where users can describe the behavior being tracked.
Required fields that display to the right of each ‘Target Behavior’ dropdown menu selection
Labels for text area fields: ‘Behavior Description’
Support multiple lines of text.
Continue Button:
User selects ‘Continue’ button to proceed to the next screen of the CICO tool creation process.
Validation Warning Errors display on input field labels and containers if the user does not enter details in the required fields.
Action Buttons:
Print Data Sheets: Opens a modal to print either blank or pre-filled data sheets.
Inactive until CICO tool is creation is complete and tool is in Active Status
Record Data: Takes the user to the Data Express CICO page to enter student data.
Inactive until CICO tool is creation is complete and tool is in Active Status
View Data: Navigates user to Data Express > View Data and displays the recorded data for the student.
Inactive until CICO tool is creation is complete and tool is in Active Status
Delete (Displays instead of Change Status button during tool creation, just like Behavior Tracking setup): Deletes the CICO tool and returns the user to the Student Dashboard > Behavior Support > CICO screen
Change Status (Displays when user reaches ‘Done’ screen or when viewing an ‘Active’ CICO tool): Allows the user to change the status of the CICO tool
Archive
Delete
Make Active (Only if tool is in Archived Status)
Discussion Panel:
User will be able to add team members or admin to the discussion and send discussion messages. (Utilize Existing Discussion Panel functionality)
User Interaction and Validation Notes
Behavior Setup:
The user must define at least one behavior for the CICO tool to progress. If less than one target behavior and behavior description is set.
Selecting ‘Other’ in the Target Behavior dropdown menu allows the user to enter a new behavior. This new behavior is automatically added to the student’s behavior bank once the form is submitted.
Data Entry Validation:
All required fields must be completed for the user to proceed.
If the user attempts to continue without completing the required fields, validation error messages will prompt the completion of the missing fields.
Target Behavior Validation: Input field label turns red, container is red, helper text below field: ‘Behavior Required’.
Behavior Description Validation: Input field label turns red, container is red, helper text below field: ‘Description Required’
Action Buttons:
Print Data Sheets: The ‘Print Data Sheets’ button will remain inactive until the user reaches the ‘Done’ screen in the create CICO process. The modal will ask for the number of copies.
User selected between:
A blank template data sheet template
Generating a CICO tool data sheet with the details input by the user: Target Behaviors, Time Period Labels, Number Range, Dates, Page Numbers
Record Data and View Data: These buttons are inactive until the tool is successfully completed and Active.
Change Status: The button is initially labeled "Delete" during tool creation. After creation and the CICO tool is Active, the button becomes "Change Status," and provides the option to Archive or Delete the tool.
Archive: Archive will archive the tool. The user has the option to make it active again in the Student Dashboard > Behavior Support > Check-In, Check-Out screen.
Delete: Delete will display a warning validation message to the user.
Heading: Warning
Text Description: Are you sure you want to delete this Check-In, Check-Out tool? This action cannot be undone. Do you wish to delete?
Cancel button: Cancels the action and returns user to the create screen they were viewing.
Delete: Confirms the Delete action. The tool is deleted and the user navigates to the Student Dashboard > Behavior Support > Check-In, Check-Out screen.
Make Active: If a CICO is in an ‘Archived’ status and the user selects ‘Change Status’, the user will have the option ‘Make Active’ to make the CICO tool Active for the student. This is the same functionality as Behavior Tracking.
Workflow Description
The user navigates to the "Create Check-In/Check-Out Tool" screen, sees the student’s name, and starts entering behaviors.
The user must define at least one target behavior and its description. If the user selects "Other," they can input a new behavior, which gets added to the student’s behavior bank.
Once behaviors are entered, the user can proceed by clicking the "Continue" button.
If any required fields are missing, the user is alerted and prompted to complete them before continuing.