Attendance data is only useful if it leads to a better decision.
The Department for Education (DfE)'s guidance on Access your school attendance data explains how schools can use the Monitor your school attendance tool. That helps leaders see the numbers. It does not, on its own, explain the story behind them.
For pupils with special educational needs and disabilities (SEND), that story matters more than the percentage.
A run of absences can be linked to anxiety, sensory overload, transport, sleep, pain, communication need, family stress, a timetable change, or a difficult transition. The number shows the pattern. The SEND record should show the reason, the response, and the next step.
The short version
If SEND attendance is slipping, the school should not start by asking, "How do we chase harder?"
It should ask:
- what is the barrier?
- what support is already in place?
- who owns the next action?
- when will we check again?
A SEND attendance concern should always have one live record that shows the pattern, the likely barrier, the agreed support, the owner, and the next review date.
If staff cannot answer those five things quickly, the process is too fragmented.
Why attendance data needs SEND context
Attendance systems are good at counting. They are not good at explaining.
That is fine for some purposes. It is not enough when a pupil's absence is tied to support needs.
A pupil might be missing first lesson because the journey into school is hard. Another might be missing after lunch because the noise and movement become too much. Another may be avoiding one subject because the support is different from room to room.
Without context, those pupils all look like attendance problems.
With context, they look like different SEND barriers.
That is why schools need a live record that sits alongside the attendance data. That makes it much easier to connect the pattern to the support that should sit behind it.
What the data can tell you
Used well, attendance data can show a lot.
Look for:
- repeated absences on the same day
- a drop after a timetable change
- absence around transitions or unstructured times
- a pattern linked to a particular lesson, staff member, or location
- a slow decline that began after a review, move, or incident
These patterns are usually more helpful than a simple percentage.
A pupil at 92 percent attendance might not raise concern in the same way as a pupil at 85 percent. But if the 92 percent pupil is missing the same slot every week, there is probably something specific going on.
What the data cannot tell you on its own
Attendance data does not tell you what support has already been tried.
It does not tell you whether the family has already raised the same issue.
It does not tell you whether the last adjustment worked for three weeks and then drifted.
That is why the SEND record has to hold the context.
If the school cannot see the last contact, the current plan, the owner, and the review date in one place, it will keep revisiting the same problem from scratch.
A simple weekly routine
A small routine is better than a heroic one.
Monday: pull the pattern
Check the pupils whose attendance moved last week.
Do not just scan the percentage. Look for change, repetition, and timing.
Tuesday: check the live SEND record
For each pupil, confirm the current support is visible.
You are checking for the latest adjustment, recent conversation, and the next review date.
If the record still points at an old plan, fix that before the week moves on.
Wednesday: decide who owns the next move
This might be the special educational needs coordinator (SENCO), attendance lead, pastoral lead, or year lead.
The important part is that one person owns the next action.
Thursday: contact the family if needed
Keep it practical.
Ask what is getting in the way, what has changed, and what support the school is already trying.
The best conversations are specific. They do not start with blame.
Friday: update the record
If the conversation changed the plan, record it.
If it did not, record that too.
Silence is not a record.
What a good record should show
Every SEND attendance concern should have a working note that shows:
- the attendance pattern
- the likely barrier
- the support already tried
- the agreed next action
- the named owner
- the review date
That is enough for the team to move.
It is also enough for a new member of staff to understand the case without reading every email that came before it.
MeritDocs connects the current plan, provision, review history and supporting evidence, so staff see the pupil’s picture rather than a loose folder of documents.
A short example
A Year 8 pupil with speech and language need starts missing first lesson twice a week.
A standard attendance letter might chase the percentage. It will not explain the pattern.
A better response notices that the absences happen after a rushed start and a noisy transition. The school agrees a calmer arrival, a shorter first task, and a check-in with one adult. The support is recorded in the live SEND record and the review date is set.
Two weeks later, the team can see whether the adjustment helped.
Without a live record, that question is much harder to answer.
What schools often get wrong
They treat the issue as pure attendance
For many pupils with SEND, attendance is a support issue as much as a compliance issue.
They keep the support information in too many places
A shared drive, an inbox, a paper file, and someone's memory are not a system.
They forget to set a review point
A response without a review date is just a hope.
They do not connect the numbers to the reason
The school may know that attendance is poor. It may not know why the pattern exists or what support is already in place.
Where MeritDocs fits
This is the kind of workflow that becomes fragile when schools rely on patchwork records.
The practical benefit is a response that joins the attendance pattern to the SEND barrier and the next review.
Frequently asked questions
Should SEND teams keep a separate attendance log?
They should keep a current note of the support side of the issue. The attendance system can hold the numbers. The SEND record should hold the context and the action.
How often should the record be reviewed?
At least as often as the problem is changing. For some pupils that means weekly. For others it may be tied to a review date already agreed with the family or the wider team.
What is the biggest mistake schools make?
They assume the number tells the whole story. It usually does not.
Will using attendance data turn SEND into a behaviour judgement?
No. Use it to investigate barriers and patterns, then connect the finding to reasonable adjustments and support. It should prompt questions about what is getting in the way, not create a label.
The takeaway
Attendance data is only powerful when it leads to the right next step.
If a pupil with SEND is slipping, the school needs one live record that shows the pattern, the barrier, the owner, and the review date. MeritDocs connects attendance-related support to the SEND workflow, linking the evidence, agreed provision and next review so staff can act on the current picture.
Use the DfE dashboard as a starting signal, not a SEND label
The DfE’s Monitor your school attendance tool gives schools, trusts and local authorities access to attendance data and downloads through VYED. The dashboard can show a pattern worth investigating. It cannot explain why a particular pupil is absent, and it should not be used as a shortcut to a judgement about the pupil or family.
The five-field triage note
When a pattern appears, record five things before deciding on a response:
- Observed pattern: which sessions, days, subjects or transitions are affected?
- Pupil explanation: what does the pupil say is happening before the absence or difficult arrival?
- Family context: what has the family noticed, and what contact has already taken place?
- Barrier hypothesis: what school factor could be changed or tested, such as an arrival routine, sensory demand, transport handover or lesson transition?
- Next test: who will try the adjustment, by when, and what evidence will be reviewed?
A weak note says “attendance concern, monitor”. A useful note says “late arrivals are concentrated on Monday tutor time; pupil reports the noisy corridor is the trigger; family can arrive ten minutes earlier; pastoral lead will trial a quiet arrival point for three Mondays and review the pupil’s view and first-period attendance on 21 October”. The example is fictional, but the structure is usable.
Keep the attendance signal linked to the live SEND record, not copied into an isolated spreadsheet that nobody updates after the first contact. MeritDocs can help staff keep the current support document, review date and agreed next action together. The attendance data remains a prompt for professional enquiry, not an automatic explanation.