When staff change, special educational needs and disabilities (SEND) support is often the first thing to drift.
A pupil's current needs, recent adjustments, parent agreements, medical notes, and next review date can all vanish into a handover that is rushed, incomplete, or written for the wrong audience.
A good handover pack stops that. It gives the next adult the current picture fast, without making them read the whole case history first.
The SEND Code of Practice expects support to stay clear and current, not trapped in old notes or scattered emails. A handover pack is one of the simplest ways to make that real.
A SEND handover pack should let a new member of staff understand the pupil quickly enough to act. If it cannot do that, it is too long or too untidy.
What should be in the pack?
Keep it tight. You are not writing the full record. You are making the next step possible.
A useful pack usually includes:
- pupil name, year group, and key contacts
- the current support plan or one-page summary
- the pupil's main needs in plain English
- what helps day to day
- what makes things worse
- any health, safety, or medicine information staff must know
- current adjustments in lessons and around school
- recent parent conversations that affect provision
- the next review date
- open actions and who owns them
If the school already has a wider provision map or support plan, do not copy everything into the pack. Link to the live record and keep the handover to the essentials.
What a strong handover answers
The best packs answer four questions immediately.
1. What does this pupil need from us now?
Not the diagnosis. The current support.
2. What has worked recently?
Use real examples, not broad phrases.
3. What are the open actions?
If there is a meeting, review, referral, or parent promise, it should be obvious.
4. Who owns the next step?
If nobody owns it, it tends not to happen.
How to build it without wasting time
You should be able to make a useful handover pack quickly if the live record is in order.
Step 1: Pull the current record
Start with the latest plan, the most recent review note, and any active adjustments.
Step 2: Strip out duplicate history
Old versions, superseded notes, and repeated emails do not help the next adult.
Step 3: Write the support in plain English
Use short sentences. Say what staff should do, not what the child was like three terms ago.
Step 4: Add the next actions
A handover pack without next steps is just a summary.
Step 5: Check it with the person receiving it
If they still have questions about what is current, the pack needs tightening.
That makes this kind of handover much easier because the pack comes from the live record rather than from memory.
MeritDocs helps staff build a handover view from the current record, with version history, review dates, controlled access and export. The receiving team still checks the content.
Common mistakes
Too much history
The pack is not the place for a full case note. Give enough context to act, then link to the fuller record if needed.
Old documents mixed in with current ones
This is one of the fastest ways to lose trust in the system. The pack should point only to the live version.
Vague support language
Phrases like "continue to monitor" or "provide support as needed" are not much use to the next adult.
No owner
If the pack does not say who updates it, it will go stale.
When to use a handover pack
Use one whenever the context changes, especially when:
- a child moves class
- a pupil joins mid-year
- a class teacher is absent for a long period
- a key support staff member changes
- a pupil's needs change quickly
- the school is preparing for a move to another setting
The aim is not to create more paperwork. It is to stop the record from losing the pupil.
A simple one-page structure
A good handover pack can be one page, with the full record behind it.
Use this structure:
Current picture A short paragraph on the pupil's main needs and the support they need now.
What helps Three or four clear bullet points.
What to watch for The triggers, warning signs, or situations that tend to go wrong.
Open actions Who is doing what, and by when.
Next review A date, not a vague promise.
That is enough for most class changes and short-notice absence.
A short example
A Year 4 teacher goes off sick midway through the term.
The school could send the new teacher a pile of emails and old plans.
Or it could send a one-page handover pack that says the pupil needs short instructions, a quieter start to the day, and a predictable warning before changes. It also shows the last parent contact and the next review date.
That version is useful. The first version is just noise.
Where MeritDocs fits
This is the sort of workflow that gets messy fast when schools rely on shared drives and memory.
Schools can pull the handover from the live record rather than rebuilding it from scratch every time staff change.
That matters because the next adult does not need a pile of history. They need the current picture.
Frequently asked questions
How long should a SEND handover pack be?
Usually one page is enough if the live record is good. The longer the pack gets, the more likely people are to stop reading it.
Should the pack replace the full support plan?
No. It should point to the current plan and give the essentials needed for the next adult to act.
What is the biggest mistake schools make?
They mix current support with old history. That makes people distrust the pack and ignore it.
How should a handover pack be managed after the move?
A handover pack may be a separate short-lived view, but it should come from the live record, have a clear recipient and review point, and be archived after the handover.
The takeaway
A SEND handover pack works when it is short, current, and tied to the live record.
If staff can open it and understand what matters quickly enough to act, it has done its job. Schools can build handover packs from the current record instead of piecing them together from memory.
Sources and further reading
Relevant official guidance for the framework discussed here includes: SEND code of practice: 0 to 25 years, and Sharing personal data.