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:

To begin setting up the behaviour management module, navigate to ‘Behaviour Management’.

Next, go to the gear icon on the bottom left of the screen. Here, you can 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 are the foundation of incident classification in Toddle. They are behaviour standards defined by your school to categorize various types of incidents. Create a new category by clicking on the ‘Add category’ button on the top right.

Each category can have either a neutral, positive or negative sentiment attached to it. It's important to note that two categories cannot have the same name.

You can also map incident categories to specific curriculums, ensuring that you create categories tailored to the unique needs of each curriculum in your school.

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, and change the curriculum and the sentiment tagged to the category. Simply click on ‘Save’ after making the desired changes.

You can add sub-categories to each category. 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 a maximum of three levels of hierarchy on this page when setting up sub-categories within each category. These levels are designed to help you organize incidents with great detail. Use the arrow icons highlighted below to adjust the hierarchy of sub-categories. When creating an incident, you or teachers can tag it to the deepest (or last) level of sub-category within a group. This ensures that incidents are categorized as precisely as possible.

Ideally, all subcategories should be configured to the same number of hierarchy levels. For example, If there are 2 sub-categories - ‘Community service’ and ‘Respecting school values’, then each of these should have the same number of further sub-categories defined. Below is an example of such a 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.

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.

These levels are linked to different sentiments: negative, neutral, and positive. Each sentiment has its own set of levels to ensure precise alignment with that sentiment.

You have the ability to customize the name of each level, allowing you to align the system with your school's specific terminology and policies. Simply click on the edit icon to customize the levels according to your preferences.

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 on the top right corner.

After naming the action, you can add the sentiment the action will be associated with. Next, choose who will be allowed to take a specific action. This ensures that the right staff members are empowered to respond appropriately to different types of incidents.

Select ‘Who can apply this action’ to determine who the action can be performed by - the school staff or just the school admin.

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.

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.

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.

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 (or last) level of sub-category within each group will be listed, for the selected category. Each sub-category will be tagged to the levels defined. For example, you might see four rows for the sub-category ‘Academic excellence’ because there are four levels defined, with each row representing a unique combination of sub-category and level. Click on ‘Edit’ to start mapping an action and defining sharing permissions for each unique combination of sub-category and level.

By clicking on the ‘+’ icon shown below, you can add actions and assign sharing permissions to each incident subcategory. These actions will then be automatically applied as default options whenever an incident with that sub-category is created.

The list of actions you can tag are 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, 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 is how the sharing permissions for a sub-category may look like. For each user/user group, you can define the access levels. You can control the view or edit access for general or confidential section of each incident independently for each type of user, apart from the user group permissions.

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.

You can also select more than one sub-categories and bulk apply actions or sharing permissions. For instance, you can select all sub-categories at ‘Commendable’ level and bulk apply an action to them. By clicking on the ‘Bulk apply actions’ option, you can add or delete any action tagged to the selected sub-categories.

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 them by level, action taken, and sharing permissions.

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.

The ‘Behaviour management’ card on the admin portal 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.

The incident dashboard provides multiple views to help you manage incidents effectively:

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. Please note that you can only edit and delete the incidents you created or those where you have been granted edit rights.

Toddle offers robust filtering options to help you focus on the most relevant incidents:

Toddle allows you to track student incident history and analyze trends with visual graphs. Simply go to a student's profile and click on 'Behaviour management' tab. Here, you will find a graph showing all published and resolved incidents of the student for the current academic year that you have access to, including those created by you, shared with you, or referred to you. The graph displays a state-wise count of published and resolved incidents. You can switch to other academic years to view the incident pattern for previous years. Additionally, you can use the ‘Add incident’ button to log incidents for the selected student from here.

Below the graph, is a tabular view of student’s incident records, including their status, category, sub-category, level, and the actions taken. The incident records show a state-wise count (including drafts, published, and resolved), providing a clear overview of the incident statuses. This table would only show the details of incidents that have been created by, shared with, or referred to you.

The table allows you to review their compiled behaviour history. To download a student's data for offline analysis or reporting, click the icon highlighted below. When ready, you can download either all the available data or filtered view to include in the file. This feature allows you to generate tailored reports focusing on particular aspects of the student's behaviour during school.

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!