The latest DfE attendance release is easy to treat as another data update. It is not. For SEND teams, it is a reminder that attendance, support, and parent contact only work when the live record is current.
If one system holds the absence pattern, another holds the SEN note, and the latest parent call sits in an inbox, the school can see that something is wrong but not what to do next. That is the bit that drags schools down. Not the lack of effort. The lack of one reliable place to look.
The release covers state-funded primary, secondary, and special schools. It includes daily, weekly, and year-to-date attendance and absence information, plus reasons for absence. You can read it on GOV.UK here: Pupil attendance in schools: 8 September 2025 to 12 June 2026.
The short version
If attendance is slipping for a pupil with SEND, the first question is rarely "How do we chase harder?" It is usually "What is the barrier, what have we already tried, and who owns the next move?"
That is the part schools lose when the evidence is spread across too many places.
A simple rule helps:
Every SEND attendance concern should have one live record that shows the pattern, the reason if known, the action agreed, the owner, and the review date.
If a member of staff cannot answer those five things in under a minute, the process is too fragmented.
Why SEND teams should care
Attendance is often handled as a behaviour problem first and a support problem second. That does not work well for many pupils with SEND.
A pupil might be missing school because of anxiety, sensory overload, transport issues, sleep, pain, speech and language need, family stress, or a difficult transition. Sometimes the absence code is accurate but still useless on its own.
What matters is the story behind the code.
When schools do not have that story in one place, they repeat work, miss patterns, and lose time. One adult thinks another has already chased it. Another adult thinks the family has already agreed a change. Nobody has the whole picture.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That matters here because attendance work only improves when the live record is easy to trust.
What the release should make leaders ask
A good attendance release should prompt a few practical questions.
1. Which pupils are missing repeatedly, not just once?
A single absence can be a one-off. Repeated absence is usually a pattern. Look for dips on the same day, around the same lesson, or after the same transition. Those repeats usually tell you more than a percentage ever will.
2. What support has already been agreed?
If the school has already changed the timetable, adjusted arrival, agreed a check-in, or changed how contact happens with home, that should be visible in the same place as the rest of the SEND record.
If it is not visible, the next person may unknowingly start from scratch.
3. Who owns the next step?
This is where many schools stall.
The attendance lead sees the pattern. The SENCO knows the context. The tutor knows the pupil. The family may know the trigger. But if nobody owns the action, the response tends to drift.
4. When will we check again?
A response without a review date is just a hope.
What better practice looks like
Better practice does not need a complicated system. It needs a clear one.
Use one live record for each attendance concern. It should show:
- the attendance pattern
- the likely cause, if known
- the support already tried
- the agreed next action
- the named owner
- the date for the next review
That record should be easy to update and easy to find. If staff have to dig through old emails or open several systems to reconstruct it, the record is already too slow.
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 attendance starts slipping.
A simple weekly routine for SEND attendance follow-up
A lightweight routine works better than a heroic one.
Monday: check the pattern
Look at pupils whose attendance moved last week.
Do not just scan the percentage. Look for change, repetition, and links to lessons, times of day, or transitions.
Tuesday: check the record
For each pupil, confirm the current notes are in one place.
Check that the latest support step, contact, and review date are visible. If the record still points to an old plan, fix that before the week runs away from you.
Wednesday: speak to the right adult
That may be the SENCO, attendance lead, pastoral lead, or year lead.
The point is not to spread responsibility around. The point is to make one person own the next action.
Thursday: contact the family if needed
Keep the conversation practical.
What has changed? What is getting in the way? What support is the school trying? What does the family think is driving the absence?
Friday: update the live record
If the conversation changed anything, record it.
If nothing changed, record that too. Silence is not a record.
A short example
A Year 8 pupil with speech and language need starts missing first lesson on two days each week.
A standard attendance letter might chase the numbers. It will not explain the pattern.
A better response notices that both absences follow a difficult morning routine and a rushed arrival. The school agrees a calmer start, a shorter first task, and a check-in with one named adult. If those actions are recorded properly, the school can see whether they help.
That is where a live record matters. Without it, nobody can tell if the adjustment worked or if the school is just guessing from week to week.
Where MeritDocs fits
MeritDocs is useful when the problem is not the absence itself but the amount of scattered information around it.
If the attendance conversation, the SEN note, the plan review, and the next action all live in one searchable hub, staff do not need to rebuild the story every time a pupil misses school again. They can open the current record, see what has already happened, and move to the next step.
That is a better use of time than chasing through folders and inboxes.
FAQ
Is this just an attendance issue?
No. For many pupils with SEND, attendance is a support issue as well. The school may need to change routines, contact, adjustments, or review timing before attendance improves.
Should SEND teams keep their own attendance record?
They should keep a current record of the support side of the issue. The attendance system can hold the numbers. The SEND record should hold the context, actions, and review point.
What does a current record need to show?
At minimum, it should show the pattern, the agreed support, the person responsible, and the next review date.
The takeaway
The latest DfE attendance release matters because it shows how important it is to act on patterns, not just percentages.
If the school wants to support SEND attendance properly, the work has to sit on a live record that staff can trust. MeritDocs keeps SEND documents in one searchable hub, so schools can track what is current, what has changed, and what happens next without rebuilding the history every time.