The Leave Rules a Residential School Couldn’t Afford to Get Wrong

At a glance: A residential school in Siliguri needed leave management that enforced its own operating rules automatically — no staff leave on session-opening days or exam days, holidays sandwiched between leave days counted as leave, and a hard cap on how many staff could be off on any single day. Vawsum configured this as a rules engine, so the policy now runs the same way every time, without depending on whoever happens to be approving that day.

The setup

A residential school runs on a tighter margin for absence than a day school does. Staff aren’t just teaching a class — many are also responsible for boarders outside class hours, which means a gap in staffing doesn’t just mean a substitute is needed, it means supervision itself is short. On top of that, certain days genuinely cannot run with reduced staff: the day the session opens, examination days, and other fixed points on the calendar where the school simply cannot absorb planned absence.

The school had built these constraints over years of running as a residential institution. The problem was that none of them lived anywhere except in the judgment of whoever was approving leave that day.

The problem

Leave approval depended on the approver remembering the rules, not the system enforcing them. No planned leave on session-opening day. No planned leave during exams. A cap on how many staff could be off at once institution-wide, because supervision and academic coverage couldn’t drop below a certain level. A sandwich-holiday rule, where a holiday falling between two approved leave days should count as leave rather than being treated as a free day off. None of this was written into any system — it depended on someone catching the conflict before approving.

That’s a fragile way to run policy. An approver who forgot the exam-day restriction, or who wasn’t aware the institution-wide cap had already been hit, could approve a request that shouldn’t have gone through. The rules existed; enforcing them consistently, every time, regardless of who was approving, did not.

What changed

Vawsum’s Staff Attendance and Leave Management System already runs on the principle that leave policy should be tested when a request is raised, not interpreted when it reaches an approver. For this school, that engine was configured around their specific constraints:

• Blackout dates were set for session-opening day, examination days, and other fixed dates the school specified — leave requests for those dates are stopped before they reach an approver, not declined one by one after the fact
• An institution-wide daily leave quota caps how many staff can be on leave on any single day; once that cap is reached, further requests for that date are stopped automatically
• Sandwich-holiday treatment was configured so that a holiday falling between two approved leave days is counted as leave rather than excluded from the charge — a stricter rule than the module’s default, applied specifically to this school’s policy
• Every one of these checks runs at the point the request is submitted, not at the point someone reviews it — so an approver is making a decision on requests that are already compliant, rather than auditing each one against a mental checklist

The result

The leave management engine stopped being person-driven and became rules-driven. The policy the school had always intended to run — no leave on session-opening or exam days, holidays sandwiched between leave counted as leave, a hard ceiling on same-day absence — now enforces itself the same way every time, regardless of which approver is on duty or how well they remember the exceptions.

That consistency matters more for a residential school than it would elsewhere. Supervision coverage isn’t optional, and getting it wrong isn’t just an academic-scheduling problem — it’s a duty-of-care one. Rules that used to depend on memory now run automatically, every time.

The same rules-driven approach is reshaping other parts of Vawsum’s leave and payroll stack — see how one 8-branch school group cut its payroll cycle from a week to under a day once attendance, leave and payroll stopped being three disconnected manual processes. The same principle — separate manual steps replaced by one connected, auditable system — also shows up in admissions: see how a reputed ICSE school ran 1,000+ annual admissions through a single pipeline, from application to first-quarter fees. See how a Kolkata residential school made hostel attendance verifiable, with a photo-checked roll call four times a day. See how a multi-branch Kolkata school tracked transport with QR codes alone, at zero hardware cost across owned and vendor vehicles. See how a Bengali-medium school with zero computers went digital using nothing but phones — a path many schools across India are still on today. See how a CBSE school in Siliguri fixed chronic late fee payment by linking admit card downloads to a fee-clearance cutoff, without ever publicly denying a student entry to an exam. And see how a West Bengal Board school in Burdwan district replaced informal cash and screenshot-based collection with a fully auditable, access-controlled fee system, how a Jalpaiguri school rebuilt its annual ID card renewal around class-teacher photo capture and parent self-service updates, cutting weeks of vendor work down to two days, and how a Kolkata-area school with 100+ teachers replaced its daily substitute scramble with rule-based, auditable allocation.

FAQs

Can leave be blocked entirely on specific dates, like exam days or session opening?
Yes. Restricted and blackout dates are configured in advance — examination and invigilation days, the day the institution reopens after a vacation, results day, or any other fixed date — and requests for those dates are stopped at the point of application rather than declined individually by an approver.

Can the school set a maximum number of staff who can be on leave on any given day?
Yes. A daily leave quota can be set for the institution. Once the number of staff already on approved leave for a date reaches that limit, further leave applications for that date are stopped automatically.

Can a holiday that falls between two leave days be counted as leave rather than excluded?
Yes, as a configurable rule. By default, weekly offs and holidays falling within a leave period are excluded from the chargeable leave count. Where a school’s policy requires the stricter sandwich-holiday treatment — counting an in-between holiday as leave — that can be configured to match.

Does this replace the approver’s judgment entirely?
No. The rules run before a request reaches the approver, so the approver isn’t deciding whether a request breaks policy — that’s already been checked. What they’re deciding is the same judgment call they’d make anyway, just without needing to separately track blackout dates, quotas, or sandwich rules in their head.

See all case studies