Attendance that works offline, syncs when the Wi-Fi comes back
Teachers mark attendance on their own phone. Marks saved while the network is down queue locally and sync the moment the connection is back — no lost records, no retyping at the end of the day. Biometric devices on the LAN hook in through a lightweight relay.
- Offline-first: marks stay on the phone until the server accepts them
- LAN biometric support via a small relay — ZKTeco, ESSL and CSV exports
- SMS to the guardian when a child is marked absent (optional)
- Period-wise or day-wise attendance; class-teacher locks
The everyday problems we hear
Hardware attendance stops when Wi-Fi drops
A single router outage loses a full morning of marks because the device-attendance dashboard freezes until the uplink is back.
Teachers re-enter marks at the end of the day
Paper registers in the morning, re-typing in the office in the evening. Half the time it does not get done.
Guardians are not told in time
By the time a mother hears her child missed class, the day is over. Trust drops.
Biometric data never makes it to the office PC
Each device has its own vendor software, each one exports differently, and no single list shows today across all devices.
Built for how your office actually runs
Every feature below is already part of EduManage BD — nothing on this list is a mock-up or a “coming soon”.
Offline on the phone
Attendance persists in local storage; when the network returns, the queued batch is uploaded with a stable idempotency key.
LAN biometric relay
A 200-line Node script on the lab PC tails ZKTeco / ESSL / CSV exports and forwards punches to the server. Add a new device model with one tiny parser file.
Absent-SMS to guardians
Optional SMS the moment the roll-call is locked; the parent sees the notice the same hour, not next day.
Class-teacher lock
Marks become read-only after the class teacher confirms; late edits need their password again.
Day / week / month views
Every list has a who-is-present-today, how-many-this-week, which-class-has-the-worst-attendance.
Rejected marks are visible
If the server rejects a mark (student moved class, for example) the teacher sees the reason and can retry or discard it.
How onboarding works
- 1
Issue a phone or tablet to each class teacher
A regular Android phone is enough; attendance works on the mobile browser.
- 2
Turn on the SMS module (optional)
Pick a gateway; absent-SMS goes out as soon as the class is locked.
- 3
Connect the biometric
Install the LAN relay on the lab PC; map device PIN → student ID once.
- 4
Run roll-call every morning
Offline-safe, SMS-ready, instantly visible on the principal dashboard.
What changes for your team
- Zero re-typing at the end of the day
- Guardians see absence the same hour, not next day
- Router outages no longer lose a morning
- Biometric punches from every device land in one list
- Attendance history survives staff turnover
Frequently asked
- Does the biometric talk to the server directly?
- No. A tiny Node relay on your LAN reads the device export and forwards it. This keeps your attendance data under your control and works for every vendor.
- What if the Wi-Fi dies halfway through roll-call?
- Nothing is lost. The phone keeps the marks locally and uploads them when the connection comes back.
- Can parents see today's attendance?
- Yes. In the parent portal, guardians see their own child's attendance within minutes of the teacher locking the class.
- What about late-comers?
- You can mark present, absent, or late. Late is colour-coded on every view.
Try offline-safe attendance for free for 30 days
Book a demo and we will configure a test class with your own students.
Or email supportedumanagebd@gmail.com · Phone: 01566-086621