The short version
Most schools do not have a SEND tracking problem.
They have a visibility problem.
The review date was known once. The intervention started on paper. The follow-up got mentioned in a meeting, then disappeared into inboxes, memory, and a separate spreadsheet nobody opens often enough.
A live SEND tracker fixes that by showing what is due, who owns it, and whether it has been done.
That sounds simple because it is. The hard part is keeping it simple enough that staff will actually use it.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. A tracker works best when it sits beside that current record, not in another disconnected place.
What a live tracker is for
A live tracker is not just a list of tasks.
It is a working view of the SEND process.
It should help staff answer six basic questions:
What needs doing?
Who owns it?
When is it due?
Has it been done?
What evidence shows that it happened?
What is the next review point?
If the tracker cannot answer those questions, it is just history in tab form.
That is why a tracker should sit on top of clear current records, not replace them.
Tracker versus action log
Some schools already have an action log.
That is useful, but it is not always enough.
An action log usually records what was agreed in a meeting.
A live tracker goes further. It keeps the work visible between meetings.
Use the action log for the decision.
Use the tracker for the follow-through.
That difference matters because SEND work goes stale very quickly if nobody is checking it.
What every row should include
Keep the tracker consistent. One structure, every time.
A useful row should include:
pupil name
year group
item type, such as review, intervention, or follow-up
short description of the task
owner
due date
status
last update
evidence or link to the current record
next review date
You can add more fields, but do not add so many that people stop updating it.
The rule is simple: if a field does not help someone act, chase, or check, it probably does not belong.
How to build the tracker
1. Decide what counts as a trackable item
Do not track everything.
Track the things that matter if they slip.
Good examples are:
annual review dates
intervention start and end dates
parent follow-ups
professional referrals
support plan updates
changes to classroom adjustments
promised documents that still need to be shared
If the item creates risk, delay, or confusion when it is missed, it should be on the tracker.
2. Use one row per action
This is where many trackers go wrong.
One row per meeting sounds tidy, but it hides the real work.
One meeting can create several actions, each with a different owner and deadline.
Split them out.
That makes the tracker much easier to scan.
3. Make the status simple
Do not build a mini project-management system.
Use a small number of clear status labels, such as:
not started
in progress
waiting on someone else
complete
overdue
Simple labels are easier to read and easier to filter.
They also stop staff inventing their own versions.
4. Review the tracker on a rhythm
A live tracker only works if someone looks at it.
For most schools, a weekly SEND check-in is enough to keep the moving parts visible.
That check-in should focus on:
what is overdue
what is due this week
what is waiting on a reply
what needs escalation
The review does not need to be long. It just needs to be regular.
5. Close old items properly
A tracker gets clogged when staff leave completed items hanging around forever.
Close things.
Add a short note if needed, then move on.
That keeps the live view clean and makes the remaining work easier to trust.
A simple example
Here is what one line might look like:
Pupil: A
Item type: review
Task: update support summary after parent meeting
Owner: SENCO
Due date: Friday
Status: in progress
Last update: draft shared with class teacher
Evidence: current support plan linked in record
Next review: two weeks
That is enough information for another adult to understand the situation without chasing the original meeting note.
Why schools lose track
The issue is rarely bad intent.
It is usually fragmentation.
One person owns the review date. Another owns the intervention. The class teacher knows about the adjustment, but the SENCO does not see the update until later. The note is in one place, the evidence in another, and the follow-up in a third.
That patchwork can keep a school going for a while.
It is much less good at giving staff one dependable version of the truth.
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 means the tracker is being fed from a live record rather than from memory.
The real gain is not just speed. It is a record people can actually rely on when the week gets busy.
How to keep staff using it
A tracker fails when it becomes another admin burden.
To avoid that, keep the rules tight:
update it in the meeting, or immediately after
only track items that matter
name one owner for each action
keep descriptions short and specific
review it at the same time each week
do not duplicate the same item in three different tools
The best trackers are boring.
That is a compliment.
Boring means predictable, and predictable means people will trust it.
What the tracker should not do
A live tracker should not become:
a second version of the file system
a long narrative of every conversation
a place where people paste whole emails
a replacement for the actual support plan
a dumping ground for old tasks nobody wants to delete
If the tracker starts to feel heavy, it is usually carrying too much history.
Trim it back.
A compact definition you can reuse
A live SEND tracker is a working list of reviews, interventions, and follow-ups that shows who owns each action, when it is due, and whether it has been completed. If it does not show the next step clearly, it is not really live.
FAQ
Is a tracker the same as a spreadsheet?
It can be built in a spreadsheet, but the format matters less than the discipline. A simple tool used well is better than a clever tool nobody updates.
Who should own the tracker?
Usually the SENCO or another named SEND lead, with clear support from the wider team. The key is that one person is responsible for keeping it current.
How often should it be checked?
Weekly is a sensible default. Some schools may need a faster rhythm during annual review season or when there are lots of live interventions.
What is the biggest mistake schools make?
Trying to track too much. If the live tracker is overloaded, people stop trusting it and go back to memory.
Final takeaway
A good SEND tracker should reduce friction, not add it.
It should make it obvious what needs doing next, not make staff hunt for the right tab, file, or email thread.
That is why the best systems usually keep the live record and the working tracker close together. MeritDocs keeps SEND documents in one searchable hub, so schools can build a tracker on top of a current record instead of patching together multiple versions of the truth.
The practical win is simple.
Less chasing, fewer missed follow-ups, and a clearer picture of what support is actually happening now.