Creating and managing staff incidents requires the Owner, DSL, or Deputy DSL role.
Creating a staff incident
1
Start a new staff incident
Click Add Staff Incident from the quick action in the sidebar, or navigate to Staff Incidents and select the Add Staff Incident button.
2
Select main staff member(s)
Choose the primary staff member or members the concern is about. At least one main staff member is required.
3
Add linked staff (optional)
If other staff members are connected to the concern but are not the primary subject, add them as linked staff.
4
Add linked students (optional)
If any students are connected to the concern, link them to the incident.
5
Set the date and time
Enter the date and time the concern arose. This may differ from the date you are recording the incident.
6
Write the description
Describe the concern in the rich text editor. You can use @mentions to tag relevant colleagues — staff who are named in the incident are automatically excluded from the mention list to protect confidentiality.
7
Select alert recipients
Choose who should be notified about this incident. Only staff with the Owner, DSL, or Deputy DSL role will appear as options.
8
Attach documents (optional)
Upload any supporting files — photos, letters, reports, or other evidence.
9
Submit for analysis
Click Next. Signal’s AI analyses the description and suggests appropriate categories.
10
Select categories and location
Review the AI-suggested categories and select the ones that apply. Choose the location where the incident occurred.
11
Save the incident
Click Save to create the completed incident record.

Viewing and filtering staff incidents
The staff incidents list shows all incidents you have access to. Remember that any incidents naming you are automatically hidden due to self-exclusion. You can filter the list by:- Date range — focus on a specific time period
- Categories — show only incidents of a particular type
- Locations — filter by where the incident occurred
- Staff members — find incidents involving a specific person

Filters can be combined. For example, you can view all “Allegations” incidents from the last term that occurred on the school premises.
Editing a staff incident
You can edit a staff incident after it has been created to add information, correct details, or update categories.1
Open the incident
Click an incident in the staff incidents list to open it. Staff incidents open in a side sheet titled “Incident Details” rather than a full page.
2
Start editing
On desktop, click the pencil icon (its tooltip reads “Edit Incident”). On mobile, open the menu and choose Edit.
3
Make your changes
Update any fields as needed — description, categories, location, linked staff, or linked students.
4
Save
Click Save to apply your changes.
Comments and collaboration
Comments allow Owners, DSLs, and Deputy DSLs to share updates, discuss next steps, and build a documented trail of actions taken on a staff incident.Adding a comment
1
Open the incident
Navigate to the staff incident you want to comment on.
2
Open the comments section
Comments are in a collapsible section within the incident side sheet. Use the Show / Hide / Add toggle to expand it.
3
Write your comment
Type your comment in the text field. You can @mention other Owners, DSLs, or Deputy DSLs to bring the incident to their attention.
4
Send
Click Send to post your comment.
Deleting a comment
You can delete a comment if you are the person who created it, or if you hold a privileged role (DSL, Deputy DSL, or Owner).
Key differences from student incidents
Staff incidents work similarly to student incidents in many ways, but there are some important differences:No agencies field
No agencies field
Staff incidents do not include an agencies field. External organisations involved in staff matters are typically referenced in the description or comments instead.
No AI recommendations panel
No AI recommendations panel
Unlike student incidents, staff incidents do not display an AI recommendations panel. AI is used to suggest categories during creation, but ongoing recommendations are not shown.
Restricted visibility
Restricted visibility
Student incidents are visible to staff with the Contributor role and above. Staff incidents are visible only to Owners, DSLs, and Deputy DSLs, and self-exclusion applies.
