Case study

A residential school halved leave-pass processing time across 7 hostels

Type Residential K-12 school
Board / affiliation CBSE
Students 1 200
Staff 180
Region Tier-2, Northern hills
Footprint Boarding · 7 hostels · single mess
Modules deployed:HostelMessCommunicationAttendanceParent-App

The school in one line

A 1 200-student residential school in the northern hills, with 7 hostels (4 boys', 3 girls'), a single shared mess, and a parent base spread across 14 Indian states + 6 countries.

The before

Weekend leave-pass processing was the worst job in the school. Every Saturday morning:

  1. A student would fill in a paper leave-pass form, get the warden's signature, get the housemaster's signature, hand it to the gate.
  2. The gate would call the parent to verbally confirm the leave. If the parent didn't pick up, the leave was denied.
  3. The form was filed; on Monday someone retyped it into a spreadsheet.

Where it broke:

  • 4 hours per warden per Saturday doing leave-pass approvals (across 7 hostels = 28 hours total)
  • 15% of leaves rejected because the parent didn't pick up the phone in time
  • No audit trail when a student came back late — was the parent really informed?
  • Mess head-count was always wrong on Sundays because nobody re-counted who'd gone home

What we changed

In 8 weeks:

  • Hostel module — student-room mapping, warden assignments, leave-pass workflow built around the parent's pre-approval, not the gate's verbal confirmation
  • Mess module — daily attendance auto-derived from hostel + leave-pass data; vendor billing accurate to the meal
  • Parent app — parent receives a "Leave request from your child" push, taps Approve/Reject. Done in 15 seconds, from any country, on a metro ride.
  • Communication engine — fallback ladder for parents without the app: WhatsApp first, SMS second, email third. Quiet hours respected (no leave requests sent at 11 PM IST when half the parents are in different time zones).

The after

Metric Before After
Warden time per Saturday 4 hours/warden 90 minutes/warden
Leaves rejected for un-reachable parents 15% 2%
Mess head-count accuracy (weekends) ~70% ~98%
Time from student request → parent approval (median) 6 hours 11 minutes
Audit-traceable parent approvals 0% 100%

The mess vendor noticed first. Their per-meal billing started reconciling to the rupee. They stopped padding their invoices because they couldn't get away with it any more.

"On a Saturday morning I'm now in the field with the kids instead of pushing paper. That changed the school."
— Senior Warden (Boys' Hostel 2)

What we'd do differently

We tried to ship the parent-app fallback ladder (WhatsApp → SMS → Email) as one feature. Parents who'd never been on the app got 3 messages in 5 minutes and called the school confused. Roll out fallback ladders gradually — one fallback channel per week, with parent-facing communication explaining the new approval flow.

Also: international parents have a 5.5-12 hour time-zone offset from the school. Quiet hours per parent (not per tenant) would have helped — instead we conservatively suppressed all leave requests between 11 PM and 7 AM IST, which delayed some weekend leaves. Per-parent timezone preferences are on our 2026 roadmap as a result.


Run a residential school? Talk to us — we know the leave-pass workflow inside out.

Want a similar rollout plan for your school?

30-minute walk-through tailored to your size and your board.

Request a demo