The short version
A SEND action log is only useful if staff can trust it.
That sounds obvious, but plenty of action logs fail for a simple reason: they are started after a meeting, filled with good intentions, and then left to drift.
The result is familiar.
Someone thinks an action has been done. Someone else thinks it is still pending. A parent believes the school agreed to one thing. The SENCO is trying to piece the story back together from memory.
A good action log stops that happening. It keeps the current decision, the owner, the deadline, and the review point in one live place.
What a SEND action log is for
A SEND action log is not a note pad.
It is the working record of what the school said it would do, who said it, and when it will be checked.
It is useful after:
an annual review
a SEN support meeting
a parent conversation
a transition meeting
a complaint or concern
a pastoral check-in that leads to action
If the action is not written down clearly, it will almost certainly be handled badly later.
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 an action log only works when the live record is easy to find.
What every action row should include
A good action log does not need to be fancy. It needs the right fields.
Use the same structure every time:
pupil name
date
meeting or event type
issue or decision
action agreed
owner
deadline or review date
status
evidence or note
That is enough to make the log useful without turning it into a spreadsheet nobody opens.
1. Issue or decision
Write what was actually agreed.
Not "support discussed".
Use a sentence that means something, such as:
parent will send sleep information to SENCO by Friday
class teacher will trial visual instructions for two weeks
SENCO will speak to pastoral lead about morning arrival support
2. Owner
One person should own the next step.
Not a team. Not "school". Not "TBC".
If two people need to do different parts, split the row into two actions.
3. Deadline or review date
Every action needs a point where it will be checked.
If there is no date, there is no pressure to finish it.
4. Status
Keep status simple:
open
in progress
done
parked
If the school uses more than four statuses, staff will stop using them properly.
A useful format for the log
Some schools prefer a table. Others prefer a short list.
The format matters less than the consistency.
A simple table might look like this:
| Date | Decision | Owner | Deadline | Status | | --- | --- | --- | --- | --- | | 23 April | Trial a shorter start-of-day routine for two weeks | Year lead | 7 May | Open | | 23 April | Send parent the revised support summary | SENCO | 24 April | Open | | 23 April | Review attendance pattern after the trial | Attendance lead | 7 May | Open |
That is the kind of record staff can scan quickly.
How to keep it live
The hardest part is not starting the log.
It is keeping it current.
Rule 1: update it on the same day if possible
If the meeting ended with actions, the log should not wait until next week.
The longer you leave it, the more detail you lose.
Rule 2: review it at the start of the next meeting
Open the log before the next conversation begins.
Check what is done, what is late, and what needs re-assignment.
Rule 3: archive the finished row, do not bury it
Once an action is complete, mark it clearly and leave it in the record.
That gives the school a clean audit trail without pretending the action never existed.
Rule 4: keep the current version easy to find
If the action log lives in five different places, it is already broken.
That is where a live records system helps. 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 actions need tracking.
Common mistakes
Too much narrative
A meeting note is not the same thing as an action log.
If the entry is three paragraphs long, nobody will use it.
No clear owner
If everyone is responsible, no one is responsible.
Actions that are too vague
"Monitor progress" is not an action.
"Check reading task completion every Friday for four weeks" is an action.
Dead records
If the log says open but no one has looked at it for months, it is not a live record.
Mixing final decisions with early thoughts
Working ideas are useful, but they should not sit in the same place as agreed actions unless the status is very clear.
What a strong SEND action log actually does
A strong log gives staff three things.
Continuity
The next person can see what happened without asking around.
Accountability
The school can see who owns the next step and whether it happened.
Confidence
Parents, staff, and leaders can trust that the same conversation will not need to be repeated from scratch.
That is especially important when the school is under pressure. The more people are involved, the easier it is for the thread to get lost.
A practical example
A parent meeting ends with three agreed steps:
The class teacher will reduce the amount of written work for two weeks.
The SENCO will check whether the pupil needs a different reading support approach.
The parent will share a private diagnosis report with the school office.
If those three steps are stored in an action log with owners and dates, the school can return to them at the next review and see what happened.
If they are only in a meeting note, the school will waste time working out which parts were actually agreed.
That is why the action log is more than admin. It is the bridge between the meeting and the real school day.
Where MeritDocs fits
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 action log sits alongside the rest of the live record instead of being hidden in a separate file that no one opens.
The Documents Hub means every pupil's current support information is findable, filterable, and exportable.
That is what makes the log useful in practice. Not the format. The fact that the school can find the current version instantly.
FAQ
Is an action log the same as a chronology?
No. A chronology tells the story over time. An action log tracks what needs to happen next. They can support each other, but they are not the same thing.
Who should own the log?
Usually the SENCO or another named lead, but the important thing is that ownership is explicit.
How often should it be reviewed?
At every meeting where the actions matter, and at least once in any term where support is changing quickly.
What if the log gets too long?
Archive closed actions, keep the live rows visible, and use a consistent format so staff can scan the important parts quickly.
The takeaway
A SEND action log should reduce uncertainty, not create it.
If it records the decision, the owner, the deadline, and the outcome in one place, staff can work from the same live information. If it does not, the school will keep repeating the same conversations and missing the same follow-up.
That is why the best logs are simple, current, and easy to trust. MeritDocs gives schools the live record behind that process, so the action log becomes part of normal practice rather than another forgotten file.