What is the 2026 SEND person-level survey?
The Department for Education is collecting person-level information about children and young people with special educational needs and disabilities. The collection is designed to improve the detail available about SEND across England, including the support children receive and how that support changes over time.
For schools, this matters because national data is only as useful as the records behind it. A child is not a neat data point. Their primary need, provision, placement, review history and changes in support sit across a working record that staff have to keep accurate.
The Department for Education guide to the 2026 SEND person-level survey sets out the collection requirements. Schools should read the guidance alongside their own data protection and information governance arrangements.
Why should school leaders care?
There are two reasons.
First, better national data depends on consistent local records. If a school has several versions of a pupil's support information, it becomes harder to know which need, provision or status is current. That creates a reporting problem, but it also creates a day-to-day safeguarding and inclusion problem.
Second, data collections expose weak processes. A request for information can reveal that the SEND register, support plan, annual review paperwork and school information system do not agree. The problem is rarely one incorrect field. It is usually a record that has not been reviewed as circumstances changed.
This is not a reason to turn the SENCO into a data clerk. It is a reason to separate the live pupil record from the extract or return produced from it.
What makes SEND data difficult to keep accurate?
SEND information changes. A pupil may move from SEN Support to an EHCP. A need may be identified more clearly after assessment. Provision may change after a review. A family may provide new information. A placement or transition may alter what staff need to know.
The record has to keep up without losing the story.
Common problems include:
- a support plan using an old description of need
- provision recorded in a document but not reflected in the central system
- a review date that passed without a clear next action
- pupil or parent views stored in an email thread rather than the main record
- staff using a familiar label that does not match the current school or LA format
- information being copied between systems with no clear owner
Each issue looks small. Together, they make the data difficult to trust.
What should a school check now?
A useful check is not a hunt for perfect data. It is a review of whether the information people rely on is current, explainable and owned by somebody.
1. Check the source of truth
For each pupil with SEN, can the SENCO identify the current support plan, review date, provision, key changes and next action without searching several locations?
If the answer is no, start there. A clean return built from scattered records is still a fragile process.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current and export when needed. That gives the school a working record before it needs to produce a report or answer a query.
2. Check the dates
Dates tell you whether a record is alive. Review dates, assessment dates, provision start dates and transition deadlines should not sit as decorative information. They should lead to a clear action.
A school should be able to answer:
- What needs reviewing this half term?
- Which records have changed since the last review?
- Who owns the next action?
- What evidence supports the change?
3. Check changes, not just labels
A broad category or primary need does not tell staff what to do tomorrow morning. The useful part of the record is the connection between need, provision, impact and next step.
For example, a change in a pupil's communication needs may mean a different classroom approach, a revised reasonable adjustment or a new transition brief. The data field matters, but the explanation around the change matters too.
4. Check who can see what
Person-level SEND data needs careful handling. Schools should confirm that access is limited to staff who need it, that exports are controlled, and that old copies are not left in shared folders or personal inboxes.
The UK GDPR school data protection guidance is a sensible reference point. The practical test is simple: can the school explain why someone has access, what they can see and how long a copy is retained?
How should schools prepare for data requests?
The best preparation is routine record discipline, not a last-minute spreadsheet exercise.
Use a short monthly check for a sample of pupils. Compare the central SEND record with the current support plan, recent review information and the school system used for reporting. Record discrepancies and fix the process that caused them.
Do not ask staff to update everything everywhere. Decide which system holds the authoritative record, then make other processes depend on that record where possible.
Keep an audit trail for material changes. A short note explaining what changed, why it changed and when it was reviewed is more useful than a pile of replacement documents with no visible history.
This is also where a proper records platform earns its keep. Patchwork files and spreadsheets can produce a return, but they rarely show the chain of decisions behind it. MeritDocs helps schools keep the current documents, review dates and changes together, so the information is easier to check before it leaves the school.
What this means for SENCO workload
The person-level survey should not become another reason for the SENCO to spend evenings reconciling files.
The answer is to reduce duplicate entry and make ownership visible. A teacher should know where to send a material change. A senior leader should be able to see which reviews are overdue. A data lead should be able to work from a record that has already been checked rather than asking the SENCO to recreate it.
That only works when the school treats SEND information as an operational record, not a collection of documents stored wherever the last conversation happened.
A practical checklist
Before the next data request, ask:
1. Is there one current record for each pupil? 2. Do the SEND register, support plan and reporting system agree? 3. Are review dates linked to actions and named owners? 4. Can staff explain recent changes in provision? 5. Are pupil and parent views kept with the relevant review record? 6. Are exports and access permissions controlled? 7. Can the school show how an old record was replaced or retained?
If several answers are no, the problem is not the survey. The survey has simply made the gap visible.
MeritDocs gives schools a practical way to keep SEND documents in one place, with current information easier to find and exports straightforward. The point is not to create more data. It is to make the record behind the data dependable when staff, families or the Department for Education need an answer.
The takeaway
The 2026 SEND person-level survey is a national data exercise, but the preparation starts locally. Schools need current records, clear ownership and a defensible trail of changes.
Good SEND data does not come from cleaning a spreadsheet once a year. It comes from keeping the underlying pupil record accurate as support changes. That is a workflow decision, not just a reporting task.