A student holds up a QR card. They are through the gate, on the register, and their parent has been told — instantly, and without anyone typing a thing. It keeps working when the network does not.
Say whether you are Kindergarten, Primary or Secondary — your classes appear from that.
Upload the student list you already keep in a spreadsheet.
Add your staff and say what each of them does.
Print the ID cards we generate for you.
A gatekeeper opens the app at the gate and scans students as they come in.
Teachers glance at a register that is already filled in, and confirm their class.
Nobody types an attendance list, adds up a roll, or sends a parent a message.
That is the whole daily routine.
A school gate at 7am is a queue with a few hundred children in it. Every one of these is a morning your gate keeps moving anyway.
They are found by name and let straight through. Their parent is told exactly as if the card had been scanned, and the school keeps a record of who let them in.
A child who comes in after the register closes is not quietly recorded as though they were on time. You can see who is repeatedly late, and so can their parents.
A student who has left, a staff member who no longer works there, a card from another school — the gate does not let them past, and nobody has to remember a face.
The camera stays open and the whole line moves through without anyone tapping between children. Your gatekeeper is watching the gate, not a screen.
The student is marked as having arrived, with the time, before a teacher has opened anything.
Their guardian is notified that their child reached school.
Who came in, at what time, through which gate, and who scanned them.
Your arrived and absent counts move as each student walks in.
The list you would use to evacuate is kept correct all day, so it is ready without anyone preparing it.
A gatekeeper signs in on the phone at the gate. Several can scan the same gate at once — there are no shifts to configure.
One scan. The register is marked, the parent’s phone lights up, and the gate log is written.
Teachers open their own class or subject. Most of it is already filled in from the gate — they confirm who is in the class.
The day’s register is already accurate, so the children who have not been scanned in are a short list rather than a guess.
Pre-approved, so reception already expects them. Photographed, badged, and timed in — and timed out when they leave.
Every child scanned onto the bus. The lead carries the list on their phone and it works with no network.
Scanned out at the gate. Parents are told. Boarders are signed out with a reason and the name of who collected them.
One tap starts a roll-call. Every child, staff member and visitor on school grounds — including the ones away on a trip — split into accounted for and not.
This is enforced on the server, on every request — not hidden in the interface. A teacher cannot reach another class’s register by guessing a web address.
The scanner, and a way to find a person with no card. Nothing else.
Their own class or subject registers. Not the whole school’s roll.
The whole day on one screen — who is in, what is wrong, what needs approving.
Who is expected today, visitors on school grounds, deliveries, and visit requests to answer.
Sign-outs, night roll-call, and the nights a boarder was away.
Their own children only — arrival, fees, trips, notices. And they cannot reply.
The phone at the gate holds its own copy of your roll. When the network drops, scanning carries on exactly as before — the gatekeeper is not told to wait and the queue does not build up.
When the connection comes back, the scans sync with the times they actually happened — not the time the network returned. A 7:42am arrival is recorded as 7:42am.
Offline scanning is capped at ten minutes, so a phone can never drift far from the truth.
A full term free. No card, and no automatic charge — we invoice at the end of it, and you decide then.