Typhoon phone trees
Class suspensions relayed adviser-to-adviser and posted on Facebook, hours after the announcement — and some families still miss it.
"Did my child arrive?"
Parents left guessing whether their child made it to campus, especially on stormy commutes.
Clipboard headcounts
During drills and real evacuations, accounting for students section by section on paper, with no live picture.
From incident to all-clear in under 30 minutes.
10:42 AM
Incident declared
Admin triggers an earthquake incident from the command center.
10:42 AM
Everyone notified at once
Push and in-app alerts reach all parents and staff — no phone trees.
10:45 AM
Roll call goes out
Staff and students check in safe; the status board fills in live.
11:10 AM
All-clear issued
Incident closed with a full record of who checked in and when.
Illustrative timeline of the built-in incident workflow.
How an emergency unfolds on Alpas
- 1
Declare the incident
One action from any authorized administrator — earthquake, typhoon, fire, or lockdown.
- 2
Everyone is alerted at once
Push and in-app notifications reach all parents and staff simultaneously.
- 3
Roll call collects check-ins
Staff and students report themselves safe; you watch the board fill in live.
- 4
Close with a record
Issue the all-clear with a complete, timestamped account of the incident.
Safety, every ordinary day too
Emergency broadcasting
Campus-wide incident alerts delivered over push and in-app channels at once.
Safety roll call
Live check-in status for staff and students during incidents and drills.
RFID gate logs
Entry and exit records for every student, every day, from campus gate scans.
Instant gate alerts
Parents get a notification the moment their child scans in or out of campus.
Absence auto-alerts
If a student is marked absent, parents know the same day — not at card day.
Class suspension notices
Weather announcements published once, delivered to every family's phone.
QR & RFID campus IDs
Cryptographically verified IDs power the gate system end to end.