Operations
Staff leave and HR basics
Run staff leave against the academic calendar, keep entitlement balances honest, and see where leave, hiring, and payroll touch each other.
Operations guide for day and boarding schools.
Last updated August 29, 2026
Staff leave sits at the junction of three modules. It draws its working-day arithmetic from the academic calendar, it feeds the timetable by generating substitute cover on approval, and it feeds HR reporting through entitlement balances. Treating it as a standalone form is the usual mistake: approve leave before the calendar is synced and the balance deduction and the cover rows are both wrong.
The hiring side is deliberately separate from student admissions. Job postings are created in the HR area and published to a public careers board that needs no login; applications arrive against the posting, and an accepted candidate is onboarded into a staff user and staff record rather than being retyped into the roster.
Where the work happens
| Area | Route | Who |
|---|---|---|
| Apply for and approve leave | /leave | Any staff member applies; Admin or leadership approves |
| Job postings and applicants | /hr/careers | HR and leadership |
| Public job board | /careers | Candidates, no sign-in required |
| Staff roster and employment records | /school-staff | HR and leadership |
| Salary runs, components, payslips | /payroll | Payroll administrators; finance may view and export |
What approval triggers
- Working days in range are computed and deducted from the entitlement balance for that leave type
- The teacher is written into the on-leave records the timetable reads
- If a substitute was named, confirmed cover rows are created for every published period on each working day
- Rejecting or cancelling the leave cancels those cover rows rather than deleting them
Handoff
Leave is the busiest crossing point in the product. It reads the academic calendar for working days, writes to the timetable as substitute cover, and reports back into HR as an entitlement balance. Hiring crosses in the other direction: onboarding an accepted candidate creates the staff user and staff record that leave, timetable assignments, and payroll all subsequently depend on, so a rushed onboarding shows up weeks later as a teacher who cannot be assigned a class.
Limits
- There is no multi-level approval chain; one approver decides
- Leave does not clock hours or integrate with biometric attendance devices
- Entitlement defaults are configured centrally rather than negotiated per contract
Common questions
Quick answers in plain language.
Is leave counted in calendar days or working days?+
Working days. Weekends and holidays inside the leave range are excluded, using the same academic calendar that drives attendance and exams, so an unsynced holiday will overcount someone leave.
Who can approve staff leave?+
Admin, Principal, or Vice Principal. A teacher may edit or withdraw their own request while it is still pending, and may view only their own leave records.
Which leave types are supported?+
A fixed Indian school set: casual, earned, sick, maternity, paternity, special casual, compensatory, child care, half pay, extraordinary, duty, leave without pay, and other. Half-day leave can be marked as first or second half.
Can staff see their own payslips?+
Yes, staff accounts can open their own payslip. Managing payroll runs, salary structures, and statutory processing is limited to payroll administrators, with finance roles able to view totals and export.
Related searches
School leaders and IT teams often search for: teacher leave approval, and school HR module.