How to report on actions taken after a behaviour incident

This article explains how to create a custom report in Arbor to track actions taken after a behavioral incident is logged. It details the necessary permissions, the specific field to include for filtering actions like detentions, and provides steps for both creating a new report and editing an existing one.

You can find more detailed guidance on the step-by-step process of creating a custom report here. To see more ways you can analyse behaviour in Arbor, take a look at these articles: Behaviour analysis

Permissions

To create and edit reports from the Custom Report Writer page, you'll need the permission School: General Admin: Export Data. If you don't have this permission, ask your admin team to assign it to you.

Reporting on actions taken after a behaviour incident is logged

When creating a report about behaviour in Custom Report Writer, there is a specific field you can add to pull through data about the actions taken after a behavioural incident is logged. This will allow users to filter behavioural incidents based on specific actions taken, such as detentions or other disciplinary measures.

When creating a new report

You can follow along with the steps in this article to set up your custom report for the first time. The report topic will need to be set to Behavioural Incidents.

Step 3 of that article describes how to add columns to your report - in this case you would need to add the column Actions Taken Category.

You can then proceed with creating the rest of the report.

When adding to an existing report

To add another column to your behaviour report, you can open up your report and click the Edit button in the top-left.

Scrolling down to the Report Columns section and clicking + Add Another will allow you to pop in the column name Actions Taken Category.