Imagine two failures. In the first, a teacher browsing a student's ordinary file finds a safeguarding report about abuse at home — information they had no need to know, now impossible to unknow, and liable to leak through staffroom conversation. In the second, a child moves to a new school, and the new school knows nothing about a protection plan that was keeping that child safe, because the old school filed the concern in a general folder that was never passed on. Both failures come from the same mistake: treating safeguarding records like ordinary school records. This safeguarding records confidentiality school guide sets out what to record, where to store it, who may access it, and how long to keep it.
The principle is simple: safeguarding information is sensitive, it is shared on a need-to-know basis, and it is stored separately from academic and administrative records. That principle protects the child from gossip and stigma, protects staff from accusations of mishandling, and protects the school when an authority asks what it knew and when. A school that can produce a clear, factual, securely held record is a school that can show it did its duty; a school that cannot is exposed, however good its intentions were.
Why Safeguarding Files Must Stay Separate
Ordinary student records — admission forms, report cards, attendance, fee records — are handled by many staff and shared routinely with parents. Safeguarding records are different in kind: they may contain allegations against named adults, a child's own words about abuse, medical observations, and correspondence with police or child-protection authorities. If that material sits in the general file, every person who handles the file gains access to it, and every routine sharing — a file sent to a new school, a copy given to a parent — risks disclosing it to someone who should not see it, including, in the worst case, the alleged abuser.
Separation solves this. The safeguarding file lives apart — a separate locked cabinet or a separate password-protected folder — with its own access list, and the ordinary file carries only a discreet marker, such as "safeguarding file held — see safeguarding lead", with no detail. That way, a teacher, an admissions clerk, or a new school receiving the ordinary file knows a safeguarding file exists and whom to ask, without learning its contents. The school's general student record keeping system should state this separation explicitly, so it survives staff changes.
What to Record — and What Not To
Record facts, promptly, in plain language. Each entry needs a date and time, the name of the person recording, what was observed or said (in the child's or reporter's own words where possible, in quotation marks), what action was taken, and the next step with a deadline. Referrals need the same treatment: the authority contacted, the date, the name of the person spoken to, and any reference number given. Injuries are described factually — location, size, colour — without diagnosis. The record should let a stranger, reading it a year later, understand exactly what happened and what was done, without needing to ask the author.
Equally important is what not to record. Do not record opinions, rumours, or judgements: "the mother is neglectful", "the family is suspicious", "the child is lying" are not facts, and they can unfairly damage a family and undermine a case. Do not record information from social-media gossip or unverified third-hand reports as if it were fact; if it is relevant, record it as what it is — "X reported that Y said..." — and note what was done to check it. Do not record a child's safeguarding information in WhatsApp groups, personal notebooks, or emails to personal accounts, even for convenience. If a note is made in haste on paper, it should be transferred to the safeguarding file the same day and the loose note destroyed securely.
Record Facts, Not Verdicts
Where and How to Store Them
Paper safeguarding files belong in a locked, fire-resistant cabinet in a room with restricted access — the principal's or safeguarding lead's office, not the general school office — with the key held only by the safeguarding lead, the deputy, and the principal. The cabinet should be locked at all times, not only at night, and files should never be left on desks or taken home. Electronic files need equivalent protection: a password-protected folder or system, accessible only to the same three people, with strong passwords changed when staff leave, and no storage on personal devices, personal email, or shared drives that all staff can open.
Digital convenience creates digital risk. A safeguarding note photographed on a personal phone, a file emailed to a personal Gmail account, or a record kept in a shared Google Drive folder can be copied, forwarded, or accessed long after the staff member leaves. The school's privacy policy and staff IT rules should forbid these practices explicitly, and the safeguarding lead should check compliance periodically — for example, confirming that no safeguarding files sit in shared folders. Where the school uses management software, safeguarding notes should use its restricted-access feature, not its general student-notes field, and the software provider's data practices should be checked before sensitive material is entered.
Who May Access, and When
Access follows need-to-know, not seniority or curiosity. The safeguarding lead, the deputy lead, and the principal hold routine access. A class teacher may be told, by the lead, the specific information they need to keep a child safe — for example, "if Ali's uncle arrives at pickup, do not release him; call me" — without being given the full file. Other staff, governors or owners, and other parents have no routine access. Even the principal's access should be purposeful: oversight, decision-making, and accountability, not browsing. Every access beyond the lead should be noted in the file — who was told what, when, and why — so the chain of sharing is itself recorded.
Parents' access is nuanced. Parents generally have a right to information about their own child, but safeguarding information may be withheld or shared through the relevant authority where sharing it with a parent could endanger the child — for example, where the concern involves a family member. The safeguarding lead should take advice from the receiving authority before sharing safeguarding records with parents in such cases, and should record the decision and its reasons. Similarly, a student old enough to understand may ask about their own record; handle such requests through the lead and the principal, with care for the student's welfare and for third parties named in the file. Health-related safeguarding notes deserve the same caution as student health records: sensitive, restricted, and shared only where necessary.
How Long to Keep, and Safe Transfer
Safeguarding files should be kept for longer than ordinary school records, because a concern may become relevant years later — a pattern across siblings, a later disclosure, or an enquiry about a former student. As a working rule, schools should retain safeguarding files at least until the child reaches adulthood, and longer where the file concerns a serious case or an ongoing process; the school should adopt a written retention rule and follow it consistently, rather than deciding case by case. When the retention period ends, files must be destroyed securely — shredding for paper, permanent deletion for electronic files — and the destruction recorded.
When a child moves school, the safeguarding file must travel separately and securely: handed directly from safeguarding lead to safeguarding lead, by hand or by a secure, tracked method, with receipt confirmed — never in the same envelope as the ordinary file, never by unrecorded email, and never via the child or parent as courier. The receiving school should confirm receipt, and the sending school should record the transfer date and recipient. If a child leaves without a known destination, the file is retained under the retention rule and the safeguarding lead informs the relevant authority if there is an open concern. A file that follows the child safely, and is destroyed securely when its time ends, completes the circle: the child's story is protected while it matters, and not left lying around after it no longer does.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. A safeguarding lead can ask it to help draft a plain-language records policy covering storage, access, and retention for safeguarding files. Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.