From a Week to a Day: How an 8-Branch School Group Automated Leave and Payroll

At a glance: An 8-branch school group in West Bengal, with 500+ staff across all locations, cut its monthly payroll cycle from about a week down to under a day — after connecting biometric attendance, leave management, and payroll into one system instead of three disconnected manual processes.

The setup

Running one school’s payroll is manageable by hand. Running eight branches — each with its own salary structures and its own biometric attendance machines that didn’t talk to any of the others — was a different problem. And the complexity didn’t stop at the branch level: within a single branch, teaching and non-teaching staff worked different shift timings, and holiday calendars varied by department rather than applying uniformly across the whole school.

That was the starting point: 8 branches, 500+ staff, shift rules that changed depending on staff category, holiday calendars that changed depending on department, and no single system tying attendance, leave, and payroll together.

The problem

Leave was entirely manual. Staff submitted leave requests by hand. Approvals happened by hand. There was no shared record of who was on leave, who had approved what, or how much leave balance anyone actually had left. Record-keeping was inconsistent branch to branch.

Payroll inherited all of that mess. At month-end, someone had to manually work out paid days for each staff member — cross-referencing biometric attendance against leave records against that person’s specific shift timing and department holiday calendar — before payroll could even be run. Multiplied across 8 branches, hundreds of staff, and varying salary structures, the process consumed the better part of a week, every month, with plenty of room for error along the way.

And once payroll was finally run, the paperwork was only getting started. Salary slips had to be printed and physically distributed to staff at every branch — its own recurring administrative task, every single month, on top of everything else.

What changed

The Staff Attendance and Leave Management System moved leave onto the platform, down to the shift and department level.

• Biometric attendance fed directly into leave calculations — no manual cross-referencing
• Shift timings were configured by staff category (teaching vs. non-teaching), not just by branch
• Holiday calendars were configured by department, so attendance and leave math reflected who actually had that day off — not a single blanket calendar
• Leave approvers were set per branch, matching the real approval chain instead of forcing everything through one central point
• Staff could see their leave balances automatically on the teacher app — no need to ask HR
• Leave requests, including document attachments, were submitted directly from the app
• Paid-days calculation became real-time instead of a month-end scramble

Payroll ran on top of the same data — automatically.

• Salary slips, salary registers, and bank instruction files were generated automatically
• Different salary structures across the 8 branches were handled without manual rework each cycle
• Payslips went straight to staff on the mobile app — no printing, no physical distribution, no chasing people down to hand over a slip

Because leave, attendance, and payroll became one connected system rather than three separate manual steps, there was no more collating, cross-checking, or paperwork at month-end.

The result

What used to take about a week came down to under a day.

The time saved wasn’t the only change. A real-time, auditable leave and attendance trail meant fewer disputes over paid days. And the paperwork that used to follow payroll every month — printing and distributing salary slips branch by branch — disappeared entirely, since payslips landed directly on staff mobile phones.

The same underlying principle — leave policy that runs on rules rather than memory — shows up differently elsewhere: see how a residential school in Siliguri configured blackout dates, leave quotas and sandwich-holiday rules into a single enforced rules engine. See how a reputed ICSE school ran 1,000+ annual admissions through one auditable pipeline, from application to first-quarter fees. See how a Kolkata residential school made hostel attendance verifiable with photo-checked roll call four times a day. See how a multi-branch Kolkata school tracked transport across owned and vendor vehicles with QR codes alone, at zero hardware cost. And 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 shift timings differ between teaching and non-teaching staff in Vawsum?
Yes. Shift timings can be configured by staff category, not just by branch, so attendance is measured against the correct working hours for each type of staff.

Can holiday calendars vary by department within the same branch?
Yes. Holiday calendars can be set at the department level, so a branch isn’t limited to a single blanket calendar for every staff member.

How does biometric attendance connect to leave and payroll?
Attendance data flows directly into leave balance and paid-days calculations, which then feed payroll — removing the manual cross-referencing that otherwise has to happen at month-end.

Can each branch have its own salary structure and payroll template?
Yes. Multi-branch organizations can run different salary structures and templates per branch within the same system, without manual rework each payroll cycle.

Who approves leave requests in a multi-branch setup?
Leave approvers can be assigned per branch, so approvals follow the school group’s real structure instead of routing everything through a single central approver.

See all case studies