The technical architecture behind real-time attendance sync
Resilience to connectivity loss has been our north star. Attendance must record reliably in a classroom, sync when the network returns, and never lose a punch.
How Skoolsewa keeps attendance, fees and messaging consistent across campuses — even when connectivity is degraded.
School networks are not data centers. A classroom in a remote campus can lose connectivity mid-lesson, and a mark taken in that moment still has to be the truth when the network returns. This report describes how Skoolsewa keeps writes consistent across campuses.
When we discovered Skoolsewa's sync layer, we pivoted to an architecture that takes full advantage of offline-first writes. The payoff has been enormous.
The Challenge
Centralized architectures fail exactly when schools need them most: during exams, festivals and load-shedding. A single lost request meant a student marked absent for the day, and reconciliation consumed hours.
The Solution
Skoolsewa records attendance as an append-only event locally, queues it for sync, and resolves conflicts with last-writer-wins per class session. Fee transactions use the same queue with idempotency keys, so retries never double-charge.
- Offline-first event queue with conflict resolution
- Idempotent fee transactions across retries
- Delta sync that transfers only what changed
- Per-campus sync status visible to administrators
The Impact
Sync failures dropped to near zero, and the platform now serves schools where connectivity is measured in hours per day, not megabits per second.
- Zero lost attendance marks during connectivity loss
- Idempotent payments — no double charges on retry
- Delta sync cuts bandwidth use by 80%
FAQs
Skoolsewa resolves conflicts per session with deterministic last-writer-wins, and both changes are visible in the audit trail.