A school runs two workforces on one campus: teaching staff on an academic calendar, and non-teaching staff on an ordinary one. Most HR problems come from trying to run both on the same rules.
The academic calendar is the system of record
Set vacations, examination periods and holidays once, and let leave accrual, attendance and payroll read them. Otherwise every August someone recalculates balances by hand.
HR, GPS attendance, shifts, leave, payroll, tax declarations, onboarding, engagement, projects and timesheets — one employee record behind all of it.
Start free See the demoWhat a school HRMS must handle
- Teaching and non-teaching policies that differ.
- Period-level absence, so substitution can be arranged.
- Leave accrual across an academic year, not a financial one.
- Payroll with PF, ESI and professional tax in the same run.
- Staff development records, because accreditation asks for them.
How MizUp BMS handles it
MizUp BMS keeps employee management, attendance, shifts, leave and holidays, payroll with tax and loans, onboarding and engagement on one record. Holiday calendars are set per group, so teaching and non-teaching staff can accrue leave on different rules without two systems.
Students, fees and attendance run in MizUp EOS on the same organisation, so a staff member who also teaches a course is one person in one place. Fee collection and vendor billing sit in MizUp Finance.
What it costs
From Rs 79 per employee per month. See BMS pricing.
Where to start
Load the academic calendar first. Everything downstream depends on it. Explore MizUp BMS.
Where schools usually go wrong
- Running staff on the student system. Student software is built around students. Payroll, statutory deductions and leave accrual need an HR system, and forcing them into an SIS creates a spreadsheet within a term.
- One leave policy for teaching and non-teaching staff. Their calendars are genuinely different. Forcing one policy produces exceptions that live outside the system.
- Leave approved without seeing periods affected. A teacher absent on Thursday is four uncovered periods. If the approver cannot see them, substitution becomes a Thursday-morning scramble.
- Recalculating leave balances each August. If the academic calendar is not the system of record, someone rebuilds balances by hand every year.
- Staff development records in a folder. Accreditation asks for them, usually at short notice.
- Payroll assembled from three sources. Attendance from a register, deductions from a chartered accountant, and salaries from last month’s spreadsheet.
A realistic first thirty days
| Week | Focus | What good looks like |
|---|---|---|
| Week 1 | Academic calendar | Vacations, examination periods and holidays loaded first. Everything else reads from this. |
| Week 2 | Staff groups | Teaching and non-teaching loaded with their own policies and accrual rules. |
| Week 3 | Leave with period visibility | Approvals show the periods affected so substitution is arranged at the time. |
| Week 4 | Payroll in parallel | One cycle alongside the existing process, then cut over. |
Load the academic calendar before anything else. Every leave, attendance and payroll number in a school is derived from it, and loading it late means loading everything twice.
The numbers worth watching
| Metric | Why it matters | How to read it |
|---|---|---|
| Uncovered periods per week | The operational number that matters on a Monday | Counted from the timetable, not estimated. |
| Substitutions arranged in advance | Whether the process is working | Share arranged before the day versus on the day. |
| Leave balance disputes | Data quality, seen from the staff side | Should fall to near zero after one academic year. |
| Payroll adjustments per cycle | How clean the inputs are | Manual corrections per hundred staff. |
| Staff training current | What an inspection asks for | Share with in-date mandatory training. |
Two calendars, one school
The recurring difficulty in school HR is that the institution runs on an academic year while payroll and statutory compliance run on a financial one. Most systems handle one well and force the other into it.
The workable answer is to keep the academic calendar as the source of truth for leave, attendance and substitution, and let payroll read from it rather than from a parallel register. Once that is set, the August recalculation disappears and nobody has to remember how last year worked.
The second recurring difficulty is that teaching staff resist systems that feel like surveillance. Framing matters here: publishing the timetable and making substitutions visible helps teachers more than it helps administration, and that is worth saying out loud during rollout.
Schools that introduce it as a scheduling tool rather than an attendance tool tend to get far better adoption, and the attendance data follows anyway.
How this fits with the rest of your stack
A school is one organisation with two record sets that must not be confused: students and staff. Most institutions end up with two vendors and a manual bridge between them.
On MizUp, BMS holds the staff record, attendance, leave against the academic calendar, payroll and statutory deductions, while EOS holds students, fees, attendance, exams and certificates. A member of staff who also teaches a course is one person in one organisation.
CRM works the admission enquiries and CLM carries parent communication on the official WhatsApp Business API, all under the same access rules.
A note on rollout timing
Schools have exactly two sensible windows for changing an HR system, and neither of them is the middle of a term. The first is the long vacation, when the academic calendar for the coming year is being set anyway and nobody is teaching. The second is the start of a financial year, when payroll is changing regardless.
Trying to move in October produces the worst of both: teachers learning a new system during an examination cycle, and an accountant reconciling two payroll formats for the same year.
If the decision is made mid-term, the practical compromise is to load the calendar and staff records immediately, run leave and attendance from the new system from the next term, and move payroll at the financial year boundary.
That sequencing costs nothing and removes almost all of the risk.
Related reading
- School management software in India
- Attendance and leave management systems
- Payroll process in India, step by step
- College ERP software in India
Frequently asked questions
Why not use the school management software for staff too?
Student systems are built around students. Staff payroll, statutory deductions and leave accrual need an HR system. MizUp keeps them as two products on one employee and student record set, so nothing is typed twice.
How does substitution work when a teacher is absent?
Leave approval should show the periods affected so a substitution can be arranged at the time, not discovered in the morning.
Can it handle the academic calendar?
Yes - holidays and vacation periods are set once and leave accrual, attendance and payroll all read the same calendar.
Does it cover non-teaching staff?
Yes, with their own shift patterns and leave policy on the same system.
Is training and compliance covered?
Staff development and mandatory training can run as courses in [MizUp EOS](/lms) against the same employee record.
