Case study
SchoolGate: Attendance System Engineering
The engineering behind SchoolGate: reliable RFID and biometric gate check-in, SMS delivery at morning scale, and attendance records schools can defend.
The challenge
A school gate at 7:30 AM is a harsh environment for software: hundreds of check-ins in minutes, readers in sun and dust, parents expecting the SMS within moments, and zero tolerance for a child being unaccounted for. The system had to be faster than a paper register and completely dependable at morning peak.
Our approach
We put throughput first: readers write check-in events to a local queue that never blocks on the network, and a background worker drains the queue to the server and dispatches SMS in batches. The gate keeps working through connectivity loss; messages flow when the link returns, ordered and de-duplicated.
Attendance truth is event-sourced, every tap is an immutable record, and daily registers are computed from events rather than overwritten, so records can be audited after the fact.
Implementation
The stack pairs gate hardware (RFID/biometric readers) with a PHP/MySQL backend and an SMS gateway integration with retry and provider-failover logic. The admin side exposes daily and termly registers, late-arrival and early-pickup flows, and authorised-pickup enforcement per learner, with role-based access for school staff.
Technology and integrations
- RFID and biometric reader integration
- Local event queue with background sync
- PHP and MySQL event-sourced attendance records
- SMS gateway with batching, retry and failover
- Role-based admin with authorised-pickup controls
Outcome
Schools run morning check-in at register-beating speed, parents receive arrival and pickup confirmations, and termly attendance reports compile from the same event record. The product continues to absorb deployment lessons, reader placement, enrolment logistics, SMS timing, into each new install.
Lessons learnt
- Peak load defines the architecture. Designing for the 7:30 AM surge, not average traffic, settled every major choice.
- SMS is part of safety, so treat it like infrastructure. Retry, ordering and provider failover were not optional extras.
- Immutable events beat editable registers. Schools trust records they can replay, and disputes end quickly.
Services used on this project
Building something similar?
If your organisation faces a comparable challenge, we can apply the same engineering approach to your context, starting with a free consultation.