A SEND complaint does not become easier because everyone remembers it differently.
It becomes easier when the school has one clear record of what happened, what was tried, what was agreed, and what still needs doing.
That matters because complaints are rarely only about the thing that triggered them. They are usually about the gap between what families think happened and what the school can prove happened.
If the school has to rebuild the story from inboxes, old Word files, and half-finished meeting notes, the complaint takes longer, staff get dragged into rework, and the SENCO spends time acting like a historian.
The fix is not more memory. It is a better evidence trail.
The short answer
When a SEND complaint lands, keep the current plan, the latest review note, the agreed actions, the family’s view, and a dated timeline of the key decisions. Keep the trail in one place, update it while the issue is still fresh, and make sure the school can show what it knew at each step.
That is the practical version of good complaints handling.
The Department for Education says maintained schools must have and publish complaints procedures, and it gives best-practice guidance on how schools should handle them. It also makes a clear distinction between a concern and a complaint, and it says problems should be resolved as early as possible where that is realistic. Best practice guidance for school complaints procedures is the main reference point.
For SEND specifically, the DfE says parents should raise SEN concerns with the school while the child is still registered there, and that they should usually speak to the SENCO first. If the issue is about a decision on an EHC plan, that is a different route. The relevant page is Complain about a school: Special educational needs (SEN).
Why SEND complaints become evidence problems
SEND complaints often start with a simple feeling.
A parent thinks support has slipped. A class teacher thinks the plan is out of date. A pupil’s needs have changed but the review did not catch it. A piece of promised support never materialised.
That is when the record starts to matter.
If the school cannot show the timeline, it cannot show the logic behind the decision. And if it cannot show the logic, the discussion quickly turns into a debate about memory, tone, and interpretation.
That is a bad place to be.
A strong evidence trail does not remove the complaint. It does something more useful. It makes the complaint answerable.
What the evidence trail should contain
A SEND complaint trail does not need to be long. It needs to be complete enough that a new member of staff could follow it without guessing.
At minimum, keep:
the current SEND support plan or EHC-related summary
the latest review note
the concern or complaint itself, dated clearly
the steps the school took before the complaint escalated
any support that was agreed and when it started
impact notes, even if the impact was limited
the family’s view, recorded in plain English
the pupil’s view, where that is appropriate
the next action and who owns it
the date of any follow-up review or meeting
If that sounds obvious, good. The problem is not usually that schools do not know what to keep. The problem is that the information ends up scattered across too many places.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That means the evidence trail starts from the live record, not from a panic search through email threads.
What to do in the first hour
When a complaint lands, do not rush to write a long response before the record is in order.
Start with four moves.
1. Name the current record
Decide which document is the live version.
If there are multiple plans, multiple summaries, or multiple review notes, pick one source of truth and stick with it. If you do not, the complaint will end up arguing with several versions of the same story.
2. Freeze the timeline
Write down the key dates while they are still fresh.
That usually means:
when the concern was first raised
when the school responded
what support was offered
when the plan changed
when the family was updated
when the next review was due
A simple timeline is often enough to show whether the school acted quickly, slowly, or not at all.
3. Gather only what you need
Do not dump everything into one folder and call it evidence.
Pull together the records that matter to the issue. If the complaint is about support in literacy, you may not need every historic meeting note from three years ago. Keep the material that explains the current decision.
4. Assign one owner
Someone has to own the response and the trail.
If everyone is responsible, nobody is.
Usually that owner is the SENCO, the headteacher, or whoever is handling the complaint process, depending on the issue and the school’s procedure.
Where schools usually go wrong
The same mistakes come up again and again.
Answering from memory
Memory is useful. It is not evidence.
If the response depends on who remembers the meeting best, the school is already on shaky ground.
Keeping the latest plan in one place and the complaint in another
This creates delay and confusion.
The people trying to answer the complaint can see the plan, but not the context. Or they can see the emails, but not the current support summary.
Treating working notes as disposable too early
Some working notes are only drafts. Others explain why a decision was made.
If the school deletes the only copy of the reasoning, it creates a gap that can be hard to fix later.
Letting parent communication live in private inboxes
That is one of the most common record problems in school SEND work.
Useful context gets trapped in one person’s mailbox. When that person is away, the record becomes thinner than it should be.
Using vague language
Words like “support has been ongoing” or “some progress” do not help much.
Better is:
what support was in place
when it started
what changed
what the family said
what the school did next
What the school should be able to show
A good complaint file should let the school answer five questions quickly:
What was the issue?
What support was in place at the time?
What changed, and when?
What did the school tell the family?
What was the next agreed action?
If the school can answer those questions without a scavenger hunt, the complaint is manageable.
If it cannot, the school is already losing time.
Why better records reduce complaint pressure
A complaint often feels like a people problem.
In practice, it is usually a records problem first.
When the current record is clear, the school can respond faster and more confidently. That helps families, but it also helps staff. It reduces the risk of contradictory answers, missed follow-up, and the awkward moment when one adult says one thing and another adult says something different.
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. The real gain is not just speed. It is a record people can actually rely on when the pressure goes up.
A simple checklist for complaint season
Use the same checklist every time a SEND complaint comes in:
identify the current record
note the complaint date and issue
freeze the key timeline
gather the last review and current plan
collect the family’s latest view
record the school’s next action
set a follow-up date
keep everything in one place
That is enough for most cases.
FAQ
Does every SEND complaint need a big evidence pack?
No. It needs the right evidence, not all the evidence.
Should we keep working notes?
Keep them if they help explain a decision. Do not keep duplicates just because they exist.
What if the complaint is really about an EHC plan decision?
That may need a different route. The DfE SEN complaints page points schools and families to the separate process for EHC plan decisions.
Should the SENCO handle every complaint?
Not always. The SENCO is usually central to the evidence, but complaint ownership depends on the school’s procedure.
The takeaway
A SEND complaint is easier to handle when the school can show a clear timeline, a current plan, and a sensible record of what happened next.
That is why patchwork systems create so much stress. They make a simple complaint feel bigger than it should be.
The more the school can keep one searchable record, the less time it spends reconstructing old decisions and the more time it has to fix the actual problem.
MeritDocs exists for exactly that reason. It keeps SEND documents in one searchable hub so the school can see what is current, export what is needed, and rely on the record when it matters most.