Loading
Module
Employees clock in and out, switch shifts, and see their own history. You get org-wide views and a day-by-day sheet. The calendar date is derived in your organization’s timezone, so a 9am start never lands on yesterday.
What this solves
Attendance looks like the simplest thing an HR system does, and it is usually the first thing that goes wrong. The reason is almost always the same: a clock-in is stored as an instant in time, then the calendar day gets derived from whatever timezone the server happens to be in. For a team in New York clocking in at 9am, a server running in UTC reads that moment as 1pm — fine. For a team in Manila or Mumbai clocking in at 9am, the same server reads it as the previous evening, and the shift gets filed under yesterday.
Nobody notices on day one. They notice at the end of the month, when the attendance report has a phantom absence, overtime lands in the wrong week, and someone has to reconstruct a timeline from memory. By then the payroll run has already consumed the bad numbers.
OneclickHR takes the organization timezone as the authority. Every attendance record carries the instant it happened and the calendar day it belongs to, and that day is computed from the timezone configured in your workspace settings. Reports, sheets, histories and payroll all read the same day.
What is included
One action to start the day and one to end it, from the employee portal. The current state is always visible, so nobody has to guess whether they are clocked in.
Teams that run more than one shift can switch between them rather than keeping a separate record per shift. The attendance entry carries which shift it belongs to.
A clock-in after the expected start is flagged as late when it is recorded, not calculated after the fact in a spreadsheet. The flag travels with the record.
Every employee can read their own attendance history in their portal: what day, what time in, what time out, which shift, and whether it was marked late.
Managers see attendance across the whole workspace, scoped by the permissions on their team role. A payroll person and a recruiter do not see the same screen.
A sheet view that reads across dates rather than down a single employee — the view you actually want when you are reconciling a month.
Attendance is not an island. The hours recorded here are the hours the payroll run reads when it calculates overtime, and the days recorded here are the days that leave requests have to agree with. Because all three read the same calendar day from the same timezone setting, there is nothing to reconcile between them.
Leave approved on the shared calendar shows up against the same dates the attendance sheet uses. Overtime rules configured in workspace settings apply to the hours as recorded. When the payroll review step shows you a number you did not expect, you can trace it back to a specific day on a specific sheet rather than guessing.
Attendance shares its records with the rest of the workspace, so these modules read the same data rather than a copy of it.
Sign your organization up, configure your timezone and brand color, and invite your team. You can be running the same day.