Safeguarding & escalation
Safeguarding cuts across every welfare app. This page describes how concerns escalate, how the most sensitive notes are restricted, and how EduPrime supports mandatory-reporting awareness and audit.
Escalation paths
Any concern about a child's safety – raised in the clinic, in counselling, through a discipline incident or by a teacher – can be escalated to the designated safeguarding lead (DSL).
- From the originating record (visit, case, incident) click Raise safeguarding concern.
- EduPrime creates a restricted safeguarding record visible only to the DSL and deputies.
- The DSL records the concern, the decision and any external referral (children's services, police, medical).
- Actions and follow-ups are tracked to closure.
| Source | Escalates to |
|---|---|
| Clinic visit | DSL + nurse |
| Counselling session | DSL + counsellor |
| Discipline incident | DSL + dean |
| Teacher observation | DSL |
Restricted notes
Safeguarding records sit behind the tightest record rule in EduPrime: only the DSL team can open them. Even welfare admins do not automatically see safeguarding notes unless they are in the DSL group. This separation prevents a child-protection concern from leaking through routine welfare access.
Audit & review
Every safeguarding record carries an immutable activity log: who raised it, who read it, what was decided and when. The DSL can run a periodic safeguarding review showing open concerns, overdue actions and trends, which supports inspection and governance.
Data handling on transfer or leaving
When a child transfers, safeguarding information is shared with the receiving school through a controlled handover, not a bulk export. When a student leaves, safeguarding records are retained for the legally required period and archived under DSL control.