Custom Behaviour Incident Workflows

You can create custom workflows for certain behaviour types, in addition to the default workflows based on severity levels. When a behavioural incident is logged, Arbor will check if the behaviour has a custom workflow assigned to it, and if so, trigger that workflow instead.

Custom Behaviour Workflows give you the ability to:

• Customisation - set up your escalations to better align with your unique policies and procedures
• Flexibility - more granular control over how incidents are managed
• Efficiency - reduce manual effort, streamlining the incident management process

As this is a brand new feature, we want to make sure it's as useful as it can be to our schools. If you have any feedback, please submit it here: Custom Behaviour Workflows

Please note that Custom Behaviour Workflows are included in all Arbor Perform packages and our newest Comms package. All other Arbor packages won’t have this feature by default. Want to upgrade or find out what package you’re on? Just get in contact with your Account Manager.

Permissions

You'll need either the Behaviour: Behaviour Policy or School: Action: Behaviour: Administer permission to set up and edit your behaviour setup. If you don't have the permission, you'll need to ask your admin team to give you permission using these instructions.

Setting up a custom workflow

Go to Students > Behaviour > Setup. Go to the Incidents tab and select Automatic Incident Workflows. 

Click on the Behaviour Types tab, and click +Add.

In the slide over, give the custom workflow a name and link it to one or more behaviour types.

Please note that you cannot link two workflows to one behaviour type. Selecting a behaviour type that already has a linked workflow will overwrite the linked workflow with this one.

In this example, adding a new workflow has removed the behaviour type from the old workflow.

Once you set up a new workflow, you'll then be taken to the overview for the workflow.

Defining what actions and escalations happen in your workflow

Here you can define the steps of your workflow, just like for standard incident workflows.

With automatic escalations you can automatically create an incident of a higher level after a certain number of incidents at a lower level - for example if you have a 'three strikes' policy. You can read more about escalations here: Taking a look at an example escalation workflow

However unlike standard incident workflows (where you select the level to escalate to), custom behaviour workflows will escalate a certain number of levels. So in the example below, -1 behaviour types will escalate to -2. This means that if you want a -1 behaviour type and -2 behaviour type to both escalate to -3, you would need to set up two custom workflows.

Top Tips:

• You can only escalate the severity level of the behaviour, not from one behaviour type to another.
• Escalations cannot go beyond level 5. So for example level -4 incidents set to escalate 2 levels will only escalate to -5.

You can choose to notify primary guardians or staff of incidents or detentions. Top Tip: You can set up custom email or SMS templates to use with each workflow: Set up different email or SMS messages for incidents and detention severities

You can also choose to:

• Assign to a member of staff (Automatic assignee)
• Assign automatic detentions or allow staff to give detentions
• Auto close
• Add/deduct points
• Email staff when incidents are assigned to them
• Assign students to internal exclusions

Removing behaviour types from a workflow

To remove behaviour types from a workflow:

1. go to Students > Behaviour > Setup
2. go to the Incidents tab and select Automatic Incident Workflows
3. click on the Behaviour Types tab
4. select the custom workflow
5. click on the Linked behaviour types field, edit the types then click Save.

Please note that this will not re-run any workflows for incidents already logged.

Deleting a workflow

To delete the workflow, click the Delete Workflow button.

Please note that this will not cancel any workflows for incidents already logged.