The Behaviour management module on Toddle is a powerful tool for you to oversee and manage student behaviour incidents/pastoral care in the school. You can configure the module to suit your school’s needs and use it to monitor incidents in real-time and coordinate responses among staff members. It also facilitates seamless communication with families. Read this article to learn more.
This article will cover:
Setting up the module
Incident dashboard
Viewing incident history
Generating an incident summary using Toddle AI
Setting up the module
To begin, navigate to the ‘Behaviour management’ section from the left pane in the admin portal.
💡Please note that the name of the module, as well as the terms used for ‘Incident’, ‘Action’, and ‘Level’ may vary depending on the custom terminology configured by you in the Nomenclature settings.
Here, use the left-hand panel to configure key elements that form the foundation of the behaviour management system for your school.
These settings enable a standardized approach to incident reporting and management across your school. By tailoring these elements, you can ensure that the Behaviour Management module accurately reflects your school's values and disciplinary procedures, promoting consistency and fairness in addressing student behaviour/pastoral care. Let’s explore all of these elements.
Categories
Categories are the foundation of incident classification in Toddle. They are behaviour standards defined by your school to categorize various types of incidents. From the ‘Categories’ tab, you can create a new category by clicking on the ‘Add category’ button on the top right.
This pop-up allows you to define the details of a new incident category. You’ll need to:
Enter a unique name for the category (duplicate names are not allowed)
Select the programme(s) the category applies to (e.g., PYP, MYP, DP)
Choose a sentiment: Positive, Neutral, or Negative
Assign a colour to visually differentiate the category
Once done, click on the ‘Save’ button to save the category.
The new category will be saved in a ‘Draft’ state. You can click on the category to view its details and begin adding sub-categories.
Adding subcategories
To add sub-categories, simply click on a category and use the ‘Edit’ button on the landing page to start adding sub-categories to it.
Use the ‘New row’ option or the ‘+’ icon to add new sub-categories.
You can create up to three levels of hierarchy when setting up sub-categories within each category. These levels help organize incidents in greater detail.
Use the arrow icons to adjust the hierarchy of sub-categories as shown below.
When creating an incident, you or teachers can tag it to the deepest (last) level of sub-category within a group.
This ensures that incidents are categorized as precisely as possible.
Ideally, all sub-categories should follow the same number of hierarchy levels for consistency.
For example, if there are two sub-categories - Community service and Respecting school values - each should have the same number of further sub-levels defined. The screenshot below shows a recommended configuration.
You can also reorder the sub-categories according to your preferences by using the rearrange button and dragging them to the desired position. To delete a sub-category, simply select it using the checkbox and hit the ‘Delete’ button at the top. Make sure you ‘Save and publish’ the changes before moving on.
If you have any unpublished changes in a category, you can go inside and click on the ‘Edit’ button to view the details.
A dialog box will appear prompting you to either ‘Retain changes’ or ‘Discard changes’ made in the previous session. Click ‘Retain changes’ to continue editing and publish when ready.
Once you're done reviewing or making edits, click ‘Save and publish’ to finalize your changes. The category’s status will automatically update to ‘Published’ once all drafts are saved.
Additionally, you can edit or delete categories anytime using the three-dot menu. If you delete a category, existing incidents tagged to that category will remain unimpacted.
On clicking ‘Edit’, you will be able to rename the category, change the curriculum, and the sentiment tagged to the category. Simply click on ‘Save’ after making the desired changes.
On the category setup page, you will also find columns that indicate the total incidents mapped to a category and the status of each category:
Total incidents
This column displays the number of incidents associated with each category, specific to the academic year you're viewing. It helps you to monitor trends in student behaviour across different categories and understand which types of incidents are being reported more frequently.
2. Status column
This column shows the current configuration state of each category using three possible status indicators:
Draft: This status means the category is incomplete; it's been created, but doesn't have any subcategories added yet. Teachers can't use it to log incidents until it's completed and published.
Published: This status means the category is fully configured and available for all staff to use when logging behaviour incidents.
Unpublished changes: This status means that the category has at least one published subcategory, but there’s also a saved draft with changes that haven’t been published yet.
Levels
Levels are used to define the seriousness and importance of incidents across the three different types of sentiments. This feature allows for a nuanced approach to incident management.
Levels are linked to three sentiments: negative, neutral, and positive. Each sentiment has its own set of default levels to ensure precise alignment with that sentiment. Each group has a gear icon; click it to manage levels for that specific sentiment.
You also have the flexibility to customize these levels for your school. Use the gear icon next to any sentiment level to modify the names or number of levels in that group as needed.
In the pop-up modal, you can view the existing severity levels for the selected sentiment, along with the number of incidents currently linked to each.
You can add, modify, or delete severity levels as needed.
To add a new level, click ‘+ Add level’ at the bottom.
Enter a level name (e.g., Extreme), choose a color indicator, and click ‘Save’.
The new severity level will immediately be available for use on the incident creation page.
To delete a level, click the trash icon next to it.
The delete icon will be disabled for levels already linked to incidents in the current academic year to maintain data integrity.
You can reorder levels using the drag-and-drop handle beside each level.
The updated order will reflect wherever severity levels appear, including the dropdown on the incident creation page.
Once all edits are complete, click ‘Save’ to confirm your changes.
Once saved, any newly created level (e.g., Extreme) will appear under its respective sentiment group, with its incident count visible beside it.
Actions
Actions represent the consequences that can be applied to an incident. These actions are versatile and can be applied to incidents of any sentiment - positive, neutral or negative.
Toddle comes with a set of three predefined actions. While these cannot be deleted to maintain system integrity, they can be disabled if they don't align with your school's policies.
💡 Note that the Toddle-defined action - ‘Referral’ cannot be disabled.
In addition to the predefined actions, you have the freedom to add custom actions tailored to your school's specific needs and protocols. Simply click on the ‘Add action’ button in the top right corner.
Next, add the following details:
Name of the action
One or more sentiments associated with the action
Select account level and programme/school level role(s) who will have access to take this action
Note: Account level roles will only include users who have the account role assigned in the same curriculum as the involved student. Not all users in the organization with this role will be included.
In order to edit or delete these actions, click on the three-dot menu. Please note that deleting an action will not impact existing incidents the action has already been tagged to.
Locations
The location option allows you to specify potential places where incidents can occur within your school.
Simply click on ‘Add location’ to add a new location in the school where incidents can occur.
While this is an optional information while creating an incident, but can be incredibly useful for identifying patterns or problem areas within the school environment. optional information
Whether it's classrooms, playgrounds, or specific buildings, you can create a comprehensive list of locations relevant to your institution. You can also edit or delete a pre-existing location.
Default outcomes
To streamline the incident management process, you, as an administrator, can set up default outcomes to ensure consistency in how similar incidents are handled across the school. This involves mapping an action and defining sharing permissions for each type of incident.
All categories defined by you will be listed here. Click on any one to configure the default outcomes for its sub-categories.
On the landing page, the deepest (last) level of sub-category within each group will be displayed for the selected category.
Each sub-category is tagged to the defined severity levels.
For example, if four levels are defined, you will see four rows for the sub-category Academic excellence - each representing a unique combination of sub-category and level.
Click ‘Edit’ to begin mapping actions and defining sharing permissions for each sub-category and level combination.
Click the ‘+’ icon to add actions and assign sharing permissions to each incident sub-category.
These configured actions will automatically appear as default options whenever an incident with that sub-category is created.
The list of actions you can tag is the ones defined by you under the ‘Actions’ section.
While adding to the ‘Shared with’ column, you can configure the default set of users with whom the incident will be shared.
You can select students, families, the homeroom advisor (if any), and individual staff members to share the incident with.
Note: While you can choose to share the selected incidents with families and students, they will be visible to the students and their families only after being published.
This section displays how sharing permissions are configured for a sub-category.
For each user or user group, you can define specific access levels.
Control view or edit access separately for both the general and confidential sections of each incident.
Permissions can be customized individually for each user type in addition to the broader user group settings.
You can also click on the ‘Remove user’ option to remove a particular user’s access to the selected subcategories with just a few simple clicks.
Make sure to click on the ‘Save’ button after you have defined the default outcomes.
Follow these steps to apply default outcomes in bulk:
Select multiple sub-categories.
For example, select all sub-categories under the Commendable level and apply a common action to them.
Click on the ‘Bulk apply actions’ option to add or delete any actions tagged to the selected sub-categories.
Click on the ‘Bulk apply sharing permissions’ option to add or delete users with whom the incidents associated with select sub-categories will be shared.
Once you have assigned some actions as default outcomes, this is what your dashboard would look like:
Next, by clicking on the ‘Bulk apply sharing permissions’, configure the default set of users with whom the incident will be shared, for the selected sub-categories.
Once you have set the default sharing permissions for the selected subcategories, this is what your dashboard would look like:
Lastly, you can streamline your view of the default outcomes dashboard by filtering it by level, action taken, and sharing permissions.
Nomenclature
The nomenclature section helps you rename and customize the specific terms and labels used within your behaviour management module in accordance with your school’s policies and preferred terminology.
You can click on the ‘Edit’ option and then select your custom terms from the dropdown available next to each function. If none of the dropdown options suit your needs, you can enter your own terminology. Simply type in the custom term, and it will replace the default Toddle terminology. The changes you make here will reflect immediately across the school for all users.
Incident dashboard
The ‘Behaviour management’ card on your curriculum homepage is your gateway to managing student behaviour/pastoral incidents in the school. Clicking on this card will take you to a detailed dashboard of all incidents.
Viewing incidents
The incident dashboard provides multiple views to help you manage incidents effectively:
All incidents: This tab displays a comprehensive list of all incidents created by you, shared or referred to you.
Created by me: This tab allows you to track the incidents reported by you.
Referred to me: This tab specifically shows incidents that have been referred to you and require your attention or action.
Shared with me: This tab includes incidents that have been shared with you by other educators or administrators, helping you stay informed about incidents involving your students or those requiring possible intervention.
💡Please note that regardless of which curriculum homepage you access the Behaviour module from, the incident dashboard will show you incidents across all programmes that are available to you.
You can click on any incident to get a detailed view. Additionally, you can click on the three-dot menu from the dashboard to edit, delete, or duplicate an incident that has been created by you, referred to, or shared with you. However, this may vary as per the sharing permissions assigned to you.
Filtering and downloading incidents
Toddle offers robust filtering options to help you focus on the most relevant incidents:
Date range filter: You can now filter incidents based on a specific time range. While viewing incidents from the current academic year, you’ll see preset options such as Last 7 days, Last 30 days, Last 90 days, Last 6 months, and the entire academic year. This filter applies to the incident date and time field, helping you quickly narrow down the incidents displayed on your dashboard.
You can also use the Custom option to define a specific date range within the current academic year.
💡When viewing incidents from a past academic year, only the selected academic year and Custom options are available.
Status filter: By default, only active incidents are displayed. However, you can use the status filter to view resolved incidents as well.
Multiple filters: You can apply one or more filters to narrow down the incidents on your feed. Filter by level, grade, location, and more to find exactly what you're looking for.
Category filters: Utilize the categories pre-defined for your school to filter incidents.
You can use the column icon to show/hide and rearrange the columns according to your preferences. This allows you to prioritize the most important information for your role.
Download data from your feed for offline analysis or reporting. You can choose to download the filtered view based on your current selections or download all data for a comprehensive overview. Additionally, you can choose the exact fields you want to include in the downloaded file.
This is how the downloaded report might look:
Viewing incident history
Toddle enables you to track student incident history and analyze trends using visual graphs and detailed records.
Navigate to the student’s profile and open the ‘Behaviour management’ tab to view incident data.
The graph at the top displays all published and resolved incidents for the current academic year that you have access to (created by you, shared with you, or referred to you).
The graph shows a state-wise count of published and resolved incidents.
You can switch between academic years to view incident patterns over time.
Use the ‘Add incident’ button to log a new incident for the selected student.
Below the graph, a tabular view lists all incident records, including:
Status, category, sub-category, level, and actions taken.
The table includes a state-wise count of drafts, published, and resolved incidents.
Only incidents created by, shared with, or referred to you will appear here.
The table helps review the student’s compiled behaviour history.
To download incident data for offline analysis or reporting:
Click the Download icon shown below.
Choose to download all available data or a filtered view as needed.
This helps generate custom behaviour reports for specific focus areas.
Generating an incident summary using Toddle AI
You can generate a summary of a student's incident history using Toddle AI. This summary includes all published and resolved incidents for the selected academic year, providing a concise overview of the student's behaviour.
However, this summary is customized based on your access permissions, meaning it will only take into account incidents that were created by you or shared or referred to you. After new incidents are added, you can regenerate the summary to ensure it is up to date.
We hope that you were able to find what you were looking for. Explore other articles for more!
