How Policies Are Used in Incidents
Once you’ve added policies to Signal, they become the foundation for AI-powered incident analysis, summaries, and suggested actions. This guide explains how policies work behind the scenes and how to get the most from policy-informed guidance.How Policy Matching Works
When an incident is created or updated, Signal’s AI:Analyzes Incident Content
Reviews the incident description, category, student information, and related context
Identifies Relevant Policies
Matches incident details against your policy library using:
- Keyword matching (e.g., “bullying” → Anti-Bullying Policy)
- Semantic analysis (understanding intent, not just exact words)
- Category alignment (safeguarding incidents → safeguarding policies)
- Student context (e.g., policies for specific vulnerabilities)
Extracts Guidance
Pulls relevant sections from matched policies:
- Required actions and timelines
- Reporting requirements
- Key considerations and risk factors
- Multi-agency protocols
Generates Contextual Summaries
Integrates policy guidance into incident summaries and action suggestions
Where Policies Appear in Incidents
- Incident Summaries
- Suggested Actions
- Incident Timeline
- Alerts & Notifications
AI-Generated SummariesWhen you view an incident, the AI summary includes:
- Policy References: Which policies apply to this incident
- Key Requirements: Must-do actions from relevant policies
- Risk Considerations: Risk factors highlighted in policies
- Procedural Guidance: Step-by-step requirements from policies
Example: Bullying Incident Summary
Example: Bullying Incident Summary
Incident: Year 7 student reported being bullied on social mediaAI Summary with Policy Integration:“This incident involves cyberbullying of a Year 7 student. According to your Anti-Bullying Policy, incidents involving online harassment require:
- Immediate contact with parent/carer (within 24 hours)
- Documentation of evidence (screenshots, messages)
- Meeting with alleged perpetrator and their parents
- Referral to online safety lead
- Follow-up meeting within 5 school days
Examples of Policy-Informed Guidance
Example 1: Child Protection Disclosure
Incident: Student discloses abuse to a teacher Relevant Policies:- Child Protection and Safeguarding Policy
- Allegation Management Policy (if staff member involved)
- Immediate verbal report to DSL (do not delay)
- Do not investigate or ask leading questions
- Record disclosure using student’s exact words
- Maintain confidentiality (need-to-know basis only)
- DSL to determine if referral to social care is required (same day decision)
- ✅ Mandatory: DSL to review disclosure and determine referral pathway (Deadline: Same day)
- ✅ Mandatory: Complete child protection record form (Deadline: End of day)
- ✅ Mandatory: Make referral to social care if threshold met (Deadline: Same day)
- ✅ Mandatory: Notify parent/carer unless doing so would place child at risk (Deadline: After DSL consultation)
- ⚠️ Recommended: Pastoral check-in with student (Deadline: Next school day)
Example 2: Repeated Low-Level Behavior
Incident: Year 9 student has 5th incident of low-level disruption this half-term Relevant Policies:- Behavior and Discipline Policy
- Pastoral Support Policy
- ✅ Mandatory: Meeting with parents to discuss behavior pattern (Deadline: Within 5 school days)
- ⚠️ Recommended: Referral to SENCo for needs assessment (Deadline: Within 2 weeks)
- ⚠️ Recommended: Develop behavior support plan (Deadline: Within 3 weeks)
- ⚠️ Recommended: Classroom observation by pastoral lead (Deadline: Within 1 week)
Example 3: Online Safety Concern
Incident: Parent reports student received inappropriate message from unknown person on social media Relevant Policies:- Online Safety Policy
- Child Protection and Safeguarding Policy
- Acceptable Use Policy
- Immediate DSL involvement for assessment
- Consider referral to CEOP (Child Exploitation and Online Protection)
- Preserve evidence (screenshots, messages) without further engagement
- Online safety education session for student
- Parent meeting to discuss online safety at home
- ✅ Mandatory: DSL to assess incident for CEOP referral (Deadline: Same day)
- ✅ Mandatory: Preserve all evidence (screenshots, messages) (Deadline: Immediate)
- ✅ Mandatory: Make CEOP report if grooming suspected (Deadline: Same day)
- ✅ Mandatory: Contact parents to discuss incident and online safety (Deadline: Same day)
- ⚠️ Recommended: 1-1 online safety session with computing lead (Deadline: Within 1 week)
- ⚠️ Recommended: Whole-class online safety reminder (Deadline: Within 1 week)
Example 4: Medical Emergency
Incident: Student with asthma had severe asthma attack requiring ambulance Relevant Policies:- First Aid and Medical Policy
- Supporting Students with Medical Conditions Policy
- Critical Incident Policy
- Immediate contact with parents (already done)
- Ambulance called (already done)
- Complete medical incident report form
- Review of student’s Individual Healthcare Plan (IHP)
- Notification to governing body (serious incidents requiring emergency services)
- ✅ Mandatory: Complete medical incident report (Deadline: End of day)
- ✅ Mandatory: Notify governing body of serious medical incident (Deadline: Within 24 hours)
- ✅ Mandatory: Review and update Individual Healthcare Plan (Deadline: Within 1 week)
- ✅ Mandatory: Meeting with parents to review medical arrangements (Deadline: Within 5 school days)
- ⚠️ Recommended: Staff asthma awareness training refresh (Deadline: Within 2 weeks)
- ⚠️ Recommended: Check all emergency inhalers are in date (Deadline: Within 1 week)
Customizing Policy Application
Overriding AI Suggestions
You always have full control over AI suggestions:- Accept All: Use suggested actions as-is
- Accept Some: Pick which suggestions to create as actions
- Modify: Edit action descriptions, deadlines, or assignees
- Reject All: Ignore suggestions and create your own actions
- Provide Feedback: Flag irrelevant or incorrect suggestions to improve AI learning
Policy Priority and Conflicts
If multiple policies apply to an incident:- Safeguarding policies take priority: Child protection always comes first
- Statutory policies override non-statutory: Legal requirements must be met
- Specific policies override general: Detailed policies take precedence over general guidance
- Most recent policy version applies: Signal uses the current active version
Disabling Policy Application for Specific Incidents
In rare cases, you may want to prevent policies from informing an incident:Disabling policy integration is logged in the incident audit trail. It should only be used in exceptional circumstances where policy guidance is genuinely not applicable.
Policy-Informed Reporting
Policies don’t just inform individual incidents—they also power reporting and analytics:Compliance Reporting
Generate reports showing:- Incidents by policy area
- Policy requirement completion rates
- Overdue policy actions
- Incidents where policies weren’t followed (with reasons)
Pattern Identification
Identify trends such as:- Which policies are referenced most frequently
- Incident types with low policy adherence
- Areas where policy guidance may need updating
- Staff members who consistently follow/exceed policy requirements
Governance and Audit
Provide evidence for:- Ofsted inspections (demonstrating policy adherence)
- Governing body reports (policy application metrics)
- External audits (safeguarding compliance)
- Local authority reviews (policy-informed decision-making)
Improving Policy Effectiveness
- Review AI Suggestions
- Update Policies
- Staff Feedback
- Audit Policy Usage
Monitor Suggestion QualityRegularly review whether AI suggestions are:
- Accurate and relevant
- Aligned with policy requirements
- Appropriately prioritized (mandatory vs. recommended)
- Timely and practical
Best Practices
Trust but Verify: AI suggestions are valuable, but always apply your professional judgment
Update Policies Annually: Review and refresh policies at least once per year or when procedures change
Provide Feedback: Flag inaccurate or unhelpful suggestions to improve AI learning
Use Policies as Training: Policy-informed suggestions help new staff learn procedures in context
Don’t Over-Rely: Policies can’t cover every unique situation—use them as guidance, not rigid rules
Monitor Compliance: Use policy reporting to identify areas where procedures may need reinforcement
Troubleshooting
Policies aren't appearing in incident summaries
Policies aren't appearing in incident summaries
Possible causes:
- Policy content is too vague or lacks procedural detail
- Policy title/keywords don’t match incident language
- Policy is archived or inactive
- Incident category doesn’t align with policy categories
- Review policy content for clarity and detail
- Ensure policy titles use language staff actually use
- Check that policies are marked as “Active”
- Add relevant tags to policies to improve matching
- Contact support if issues persist
Suggested actions don't match our actual procedures
Suggested actions don't match our actual procedures
Possible causes:
- Policy content doesn’t accurately reflect current practice
- Policy text is outdated
- Multiple conflicting policies causing confusion
- Update policy content to match actual procedures
- Archive outdated policies
- Consolidate or clarify conflicting policies
- Add specific procedural steps to policies (not just principles)
AI suggests mandatory actions that aren't actually required
AI suggests mandatory actions that aren't actually required
Possible causes:
- Policy language uses “must” or “required” for recommended actions
- AI misinterprets policy intent
- Use clear language: “must” for mandatory, “should” for recommended
- Explicitly label mandatory vs. optional actions in policies
- Provide feedback on the suggestion to correct AI interpretation
Too many policy references in summaries (overwhelming)
Too many policy references in summaries (overwhelming)
Possible causes:
- Policies are too broad and match many incident types
- Multiple overlapping policies covering the same area
- Consolidate overlapping policies where possible
- Use more specific policy titles and categories
- Mark some policies as “reference only” (not for AI suggestions)
- Simplify your policy structure
Incident summaries ignore a relevant policy
Incident summaries ignore a relevant policy
Possible causes:
- Policy keywords don’t match incident content
- Policy category misalignment
- Policy is too general or too specific
- Add relevant tags and keywords to the policy
- Review policy category assignment
- Add examples or scenarios to policy content to improve matching
- Manually reference the policy in the incident if needed
Advanced: Policy-Informed Alerts
You can configure Signal to generate automatic alerts based on policy thresholds. For example:- “3 behavior incidents in a half-term triggers pastoral support meeting” → Alert DSL when threshold reached
- “Any safeguarding incident involving a LAC student requires immediate virtual school notification” → Alert designated staff when LAC incident created
- “Medication errors require governing body notification” → Alert clerk to governors when medical incident is logged
Parent Mode and Policies
When reviewing incidents with parents using Parent Mode, policy references are:- Hidden by default: Policy names and detailed requirements are not shown to parents
- Summarized: Actions and next steps are presented without referencing specific policies
- Simplified language: Policy jargon is replaced with parent-friendly explanations
Next Steps
Add Policies
Start building your policy library to power AI guidance
Bulk Import Policies
Quickly import multiple policies from your school website
Configure Alerts
Set up policy-based alerts for automatic notifications
Incident Analysis
Learn more about AI-powered incident analysis
Need Help?
If policies aren’t working as expected or you need guidance on improving policy application, contact support@signalschools.co.uk.
