GullyHR configures how attendance is captured, how shifts and rosters are assigned, and how leave and regularisation requests travel: leave types and entitlements, accrual rules, shift patterns, the correction route for a wrong entry, the holiday calendar, and the approval level behind each. You supply the current leave policy, shift patterns, holiday list and attendance method, and you make the decisions that belong to management, such as how much leave of each type an employee gets and who may approve an exception to it. This runs as configuration, a test against a sample cycle and role-based training inside a GullyHR software engagement, and we design around a biometric device you already own where it genuinely supports the process.
Attendance is recorded against the shift the person was actually on.
A daily attendance record for each employee, held against their configured shift, which every other module that needs it, payroll inputs above all, reads from rather than keeping its own copy.
An existing biometric device is assessed before anything is promised about it.
Where a punch or biometric device is already installed, we look at what it can actually export and bring that data in where it is genuinely possible. Where it is not, we say so and describe the manual alternative.
The roster leaves the supervisor's head and becomes visible.
Shift patterns configured to how the business really operates, with rosters assigned to individuals or teams and readable by the managers and employees they affect, so nobody works a shift they did not know about.
A leave request reaches the manager who is meant to decide it.
Employees apply against configured leave types and see their own balance, and the request routes along the reporting line held in the system instead of depending on who they happened to speak to.
Every approval and rejection leaves a record with a date on it.
Leave and regularisation decisions are recorded against the employee and the approver, so a disagreement months later is settled by looking rather than by remembering.
A missed punch has a correction route instead of a quiet edit.
The employee or the manager raises a regularisation for a missed or wrong entry, an approver accepts or rejects it, and only then does the attendance record and the payroll input change.
Holidays can differ by location without anyone tracking it by hand.
A configured holiday calendar that can vary by site, which matters as soon as you operate in more than one state and the lists stop matching.
Attendance and leave close before payroll inputs open.
Exception, absenteeism and balance reports built from the same records used for approval, with an agreed cut-off, so the payroll cycle starts from data that is already settled.