Schools have a duty to keep children safe, and concerns often arrive by email. Ravenclerk is designed so that technology never slows a concern down or exposes it to the wrong people.
How a flagged email is handled
- Checked first. Every incoming email is screened for safeguarding signals, such as a disclosure, a welfare worry or a risk of harm, before normal routing begins.
- DSL and deputy only. A flagged email is forwarded directly to the Designated Safeguarding Lead and the deputy DSL, marked as a priority alert.
- No auto-reply. Ravenclerk never sends an automatic reply to a flagged email.
- No summaries in shared places. The content of a flagged email is never summarised into shared mailboxes, channels, dashboards or review queues.
- When unsure, safeguarding. If the AI cannot confidently rule out a concern, the email is treated as safeguarding and sent to the DSL.
What Ravenclerk is not
Ravenclerk is a routing tool. It does not make safeguarding judgements, it does not replace your DSL, and it does not change your school's safeguarding policy or reporting procedures. Staff should continue to follow your procedures and report concerns in the usual way.
Emergency. If a child is in immediate danger, call 999. Ravenclerk is not an emergency service.
Setting it up
During setup, the school names its DSL and deputy DSL in the dashboard, and only school administrators can change them. Every safeguarding route is recorded in the audit log, which is visible only to authorised staff.
Book a demo to talk through how this would work in your school.