Attendance workflow
Try this experience Leave types
Define the leave reasons used when a student or staff member is not present.
Leave types in LiveSchools365 Attendance
Leave types is a Attendance workflow in the Daily operations area of LiveSchools365 school management software. Define the leave reasons used when a student or staff member is not present. Schools use it so Reliable registers and clearer attendance accountability.
Record and review daily student attendance by campus, grade, section, and status. 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
- Present stays built in This sits inside Attendance rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Edit and delete unused types This sits inside Attendance rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Types already used on attendance stay unchanged This sits inside Attendance rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
How it fits the rest of Attendance
Open these related Attendance guides when you want the step before or after Leave types:
- Attendance dashboard — Review daily, monthly, and annual attendance position.
- Student attendance — Mark one absent student from any class, or load a section register.
- Attendance machines — Connect a biometric or card machine with a serial number and connection key.
- Staff attendance — Mark staff for a campus and day, including punches from a staff machine.
- Student attendance analysis — Compare grade and section attendance, then open the students behind an absent percentage.
- Staff attendance analysis — Compare each staff member's attendance 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 Attendance 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.
Leave type nameText · Input
- Purpose
- Type the reason, such as Sick or Casual.
- Rules
- The name is required. A name already used on attendance stays as it is.
- Application effect
- The name appears on Student Attendance and Staff Attendance.
Edit and deleteRow actions · Input
- Purpose
- Change or remove a leave type that has never been used.
- Rules
- If the type is already on a student or staff mark, the form explains that and leaves it unchanged.
- Application effect
- Unused types can be renamed, made inactive, or deleted.