How to Write a School Attendance Policy That Works

There are two kinds of attendance policy. The first is written to satisfy an inspector: comprehensive, defensible, and read by nobody. The second is written to be used at eight in the morning by a form tutor deciding how to mark a child whose parent has emailed something vague about a dentist. Only the second kind changes anything. This is a guide to writing that one.

The test throughout is simple. Could a teacher who joined last week, holding your policy, mark a register correctly and know what to do when something is off? If not, the policy is decoration.

Start with the codes, because everything hangs off them

The foundation of a usable policy is a defined, finite set of attendance codes, each with a plain-language meaning. Without them, "present" and "absent" absorb a dozen situations that ought to be distinguished, and your data becomes impossible to act on.

A workable set is small. Present. Late (before a cut-off). Late (after the cut-off, which in many systems counts as absent). Authorised absence. Unauthorised absence. Off-site but supervised — a trip, an exam, a sports fixture. Perhaps a code for a known future absence approved in advance.

The exact list matters less than two properties: every code means exactly one thing, and every member of staff reads a code the same way. A code that two teachers interpret differently is not a code; it is a source of bad data.

The line that causes every argument: authorised versus unauthorised

The hardest and most important distinction in any policy is which absences the school authorises and which it does not. This is where consistency collapses in most schools, because it gets left to individual judgement and individual judgement varies enormously.

The policy's job is to remove that variation. Set out plainly what is authorised — illness, medical appointments that cannot be made out of hours, religious observance, approved exceptional circumstances — and what is not — shopping, a cheaper family holiday in term time, an unexplained day. State who has authority to approve a borderline case, and that nobody else may. State what evidence is required and when.

The point is not to be harsh. It is to be the same for everyone. A parent who learns that the answer depends on which tutor they happen to email has learned that the rules are negotiable, and will negotiate.

Build an escalation ladder with numbers on it

A policy that says the school will "monitor attendance closely" has said nothing a tutor can act on. A ladder with thresholds has said everything. Each rung should name a trigger, an action, and an owner.

A compact example structure, in prose rather than a form:

• At a short run of unexplained absence — the form tutor contacts home the same day, and logs it.
• At a defined level of accumulated absence — the head of year reviews the case and a letter goes home setting out the concern.
• At the next level — a meeting with the family, a written plan, named targets and a review date.
• At persistent absence crossing your reporting threshold — the designated lead takes over, and whatever external referral your jurisdiction requires begins.

Fill the thresholds with real numbers suited to your setting. The structure is portable; the figures are local. What makes the ladder work is that nobody has to decide afresh each time — the student's data lands them on a rung, and the rung dictates the move.

Name who does what

Policies fail at the seams between people. Make the roles explicit so that no action is left to "someone." Who takes the register and by when. Who follows up a same-day absence. Who authorises a borderline case. Who owns the escalation at each rung. Who is responsible for the formal reporting. Who reviews the data weekly and who reviews it termly.

When every action has exactly one owner, things stop falling through gaps. When ownership is shared or implied, the busiest person assumes someone else has it, and nobody has.

Write it to be read

A few habits separate a living policy from a dead one. Keep it short enough that a tutor will actually read it — a long policy is an unread policy. Use plain language, not legal throat-clearing. Put the common cases first and the rare ones later. Include a one-page summary a new member of staff can absorb in five minutes. And review it once a year against what actually happened, because a policy that never changes is one nobody is checking against reality.

The measure of success is not that the document exists. It is that a register taken in any classroom, by any teacher, on any morning, comes out consistent — and that when a student starts slipping, the next step is already written down rather than improvised.

Classable will not write your policy for you, but it gives you the controls to run one consistently — present, late, absent and excused statuses, a configurable late threshold, a duplicate-check policy and email notification thresholds — so a register is marked the same way in every classroom, every morning.