Setting Up Automated & Progressive Consequences

Set up consequences for your students' Praise and Guidance Behaviors. Automatically notify your admin staff and parents when behaviors are assigned. Automate creating Consequences based on the number of Behaviors received.

Permission Level: Owner | District Manager | Manger

This article is based on the COMING SOON January 12, 2024 update to Minga. 

1. Set up Behaviors

Before you start, ensure you have set up your Praise and/or Guidance behaviors.

2. Set Up Consequences

The consequences you create can be assigned manually or triggered automatically in many different ways. For example you may create a Lunch Detention and After School Detention. These can later be set up to be triggered by different automations i.e. step 3 of your Tardy Policy Automations or step 5 of your Cell Phone Policy Automations. You don't need to set up separate detention consequences for each behavior that may trigger the consequence.

Step by Step:

  1. Go to the Behavior Manager from the main navigation
  2. Click Behaviors tab
  3. Click Create > Consequence
  4. Enter Consequence Name and Description
  5. Select Praise or Guidance category
  6. Toggle on Enable due date if the consequence is time bound
  7. Choose to toggle on ability to Add Notes to Consequence (only relevant for manually assigned consequences)
  8. Toggle on Parent Notifications if you want notifications to be sent automatically for that behavior
  9. If you wish, customize the email and SMS notifications that are sent to parents. This allows you to add relevant information, ensuring enhanced communication and clarity. (Customized emails to parents can be created for both behaviors and consequences) 

Screenshot 2023-12-27 at 1.46.15 PM

Screenshot 2023-12-28 at 10.37.27 AM

3. Set Up Automation Group

The Automation Group creates the triggers that assign each consequence to a student based on a set threshold of behaviors being counted for that particular student. You can set up a progressive framework of consequences that will assign more severe consequences as more behaviors are counted, i.e. a Tardy Policy

Step by Step:

  1. Go to the Behavior Manager from the main navigation
  2. Click Behaviors tab
  3. Click Automations in the top left corner and then select Create and select Automation Group

Screenshot 2023-12-27 at 1.50.28 PM

Screenshot 2023-12-27 at 1.50.35 PM

4. Enter Automation Group Name (Optional: You can enter an Internal Description)

5. Choose a Behavior that will trigger the Automation. Note: only ACTIVE behaviors will populate in the list

6. Optional: Toggle on the Reset Counter. This will cause the count to reset automatically at a selected time

7. Select from drop-down the frequency you would like the numbers to reset: Daily, Weekly, Monthly or Custom. Select on which date of the week you would like the counter to reset

*Minga’s best practice is to select “Custom” in the drop-down and input the dates of the semester. Then select 12:01 am for the reset as it will not interfere with School operating hours

Screenshot 2023-12-27 at 2.06.05 PM

Add Automation Triggers

Step by Step:
  1. Select the Automation Group and ensure it is toggled to Active
  2. On Add automation on the right side of the screen, name the first step of the behavior automation
  3. Set Behavior Threshold - How many times the behavior has to occur for the automation to be enacted
  4. Assign Behavior to be automated from the drop-down menu 
  5. Optional: Toggle on "Send note to student" to automatically send a note to the student when the automation is triggered. If you wish, admins can also customize the note to contain relevant information, ensuring enhanced communication and clarity
  6. If applicable, select the number of days to complete the consequence
  7. If the automation is for two steps of the consequence, toggle Repeat automation on
  8. Select the automation to repeat after the desired amount of behavior thresholds have been met and end after the desired occurrences
  9. Click Add
  10. Repeat for further steps in the automation sequence
Screenshot 2023-12-27 at 2.27.07 PM