The short version
The latest DfE attendance release is not just a statistic update. It is another reminder that attendance work only improves when schools can see the full story, not just the missed days.
For SEND teams, that means the attendance log, the SEN support record, the parent conversation, and the next action all need to line up. If they do not, the school ends up reacting to absence instead of understanding it.
The official release covers attendance and absence in state-funded primary, secondary, and special schools. That matters because the same data problem shows up across all three settings: the school knows a pupil is absent, but the reason, context, and next step are not always held together in one place. See the latest DfE release.
> The real problem is rarely that schools do not notice absence. The problem is that the evidence is scattered. One system shows the attendance pattern, another holds the SEND note, and the parent conversation lives in an inbox.
Why SEND teams should care
Attendance is often treated as a behaviour issue first and a support issue second.
That is risky.
A pupil with SEND may miss school for reasons that are not solved by the same response you would use for a disengaged pupil. Pain, anxiety, transport, transition, sensory overload, sleep, speech and language needs, and family stress can all play a part. If the school only records the absence code, it misses the pattern underneath it.
That is where many schools lose time. Staff know the pupil has become harder to reach, but the live record does not show what has already been tried, who agreed it, or when it needs to be reviewed.
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 attendance work only gets easier when the live record is easy to trust.
What the release should make leaders ask
A new attendance release should prompt three questions.
1. Which pupils are missing repeatedly, not just once?
Single absences matter, but patterns matter more.
Look for pupils whose attendance dips at the same point each week, after certain lessons, or around transitions. Those patterns usually tell you more than a one-off code ever will.
2. What support has already been agreed?
If a pupil has already had a conversation, a check-in, a timetable adjustment, or a parent agreement, that should be visible in the same place the school uses to review provision.
If it is not, staff will repeat work that has already happened or miss the next step entirely.
3. Do staff know who owns the next move?
A common problem is that everyone notices the absence, but nobody owns the action.
The attendance lead may be watching the data. The SENCO may understand the need. The form tutor may know the family well. Yet the next step still sits in limbo because no one is holding the thread.
What better practice looks like
A better process does not need to be complicated.
It needs to be visible.
Start with a short rule: 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.
That record should answer these questions in under a minute:
What is happening?
What do we think is driving it?
What have we already tried?
Who is doing what next?
When will we check again?
If the answer is spread across three systems, the process 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
If you want a routine that staff will actually use, keep it light and repeatable.
Monday: check the pattern
Look at the pupils whose attendance moved last week.
Do not just scan the raw percentage. Look for change, repeated absence, and any link to transitions, subjects, or times of day.
Tuesday: check the record
For each pupil, confirm the current notes are in one place.
Make sure the latest support step, contact, and review date are visible. If the record still points to an old plan, fix that before the week moves on.
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
The conversation should be practical.
What is happening? What has changed? What support is the school trying? What does the family think is getting in the way?
Friday: update the live record
If the conversation changed anything, record it.
If nothing changed, record that too. Silence is not a record.
A useful example
A Year 8 pupil with speech and language needs starts missing first lesson on two days each week.
The school could send a standard attendance letter.
Or it could look at the pattern and notice that both absences follow a difficult start to the day and a rushed transition from home.
In that case, the school might agree a shorter first task, a calmer arrival routine, and a check-in with one named adult. If those actions are recorded properly, the school can see whether they help.
If the actions are not recorded, everyone will forget what was agreed and the same conversation will happen again in two weeks.
That is exactly the kind of problem MeritDocs is built to reduce. The Documents Hub means every pupil's current support information is findable, filterable, and exportable, so attendance follow-up does not depend on memory.
What not to do
A few mistakes show up again and again.
Do not treat all absence as a discipline issue.
Do not keep attendance notes separate from SEND support notes if the issues are connected.
Do not rely on one staff member to remember the whole story.
Do not leave the next review date in a private notebook.
Do not assume a parent email is enough if the school has not updated the live record.
The point is not to create more admin. The point is to stop the same issue being re-explained from scratch every time it comes back.
FAQ
Is this only relevant to special schools?
No. The DfE release covers primary, secondary, and special schools, and the record-keeping problem exists in all three settings.
Does better attendance tracking need more meetings?
Not always. It usually needs better structure, a clearer owner, and one live place to hold the current decision.
What if the cause of absence is not clear?
Record that honestly. Then note what the school is testing next. A useful record can hold uncertainty as long as it also holds action.
The takeaway
The latest attendance release should not push SEND teams towards more reactive letters.
It should push them towards better visibility.
If attendance, support, contact, and follow-up all live in one current record, the school can respond earlier and more consistently. If they do not, the same pupil can keep missing learning while staff keep rebuilding the same story.
That is why attendance work and records work belong together. MeritDocs gives schools the live record they need, so the next attendance conversation starts with the full picture rather than a half-remembered trail.