From gate slips to a perimeter you can prove
Representative scenario — illustrativeA 1,600-student day school runs its gate on paper: visitors sign a register, early-exit passes are a scribbled chit, and walk-in admission enquiries go onto a notepad by the desk.
Nobody can say who is on campus right now without a physical round. A child once left with the wrong relative because the chit was never checked against the guardian. And walk-in enquiries — families ready to admit — evaporate somewhere between the notepad and the admissions clerk.
The cheap ERP digitised the visitor book and stopped there: check-ins on a screen, but gate passes still do not verify the guardian, and enquiries land nowhere near admissions. Six months in, reception keeps a parallel diary for couriers and enquiries, security still walks a round to know who is inside, and the leaked enquiries never surface anywhere.
ez.school makes the desk feed the school. Visitors badge in against purpose and host, so “currently inside” is a glance; gate passes verify the recorded guardian and the authorising staff before the gate opens; and walk-in enquiries drop straight into the admissions pipeline, captured once.
| By hand | Ordinary ERP | ez.school | |
|---|---|---|---|
| Who is on campus | A headcount, or a guess | Screen log, no live view | Currently-inside at a glance |
| Early exit | Unverified chit at the gate | Logged, guardian not checked | Recorded guardian verified first |
| Walk-in enquiry | Notepad, often lost | Captured but siloed | Straight into admissions pipeline |
| Couriers & dispatch | Parallel gate diary | Not handled | Logged with recipient and time |
- At a glanceWho is inside
- VerifiedGuardian before exit
- None lostEnquiries to admissions
94% clear within SLA; the slow 5%+ tail is all police-verification cases — track those on a separate clock.
Enquiry-to-admissions turnaround — a walk-in captured at the gate reaches an admissions officer the same day, not a notepad no one reads.