Compliance

School Records Retention: What to Keep and What to Delete

Published 18 November 2026

School records retention, frequently asked questions

Is there a statutory retention schedule for school records?

Partly, and the distinction matters. The Department for Education publishes retention periods for school records on GOV.UK and describes a set of them as having statutory retention periods, covering pupil records, safeguarding files, staff and recruitment records, admissions, attendance and finance. For everything outside those tables the DfE says a school should decide how long it needs to keep the record in line with the business need of the school. So part of the schedule is set for you and part of it is a decision you are expected to make, document and be able to defend.

How long do schools keep child protection files?

Until the child turns 25, with a longer period of up to age 75 applying to a defined category of file set out in the DfE schedule. That second period is the one most often missing from an inherited retention schedule, and it is a fifty year difference. Child protection files also follow the pupil: where a child moves to another school the file transfers rather than staying put, which is why a school can hold a file for a pupil it never taught for very long.

How long should a school keep records of an allegation against a member of staff?

Until the person reaches normal retirement age, or for ten years from the date of the allegation, whichever is later. That applies to allegations found to be unfounded as well as substantiated ones, which surprises people, but the purpose of the record is to show that the allegation was handled properly and that pattern is visible if anything similar happens again. It is also far longer than the six years a general personnel file is kept for, so the two must not be managed as one thing.

Do schools need to keep a copy of a DBS certificate?

No, and in most cases they should not. Keeping Children Safe in Education requires the single central record to show that a check was carried out and when, not to hold the certificate itself. Where a school does take a copy there must be a reason for it, and the DfE sets the retention at six months from the date of recruitment, after which it is disposed of securely. The simplest safe position is to record the certificate number and date on the single central record and keep no copy at all.

When does a school retention period start?

On the trigger the schedule names, which is rarely the date the document was created. A secondary pupil record runs to the pupil 25th birthday, an admission record runs six years from the date of admission, an attendance register runs six years from the date of entry, and a personnel file runs six years from the end of employment. Applying a single period from the creation date to everything is the most common way a school ends up both deleting things too early and holding others for decades longer than it should.

What does KCSIE 2026 expect schools to evidence about records?

Keeping Children Safe in Education 2026 has been in force since 1 September 2026 and carries expanded expectations on record keeping and information sharing, including evidencing the filtering and monitoring checks a school carries out. The practical test is whether a school can produce the record, show who has seen it and show that it has been kept or disposed of according to the schedule. Being able to say what the policy is has never been the hard part. Being able to show that it was actually applied is.

Can school records be kept electronically?

Yes. Nothing in the DfE guidance requires paper. What is required is that records are kept securely, can be produced when needed and are disposed of at the right time. A controlled electronic system evidences all three far more convincingly than a locked cabinet, because it can apply a retention period automatically from the correct trigger date, record every access and amendment, and show that a disposal happened when it was supposed to and was authorised.

Paul Benson, Technology Director at Mastercopy
Written by
Paul Benson
Technology Director, Mastercopy

Paul is Technology Director at Mastercopy, where he leads the development of DocFlow, Mastercopy's AI-powered document management platform. With 18+ years in enterprise technology and systems architecture, he specialises in document intelligence, workflow automation and information security.

Evidence your retention, do not assert it

See how DocFlow applies each retention period automatically from the trigger date the schedule names, and audit-trails every access, amendment and disposal.