Why SEND records fail during transitions, and how schools can fix it
Transitions are where a lot of good SEND work quietly breaks down.
A child changes class. A staff member leaves. A pupil moves school. Everyone assumes the information is somewhere. Then the search begins.
This is usually not a dramatic failure. It is a slow one.
The transition problem
In theory, SEND records should travel with the child in a clean and useful way.
In practice, the information often exists in fragments:
- an old support plan in one folder
- meeting notes in another
- an email trail in someone’s inbox
- a spreadsheet that no one has opened for months
- a paper file in a locked cabinet
That makes handover harder than it should be.
Why this matters
When records are incomplete or hard to find, schools lose more than time.
They risk:
- repeating assessments that already happened
- missing important context
- delaying support after a move
- giving different staff different versions of the story
- creating unnecessary stress for parents
Continuity matters more than neatness here.
The two kinds of transition
1. Pupil transition
This includes:
- moving from nursery to primary
- primary to secondary
- one school to another
- class or key stage changes
- phase transfer for pupils with EHCPs
Each move should carry over the things that actually help the child.
2. Staff transition
This is the part people forget.
When a SENCO, teacher, or support lead changes role, the school may lose context that was never written down properly.
If the school relies on memory, the record is weaker than it looks.
What a useful handover should contain
A strong transition pack does not need to be huge.
It should answer:
- what the child needs
- what support is currently in place
- what has been tried already
- what works well
- what still needs attention
- who was involved last term
- what needs to happen next
That is enough for most people to continue the work without starting again from scratch.
Common failure points
Too much detail in the wrong place
Long notes are not the same as useful notes.
If staff cannot scan the record quickly, they will not use it properly.
Too many versions
If there are several copies of the same plan, nobody is sure which one is current.
No owner
If no one is responsible for closing the loop, the handover stays half-finished.
Missing context
A record might say that a strategy was used, but not why it was chosen or why it was changed later.
That makes the next person’s job harder.
A better model
The best records are:
- short enough to read
- specific enough to act on
- dated enough to trust
- structured enough to search
In other words, they are built for continuity, not just compliance.
What schools can do now
A few practical changes make a big difference.
- use a single source of truth for live records
- agree what must move at transition points
- keep the latest version obvious
- save actions as well as notes
- write records so another staff member can understand them quickly
- review handover after the transition, not just before it
Why this is a research question, not just an admin issue
The SEND system depends on continuity.
If a school cannot carry support from one term to the next, or from one school to another, then a lot of the effort spent on assessment and planning is wasted.
That is why record design matters. The quality of the support is partly shaped by the quality of the handover.
In practice
A system like MeritDocs can make it easier to hand over a live record rather than a loose pile of notes.
Final thought
The real test of a SEND record is not whether it looks complete in a folder.
The real test is whether the next person can use it quickly, understand what matters, and keep the support moving in the right direction.