What Attendance Codes Are and Why Schools Need Them
An attendance code is a short, standardised mark that records not just whether a student is present, but why they are absent when they are not. A single letter or symbol in a register box distinguishes a student who is ill from one whose family has taken them on holiday, and that distinction carries legal and financial consequences.
Codes exist because raw attendance numbers hide the information schools actually need. Counting only present and absent tells you a student missed five days. Knowing that two were medical appointments, one was authorised family leave, and two were unauthorised tells you where an intervention is warranted.
Codes also feed the reporting that schools owe to their education authority and, indirectly, to families. Consistent coding means the school-wide attendance percentage, the persistent-absence list, and any termly reports are all derived from the same underlying data rather than from each teacher's personal interpretation.
The Standard Categories Most Schools Use
Every school's code set ultimately reflects the official code list used by its education authority or national framework, but the categories behind the letters are broadly consistent. First, there is present — covering both the morning and afternoon session, and sometimes recorded separately for each.
Absence categories then split by whether the school has authorised the absence. Illness and medical or dental appointments are the classic authorised reasons. Religious observance, approved interviews, educational visits off-site, and other pre-agreed activities are also commonly authorised. Unauthorised absence covers holidays taken without permission, unexplained absences, and any absence the school declines to excuse.
Within the present category sits late: a student who arrives after the register has closed is present for the session but the lateness is recorded, because chronic lateness is an early-warning signal that raw present/absent counts conceal. Some code sets also distinguish delayed lateness from lateness after the cut-off.
Designing a Code Key Your Staff Will Actually Use
A code key fails when it is too large or too ambiguous. If staff must choose between eight shades of absence, they will guess — and guess differently. Keep the working set small: present, late, authorised absence with a handful of reason codes for the common cases, and unauthorised absence as the fallback for everything else.
Make the key visual and physical. It belongs at the top of every printed register, on the staffroom wall, and in the front of every substitute folder. Symbols or colour bands alongside letters help supply teachers who have never seen your code set before make correct marks on their first morning.
Write a one-line decision rule for each code rather than a paragraph. “Medical or dental appointment with notification” is actionable in the moment; a long definition is not. The moment a teacher has to stop and interpret, marks get delayed and data quality drops.
Training and Consistency: Keeping Marks Uniform
Two teachers recording the same absence differently is the most common cause of attendance data that cannot be trusted. The fix is brief, recurring training rather than a single induction slide: walk through three ambiguous scenarios each term — a family holiday requested late, a student leaving early for a funeral, a recurring Monday absence — and agree the mark.
Audit a sample of registers each term. Compare marks across year groups and look for systematic differences: one year group recording every late arrival as present, another recording the same case as unauthorised. Systematic differences point to a training gap, not individual error.
Give supply and cover staff a reduced card: present, absent, late, and “send to office for reason” is often enough. The goal for occasional staff is a defensible mark, not perfect granularity — better an honest generic mark than an invented specific one.
From Codes to Reports: What the Data Means
Once codes are consistent, the aggregates become actionable. Authorised and unauthorised absences are reported separately because they drive different responses: authorised patterns may indicate chronic illness or caring responsibilities, while unauthorised patterns usually trigger family engagement.
Session-level totals produce the attendance percentage used to identify students at risk. In England, students whose attendance falls below 90% across the year are classified as persistently absent — a threshold that can only be computed correctly if every session carries a valid code.
Codes also surface the patterns that a percentage hides. A student at 94% attendance who is absent every Friday looks very different from one who was ill for two solid weeks and present every other day. Reviewing coded absences alongside the headline percentage is what turns a number into a decision.
Printable Code Key and Rollout
Roll out a revised code key in three moves. First, agree the final set with leadership and your education authority's requirements. Second, print the key onto every register template before the next term begins — a code key that is not on the form will not be used.
Third, brief every member of staff — teaching and non-teaching — in a single short meeting, with the same ambiguous examples used in your audit. Emphasise the two rules that matter most: mark every session, and when unsure, use the generic absence mark and refer the reason to the office rather than inventing a code.
Review the key once a term against the questions your office actually receives. If staff are consistently asking which code to use for the same situation, that situation needs either its own code or an explicit ruling in the key. The code set should be a living document, but changes must be version-dated so historical registers remain interpretable.
Resources & Templates
Daily Attendance Summary
templateA daily sheet for recording marks by class with a legend area for your code key at the top of the form.
Weekly Attendance Register Template
templateFive-day register grid that keeps codes consistent across the week and doubles as a printable code-key carrier.
Quick Checklist
- Confirm the official code set your reporting framework expects
- Reduce the internal working set to the codes staff can apply without hesitation
- Print the code key on every register template
- Brief all staff with the same ambiguous examples each term
- Audit a sample of registers each term for systematic marking differences
- Review authorised vs unauthorised splits alongside the headline percentage
- Version-date any change to the code key
Frequently Asked Questions
What is the difference between an authorised and an unauthorised absence?
An authorised absence is one the school has approved — illness, medical appointments, and other pre-agreed reasons. An unauthorised absence is any absence the school has not excused, such as holidays without permission or unexplained non-attendance. Both count against total attendance, but only unauthorised absences signal a safeguarding or engagement concern.
Do schools have to use the official government code list?
Schools that report attendance data into a national or local framework must map their marks to the official codes that framework expects — in England, for example, the DfE's attendance codes. Internally, schools can use friendlier codes on day-to-day registers as long as they translate correctly when data is submitted.
How should lateness be coded?
Record lateness as present for the session if the student arrived before the register closes for that session, and use your lateness or late-after-lunch code where the session was missed. The key point is to record lateness at all — a student who is “present” but arrives after registration every day will otherwise show a clean attendance record.
What code should a supply teacher use if they are unsure?
Use the generic absent mark and pass the reason to the office rather than guessing a specific code. An honest generic mark that is corrected later keeps the data recoverable; an invented specific mark silently corrupts it.