How Long Should You Keep Student Attendance Records?

Schools tend to err in one direction on records: they keep everything, forever, because deleting data feels risky and holding it feels safe. On attendance records — personal data about children — that instinct is exactly backwards. Holding a child's attendance history for decades after they have left is not caution. Under modern data-protection law it is a liability, and an avoidable one.

The right answer is a deliberate retention schedule: a written decision about how long each kind of record is kept, why, and what happens when the clock runs out. Getting there means holding two duties in tension.

Two duties pulling opposite ways

The first duty is statutory retention. Various laws and regulations require schools to keep certain records for a defined minimum period — to support safeguarding, to resolve later disputes, to meet an audit or inspection. You cannot delete a record the law obliges you to retain, however privacy-minded you feel.

The second duty is data minimisation, the principle at the heart of GDPR and most comparable regimes: personal data should be kept only as long as it is needed for the purpose it was collected for, and no longer. Once a record has served its purpose and no statutory duty requires it, continuing to hold it is itself a breach. Indefinite retention "just in case" is precisely what the principle forbids.

A retention schedule is the document where these two duties are reconciled, record type by record type.

Purpose sets the clock

The question to ask of every category of data is not "might this ever be useful?" — almost anything might — but "what specific purpose justifies keeping it, and for how long does that purpose last?"

Attendance data serves several purposes with different lifespans:

• Operational — running the current term, chasing absence, reporting now. Lifespan: the school year, give or take.
• Pastoral and safeguarding — understanding a child's history while they are a student, and for some period after, where a duty applies. Lifespan: longer, and often set by statute.
• Statutory and audit — satisfying a legal retention minimum. Lifespan: whatever the relevant law specifies, and not a day longer than you can justify.

Map each purpose to a period, write it down, and you have the spine of a schedule. The detailed figures are jurisdiction-specific and belong to your own data protection officer or authority — but the method is universal.

Deletion is not an afterthought

A retention schedule that nobody enforces is just a longer way of keeping everything. The harder, more important half of the work is what happens when a retention period expires — and "delete it" is less simple than it sounds.

Two routes are worth understanding:

• Secure deletion means the record is genuinely gone, not merely hidden from the interface while sitting in a backup forever. Real deletion has to reach the backups and archives too, on a defined cycle, or the data was never deleted at all.
• Anonymisation is the useful middle path. Strip the identifiers — names, student numbers, anything that ties a record to a person — and what remains is statistics, not personal data. You can keep anonymised attendance trends for as long as you like, because they are no longer about an identifiable child. This lets a school preserve the value of its historical patterns without carrying the privacy risk of named records.

Anonymisation only counts if it is irreversible. Data that can be re-linked to an individual with a little effort has not been anonymised; it has been lightly disguised, and the law still treats it as personal.

Build the schedule, then work it

The practical path is unglamorous and effective. List every category of attendance-related data you hold. For each, record the purpose, the retention period, the legal basis for that period, and the action at expiry — secure deletion or anonymisation. Assign an owner, and put the review on a fixed calendar with a standing reminder, because a schedule that depends on someone happening to remember each August is a schedule that will lapse the first busy August.

The uncomfortable truth is that over-retention is the common failure, not under-retention. Schools rarely get into trouble for deleting too soon under a documented schedule; they get into trouble for holding named children's data for a decade with no reason anyone can state. A retention schedule is how you stop doing that on purpose.

Classable supports this directly — records are retained until your school asks for them to be erased, and you stay in control with manual data export and manual GDPR erasure, each organisation's data isolated from every other's — so a school can hold attendance data for as long as its duties require, and then genuinely let it go.