HRMS · Time

Clocked in,
and where from.

Clock in against an office with a location, with a photo, a biometric or an NFC card depending on what the role needs. A missed punch is corrected through a request that somebody approves — not by an administrator editing the record.

The record has to be defensible. Attendance that an admin can silently edit is not evidence of anything.

Clocking in

Several ways, because roles differ.

Location validatedThe punch is checked against the office’s geofence, so remote clock-in from a sofa is a decision you make rather than one you discover.
With a photoFor the roles where the location alone is not enough.
BiometricDevice enrolment and a challenge flow, with the ability to reset an employee’s enrolment when a device changes hands.
NFC cardsIssued, assigned and revoked as records — for shop floors and sites where a phone is not practical.
Location pingsFor field staff, a trail rather than two points in a day.
When it goes wrong

Regularisation, not editing.

Punches get missed. What matters is that fixing one leaves a trail.

A request, not an editThe employee raises it, a manager approves or rejects it, and the record shows both.
Pending queueWhat is waiting on you, so regularisations do not sit unresolved until payroll day.
Team viewA manager sees their own team’s attendance and requests, rather than everybody’s or nobody’s.
Manual entry, recorded as manualWhen HR does have to enter attendance directly, it is marked as such rather than passing as a punch.
Shifts

Rosters, and what counts as late.

Shift definitionsStart, end and the tolerances that decide whether a punch is late — configured rather than assumed.
Assigned to peopleSo the same clock-in means different things for a morning shift and a night one.
Feeds payrollDays counted come from here, which is why the payslip can show the days it used.
Nearby

Related capabilities.

Leave · Payroll · Employee self-service

A record that holds up.

Every correction has a requester, an approver and a timestamp.