Before you begin
Make sure the following are in place:- Your school has been set up in Signal (at minimum, incident categories have been configured).
- You have an account with at least the Contributor role.
- You are logged in.
Recording an incident
What happens next
Once your incident is saved, several things happen automatically:- Workflows are checked. If the incident matches any workflows your school has configured, the relevant staff are notified.
- It appears on dashboards. The incident shows up in the student’s timeline and on the dashboards of staff who need to see it.
- AI analysis is stored. The categories, events, and any matched policies are linked to the incident for future reference.
- AI Recommendations (optional). After submitting, you can click the Run Analysis button to generate Short Term Actions as recommendations for the incident. This step is entirely optional.
- Collaboration begins. Other staff can add comments and @mentions to discuss the concern and coordinate a response.
If you are a DSL or Deputy DSL, you can also edit the incident later to add further details, update categories, or link additional students. See Managing incidents for more.
Next steps
Now that you have recorded your first incident, explore these related topics:Recording incidents in detail
Learn about all the fields and options available when creating incidents.
Comments and @mentions
Collaborate with colleagues by adding comments and tagging staff on incidents.
Email drafts
Find out how staff can report concerns by email, creating draft incidents for you to review.
AI features
Discover how AI analyses incidents, generates summaries, and powers the AI Assistant.