Unknown balances
Staff argue about remaining CL/EL with no shared ledger.
Apply, approve, balance — leave that payroll and substitutes can trust
Leave Management gives every employee a clear balance, a simple request flow, and approvals that update calendars and optional LOP for Faculty Payroll.
Balances
by leave type per employee
Approvals
with manager/HR routing
Calendar
views for teams and substitutes
The problem
Why leave still happens on WhatsApp
Verbal approvals create no balance truth, no substitute plan, and no payroll accuracy.
Approval fog
A yes in chat never reaches HR or the timetable.
Substitute scramble
Classes discover a missing teacher at the first period.
Payroll surprises
Unpaid leave is discovered after salaries are paid.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Leave types & policies
CL, EL, SL, LOP, and institution-specific codes.
Self-serve apply
Employees request dates with optional attachments.
Approval workflow
Route to reporting manager and/or HR.
Balance ledger
Accrual, usage, and carry-forward rules.
Team calendar
See who is out for substitute planning.
Timetable awareness
Flag teaching conflicts for academic coordinators.
Payroll hooks
Push unpaid/LOP into Faculty Payroll runs.
Holiday respect
Honor Academic Calendar non-working days in calculations.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Apply
Staff submits leave type, dates, and reason.
-
02
Approve
Manager/HR accepts, rejects, or asks for changes.
-
03
Publish
Calendar and substitute views update.
-
04
Settle
Balances adjust; LOP feeds payroll when applicable.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
Employee
Requests leave and tracks remaining days.
Manager / HOD
Clears team requests with calendar context.
HR
Owns types, accruals, and exceptions.
Academic coordinator
Plans substitutes against approved absences.
Connected stack
Works with the modules you already need
Each module is an edge in the campus operating graph — not a silo.
Outcomes
What changes after go-live
Measurable ops wins institutions report once this module runs inside ScholarERP.
Transparent
balances for every employee
Fewer
surprise teacher absences
Accurate
LOP in the next payroll run
“Substitutes stopped being a morning surprise — approved leave was already on the team calendar.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Can different roles have different leave policies?
Yes. Configure accruals and entitlements by employee category or role.
Does leave auto-update the timetable?
It surfaces approved absences for coordinators; substitution assignment still uses Timetable Scheduler workflows.
How does unpaid leave reach payroll?
Approved LOP/unpaid codes can reduce the Faculty Payroll period when mapping is enabled.
Are holidays counted as leave?
Calculations can exclude Academic Calendar holidays and weekly offs per your policy.
Apply and approve a sample leave in the demo
See balances, calendar impact, and payroll LOP linkage.