Attendance & Time

How it is used

Staff punch in and out; the exceptions queue holds anything the system could not settle on its own — a missing clock-out, hours past the shift — and a month cannot be approved while one is open.

How it works, screen by screen

Every screen below is the real one, photographed from a working tenant, with the route it lives at so you can go straight to it.

1. 01

   See the floor as it stands

   /admin/attendance

   Who is in, who is late, who has not punched at all — today, not yesterday's export. The counts at the top are the board's own rows, so they agree with it by construction.

   
2. 02

   Every punch is kept

   /admin/attendance/time-logs

   Each punch and the hours it computes to stays on the record, with late, undertime, overtime and night differential worked out against the assigned shift. A correction is filed and adjudicated — never written over the original.

   
3. 03

   Settle what the system cannot

   /admin/attendance/exceptions

   A missing clock-out, or hours past the shift, lands in exceptions. A cutoff cannot be approved while one is open, which is the step that stops payroll running on a broken timesheet.

   

What it does

• Live daily attendance across the whole company
• Time logs with the full punch trail per employee
• Punch exceptions raised as they happen
• Correction requests filed by employees, routed for approval
• Overtime filing and approval before it is paid
• Timesheet review and lock per period
• Per-employee clock-on toggle owned by the company owner

Where to find it

How it connects to the rest

Nothing below is an integration to switch on. These are the same records, read and written by more than one module.