Leave Management workflow
Try this experience Leave Type Definition
Define each leave type once, including the register letter, who it applies to, and the approval path.
Leave Type Definition in LiveSchools365 Leave Management
Leave Type Definition is a Leave Management workflow in the Daily operations area of LiveSchools365 school management software. Define each leave type once, including the register letter, who it applies to, and the approval path. Schools use it so Clear leave position, controlled approvals, and auditable absence decisions.
Manage staff and student leave through dedicated request, balance, evidence, and approval workflows. The people who typically work here are Teacher, Administrator, Principal, Staff. The rest of the module stays one click away, so an inquiry, register, invoice, or stock movement does not have to be re-typed into another product.
What this workflow changes
- One definition for student and staff requests This sits inside Leave Management rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Register letter and balance rules This sits inside Leave Management rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Active types appear on the request This sits inside Leave Management rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
How it fits the rest of Leave Management
Open these related Leave Management guides when you want the step before or after Leave Type Definition:
- Leave management dashboard — Open staff and student leave operations from one module dashboard.
- Leave count — Count leave by type for one section, then open the students and requests.
- Student leave register — Read a full month for one section, with students on one line and the days across the top.
- Staff leave register — Read a full month for one campus, with staff on one line and the days across the top.
- Student leave analysis — Compare leave percentages by grade and section, then open the students behind an absent percentage.
- Staff leave analysis — Compare each staff member's leave for the selected period.
How schools evaluate this screen
During a demonstration or trial, Teacher, Administrator, Principal, Staff should complete one realistic example: a new inquiry, a section register, a fee receipt, a notice, or a stock issue, depending on the module. Then confirm that the same record appears on the dashboard, the related report, and the next workflow. That is the test of a school ERP: one operational picture instead of parallel files.
Trend Developers can walk this exact screen against your admission, attendance, exam, or fee process. You can also start a 14-day trial and use the matching live form after sign-in.
All Leave Management workflows · Start a trial · View pricing · Request a demonstration
Guide depth
Interface
Fields, controls, and effects
Use this reference to understand what each area accepts and what it changes.
Code and nameText · Input
- Purpose
- Give the type a short code and the name people see on a request.
- Rules
- Both are required.
- Application effect
- The name appears on student and staff leave requests.
Register letterOne letter · Input
- Purpose
- Enter the letter the leave register shows, such as S for Sick Leave.
- Rules
- The letter is unique. P is reserved for Present.
- Application effect
- The leave register prints that letter in red.
PolicyApplies to, balance, evidence, approval · Input
- Purpose
- Choose students, staff, or both. Set pay, annual balance, evidence, and HOD, HR, or Principal review.
- Rules
- A balance-tracked type needs annual days.
- Application effect
- Leave Entitlement then assigns those days to a designation.
Edit and inactiveRow actions · Input
- Purpose
- Change a type or make it inactive.
- Rules
- An inactive type stays on requests already saved.
- Application effect
- New requests use the active types.