Attendance that survives a dead network.
Teachers mark on their own phones — no app to install. If the signal drops mid-class, marks queue on the device and sync the moment it comes back. The register never depends on the school's wifi.
Built for the classroom you actually have.
Patchy wifi included.
Most attendance modules assume a stable connection and a teacher at a desktop. Ours assumes a phone, a full classroom, and a network that comes and goes.
Tap a student's card to cycle through present, absent, late, or leave. It runs in any phone's browser — nothing to install, nothing to update, nothing the teacher has to be trained on twice.
No signal? Marks queue on the device instead of failing. A background flush pushes them to the database seconds after each tap — or the moment the connection comes back. A status badge shows pending, syncing, or failed, with one-tap retry.
A teacher sees only the classes they're the assigned class teacher for, or where the timetable puts them in period 1 that day. Admin and Principal-tier accounts see every class the moment marks land — no end-of-day roll-up to wait for.
Teachers never have to guess whether marks went through. One small badge tells the whole truth, in three states:
Mark. Sync. Visible. Nobody chases anybody.
Four steps, and the last one happens without anyone asking for it.
Teacher opens today's class
On their own phone, in the browser. Works whether the school's wifi is up or not.
Taps through the roster
Each tap cycles present, absent, late, leave. Every mark is stamped with a tick the moment it's made — that stamp matters later.
Marks flush in the background
A debounced flush pushes queued marks to Supabase seconds after each tap. Offline marks wait on the device and go the instant the signal returns.
The principal sees the percentage
Class-wise attendance updates on the admin dashboard as marks land — not after someone compiles a register at 6pm.
Two staff mark the same student.
Here's why nothing breaks.
A school often has two people who can mark the same class — the subject teacher and the class teacher. If both mark the same student before either one syncs, a naive system either double-counts or silently overwrites one of them. You find out at report-card time.
Every mark carries a tick — a stamp from the moment it was made on the device, not the moment it happened to reach the server. When two marks collide, the server keeps whichever tick is actually newest, and the client reconciles to match. Last write wins, honestly. No silent overwrites, no double entries to clean up later.
Every write lands in the attendance table with who marked it and when — so if a principal ever asks “who changed this?”, the answer is one query away.
Mark one real class. Then decide.
7 days free, full product, no credit card. Import your roster, hand a teacher their own phone, and watch the percentage land on your dashboard.