Time & Attendance

Overview

What it solves

Paper sheets and fingerprint exports are reconciled by hand every month, and lateness is argued about.

Why it helps

• Employees check in from the dashboard; the company chooses whether location is ignored, flagged or enforced. Managers and HR staff can check in too.
• Punches, lateness and “today” are judged on the company’s own clock, and night shifts close with the morning punch.
• Shifts with grace periods decide who is late; people without a shift follow the company work schedule.
• Attendance for a month locks once that month’s payroll is finalized.

Used by

HR AdminManagerEmployee

Availability

Every plan

123

1. 1Record a punch on someone’s behalf
2. 2Review correction requests
3. 3Flagged attendance patterns

Quick answers

What you can do

• Self check-in from the dashboard
• Company clock: times, lateness and “today” follow the company timezone
• Night shifts: a check-in after midnight closes the previous day’s shift
• Company work schedule: working days, default hours, grace, night shift and timezone
• My schedule: your working hours for the next two weeks
• Geofence policy: off, flag or block
• Work locations with latitude, longitude and radius (10 m – 100 km)
• Shifts with start/end time, grace minutes, working days, overnight shifts
• Shift assignments, bulk assign and day overrides
• Daily attendance with Present / Absent / Late / On leave counts
• Monthly attendance report with Excel export
• Manual punches with a mandatory reason
• Attendance correction requests (employee asks, HR answers with a reply)
• Unusual patterns (AI anomalies)
• Import punches from a file
• Punches blocked for a month whose payroll is finalized

Screens

123

1. 1Record a punch on someone’s behalf
2. 2Review correction requests
3. 3Flagged attendance patterns

123

1. 1Latitude of the office (from a map pin)
2. 2Longitude of the office
3. 3How far away an employee may still check in

12

1. 1Check in for the day
2. 2Ask for time off

1

1. 1Fix a missed or wrong punch

Workflows

Self check-in with geofence

flowchart TD
  A[Employee taps Check in] --> A2{Same punch in the last 60 s?}
  A2 -- yes --> OK0[Returns the same punch]
  A2 -- no --> A3{Approved full-day leave?}
  A3 -- yes --> X2[Refused: on leave]
  A3 -- no --> B{Month payroll finalized?}
  B -- yes --> X[Refused: period locked]
  B -- no --> C{Geofence policy}
  C -- off --> OK[Punch saved]
  C -- flag / block --> D{Location shared?}
  D -- no --> Y[Refused: location required]
  D -- yes --> E{Inside a work location radius?}
  E -- yes --> OK
  E -- no, flag --> F[Saved, marked outside fence for HR]
  E -- no, block --> Z[Refused: N m away from site]

• Lateness is judged against the assigned shift and its grace period, on the company’s own timezone.
• On a night shift, the morning punch closes the shift that started the evening before.
• Tapping Check in twice within a minute does not create a second punch, and you cannot check in on a day of approved leave.

Attendance correction request

flowchart LR
  A[Employee: Request correction with a note and proposed times] --> B[Pending · HR and line manager notified]
  B --> C{HR answers}
  C -- Approve --> D[Proposed times applied as manual punches]
  C -- Reject + reply --> E[Rejected with the reply]
  D --> F[Employee notified]
  E --> F

• HR approves the request, optionally with the corrected times, or rejects it with a reply.
• You are told the answer, and a month whose payroll is finalized cannot be changed.

How-to guides