Staff apply for leave from the Teacher App, and a manager approves it on the web portal or in the Owner App. Approved leave then feeds into the month-end salary calculation, so payroll reflects it.
How does staff leave work in EDUBase?
Leave Management in EDUBase starts with the staff member and ends with a manager's decision. Teachers and other staff with a Teacher App login apply for leave from their phone. The request then waits for a manager to approve it.
The leave feature sits inside Staff Management (HRM), next to employee profiles, shifts and the Teacher App login. Because everything is linked to the same employee record, the principal does not need to keep a separate register or a pile of paper applications.
How does a teacher apply for leave?
The teacher opens the EDUBase Teachers App on an Android phone and submits a leave application. The app is free, and the same app is where the teacher marks attendance, writes the diary and reads notices.
The teacher can only apply if the school has created a Teacher App login from the employee record in Staff Management (HRM). This is a one-time step that the office completes when the employee is set up.
- Create the employee profile in Staff Management (HRM).
- Create the Teacher App login from the same record.
- Assign classes and subjects where the teacher takes classes.
- Ask the teacher to submit leave requests from the app.
Where does the principal approve leave?
A manager can approve leave in two places: the web portal, or the EDUBase Owners App on Android. The Owners App lists employee leave among the approvals you can action on the phone, together with advance salary, increments, salary plans, student leave and diary approvals.
This is useful when the principal is away from the desk. A request can be decided the same day without waiting to be back at the office computer.
- On the web: use the Leave approval feature in Staff Management (HRM).
- On the phone: open the Owners App and go to the approvals for employee leave.
- Either way, the decision belongs to a person with the right to approve.
Who is allowed to approve, and how is it tracked?
EDUBase lets the school control who can see and do what. Rights are given per user, per screen and per action, so you decide which managers may approve leave and who can only view it. Leave is one of the items that can require a second person.
User Logging records who created, changed or deleted a record, in plain sentences with a severity badge. A daily summary of important changes reaches the navbar bell and the Owner App. If a dispute arises about a leave decision, you can check who acted and when.
How does approved leave affect attendance and salary?
Employee attendance and payroll are part of the same system. The month-end salary calculation uses attendance, leave, late arrival and lecture-based adjustments. Late arrival, short leave and absence feed the calculation automatically.
Employee Attendance also lets you lock a month once salaries are done, so nothing changes afterwards. The principal should therefore decide pending leave requests before the month is closed and payroll is run.
- Decide pending requests before month-end.
- Run the salary calculation.
- Lock the month in Employee Attendance once salaries are done.
Which approach to leave suits a school best?
Many schools still handle leave through paper notes or messages to the principal. The table compares these common approaches with a system-based workflow.
Common ways schools handle staff leave compared with an app-based approval workflow
| Approach | How leave is requested | How it is approved | Record and follow-up |
|---|---|---|---|
| Paper application | Staff write a note and hand it to the office | Principal signs the paper | Filed by hand; hard to search and easy to lose |
| Phone message | Staff send a message to the principal | Principal replies informally | Lives in a personal chat; the office may not see it |
| App-based workflow (EDUBase) | Staff apply from the Teacher App | Manager approves on the web portal or in the Owner App | Held against the employee record, with User Logging showing who acted and when |
Related modules
- Staff Management (HRM) — Employee records, shifts, documents, letters, leave and the Teacher App login, in one place.
- Employee Attendance — Daily or monthly staff attendance from the register, the app, QR or a device, locked once payroll runs.
- Payroll & Salaries — Salary plans, allowances, deductions, approvals, payslips and salary sheets, posted to the ledger.
- Owner Dashboard & Reports — Daily P&L, collections, attendance and strength at a glance, on the web and in the Owner App.
- Users, Privileges & Activity Log — Give each staff member exactly the screens and actions they need, and see who changed what.
- Daily Diary, Notices & Houses — Homework diary from the Teacher App, notices to parents, complaints handling and house system.