Academics & Learning

ID Cards

Design and issue student & staff ID cards with QR verification.

Get started Book a 20-min demo

Certificates issuedThis term

1,284Issued / term

9,742Verified

99.8%Valid

AprJunAug

Bonafide 48%Transfer 24%Character 16%Others 12%

Bonafide requests spike each admission season — pre-generating templates cut the counter queue in half.

Overview

ID cards sit at the boundary between your campus and the world, but most institutions manage them as a design file at a print shop: no record of what was issued, no way to invalidate a lost card, and no connection to who is actually enrolled. ID Cards in ez.school designs, issues and tracks cards against the live student and staff registers — with QR verification at the gate and instant revocation when a card should no longer work.

Template designer & ready-made layouts
Bulk photo upload & roll-forward
Print-ready multi-card PDF sheets
Issuance history for students & staff
Public QR verification

Case study · ID Cards

From a print-shop design file to a real credential

Representative scenario — illustrative

A 1,600-student school orders ID cards the way most do: a designer’s file emailed to a local print shop each July, with a name-and-photo list pasted from last year’s cards.

Doing it by hand

The list is never quite current — cards get printed for students who left and missed for those who joined mid-session. When a card is lost there is no record of what was issued, so nothing can be invalidated; the gate guard is left matching a face to a laminated photo and waving through anyone who looks about right. No one can say how many cards are out in the world.

The cheap-ERP trap

The cheap ERP added a card designer but nothing behind it — the QR, if there was one, resolved to nothing, so a card was still just a printed photo. It couldn’t revoke a lost card or tell issued from expired, and issuance ran off an uploaded list rather than live enrolment. Six months on it was easier to email the print shop again, so the school did.

With ez.school

ez.school designs, issues and tracks cards against the live student and staff registers. A card cannot be produced for a student who left, batch printing tracks exactly which cards are out, and each card carries a QR that resolves to valid, expired or revoked. A lost card is revoked in one action and fails at the gate that same day — the difference between a photo ID and an access credential.

The difference, side by side

	By hand	Ordinary ERP	ez.school
Who gets a card	Pasted list, out of date	Uploaded spreadsheet	Live enrolment register
A lost card	Nothing to invalidate	No revoke, stays valid	Revoked in one action
At the gate	Guard matches a face	A dead QR	Scan shows valid/expired/revoked
Cards in the world	Unknown count	Untracked print run	Every issue on record

The outcome

Same dayLost card stops working
Live registerNo cards for leavers
Every cardTracked and revocable

Screening coverageThis cycle

92%screened

1,842Screened
158Pending
46BMI flags
96%Vaccinated

92% screened this cycle; the 46 BMI flags are routed to counsellors — closing the loop, not just measuring.

Issuance coverage by class against live enrolment — the gaps are joiners still to be carded, not leavers still holding one.

Inside the app

How ID Cards works for you

Design once, issue against the register

Card designs are templates — photo, fields, colours, both sides — applied per class or role. Issuance runs against current enrolment, so a card cannot be produced for a student who left, and batch printing tracks exactly which cards are out in the world.

Utilization & capacityThis week

96%Peak load

84%Avg capacity

3Idle units

7a10a1p4p7p

Load by hourCapacity

Route 1292%
Block A84%
Lab wing91%
Library68%

Two peaks hit 96% while the library sits at 68% — shift a session to smooth load and defer buying new capacity.

A card that can be checked, and cancelled

Each card carries a QR resolving to a verification page: valid, expired or revoked. A lost card is revoked in one action and fails at the gate immediately — the difference between a photo ID and an access credential.

Screening coverageThis cycle

92%screened

1,842Screened
158Pending
46BMI flags
96%Vaccinated

92% screened this cycle; the 46 BMI flags are routed to counsellors — closing the loop, not just measuring.

The cycle

The card lifecycle

1Design template
2Generate for class/staff
3Print batch
4Verify at gate
5Revoke & reissue when needed

Who uses it

One app, seen from every seat

Admin officeProduces a class set in one batch — photos, fields and serials handled.

Gate securityScans a QR and sees valid, expired or revoked — no judgement calls.

ParentA lost card stops working the day it’s reported, not the day it’s found.

Evaluation questions

ID Cards — asked and answered

Can we design our own card layouts?

Yes. The designer controls both sides — photo, institution branding, fields, QR placement — with separate designs per role or class where needed.

What happens when a card is lost?

Revoke it. Verification fails immediately for the old card, and the reissued card carries a fresh QR. The issuance record keeps both events.

Does verification expose student data?

No. The public verification page confirms validity and identity essentials only, is bound to your institution, and is rate-limited against scraping.

Same pillar

Bring ID Cards to your campus

Guided onboarding, local-currency pricing, and human support from day one.

Get started View pricing