# How long should schools keep SEND records? A practical UK retention guide
The short answer is this: schools should keep SEND records for as long as they need them, but no longer. That sounds simple until you look at the reality of school life. SEN support plans, review notes, parent emails, EHCP evidence, attendance context, and old versions of documents often end up spread across shared drives, MIS notes, email inboxes, and paper files.
That is where mistakes start.
The Department for Education's data protection guidance is clear. Schools should only keep personal data for as long as they need it. They should review what they hold every year, keep a retention schedule, and dispose of information safely when it is no longer needed. The guidance also says schools should be able to prove they are not keeping data for longer than necessary. Record keeping and management is the key page.
For SEND teams, the hard part is not knowing that retention matters. The hard part is knowing which records belong in the pupil record, which ones support active decision-making, and which ones are now just clutter.
What the DfE guidance actually says
The DfE manual is not asking schools to delete everything quickly. It is asking them to be intentional.
The core points are straightforward:
keep data only as long as you need it
review held data each year
write a retention schedule that says how long different types of data will be kept
dispose of unneeded data safely
have policies and processes that show your approach is controlled, not improvised
The same guidance also gives a helpful baseline for pupil records. Primary school pupil records are kept until the pupil leaves the school, with MIS data kept for two terms after the pupil leaves. Secondary school pupil records are kept until the pupil's 25th birthday.
That does not mean every SEND note should stay exactly that long. It means your SEND retention rule should sit inside a wider school record-keeping policy, not outside it.
Which SEND records need the longest life?
Not every SEND document has the same purpose.
Some records are operational. They help staff support a pupil this term.
Some are evidential. They show what was agreed, what was tried, and what changed.
Some are historical. They are only there because no one has decided they can go.
A simple way to think about it is this:
1. Current support documents
These are the live records staff use now: SEN support plans, current provision summaries, review dates, parent-agreed actions, and any live adjustments.
These should be easy to find, current, and version-controlled. They should not be duplicated in five different places.
2. Evidence of decisions
This includes review notes, meeting records, correspondence that changed provision, and documents showing why a decision was taken.
These records matter because they explain the journey, not just the outcome. If a challenge comes later, the school needs to show what it knew and when.
3. Pupil record material
This is the information that belongs in the permanent pupil record or the school's defined retention schedule.
For many schools, this includes a summary of SEN history, key reports, and core documents that are needed for future reference.
4. Working notes that have done their job
Some notes only exist to help a meeting happen or to draft a plan. Once they have been folded into the final record, they may no longer need separate retention.
That decision should be made through policy, not habit.
A practical retention rule for SEND teams
If you want a rule you can actually use, try this:
> Keep the live SEND record for as long as it is needed to support the pupil, then move it into the school's retention schedule. Keep the evidence that shows why a decision was made, and safely dispose of duplicate working notes once they no longer serve a purpose.
That is the balance schools are trying to strike.
It is also where many schools get stuck. They keep too much because they are nervous about losing evidence. Or they keep too little because staff do not know which version is final.
Both problems come from the same issue: there is no dependable source of truth.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That makes retention easier because you are not trying to manage the same record in half a dozen places at once.
A simple SEND retention schedule could include
If you are writing or updating a school retention schedule, start with the records your SEND team actually uses.
SEN support plans
EHCP evidence packs
annual review papers
parent communication records that affected provision
assessment summaries and intervention outcomes
agency correspondence that influenced decisions
review dates and action logs
transition notes where support handover matters
archived versions that have been superseded
For each item, record:
what it is for
who owns it
where the current version lives
how long it should be kept
who can approve disposal
what happens at the end of retention
That is enough to make the schedule useful.
If the schedule is too vague, staff will ignore it.
If it is too complicated, they will not use it.
Where schools go wrong
The usual mistakes are predictable.
Keeping everything forever
This is the easiest mistake to make. It feels safe. It is not safe. It increases risk, makes searches harder, and creates version confusion.
Deleting working notes too early
Schools sometimes delete notes that explain why a decision was made before the final record captures it properly. That can leave a gap in the evidence trail.
Treating SEND paperwork as if it all has the same value
It does not. A live SEN support plan and an old duplicate draft are not equally important.
Storing records in places no one can search
Shared drives, inboxes, and personal desktops are not retention systems. They are hiding places.
MeritDocs helps schools run this properly by keeping SEND documents in one place, with current information easier to find, review dates visible, and exports straightforward. The real gain is not just speed. It is a record people can actually rely on when it matters.
A good yearly retention check
Once a year, ask three questions:
What SEND data do we still need for pupils who are on roll?
What has already been superseded or archived?
What can now be disposed of safely under policy?
That annual check does two things.
First, it keeps you honest about what you hold.
Second, it stops SEND records from becoming a digital attic full of forgotten versions and unresolved actions.
FAQ
Should SEND records always stay in the pupil record?
No. Some information belongs in the pupil record, but not everything does. The school retention schedule should decide what is core, what is evidential, and what can be safely removed when its job is done.
Can we delete old SEN support drafts?
Usually yes, if the final record captures the decision and the working draft has no separate evidential value. Check your policy and make sure you are not deleting the only copy of a decision trail.
What about EHCP evidence packs?
These usually need a more careful retention rule because they often sit behind statutory processes. Keep the working evidence for as long as it is needed, then archive it under the school's schedule.
What is the biggest mistake schools make?
They store too much in too many places and then cannot tell which version is current. That is why retention and records management need to be part of the same conversation.
The takeaway
Schools do not need to keep every SEND file forever. They do need a retention rule that is clear, consistent, and defensible.
The DfE guidance gives the right framework. The school retention schedule turns it into practice. And a system like MeritDocs makes it much easier to keep current SEND documents in one searchable hub, so the school can manage retention without losing the record that matters.