How GatePass works
The moment a student scans at the gate, the gatekeeper sees confirmation, the parent is notified, and the attendance record is written — all in under two seconds.
✓ Confirmed
Amani Nakato
P.4B · 7:42 AM
GatePass
Amani arrived safely
St. Mary's College
Gate A · 7:42 AM
47 arrived · 3 late · 8 absent
There is one GatePass app for everyone — parents, staff, gatekeepers and visitors. When you first open it, you choose your context. The app forks at that point: different homescreen, different tools, same account system.
School staff / admin
Gate scanning, attendance, boarding, reports
Parent / Guardian
Arrival alerts, boarding confirmations, checkout notices
Visitor / general public
Pre-book a visit, self-check-in at the gate, get a pass
This is what the gatekeeper experiences from the moment school starts. Every step takes seconds, not minutes.
The admin prints QR ID cards from the GatePass web dashboard — one per student. Cards are credit-card sized. No special printer needed.
The gatekeeper opens GatePass, taps "Start scanning". The camera opens and stays open. No tapping between students. Continuous mode until they tap Stop.
Student holds up their printed card or opens the GatePass app on their phone. No battery needed for the printed card.
The gatekeeper sees name, class, and photo on screen. An audible beep confirms the scan. The student walks through.
"Amani arrived safely. St. Mary's College · Gate A · 7:42 AM." No SMS bundle behind it — no per-message fee to the school or to the parent.
The attendance dashboard reflects the scan in real time. Admin can see who has and hasn't arrived at any moment during the morning.
Connection lost
08:14:23 · offline mode active
Scanning continues. Every entry keeps the time it actually happened. Parent notifications will be queued and delivered once reconnected.
Reconnected · syncing
08:24:01 · 3 entries synced
All 3 offline entries synced with their original scan timestamps. Parent notifications delivered. Attendance record is accurate.
Mobile networks drop, and they drop hardest during the morning rush. If the connection goes while the gatekeeper is scanning, scanning carries on. Every entry keeps the time it actually happened, and once the connection is back the school's record and the parent notifications catch up — with the real arrival time, never the time they caught up.
The queue keeps moving
The gatekeeper carries on scanning. There is nothing for them to notice, switch or decide.
Real arrival times, always
A pupil who arrived at 7:44 reads 7:44 — lateness is never manufactured by a bad connection.
Parents are still told
Notifications go out once the connection is back, in the order the pupils actually arrived.
The office is told plainly
The school can see how many notifications are still waiting, so nobody assumes parents have been told when they have not.
No hardware to install. No IT project. Just an account, printed cards, and one person at the gate with a phone.
Sign up on the GatePass web dashboard. Add your school details and set up your first campus.
Upload your student and staff list. GatePass generates a QR ID card for each person automatically.
Print from any printer. Credit-card size. Laminate for durability — or reprint if lost.
Gatekeeper opens GatePass and taps Scan. You're live. Parents receive alerts from the very first scan.
Start a trial and set up your context — your gate, your roles, your notification flow — within an hour.