The short version
A SEND evidence pack is not just a folder of paperwork.
It is the current set of records that explains what support a pupil gets, why the school chose it, what changed, and what needs to happen next.
When those records are scattered, annual reviews take longer, complaints become harder to answer, and Ofsted conversations lose their sharpness.
A good evidence pack fixes that. It gives the school one dependable place to look before a meeting, during a challenge, or after a decision has to be justified.
That matters now because the wider SEND picture is still moving. The DfE SEND and Alternative Provision Improvement Plan keeps the focus on joined-up support and local accountability, while the Ofsted inspection reforms keep leaders thinking about what evidence looks like in practice. If you want a legal pressure check, IPSEA is still one of the clearest sources on where schools go wrong.
The common thread is simple: if your record cannot be found, trusted, and explained quickly, it is not doing its job.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That matters because a usable evidence pack depends on the live record being easy to find in the first place.
What should go in the pack?
A strong evidence pack should answer three questions:
What support was in place?
Why was that support chosen?
What happened next?
If the pack cannot answer those questions, it is too thin.
For most pupils, the pack should include:
the current SEND support plan or equivalent working plan
the most recent assess, plan, do, review note
the latest review outcomes and next actions
any relevant intervention summary, with dates and duration
the main parent communication note, if it changed the plan
any professional advice that shaped the current support
clear evidence of impact, even if that evidence is simple and local
the current review date and the person who owns the next step
The aim is not to store everything.
The aim is to store the right things in a way that someone else can understand later.
What makes a pack actually usable?
A pack is only useful if it is current.
That sounds obvious, but many school packs fail in one of two ways.
The first is overstuffing. People dump old drafts, duplicate notes, historic emails, and out-of-date versions into one big folder. When the pack is opened again, nobody knows which file matters.
The second is under-recording. Staff remember the broad story, but the detail never gets written down. That makes the pack look tidy right up until someone asks for the evidence behind a decision.
A usable pack sits between those two extremes.
It should be:
current
short enough to scan
detailed enough to trust
easy to update after the meeting
clear about who owns the next action
If a new SENCO, headteacher, or external professional cannot make sense of the pack in a few minutes, it needs work.
A simple structure that works
The easiest way to build the pack is to keep the same structure for every pupil.
That way, staff do not have to relearn the system each time.
A practical structure looks like this:
1. Current support summary
This is the front page.
It should say, in plain English, what the pupil needs, what support is active now, and what adults should do differently.
Keep it short. A page or less is usually enough.
2. Reason for support
This section explains why the support exists.
It can include assessment findings, teacher observations, pupil voice, parent concerns, and professional advice.
The purpose is not to write a long history. It is to show the school did not choose the plan at random.
3. What the school tried
List the adjustments, interventions, or changes that have already been made.
Be specific.
Not "extra support".
Better:
10-minute pre-teach before English
seat changed near the teacher and away from the door
shorter written instructions with a visual prompt
check-in at the start of lunch to support transition
4. What changed
This is where the pack starts to earn trust.
Record what happened after the support changed.
Did attendance improve? Did transitions get easier? Did the pupil stop missing the first ten minutes of the lesson? Did the parent report fewer evening meltdowns?
It does not have to be perfect data.
It just has to be honest, current, and usable.
5. Next step and review date
Every pack should show what happens next and when the school will look again.
Without that, the pack becomes a filing cabinet instead of a working tool.
Why schools struggle to keep evidence packs live
The problem is usually not lack of care.
It is fragmentation.
One adult keeps the notes in email. Another stores a PDF on a shared drive. The intervention leader has a spreadsheet. The class teacher keeps a notebook. The parent conversation lives in a separate inbox thread.
That patchwork works until it does not.
When the school needs the latest version, there is no single source of truth.
That is why MeritDocs is useful here. The Documents Hub means every pupil's current support information is findable, filterable, and exportable. It does not magically remove judgment, but it does remove a lot of the hunt for the right file.
The real gain is not just speed. It is a record people can actually rely on when a review, complaint, or inspection question lands fast.
How to keep the pack current
A good evidence pack is not built once and ignored.
It needs a simple maintenance rhythm.
Try this:
update the pack straight after any meaningful meeting
keep review dates visible on the front page
retire old versions instead of leaving them in the active folder
link every action to a named owner
store short evidence notes as soon as support changes
review the pack before annual review season, not the day before the meeting
If the school only updates evidence packs in a panic, they will always feel heavy.
If the school updates them as part of normal practice, they stay light and useful.
What this looks like in practice
Imagine a pupil whose support has changed three times this term.
The evidence pack does not need every email.
It does need to show:
the original concern
the current support summary
what changed after each adjustment
what the parent and school agreed
the next review date
That is enough for the pack to tell the story.
It is also enough for a new member of staff to understand what they are inheriting.
A compact definition you can reuse
A SEND evidence pack is a live bundle of the records that explain current support, show what changed, and make the next step clear. If it cannot be found quickly or read in minutes, it is not a dependable evidence pack.
FAQ
Is an evidence pack the same as a SEND file?
Not quite.
A SEND file can become a dumping ground. An evidence pack should be curated, current, and built around the questions the school actually needs to answer.
How much should be in it?
Enough to explain the support and defend the decision, but not so much that nobody can find the current version. Shorter is usually better if the structure is clear.
Who should own it?
Usually the SENCO or another named SEND lead, but the pack works best when updates are part of normal school workflow, not one person's memory.
Do schools need separate packs for every meeting?
No. One live pack is better. You can pull a meeting version from it when needed.
Final takeaway
The best SEND evidence packs do not feel impressive.
They feel calm.
That is the point. A good pack gives the school one dependable version of the truth, so annual reviews are easier to run, complaints are easier to answer, and inspections are easier to face.
If the records are still scattered across inboxes, shared drives, and old files, the school is doing too much work to find what it already knows. MeritDocs helps schools run this properly by keeping SEND documents in one place, with current information easier to find, review dates visible, and exports straightforward.
That does not replace professional judgement.
It makes the judgement easier to trust.