The real problem with staff change
Staff turnover is one of the quiet reasons SEND systems fall apart.
When the SENCO changes, a pastoral lead moves on, or a class teacher is replaced mid-year, the school does not just lose a person. It loses context. The pupil’s current support, the last review outcome, the parent’s concern, and the next action can all disappear into email threads and old files.
That is why schools often feel a small crisis the moment someone leaves. The information probably exists somewhere, but nobody can find it quickly enough to trust it.
The answer is not to make people remember more. It is to make the record hold the memory. That sits neatly with the SEND Code of Practice: 0 to 25 years, which depends on clear planning, review, and joined-up support.
What gets lost first
The first things to go missing are usually the details that matter most.
what the concern actually was
which interventions were tried
what worked and what did not
what the parent said at the last meeting
when the next review should happen
who is responsible for the next step
If those details sit in different places, staff turnover turns a live process into a reconstruction exercise.
Why patchwork systems break down
Patchwork systems can keep a school going for a while. Shared drives, inboxes, paper folders, and staff memory all help in the short term. The trouble starts when one of those pieces disappears.
Then the school has to rebuild the story from fragments.
That is slow for the SENCO, but it is worse for the pupil. A support plan that should have been adjusted last week might sit untouched for half a term because nobody can confidently say what happened last time.
This is where 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 Documents Hub means every pupil’s current support information is findable, filterable, and exportable.
What a resilient SEND record needs
A record that survives staff change needs to do more than store a PDF.
It needs to answer the questions a new member of staff will ask on day one.
1. What is current?
There should be one place to check the latest support plan, review date, and agreed actions. If there are multiple versions, confusion starts immediately.
2. What has already been tried?
The new staff member should not have to repeat interventions that failed six weeks ago because the record was unclear.
3. What did the family say?
Parent views and pupil voice often disappear first. They should not. They are part of the evidence trail and part of the trust the school has built.
4. What happens next?
A good record makes the next action obvious. It should not leave the new staff member guessing whether the family is waiting for an LA call, a review meeting, or an updated plan.
A simple handover process that works
Schools do not need a complex system to improve this. They need a disciplined one.
Step 1: Identify the current record
Before anyone leaves, agree which document is the source of truth for each pupil. That record should show the current support and the latest review outcome.
Step 2: Capture the next action in one place
Every pupil with SEND should have a visible next step. If it lives only in a meeting note, it will be lost.
Step 3: Export a clean summary for handover
The new SENCO, new teacher, or new support staff member should receive a clean summary, not a bundle of attachments.
Step 4: Check dates and ownership
A handover is only useful if someone owns the next action. Review dates should be visible. Responsibility should be obvious.
Step 5: Keep the record live after the handover
The most common failure is treating handover as a one-off event. It is not. The record has to stay current after the staff change, or the school will be back where it started.
Why this matters for more than admin
This is not just an efficiency point.
When SEND knowledge disappears, pupils feel it first. The school may still be polite, still be trying, still have good intentions. But the support becomes less consistent and less trustworthy.
Families notice when they have to repeat the same story to a new adult. Teachers notice when they are given a plan that does not match the reality in class. Leaders notice when the review cycle slips and nobody can explain why.
MeritDocs is built for UK SEND compliance, not retrofitted from a generic document tool. That matters because schools need more than storage. They need continuity.
What schools should stop doing
A few habits make staff change far worse.
keeping the most important detail in one person’s inbox
storing current plans and old plans in the same folder with no clear naming rule
treating review notes as optional
leaving parent updates in meeting minutes that nobody reopens
rebuilding each support plan from scratch instead of updating the current one
If any of those sound familiar, the school already knows where the risk sits.
What schools should start doing
The fix is usually smaller than people think.
use one current document per pupil
make review dates visible
record impact, not just activity
capture pupil and parent voice in the same record
standardise the handover format
keep exports easy
The result is not just tidier admin. It is a record that still works when the person who created it is no longer in the room.
A practical example
Imagine a Year 8 pupil with speech and language need, some attendance drift, and a recent change in support assistant.
A weak system would leave the new staff member asking around:
What support was in place?
Was there a parent meeting?
What did the last review decide?
Has the LA been contacted?
A stronger system would show all of that in one current record. The new staff member could open it, see the latest review, check the next date, and pick up the work without waiting for a long handover conversation.
That is the difference between a school that merely stores information and a school that can actually use it.
FAQ
Is this just a SENCO issue?
No. SENCOs feel it most, but the problem affects class teachers, pastoral staff, senior leaders, and anyone who needs to support the pupil.
Do schools need more paperwork to solve it?
No. They need less fragmentation. The aim is one current record, not another folder.
What is the first thing to fix?
Start with naming the source of truth for each pupil. If staff cannot tell which version is current, nothing else will stay reliable.
Final takeaway
Staff will always move on. That part of school life will not change.
What can change is whether the SEND record survives the move.
If one current record holds the history, the next action, and the review date, the school keeps its knowledge even when people leave. That is the practical difference between a system that depends on memory and a system that can keep working.