The system fails at the rules, not the device
Most attendance projects that go wrong did not fail at the reader. They failed because the rules were never written down: how a night shift crossing midnight is counted, when overtime starts, how a missed punch is treated, who may approve an exception, and what happens on a public holiday.
We start with those rules. Before a device is mounted we agree the shift patterns, grace periods, rounding, overtime thresholds and exception handling with HR and payroll, then configure the software to match and test it against real scenarios from your own records.
Because the same rules differ site to site, multi-branch deployments are configured per site with group-level policies, and supervisors see only the people they are responsible for.
What the system covers
Each element is configured and tested, and the acceptance criteria are agreed before the project starts.
Clocking devices
Fingerprint, face, card or PIN terminals selected per site and entrance, including outdoor and industrial positions where relevant.
Mobile and remote clocking
Where field or hybrid staff need it, mobile clocking with location context, subject to the policy you agree for those roles.
Shift and overtime rules
Shift patterns, cross-midnight handling, grace periods, rounding and overtime thresholds configured to your HR policy rather than a vendor default.
Exceptions and approvals
Missed punches, corrections and leave handled by a documented workflow, with supervisor approval recorded against the change.
Payroll export
A tested export in the format your payroll process accepts — file, API or scheduled extract — validated against a real pay cycle before go-live.
Reporting
Attendance, lateness, absence and overtime reports configured for supervisors and HR, with access limited by role.
From clock event to payroll
The approval step is deliberate: exceptions are decided by a named supervisor and recorded, rather than silently corrected.
- Clock event — Device, card or mobile punch
- Rules engine — Shift, grace and overtime policy
- Timesheet — Calculated with exceptions flagged
- Approval — Supervisor reviews and signs off
- Payroll export — Tested file or API handover
Where it is used
Shift-heavy and multi-site employers get the most from a properly configured system. Typical deployments include:
Industrial and production sites
Shift rotations, overtime and contractor attendance, with terminals placed at gates and muster points.
Retail chains
Branch-level clocking with head-office visibility, part-time rotas and split shifts handled by policy rather than spreadsheets.
Hospitality
Variable shifts and late finishes, with approvals that reflect department structure and service periods.
Offices and hybrid teams
Core-hours and flexible patterns, with card or mobile clocking where a fixed terminal is impractical.
Education
Academic calendars, part-time and hourly staff, and term-time rules configured per group.
Warehouses and logistics
Shift handovers and agency staff, with attendance records that align to gate and loading schedules.
Support after go-live
Attendance is a monthly obligation, so support has to be predictable. Contracts are scoped around the number of devices and sites.
Device maintenance
Scheduled checks of terminals, sensors and connectivity, with cleaning and calibration where the technology requires it.
- Terminal and sensor checks
- Connectivity and time sync
- Firmware review
- Written visit report
Rule and calendar changes
A route for changes to shifts, holidays and overtime policy as your organisation changes, without re-implementing the system.
- Policy and calendar updates
- New site or group setup
- Report adjustments
- Change record per request
Fault response
Support for devices that stop clocking or data that stops syncing, including temporary arrangements so the pay cycle is not disrupted.
- Single fault-reporting channel
- On-site diagnosis and repair
- Replacement terminal handling
- Closure report per incident
Contract scope, visit frequency and response terms are agreed per site. Data protection obligations for biometric or location data remain with your organisation and its advisers.
How an attendance project runs
The rule workshop is the step most projects skip. We do not.
1. Rules workshop
HR and payroll walk us through shifts, overtime, holidays and exceptions; the outcome is a written rule set.
2. Design and proposal
Device placement, connectivity, software licensing and export design, priced as a single scope.
3. Installation
Terminals mounted and connected, with network and power arranged at each clocking point.
4. Configuration and parallel run
Rules configured and tested against a real pay period, ideally alongside the current process before cutover.
5. Training and handover
Supervisors and HR trained on approvals and reporting, with documentation and an agreed support route.
Common questions
Can employees clock in from a phone?
Yes, where the policy allows it. Mobile clocking can include location context for field and hybrid roles. We agree with you which roles may use it and what is recorded, since this is a policy decision as much as a technical one.
What happens if a device goes offline?
Terminals typically buffer punches locally and sync when connectivity returns. We verify that behaviour during commissioning and agree a temporary manual process so payroll is not held up while a device is repaired.
Will it work with our existing payroll system?
In most cases yes, through a file export or an API where the payroll product supports one. We validate the export against a real pay cycle before go-live rather than assuming the format is accepted.
Can we use the access control cards for attendance?
Where the platforms support a shared credential, yes — one card for doors and clocking. We confirm compatibility during the survey and note any licensing implications.
How is biometric data protected?
Templates are held by the attendance platform rather than by us, and retention, consent and deletion are configured to your policy. We will document what the system stores and where, so your data-protection review has a factual basis.
Related services
- Access control systems — Doors, credentials and entry records from the same platform family.
- IT infrastructure maintenance — Ongoing support for the servers and network these systems depend on.
- All services — The full White Cloud Services catalogue across both divisions.
Replacing spreadsheets with a real system?
Send us your shift patterns and the payroll output you need, and we will come back with the rule questions that decide whether an attendance project succeeds.