The shape of the morning #
Messages arrive on every channel a school has ever published: the answerphone, the office inbox, the parent app, text messages, a note handed in at the gate, and a parent who tells a teacher on the way past.
Registers close, and the guidance is clear that the register should stay open for the same length of time every session and for no longer than thirty minutes. Then the list of unexplained absences comes out of the management information system, and somebody works down it.
The work is not the dialling. It is the reconciliation. Every message has to be matched to the right child, in the right class, in a family that may have three children on roll under two surnames, and then the right code has to go in the register.
A message left at 8.12 on the answerphone about a child who was marked present at 8.55 still has to be resolved, because the register is a legal record.
What the guidance actually requires #
The statutory guidance, Working together to improve school attendance, last updated on 9 July 2026, is more specific than most schools realise, and less prescriptive in the places that matter.
-
Take the register morning and afternoon
Schools must take the attendance register at the start of each morning session and once during each afternoon session, at the same time for all registered pupils.
-
Contact parents on the first day where no reason has been given
Schools are expected to ask parents to contact them to explain an absence, and to have processes in place to contact parents on the first day of absence where no reason has been given. Where absence continues without explanation, further contact should be made to ensure safeguarding.
-
Code an unexplained absence within five working days
Where an absence is unexplained, the correct code should go in as soon as the reason is established, and no later than five working days after the session.
-
Hold more than one emergency contact number
Schools should hold more than one emergency contact number per pupil where reasonably possible.
-
Treat the register as a legal record
Registers are legal records. Every entry must be preserved for six years, and any amendment must show the original entry, the amended entry, the reason, the date and the name of the person who made it.
Notice what is not there.
- The guidance does not say a human must make the first contact
- It does not name a channel
- It does not say the office has to be the one doing it
Where the morning goes wrong #
Three failures come up again and again, and none of them is about effort.
-
The channels do not meet
An absence reported through the parent app and an absence left on the answerphone end up in two different places, so somebody checks both lists against a third. That is the double keying the DfE's own research keeps finding: in Exploring teachers' admin time, participants described moving the same information between systems by hand as routine.
-
The contact data is stale
A number that rings out is indistinguishable from a number that has been disconnected for a year. Offices discover this one child at a time, on the morning it matters, which is the worst possible moment.
-
The follow up is invisible
Three attempted calls that nobody logged look exactly like no attempt at all when the case is reviewed later, and the school has no way to show what it did.
Which parts run on rules #
The DfE has published its own view of this. The Workload Reduction Taskforce's initial recommendations of January 2024 include a list of 23 administrative tasks that should not require a teacher, and item 9 on that list is investigating a pupil's absence.
The taskforce was making a workload point, not a technology one, but the test it sets is the right one: does the task need doing at all, is it administrative or clerical, and does it call for professional judgement? Put the morning through that test and it splits cleanly.
The rules half
- Collecting absence reports from several channels into one list
- Matching them to pupils
- Applying the correct code where the reason is unambiguous
- Identifying who is still unexplained
- Attempting contact against the numbers held, and logging every attempt
Fixed trigger, fixed steps, fixed output.
Needs somebody who knows the child
- Deciding whether an explanation is credible
- Noticing that this is the fourth Monday in a row
- Deciding when unexplained absence stops being an administrative matter and becomes a safeguarding one
- Making the call to a family the school already has concerns about
The other half is not automatable and should not be.
The reason worth clearing the clerical half out of the way is so that the people who make those judgements have the time to make them.
The pupil data question comes first #
Every part of this is personal data about children. The ICO treats children's personal data as meriting specific protection, and the school is the data controller for all of it.
A supplier is a processor acting on the school's documented instructions, the school stays accountable, and the answer to "where does this data sit and who can see it" has to exist before anything is changed.
If you want a number for what the morning costs before you talk to anybody, the cost of admin time calculator will count it from your own figures. The follow on to this page is attendance returns and reporting, which is where the same data gets used a second and third time.