Safeguarding Software for International Schools

Guided concern intake for every staff member

Early identification of student harm depends on whether teachers, specialists, and support personnel can submit observations quickly and accurately. SafeguardIS provides a guided reporting interface designed for every school employee, regardless of their familiarity with specialized child protection terminology.

The submission flow asks structured questions to capture observed facts, direct quotes from children, dates, times, and specific campus locations. Staff can indicate physical marks on an interactive body map and classify concerns across welfare, attendance, behavioural, or child-on-child categories without guessing statutory thresholds.

• Interactive body maps to record location, size, and appearance of physical marks
• Campus location tagging to highlight risk zones across boarding, transport, and playgrounds
• Clear separation between verbatim statements from the child and adult observations
• Instant confirmation that the report reached the designated safeguarding team

Mandatory DSL triage queue and chronological case files

Every submitted incident report enters a central triage queue restricted to the Designated Safeguarding Lead (DSL) and appointed deputies. The DSL assigns priority levels, requests clarifying information from the reporting staff member, and determines escalation pathways according to school policy.

SafeguardIS automatically compiles incident records into an immutable, chronological case chronology. When multiple concerns involve siblings or recurring peer interactions, the system links related records, giving safeguarding leads a complete picture of cumulative harm across terms.

• Configurable triage statuses: Under Review, Action Required, Multi-Agency Referral, and Monitoring
• Chronological timeline generation displaying incidents, decisions, parent communications, and agency notes
• Sibling record linking to track family-level risk without duplicating manual entries
• Custom tags for contextual safeguarding issues such as online harm, attendance, or self-harm

Low-level adult concerns and allegation workflows

Managing allegations against adults requires confidentiality and strict separation from pupil welfare chronologies. SafeguardIS maintains an isolated Low-Level Concerns and Adult Conduct register accessible only to the Head of School and named senior safeguarding officers.

The workflow supports the identification of concerning adult behaviours, boundary blurring, and policy departures before harm occurs. When an allegation meets the threshold for formal investigation, cases follow structured local authority designated officer (LADO) principles and host-country statutory reporting protocols.

• Complete isolation from student records to prevent accidental disclosure or staff gossip
• Structured low-level concern forms capturing adult conduct, boundary issues, or policy departures
• Direct routing to the Head of School for objective risk assessment and response tracking
• Audit logs recording all investigative steps, external consultations, and outcome determinations

Role-based access, field encryption, and inspection evidence

Child protection data demands rigorous access control. SafeguardIS applies strict role-based access control, ensuring classroom teachers only see reports they submitted, while DSLs, deputies, and heads access scoped caseloads.

Sensitive narrative case notes and identifying student details use AES-256-GCM field-level encryption. The system generates tamper-evident audit logs of every status change, referral export, and review action, providing verifiable evidence during CIS, COBIS, and BSO inspection visits.

• AES-256-GCM field-level encryption on confidential narrative descriptions and case files
• Granular permissions distinguishing between DSLs, case workers, senior leaders, and reporting staff
• One-click anonymised reporting for accreditation visits, inspection teams, and governing boards
• Tamper-evident system activity records documenting every case transition and review event

Operating alongside ManageBac, iSAMS, and school MIS

SafeguardIS is designed to work smoothly alongside primary school management information systems, including ManageBac, iSAMS, and other student information platforms. Rather than mixing sensitive child protection records into everyday academic databases, SafeguardIS keeps safeguarding casework in a purpose-built, secure environment.

Student demographic rosters, class lists, and basic family structures can be synchronized periodically, ensuring pastoral leaders maintain up-to-date pupil profiles without exposing confidential child protection chronologies to general teaching staff.

• Clean coexistence with ManageBac, iSAMS, and web-based international school MIS platforms
• Separation of general academic records from confidential child protection files
• Consistent pupil identifiers to ensure accurate matching across school databases
• Zero disruption to existing attendance, grading, or reporting software infrastructure

Standards and inspection alignment

SafeguardIS workflows are mapped to international child protection guidance and safer recruitment standards:

• ITFCP Child Protection Standards
• KCSIE 2026 Part 1 & Part 2
• CIS International Accreditation Protocol
• COBIS Standards for International Schools
• BSO Standards for British Schools Overseas

Questions school leaders ask

How does SafeguardIS protect confidential child protection records?

SafeguardIS isolates sensitive safeguarding chronologies from everyday school databases. Narrative case notes receive AES-256-GCM field-level encryption, access is strictly governed by role-based permissions, and all administrative interactions produce verifiable audit logs.

Can any school employee submit an incident report?

Yes. All teaching and non-teaching staff members can log into the guided reporting portal to submit observations. Structured forms prompt for objective facts, dates, locations, and body map indicators without requiring complex technical training.

How are low-level adult concerns kept separate from student files?

Low-level concerns regarding staff conduct are routed into a dedicated register visible exclusively to the Head of School and nominated leads. They are never linked to public pupil records, preserving staff confidentiality and fairness.

What evidence does the software produce for accreditation inspections?

The platform exports aggregated, anonymised incident trends, chronologies, and practice evidence mapped directly to CIS, COBIS, BSO, and KCSIE 2026 standards, proving compliance while protecting child privacy.

Explore the platform architecture

Guidance and related resources

• How to record a safeguarding concern: facts, body maps and quotes
• How to write a safeguarding chronology: timeline, threshold and actions
• Low-level concerns policy: practical guidance for international schools
• Managing allegations against staff: procedure, investigation and LADO principles
• Take the free 5-minute safeguarding culture audit
• Browse child protection laws by country for international schools