Four punch sources.
One timeline.
A factory floor uses a device. A field team uses the phone. Head office signs in from a browser. Someone always forgets, and that becomes a regularisation with an approver. All four arrive on the same timeline, each read on the clock of the office it happened in, and payroll reads that timeline rather than a summary someone typed.
The four sources
Different people, different doors, same record.
Most attendance problems are not measurement problems. They are reconciliation problems: three systems each holding part of a day, and a person at the end deciding which to believe. There is one record here, and every punch on it says where it came from.
Biometric devices
eSSL and ZKTeco readers push punches over ADMS as they happen and are mapped to a location, so a shared device still produces the right employee's row.
Mobile with geofencing
The app checks in against the office's circle, 200 m unless you draw it otherwise on the map. The employee sees the fence and is told plainly when they are outside it.
Web check-in
For people at a desk. Same timeline, same shift rules, no separate desk-worker module.
Manual regularisation
A missed punch becomes a request with a reason, routed to an approver. The correction is visible as a correction.
Tue 14 Sep · Diya Krishnan
General shift · 09:00–18:00Shifts and calendars
The edge cases are the job.
Any system can record nine to six. What decides whether attendance is trustworthy is what it does with a shift that ends the following morning, a Sunday somebody worked, and three offices that do not share a clock or a holiday list.
- Shifts with grace and breaksDefine a shift once with its start, end, break and grace minutes. A late mark is a rule, not a manager's judgement at the end of the month.
- Night shifts that cross midnightA 21:00 to 05:30 shift is one attendance record belonging to its start date, not two half-days that each look like an absence. This is the case most attendance tools get wrong, and it is the one that costs a factory a payroll cycle to notice.
- Working weeks, including alternate SaturdaysA named work schedule says which days are full, half or off, down to the 2nd and 4th Saturday of the month, so a six-day week and a five-day week sit in the same workspace.
- Rest-day overtime at its own rateHours worked on a weekly off or a holiday get their own line on the payslip at their own multiplier, and an unworked Sunday is a weekly off, not an absence.
- Holiday calendars per locationChennai and Gurugram do not observe the same days. A holiday can apply to every office or only some, and leave and payroll both read that one list.
Night shift · 21:00–05:30
One record, 8h 30m, attributed to Tuesday. The punch at 05:30 on Wednesday closes Tuesday's shift instead of opening a new day, so Wednesday is not counted as a late arrival and Tuesday is not counted as a half day.
What it feeds
Nothing is re-keyed downstream.
Attendance is only worth keeping accurately if the accuracy survives the journey to the payslip. Here it does, because there is no journey — payroll reads the same rows.
Each office on its own clock
A London check-in at 08:52 shows as 08:52 BST, not as 13:22 in a Bengaluru workspace, and a correction typed for a London punch is stored in London time. Web and mobile punches carry the office's zone; device punches are read on the workspace clock.
Straight into payroll
Loss of pay and overtime are derived from the timeline during the run. No export, no import, no second total that has to be reconciled against the first.
One approvals engine
A regularisation goes through the same Request to Approver to Decision to Action chain as a leave request or an expense claim. Managers learn one inbox.
Off means off
A workspace that does not track attendance can switch the module off, and shifts, regularisation, dashboards and the nightly sweep all stop with it. Nobody is marked absent by a module they never used.
In the product
The day, and the month behind it.
Book a demo · 30 min
Bring your worst attendance month.
A shift that crosses midnight, a Sunday that was worked, offices in two timezones and a month of device punches. We will run it through and show you what payroll sees at the end.