The short version
The problem is rarely that schools do not have a SEND plan.
The problem is that they have too many versions of the same thing.
One sits in a shared drive. Another is attached to an email. A third is printed in a file somewhere. The latest one exists, but the old one is easier to find, or easier to recognise, so staff keep reaching for it.
That is a version-control problem, and it is more common than people like to admit.
The fix is not complicated. Every pupil should have one live SEND record, one clear place where that record lives, and one obvious way to archive older versions so they do not come back into circulation.
If a school cannot tell the difference between current and archived in under a minute, the system is too loose.
What version control means in a school
In schools, version control is not about software releases. It is about making sure the right plan is the one staff actually use.
A good version-control rule does three things:
- keeps one current document active
- makes old versions easy to archive but hard to confuse with the live one
- shows who owns the record and when it was last reviewed
That sounds obvious. It usually only becomes obvious after somebody prints the wrong version, sends it to a parent, or hands it to a cover teacher who then builds a week around outdated information.
That is when the school realises the issue is not content. It is control.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That is what version control looks like when it works. The live record is visible, and the old ones are there if you need them, but they are not competing for attention.
Why old plans keep coming back
Old SEND plans usually survive for boring reasons.
1. They have a familiar title
Staff recognise the file name, so they assume it is the right one.
2. They are easier to find
The most recent file is not always the easiest file to find. If the current version is hidden in a folder no one checks, the school has already lost the battle.
3. People do not trust the system
If the live document has been unreliable before, staff stop believing it is current and save their own copy instead. That is how the mess grows.
4. There is no clear owner
If nobody is responsible for updating the document, then everyone assumes somebody else has done it.
5. Archiving is not obvious
If old versions are left in the same place as active ones, staff will continue to use whichever file looks closest to the current record.
A simple rule that works
You do not need a complicated policy to fix this.
Use one rule:
There is one live SEND record per pupil. Everything else is archived.
That rule only works if everyone knows what it means in practice.
The live record should always show
- the pupil’s current support
- the latest review date
- the name of the owner
- the next action
- any important changes since the last review
The archived version should be
- clearly labelled as archived
- dated
- stored where staff can find it if needed, but not where they will mistake it for the current copy
The key point is not to hide history. It is to stop history pretending to be current.
How to set up a sensible document system
1. Put the active version in one place
The current plan should have one home. Not a copy in every folder. Not the same file emailed around in different forms.
A shared drive can work if the structure is disciplined. A proper records hub works better because staff are less likely to lose the plot.
2. Name files in a way that makes the current one obvious
File names should help staff, not confuse them.
Use something like:
- pupil name
- document type
- current date
- status if needed
Avoid file names that are almost identical except for a tiny change in the date or a hidden suffix.
3. Put the review date where people can see it
If staff have to open the document to discover whether it is current, the system is too slow.
Make the review date visible in the record summary, not just buried in the body.
4. Archive old versions properly
Old files should move out of the active workflow when they are replaced.
That does not mean deleting them. It means making sure nobody accidentally uses them as if they were live.
5. Record the change when the plan changes
Every update should tell the next adult what changed and why.
That can be short:
- support changed after review
- parent requested a communication adjustment
- new sensory break agreed
- intervention stopped because it was not helping
The point is to preserve the decision, not write a novel.
What cover staff and teachers actually need
Most staff do not need the full case history.
They need the current picture fast.
That means the live record should make these things obvious:
- what helps day to day
- what makes things worse
- what has changed recently
- who to contact next
- whether there is an urgent review or meeting coming up
If the record does not do that, it is too heavy for practical use.
This is where schools often accidentally make things worse. They create a long document to be thorough, then no one reads it because the useful bits are buried. A shorter, cleaner live record will usually be used more often and trusted more.
Common mistakes
Keeping old and current versions side by side
This is the most common way to confuse staff.
Emailing PDFs instead of updating the live record
Emails are useful for notification. They are poor as the main record.
Letting different adults keep different copies
Once that happens, the school no longer has one record. It has several opinions.
Using vague labels like final, latest, or amended
Those words do not tell staff enough. Dates and status do.
Forgetting to archive after a review
This is how the old plan quietly takes over again.
Why this matters for SEND work, not just admin
Version control sounds like paperwork. It is actually about support.
If a teacher uses an old plan, the adjustment may be wrong. If a supply teacher uses the wrong version, the first lesson of the week may go off the rails. If a parent sees an old file, trust drops immediately.
So this is not admin for its own sake. It is part of making sure the school response is actually current.
That is also why a linked article like how to run a SEND record audit before the end of term is useful. If a school wants to clean up the system properly, the audit has to expose the duplicate versions as well as the gaps.
Where MeritDocs fits
MeritDocs helps schools solve this in a practical way.
The Documents Hub means every pupil’s current support information is findable, filterable, and exportable. That matters because the system itself helps staff see what is current, rather than leaving them to guess.
It also means schools can keep older versions without letting them sit in the way of the live record. The real gain is not just tidiness. It is trust.
If the school can rely on one current record, staff spend less time checking, less time reworking the same document, and less time wondering whether they are looking at the right thing.
A short practical summary
A good version-control rule for SEND records is simple:
- one live document per pupil
- old versions archived, not floating around active folders
- the review date and owner visible at a glance
- the live record easy to find and export
That is enough to stop most of the chaos.
FAQ
Is it a problem if staff keep personal copies?
Yes, if those copies start replacing the live record. Staff can keep notes, but the school needs one source of truth.
Do we need fancy software for version control?
Not always, but the process has to be clear. The more people involved, the more useful a proper hub becomes.
Should we delete old plans?
Usually not. Archive them properly so the history exists without competing with the current version.
What is the quickest first step?
Find the current plan for each pupil, check whether there is more than one active version, and move every old copy out of the active workflow.