Attendance workflow
Try this experience Late days
List students or teachers who were late on at least the chosen number of days.
Late days in LiveSchools365 Attendance
Late days is a Attendance workflow in the Daily operations area of LiveSchools365 school management software. List students or teachers who were late on at least the chosen number of days. 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
- Campus, dates, and minimum late days This sits inside Attendance rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Student code, name, grade, section, and late days This sits inside Attendance rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Teacher code, name, designation, and late days 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 Late days:
- Attendance dashboard — Review daily, monthly, and annual attendance position.
- Student attendance — Mark one absent student from any class, or load a section register.
- Campus hours — Set the campus start and end time used to decide who is late. Each change is kept.
- Late arrivals — See students or staff who arrived after the campus start time.
- Late register — A year of late arrivals by grade and section. Open a count to see the students, then a month count to see each arrival time.
- Attendance machines — Connect a biometric or card machine with a serial number and connection key.
- Staff attendance — Record staff time in and time out for a campus and day.
- Attendance terminal — A teacher types an ID and presses Enter. The clock time is saved as the arrival.
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.
Who / campus / dates / late daysFilters · Input
- Purpose
- Choose students or teachers, the campus, the period, and the minimum late days.
- Rules
- The period can be up to one year. The default is 3 days.
- Application effect
- A late day is an arrival after the campus start that covered that date.
GridList · Output
- Purpose
- Students show code, name, grade, section, and late days. Teachers show staff code, name, designation, and late days.
- Rules
- The list is ordered with the most late days first.
- Application effect
- Use it when deciding a student fine or a teacher salary deduction.
PrintCommand · Output
- Purpose
- Open the browser print dialog for the list currently on screen.
- Rules
- Show the list first. Print is available when at least one person is listed.
- Application effect
- The printed page names the campus, dates, and late-day rule for Finance.