In short: a special educational needs and disabilities (SEND) record handover should give the receiving setting a current picture of the pupil, the support being provided, what has changed, what the pupil and family say, and what still needs doing. It should have a named owner, a secure transfer route and a way to confirm that the receiving setting can use the information.
A transition is not complete because a folder was sent. The receiving adult needs to understand the pupil well enough to act on the information without rebuilding the history from scattered emails and old documents.
Why SEND handovers fail
Most failures are ordinary process failures rather than one dramatic mistake. For example:
- the plan is sent, but the latest review note is in another folder;
- historic reports are included, but the current provision is not obvious;
- a parent view is known to the special educational needs coordinator (SENCO) but not recorded in the handover;
- an action is mentioned in an email but has no owner at the new setting;
- staff assume the receiving school will ask if something is missing;
- the record is transferred securely, but nobody confirms what arrived or who is using it.
The result is a familiar pattern. The new teacher has a large file and very little confidence about what matters today.
Treat the handover as a decision, not a document dump
Start by deciding what the receiving setting needs to know at the point of transition. The answer will depend on the pupil, the reason for the move and the setting they are joining.
For many pupils, the handover needs a short current summary supported by the relevant source documents. The summary should not replace the full record. It should help the next adult navigate it.
A useful first question is:
If the pupil arrived tomorrow, what would the receiving team need to know before the first lesson, first meeting or first support decision?
That question keeps the handover focused on continuity rather than volume.
The minimum useful SEND handover
Current profile and strengths
Include the pupil’s strengths, interests, communication preferences and the conditions that help them take part. Avoid presenting the pupil only through needs or difficulties.
Current barriers and support
Describe the barriers that matter in the receiving setting and the adjustments, provision or strategies currently in use. Say where they apply. A strategy that works in a quiet one-to-one task may not transfer unchanged to a busy classroom.
Outcomes and recent evidence
Show the current outcomes, the starting point where relevant and the evidence of progress or continued difficulty. Make clear which evidence is recent and which is historic.
Pupil and family views
Record what the pupil and family say is working, what they want the new setting to understand and any concerns about the move. If the pupil cannot contribute in the usual way, record how their views were sought and interpreted.
Reviews and open actions
List the last review, the next review date, outstanding advice, agreed actions and the person responsible for each next step. Do not leave the receiving school to infer deadlines from email timestamps.
Relevant source documents
Include the current plan and the reports or evidence needed to understand decisions. Keep the current version clear. Archive or label superseded versions so staff can see the history without mistaking it for today’s instruction.
A practical handover sequence
1. Confirm the move and the receiving contact
Use a named professional contact and confirm what information the receiving setting needs. Keep a record of the request, the date and the agreed transfer route.
2. Check the live record
Before exporting or sending anything, check the current plan, recent review outcome, active provision, pupil and family views, next dates and open actions. This is a good point to run a short SEND record audit rather than copying every file in the system.
3. Create the current summary
Write for the adult who does not know the pupil. Put the most important information first. Use plain language and distinguish observed information from professional interpretation.
4. Transfer securely and traceably
The Department for Education’s data-protection guidance says that when a pupil moves to another school, the school should transfer the pupil’s records securely. It states that the record should be transferred within 15 days of confirmation that the pupil is registered at the new school and that the transfer should be traceable.
The school should use the route approved for the record, such as the School to School system, an encrypted transfer or the local authority’s process. Do not send pupil records through ordinary personal email or an unapproved file-sharing link.
5. Confirm receipt and next ownership
Ask the receiving setting to confirm that the relevant information arrived and identify who will review it. Where the pupil’s needs or transition risk make it useful, arrange a professional handover conversation rather than relying on documents alone.
6. Close the old-school actions
Record what was transferred, when, to whom and what remains with the originating school under its retention and safeguarding processes. Do not assume that transferring a record means every local copy should be deleted immediately. Follow the school’s retention schedule and relevant guidance.
What software can and cannot solve
A SEND document management system can reduce the risk of version confusion by keeping current documents, review dates, evidence and actions in one searchable place. It cannot decide what the receiving setting needs, remove the requirement for secure sharing or replace professional discussion.
MeritDocs supports a searchable Documents Hub, document versions, review information, exports and structured SEND document workflows. That can make the current record easier to identify before a handover. The school remains responsible for checking the content, access and transfer route.
Moving records into a new SEND system
A pupil transition between schools is not the same as migrating a whole school’s existing records into new software. The first is about secure continuity between settings. The second is an implementation project involving source formats, mapping, permissions, staff training and review.
If a school is moving from Word files, Portable Document Format files (PDFs), scans or another service, ask the provider:
- what formats can be imported;
- how different local templates will be mapped;
- how warnings and unmapped content will be shown;
- how historic versions will be separated from current records;
- how staff will review imported documents;
- how the school can export the records later.
No provider should promise that every SEND document will convert perfectly. SEND records vary by area, setting and pupil, so a best-fit process with human approval is the sensible standard.
Implementation support for schools
MeritDocs can arrange for its team to visit the school and run a live demonstration for all staff who need to use or understand the platform. This can include SEND staff, school leaders and the existing information technology (IT) team.
The team can help set up MeritDocs and support migration of existing SEND records while working alongside the school’s IT and SEND staff on site. The school remains involved in agreeing access, checking the migration plan and reviewing the imported information before it becomes the working record.
That collaborative approach matters because implementation is not just a technical upload. Staff need to know where the current record lives, how changes are controlled, how reviews are followed up and how the school will handle future handovers.
A transition handover checklist
- [ ] The receiving setting and named contact are confirmed.
- [ ] The current plan and version are clearly identified.
- [ ] Current provision and useful adjustments are summarised.
- [ ] The pupil’s strengths, views and communication preferences are included.
- [ ] Parent or carer views and relevant professional advice are recorded.
- [ ] Recent evidence, review outcomes and open actions are linked.
- [ ] Next review dates and owners are visible.
- [ ] The transfer route is approved, secure and traceable.
- [ ] Receipt and next ownership are confirmed.