Setting up your school requires the Owner or DSL role. If you do not have one of these roles, ask your school’s Signal administrator for help.
Setup checklist
Year groups define your school’s academic structure — Reception through to Year 13. Each year group contains one or more classes (such as 7A, 7B, or 8Red).
Students are assigned to a year group and class, and these are used for filtering throughout Signal — in incident lists, insights, alert rules, and student searches.
If you plan to connect your MIS (such as Arbor), year groups, classes, and students can be synced automatically. You may want to set up your MIS integration first to save time.
Categories are how you classify safeguarding concerns. Common examples include Physical, Emotional, Neglect, Sexual, Online Safety, Attendance, and Behaviour.
Student incidents and staff incidents have separate category sets, so you can tailor each one independently.
Go to Settings > Categories to create your categories. For more detail, see Setting up categories.
Locations represent the places where incidents might occur — classrooms, playgrounds, corridors, off-site locations, and so on.
Go to Settings > Locations to add your school’s locations. For more detail, see Setting up locations.
Agencies are the external organisations your school works with on safeguarding cases — social services, police, CAMHS, school nursing teams, and others.
Go to Settings > Agencies to add your agency list. For more detail, see Setting up agencies.
Add your colleagues to Signal and assign each person a role. Signal uses a hierarchical role system:
Go to Settings > Staff to invite team members and assign roles. For more detail, see Managing staff.
Upload your school’s safeguarding policy documents so that Signal’s AI can automatically match relevant policies to incidents.
Go to Settings > Policies to upload your documents. For more detail, see Adding policies.
Workflows automatically take action when incidents matching certain criteria are logged — alerting staff, emailing parents, or restricting visibility. For example, you might set up a workflow to alert all DSLs whenever a Physical incident is recorded for a student in the Children in Care group.
Go to Settings > Workflows to create your first workflow. For more detail, see Workflows.
If your school uses Arbor, you can connect it to Signal to automatically sync student, staff, contact, and attendance data. This saves significant manual data entry.
Go to Settings > Integrations to connect your MIS. For a detailed walkthrough, see MIS Integration.
Tips for getting started quickly
- Start with categories and staff. These are the minimum requirements for recording incidents. You can add locations, agencies, and policies later.
- Connect your MIS early. If you use Arbor, setting up the integration first will automatically populate your year groups, classes, students, and staff.
- Create a few alert rules. Even basic rules (such as alerting DSLs on all incidents) ensure nothing is missed from day one.
- Upload your core policies. Start with your main safeguarding policy and child protection policy. You can add more over time.
- Invite a small group first. Consider onboarding your safeguarding team before rolling out to all staff, so you can answer questions and refine your setup.
