Most attendance problems are not tracking problems — they are trust and reconciliation problems. duduHR captures where and when each punch happened, tags it against the employee's roster automatically, and gives managers a clean exception list instead of a spreadsheet to audit.
Every punch records latitude, longitude and an optional selfie, then resolves against the geofence sites you define — each with its own centre and radius. The event is stored as inside, outside or no-location, along with the exact distance in metres from the site. You get the assurance of a fingerprint scanner without buying, mounting or maintaining hardware, and it works for field staff who were never going to walk past a device anyway.
Define shifts with start and end times, break minutes, and separate grace windows for arrival and departure. Working days are set per shift, and alternate-Saturday patterns are handled natively rather than bolted on. Once a roster is assigned, duduHR tags each punch on-time, late or early and stores the deviation in minutes — so "how late, and by how much" is already answered before anyone asks.
Forgotten punches are a fact of life. Employees raise a regularisation request against the specific day with corrected in/out pairs and a reason; the manager approves or rejects it in one place. The original event is preserved alongside the correction, so the audit trail shows what actually happened rather than quietly overwriting history.
Weekend or holiday work earns compensatory off with an explicit earned-days value and an expiry date, so credits do not accumulate indefinitely into a liability nobody budgeted for. Approved comp-off flows into the same balance system as the rest of leave.
Only if you require it. Geofence sites are optional and configurable per organisation. If you allow remote work, punches outside a site are still recorded — flagged as outside with the distance — rather than blocked, so managers can decide rather than the system deciding for them.
For most teams, yes. Location plus an optional selfie gives comparable assurance without hardware, installation or per-site maintenance, and it covers field and remote staff that a fixed device cannot.
Yes. Saturday working weeks are part of the shift definition, so a first-and-third-Saturday pattern is configuration rather than a monthly manual correction.
Attendance, leave and loss-of-pay feed the payroll run directly, so the days you pay for are the days the system recorded rather than a re-keyed summary.
Automated accrual, carry-forward & lapse, half-day sessions, per-org policies, encashment and a team calendar — plus floater holidays and multi-level approvals.
Track effort against projects and tasks with manager review and approvals.
Salary structures, payroll runs, payslips, Form-16, loss-of-pay and leave encashment — generated in a click.
We’ll set up your branded workspace at your-company.duduhr.com and walk your team through it.
Talk to us