Edu360
Connect
CappsAI StudioProduct · Edu360 · By CappsAI Technology Private Limited · Published Sep 19, 2026 · Updated Oct 9, 2026
School leave management covers two workflows: staff and teacher leave (applying against a leave policy and getting approval from a reporting manager) and student leave (a parent's request approved by the school). Both should end in the same place: an approved record that shows correctly in attendance and, for staff, in payroll. Leave management sounds simple until it's a paper note that never reaches the right person. Here is the workflow in Edu360.
Teacher and staff leave
1. The leave policy
The school sets up leave types (for example casual or sick leave) and a yearly quota for each. Every staff member's page names their reporting manager, so requests always have somewhere to go.
2. Applying
A teacher or staff member opens My Leave on the web or mobile app, chooses the leave type, from and to dates and a reason, and submits. The request and its status appear on the same page, and a pending request can be cancelled.
3. Approval
The request goes to the person's reporting manager, with an optional skip-level approver. The approver sees it under My Approvals and approves, rejects or returns it with a remark. The applicant is notified of the decision.
4. Attendance and payroll
Approved leave shows on the staff attendance calendar. Leave taken beyond the quota is marked as loss of pay, which payroll uses, so nobody has to reconcile a leave register with salary by hand.
Student leave
A request, not a note
Instead of a paper note or a message in a WhatsApp group, a parent submits a leave request from the parent app: which child, the dates and the reason. It's logged against that student's record, not left to be remembered.
Routed to the right approver
The request goes to the school's Student Leave Approver, who approves or rejects it. There is no step where someone has to forward or re-type it from a register, and the parent is notified of the decision.
Reflected correctly in attendance
On the day, the student can be marked as on leave rather than appearing as an unexplained absence. This is why leave and attendance management are connected modules in Edu360, not two separate systems that need reconciling.
Who approves what
| Request | Raised by | Approved by |
|---|---|---|
| Staff or teacher leave | The employee | Their reporting manager (optional skip-level approver) |
| Student leave | Parent | Student Leave Approver |
| Staff attendance correction | The employee | A user with attendance approval permission |
| Loan or salary advance | The employee | Their reporting manager |
Which roles may approve is set by the school under roles and permissions, so a large school can delegate approvals while a small one keeps them with the principal.
Frequently asked questions
How does teacher leave management work in a school ERP?
Teachers apply against leave types with yearly quotas, the request goes to their reporting manager for approval, and approved leave flows into attendance and payroll automatically.
Can leave be applied from a phone?
Yes. In Edu360, staff apply for and approve leave in the mobile app, and parents apply for a student's leave from the parent app.
What happens when a teacher exceeds their leave quota?
The extra days are marked as loss of pay, which payroll uses when calculating salary.
Related: teacher management software and what a school ERP is.