A solution shaped around your work.
Field teams may need to confirm where a work shift begins. Collect only the evidence agreed for that check-in, explain its purpose and avoid background location collection unrelated to the attendance event.
What this service covers
- Approved site boundaries and check-in requirements
- Employee consent and event-specific permission prompts
- Restricted image access and retention configuration
- Location exception review and alternative check-in testing
We confirm the selected equipment, responsibilities and deliverables in your project proposal before work begins.
How we deliver the work
- 01
Map people and permissions
Define employee groups, attendance rules, access zones and administrator responsibilities. Identify the enrollment method and the records that each role needs to view.
- 02
Configure the workflow
Configure the selected devices or application around approved schedules and permissions. Check connectivity and any interfaces with HR, payroll or existing door equipment.
- 03
Test real scenarios
Test agreed employee and administrator scenarios, including exceptions and access removal. Hand over the operating steps and clarify who maintains users and reports.
A clear handover
Agree the records your team needs to operate and maintain the solution. Depending on the selected scope, these can include:
- Device or application configuration summary
- User administration and exception-handling steps
- Agreed reporting and integration checks
What to prepare for your project
Identify approved work sites, consent procedures, retention periods and supervisor roles. Provide the required check-in rules without sharing employee selfies or historical location records.
Discuss this serviceYour questions, answered
Does GPS attendance require continuous employee tracking?
No. The intended workflow captures authorised evidence at check-in or check-out. Device permissions and application behaviour must be reviewed so background tracking is not enabled as part of this attendance scope.
How do we choose between face, fingerprint and card attendance?
Consider employee numbers, entrance conditions, shifts and how exceptions will be handled. We review the proposed device, software and enrolment method before confirming a suitable configuration.
What needs to be checked before attendance data reaches payroll?
Confirm the HR or payroll application, supported export or API, employee identifiers and approval rules. Test sample records and overnight shifts before using the integration for payroll.
What information should be shared at the enquiry stage?
Share approximate employee and door counts, shift patterns and existing device models. Use sample field names or anonymized examples to discuss integrations; actual biometric templates, employee files and passwords are not needed in the website form.