Attendance workflow
Try this experience Attendance machines
Connect a biometric or card machine with a serial number and connection key.
Attendance machines in LiveSchools365 Attendance
Attendance machines is a Attendance workflow in the Daily operations area of LiveSchools365 school management software. Connect a biometric or card machine with a serial number and connection key. 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
- Student or staff machine This sits inside Attendance rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- One connection per machine This sits inside Attendance rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Existing marks stay in place 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 Attendance machines:
- Attendance dashboard — Review daily, monthly, and annual attendance position.
- Student attendance — Mark one absent student from any class, or load a section register.
- Leave types — Define the leave reasons used when a student or staff member is not present.
- 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.
Register machineDialog · Input
- Purpose
- Name the machine, choose its campus, and choose whether it is for students or staff.
- Rules
- The serial number is required and can be used only once.
- Application effect
- The machine appears in the list with a connection key.
ConnectionCopy block · Output
- Purpose
- Give the machine vendor the push address, the serial number, and the connection key.
- Rules
- A student machine uses the student code. A staff machine uses the staff code or biometric code.
- Application effect
- A new punch marks that person Present. A day already marked is left unchanged.
New keyRow action · Input
- Purpose
- Replace the connection key when it has been shared too widely.
- Rules
- Update the machine with the new key. The previous key stops working.
- Application effect
- Later punches use the new key.