How to Choose a School Attendance System: A Checklist

Most attendance software looks excellent in a demo. The demo runs on good wifi, with ten tidy students and a salesperson who knows exactly which buttons to press. Your school is six hundred students at 8:50 on a wet Monday, with a flat tablet and a supply teacher who has never seen the app. The gap between those two scenes is where a purchase succeeds or quietly fails.

This is a guide to buying for the Monday, not the demo. Work through it in order; the early items matter more than the late ones.

1. Can it be cheated?

Start here, because an attendance record you cannot trust is worse than no record — it gives false confidence. Ask directly how the system stops one student marking another present.

• A static QR code or a shared class PIN can be screenshotted and sent to a friend at home. If that is the whole defence, assume the data will be gamed.
• Look for a check-in bound to the moment — a rotating code that expires in seconds — or to a place, via a fixed device at the door. Both together is better.
• Ask what an anomaly looks like in the data and whether the system surfaces it, rather than leaving you to find it.

2. Does the fast path survive a crowd?

Attendance is a peak-load problem. The daily average is irrelevant; the busiest five minutes decide everything.

Walk through arrival in your head. How many seconds per student? How many devices at the main entrance? Does check-in need a login, or is it a single scan? A flow that takes eight seconds instead of four does not feel twice as slow in a demo — but it doubles the queue at the gate, and a doubled queue starts the school day late.

3. Is the check-in validated on the server?

A check-in is only trustworthy if the server, not the student's device, decides whether it counts. Ask whether every scan is validated centrally — so an expired code, a reused code or a check-in aimed at the wrong session is rejected rather than quietly accepted. Client-side-only checks are easy to fool; server-validated check-in is what makes the mark something you can stand behind. Pair that with clean exports — the data out as CSV, Excel and PDF whenever you need it — and you have a record that is both honest going in and portable coming out.

4. Will the reports answer real questions?

Capturing attendance is the easy half. The value is in what you can get back out.

• Can you produce the exact export your authority or ministry requires, in the format they want, without re-keying anything?
• Can a head of year see chronic absence — the students missing ten percent or more — not just today's total?
• Can you get the data out as PDF, Excel and CSV, so the tool is not a one-way box you can never leave?

A system that captures beautifully but reports poorly just moves your spreadsheet work to a different desk.

5. Who can see what?

Attendance is personal data about children, and not everyone in a school should see all of it. Check that roles are real and granular: a classroom teacher, a head of year, an office administrator and a parent should each see a different, appropriate slice. If the only options are "admin" and "not admin," that is a privacy incident waiting to happen.

6. Where does the data live, and who else touches it?

Ask the unglamorous questions. Where is the data hosted? Is it encrypted in transit and at rest? If the vendor serves many schools, is each school's data genuinely isolated from the others? Is there a data processing agreement you can actually sign? Can you export your full data on request, and have records erased when you ask? Vague answers here are a reason to walk away, whatever the demo looked like.

7. What does it really cost?

Headline pricing is rarely the whole bill. Ask about setup and migration, training, support, and any charge for the modules you assumed were included. Ask what happens to the price at renewal, and what it costs to leave — specifically, whether you can export your full history on the way out. A cheap tool that holds your data hostage is not cheap.

A quick way to run the shortlist

Do not score tools on a spreadsheet of ticked boxes alone. Run a short pilot with one year group, on your real devices, on your real network, during your real morning rush. Two weeks of that tells you more than any sales call. Watch where staff hesitate, where the queue forms, where someone reaches for the old paper register out of habit.

The best system is the one your busiest, most sceptical member of staff stops complaining about. Classable was designed against this checklist — rotating-QR anti-fraud, kiosk flow built for the peak, server-validated check-in, role-based access, multi-tenant isolation and plain exports — so the Monday morning version holds up, not just the demo.