Skip to main content
Recording an incident in Signal is a guided process. You write the description, and Signal’s AI helps you classify and complete the record. This page walks you through each step.
You need at least the Contributor role to create incidents.
The Add Incident button highlighted in the sidebar

​
Creating an incident step by step

​
What happens after saving

Once the incident is saved, several things happen automatically:
  • Workflows are checked — if the incident matches any of your school’s workflows, actions are triggered automatically — alerting staff, emailing parents, or restricting visibility.
  • The incident appears on dashboards — it shows up in the incident list, on the student’s timeline, and in any filtered views that match its categories or other attributes.
  • It feeds into insights — the incident contributes to your school’s safeguarding analytics and trend data.
  • The AI Assistant can reference it — the incident becomes available to the AI Assistant for future queries and research.

​
Tips for recording incidents

Be specific in your description. Include what you directly observed, heard, or were told. Use the child’s own words where possible, enclosed in quotation marks. Note the date, time, and location, and describe any visible injuries or signs of distress.
Attach evidence where possible. Photographs, body maps, letters, screenshots, or other documents strengthen the record and provide important context for anyone reviewing the incident later.
Record concerns promptly. The sooner you record a concern after it arises, the more accurate and detailed your account will be. Signal is designed to make this quick — you can create an incident in just a few minutes.
The AI suggestions are there to help, not to decide for you. Always review the suggested categories, location, and agencies to make sure they accurately reflect the concern. You have the final say on how every incident is classified.