Most SEND intervention logs fail for the same reason.
They try to record everything, so they end up helping nobody.
A good log does not need to be long. It needs to answer five questions quickly:
What was the need?
What was done?
When will we review it?
Did it help?
What happens next?
If staff cannot answer those questions in a few seconds, the log is too heavy.
> The best intervention log is not the one with the most detail. It is the one that makes the next decision obvious.
That matters because SEND support depends on the assess, plan, do, review cycle. If the intervention trail is weak, the school loses confidence in what is current, what worked, and what needs to change.
What a useful intervention log needs to show
A useful log is a live working record, not a memory aid.
It should be easy to read, easy to update, and easy to hand over.
1. The starting point
What was the issue before the intervention began?
Keep this short. One or two lines is usually enough.
For example:
reading fluency below age-related expectation
anxiety making transitions difficult
language needs affecting class participation
repeated disengagement in the first lesson of the day
Do not write a paragraph of background. Write the current problem.
2. The intervention itself
What exactly was put in place?
Be specific.
A log that says "support given" is not useful. A log that says "two 20-minute small group language sessions per week for six weeks" is much better.
That level of detail helps staff see what actually happened.
3. The adult owner
Who is responsible for the next step?
If the answer is not clear, the action will drift.
The owner could be the SENCO, class teacher, pastoral lead, TA, subject lead, or an external specialist. The key is that one named person owns the update.
4. The review date
Every intervention should have a date attached to it.
No date usually means no review.
When the review date is visible, staff are far more likely to come back to the record rather than leave it to memory.
5. The impact note
This is the part schools often under-record.
What changed?
Did the pupil engage more? Did attendance improve? Did the class teacher notice a difference? Did the family say something changed at home? Did nothing change at all?
Honest impact notes are better than optimistic ones.
6. The next step
What happens now?
The log should make the next move clear. Continue, adjust, stop, escalate, or refer.
If the log does not answer that, it is not finished.
Keep the format short enough for busy staff
The biggest mistake schools make is designing a log that only works when people have time they do not have.
A good rule is to keep the core fields to six or seven items.
For example:
Pupil name
Need or concern
Intervention
Owner
Start date
Review date
Impact / next step
That is enough for most school workflows.
If you add too many free-text fields, staff stop using the log properly. They start writing vague summaries instead of useful updates.
A simple structure that works in practice
Here is a clean format you can copy.
Intervention log fields
**Pupil**
**Current need**
**Intervention in place**
**Who owns it**
**Start date**
**Review date**
**Impact so far**
**Next action**
That is all a new member of staff usually needs to understand the situation.
If your school wants a fuller historical record, keep that elsewhere. Do not overload the live log with old detail.
How to keep the log current
A log only works if it is updated as part of normal school routines.
Weekly check-in
Set a short weekly slot to review active interventions.
Ask:
Which logs are due for review?
Which actions are complete?
Which interventions need to change?
Which records are out of date?
A 15-minute routine is better than a half-day tidy-up once a term.
Update the record at the point of action
If staff wait until the end of the week, they will forget details.
The best time to update the log is right after the conversation, review, or intervention session.
That does not mean the note has to be long. It just has to exist.
Make old versions easy to spot
If the school still uses spreadsheets or documents, there should be one clearly current version.
Multiple versions create confusion fast. Someone always opens the wrong file.
This is one reason MeritDocs helps schools run this properly by keeping SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed.
The real gain is not just speed. It is a record people can actually rely on when they need to make the next decision.
Common mistakes to avoid
Mistake 1: Recording activity instead of impact
A log that only lists sessions delivered is incomplete.
Activity matters, but it is not enough.
Mistake 2: Writing vague outcomes
Avoid phrases like:
doing better
some progress
settled a bit more
improving slowly
Say what changed, and if possible, how you know.
Mistake 3: Leaving ownership unclear
If several adults think someone else is updating the log, nobody does.
Mistake 4: Forgetting the family view
Parent observations can matter just as much as what staff see in school.
If a pattern changes at home, that should be captured.
Mistake 5: Treating the log as a back-office task
The log is part of support. It is not separate from it.
If the record is weak, the support usually becomes less consistent too.
A simple example
A Year 4 pupil struggles with transitions after lunch.
A weak log might say:
"Support given. Monitor."
A better log would say:
**Need:** transitions after lunch are triggering distress
**Intervention:** five-minute check-in, visual transition card, quiet return routine
**Owner:** class teacher
**Start date:** 6 May
**Review date:** 20 May
**Impact so far:** fewer delays returning to class on three days out of five
**Next action:** continue for two weeks, then review whether the check-in is still needed
That version is useful because it tells the next adult what happened and what to do next.
Why this matters for schools
Intervention logs often fail when schools rely on memory, inboxes, and scattered files.
That creates three problems.
First, staff repeat work that has already been done.
Second, leaders cannot see whether interventions are working.
Third, families get inconsistent answers because nobody is reading the same current record.
That is why the case for better workflow software is so strong here. A school does not need more admin. It needs a dependable current record.
MeritDocs is built for UK SEND compliance, not retrofitted from a generic document tool. It gives schools one place to hold the live record, the review dates, and the exportable summary without forcing staff to rebuild the story every time.
FAQ
Should every SEND intervention have a log?
If the intervention changes support, yes. A short log is usually enough. The point is to keep the current picture visible.
How detailed should the log be?
As detailed as needed to make the next decision, but no more. If staff are not reading it, it is too long.
What is the best sign that the log is working?
A new member of staff should be able to understand the pupil’s current support, the last review, and the next action without asking around the school.
The practical takeaway
A SEND intervention log should do one job well.
It should help the school answer, quickly and honestly, what was tried, whether it helped, and what happens next.
If it can do that, staff will use it.
If it cannot, the school will keep rebuilding the same story from scratch.
The better answer is a live record people can trust. That is the gap MeritDocs is built to close.