AEVOMIND INSIGHTS — SCHOOLS
SEND administration in schools: the statutory deadlines, the growing caseload, and how software keeps up

SEND administration in a school is a growing pile of statutory deadlines and evidence attached to real children, and the caseload is rising fast — pupils with an EHC plan were up 11.6% in a single year. Software does not decide what a child needs; it makes sure a missed deadline or a lost document is never the reason a child is let down.
The short answer
SEND administration in a school is a growing pile of statutory deadlines and evidence, attached to real children, held together by a SENCo and a spreadsheet. The caseload is rising fast — pupils with an EHC plan were up 11.6% in a single year — and the admin is rising with it. When it fails, it is not a tidy-desk problem: a missed annual review is a child’s support left unreviewed and a duty unmet.
Software does not decide what a child needs. It makes sure the deadlines, the records and the evidence are never the reason a child is let down.

The scale, in the national figures
This is not a problem at the margins. In 2026 the Department for Education recorded 538,547 pupils with an EHC plan in England — 6.0% of all pupils — and a further 14.8% on SEN support (DfE, special educational needs in England). Together that is over 1.8 million pupils with identified special educational needs.
And it is accelerating: the number of pupils with an EHC plan rose 11.6% in one year. Each of those plans carries a statutory review cycle and a file of evidence. The work grows with the caseload; the SENCo’s week does not.
The deadlines that must not slip
Two statutory timescales sit at the centre of it. A local authority must normally complete an EHC needs assessment and issue the final plan within 20 weeks of the request. And once a plan exists, the Children and Families Act 2014 requires it to be reviewed at least every 12 months — the annual review.
The 20-week duty is the local authority’s. The annual review is where the school is squarely in the frame: in practice the school convenes the meeting, gathers the reports and views, holds it, and sends the paperwork back to the authority within the required timescales. The duty is the authority’s; the deadline pressure is the SENCo’s. Multiply one review cycle by a caseload rising 11.6% a year and the scheduling alone becomes a job.

The admin, measured
SEND administration is invisible until a date is missed. Take an illustrative school and a month of it.
Illustrative inputs, not client data. Totals: 22 hours a month by hand against 6 with a system. A system does not make the SEND decisions — it holds the register, the deadlines and the evidence so the SENCo spends the time on children, not paperwork. Substitute hours you have measured.
Show the data
| By hand | With a system | |
|---|---|---|
| Maintaining the SEN register and plans | 5.0 hrs | 1.5 hrs |
| Scheduling and papering annual reviews | 7.0 hrs | 2.0 hrs |
| Gathering evidence for reviews and funding | 6.0 hrs | 1.5 hrs |
| Reporting: SEN information report and returns | 4.0 hrs | 1.0 hrs |
That is roughly 22 hours a month by hand against 6 with a system — about 16 hours back a month, or something like 144 hours across a school year, measured against the ONS median full-time week of 37.5 paid hours. But hours saved is the smaller point. The bigger one is that the deadlines stop depending on someone remembering. The method is the one in how many hours automation can save: measure your own before trusting any figure.

What software can do here — and what it can’t
It cannot assess a child, write provision or replace a SENCo’s judgement. What it can do is make sure the administration never fails the child:
- Hold the SEN register and every plan in one place, current and shared, not in one person’s spreadsheet.
- Track every annual-review date and warn well before it is due, so the cycle runs on the calendar, not on memory — the job of reminders and comms.
- Keep the evidence per pupil: reports, meeting records, provision and outcomes together, so a review or a funding case is assembled, not reconstructed.
- Map provision against need, so what each child is actually receiving is visible and reviewable.
- Produce the reporting — the SEN information report and census returns — from the records you already keep, with the audit trail behind it (audit trail and governance).
This sits with the rest of a school’s systems — see the MIS features that actually matter and the wider schools platform — so a pupil’s SEND record is part of their record, not a separate island that has to be kept in step by hand. The same pressures run through colleges, where high-needs students carry the same plans and reviews.
Where schools lose control of SEND admin
- Review dates in one spreadsheet, known to one person; when they are away or leave, the cycle stalls.
- Evidence scattered across email, shared drives and paper, so every review starts with a search.
- No early warning, so reviews are noticed when they are due rather than in time to arrange them.
- Provision recorded nowhere central, so what a child is actually getting is hard to evidence.
- Reporting rebuilt from scratch each time, because the underlying records do not add up on their own.
The related attendance workload has the same shape — see school attendance admin.

Where to start this week
- List every EHC plan and its annual-review date in one place, and mark any that are overdue or due within the next term.
- Check who else can find that list if the SENCo is away tomorrow.
- Pick three recent reviews and see whether the evidence and paperwork can be produced in minutes, or require a hunt.
- Time a month of SEND admin honestly, separating the paperwork from the time spent with children, before deciding whether a system earns its place.
The test is simple: could the school show, today, that every EHC plan’s review is on track — without one person opening one spreadsheet?
Frequently asked questions
How many pupils have special educational needs?
In 2026, over 1.8 million pupils in England had identified special educational needs. The Department for Education recorded 538,547 pupils with an Education, Health and Care (EHC) plan — 6.0% of pupils — and a further 14.8% on SEN support. The number of pupils with an EHC plan rose 11.6% in a single year, which is why the administration behind them is growing faster than the staff doing it.
What are the statutory deadlines in SEND?
Two matter most. A local authority must normally complete an EHC needs assessment and issue the final plan within 20 weeks of the request. And under the Children and Families Act 2014, an EHC plan must be reviewed at least every 12 months — the annual review, which schools in practice convene, run and paper. A missed annual review is both a failure for the child and a compliance risk for the setting.
Whose job is the EHC annual review, the school or the local authority?
The legal duty to review sits with the local authority, but in practice the school usually convenes the annual review meeting, gathers the reports and views, holds the meeting and sends the paperwork to the local authority within the required timescales. So while the duty is the authority's, the work — and the deadline pressure — lands largely on the school's SENCo.
Can software do SEND administration?
It can carry the administration and the evidence, not the professional judgement. A system can hold the SEN register, track every EHC plan's annual-review date and warn before it is due, store the evidence and reports in one place per pupil, map provision against need, and produce the data for the SEN information report and census returns. The SENCo still decides what a child needs; the system stops a deadline or a document being the reason a child is let down.
How much time does SEND administration take?
More than most schools have. On an illustrative estimate the register, reviews, evidence and reporting add up to around 22 hours a month by hand — much of it on scheduling and paperwork rather than children. A system can cut that sharply, but the larger point is reliability: the deadlines that must not be missed are the ones a manual process misses first. Measure your own before deciding.