An attendance system needs a clear fallback so an unsuccessful recognition attempt does not leave a learner unaccounted for. Staff should know how to assist without making assumptions.
A practical starting point
A student arrives with the class but the device does not create a record. A teacher needs a reliable way to confirm arrival and correct the register.
Turn the idea into a working routine
- Define who supervises the entrance and verifies an unresolved check-in using approved procedures.
- Record the exception with the relevant time and staff action rather than inventing a device success.
- Review recurring failures with the authorised support team and confirm the final attendance record.
Measure what matters
Track unresolved exceptions and time to correction. A low exception count means little if missing cases are not recorded.
Treating “no device record” as proof that a learner is absent can lead to an incorrect message or report.
What should the team agree before putting this into practice?
Agree the fallback procedure and the staff member responsible for confirming attendance before any family notification is escalated.
MAKE IT PRACTICAL
Your planning checklist
Use this checklist during a team discussion. It tracks your planning progress, not a score of your institution’s quality. Selections stay in this page and are not submitted.
A dependable fallback is part of the attendance workflow.
About this archive: 9 March 2025 is the collection’s reference date. This article was prepared and published on 7 November 2026. It is AI-assisted editorial content; examples are illustrative and do not describe a specific customer deployment.
