Map the morning arrival process
Document where learners enter, who currently takes the register, peak arrival times and how late or exceptional arrivals are handled. Decide whether the first rollout will be at one gate or across the school.
Prepare student records and ID cards
Confirm admission numbers, names, classes and guardian WhatsApp details. Check that student ID QR codes are readable and define a replacement process for damaged cards.
Assign people and devices
Name the authorised administrators, teachers or security staff who will use the app. Assign each device, protect access and decide who may view fee information.
Test online and offline
Run realistic scans, manual lookups, already-captured attendance, pending sync and restored-connectivity scenarios. Confirm what parents receive on WhatsApp and when an offline event is delivered.
Train for privacy and exceptions
Teach the standard scan-confirm-capture sequence and the private route for fee queries, recent payments, missing students and unreadable cards. Give staff a short written gate procedure.
Review the first weeks
Check sync queues, exception types, guardian contact problems and peak-time throughput. Correct source records and training gaps before expanding the rollout.
See the workflow in Sekani
Sekani connects mobile attendance with the student record, school ID, fee context, offline synchronisation and parent or guardian communication. The most useful evaluation is a guided demonstration using your school’s own gate and attendance scenarios.