Comparison table
| Method | Where | Condition | Limit |
|---|---|---|---|
| Location | Staff phone | Inside the branch area | Needs location permission and internet |
| Branch code with location | Staff phone | Scan plus location together | A code alone is never enough |
| Approved network | Staff phone | Approved branch networks | Set per branch |
| Face with location (within the target release) | Staff phone after a one-time enrollment | 1:1 face verification plus branch area | Check-in and check-out alike |
| Face with network (within the target release) | Staff phone after a one-time enrollment | 1:1 face verification plus approved BSSID — no location and no substitute | Useful indoors where GPS is weak |
| Kiosk recognition (within the target release) | Branch tablet after a one-time enrollment | 1:N face recognition within the branch roster | Phone-free check-in and check-out daily |
| Crew | Supervisor | Approved supervisor for their team | Documented responsibility |
| Branch point | Screen plus staff phone | 3 successive valid scans | Needs the staff app and camera |
| Devices and import | Device/file | Model compatibility | Confirmed with support |
| Administrative correction | Manager | Written reason and evidence | Stays reviewable |
Note: guided face enrollment is a one-time setup, not an attendance row in this table.
Location
For field teams and open sites: open the app inside the branch area, grant location permission, tap check-in, and confirm the acceptance message. The system verifies the area before accepting the request under company policies. Requirements: a modern phone, internet, and location permission. Limit: accuracy weakens indoors, and location alone does not prove identity.
Printed branch code
A fixed sticker on the branch door for single entrances: open the scanner, grant camera permission, scan the sticker with location proof in one request, and confirm acceptance. The printed code never changes, so location is mandatory with it. Requirements: a clear sticker, camera, and location. Limit: a copied photo of the sticker fails outside the area.
Rotating code
A branch screen shows a rotating code: open the scanner, scan the code shown now, send it with location immediately, and rescan if it expires. Each code is single-use per employee and purpose, so a colleague's scan never consumes yours. Requirements: a display running during hours, camera, and location. Limit: fast expiry may need a second scan.
Approved network
For stable offices: join the branch network, open the check-in screen, confirm while connected, and verify acceptance. Every router band is approved so nobody is rejected. Requirements: approved networks per branch. Limit: connection alone never records — request and confirmation are two steps.
Clarification: authorization by an approved BSSID is mandatory, every used router band is registered, and each check-in needs explicit confirmation. The phone OS may ask for a network- or location-related permission to read the network identifier (BSSID) — a read permission, not GPS coordinates. A location or geofence check applies only when branch policy requires it for the ordinary network method. Unlike face with network, which never uses location and has no substitute.
Face with location
within the target release
Face verification and a branch geofence check in one attendance flow: enroll once with the guided flow, then on arrival verify your face inside the branch area — for check-in and check-out alike. Requirements: a modern phone, camera, prior face enrollment with consent, and location permission. Limit: poor light may need a retry — face verification combined with an area check, with no accuracy guarantees.
Face with network
within the target release
For offices and indoor places where GPS is weak: enroll once, then check in daily with your face plus the approved branch network alone — no location needed at all. Authorization by the approved branch network (BSSID) only: no coordinates, no geofence, no substitute. Requirements: connection to the approved branch network (approve every router band, 2.4 and 5 GHz) plus prior face enrollment. Limit: the phone OS may ask permission to read the network — a network-read permission, not location verification — and connection alone never records.
First time: guided enrollment
within the target release
Before your first face check-in: an activated employee account, then read the instructions and explicitly consent to the face template, follow the guidance for good light and framing, capture as guided, and wait for the server enrollment result — success moves you to your chosen attendance method, a documented failure means retry. This is a one-time setup enrollment, not a punch.
Crew
For mobile sites with no phone per worker: the approved supervisor opens the crew screen, marks who is present, records for the team under their responsibility, and management reviews later. Recording needs supervisor permission. Requirements: an approved supervisor and one phone. Limit: supervisor responsibility is documented and reviewable.
Kiosk recognition
within the target release
The branch point recognizes you: after a one-time enrollment (guided from your phone or supervised at the branch device), stand before the branch tablet — the system matches you within the branch roster (1:N) and records check-in and check-out, with no phone needed daily. Unlike Triple Scan, which needs your phone and camera for every punch. Requirements: a paired branch tablet, prior enrollment, and company activation. Limit: standing before the screen is required each time; when matching fails the request is not recorded — retry or see your branch manager to choose an approved method if needed.
Branch point: triple scan
A shared branch screen shows a changing code: open the scanner in the employee app, scan the first code, then the second at the screen's pace, then the third — which records attendance directly — and confirm the message. The screen is display-only and grants no identity; the only guarantee is three successive valid scans. Requirements: a running screen plus the staff phone, camera, and permissions. Limit: any expired code restarts the count.
Illustrative diagram: the three-scan steps
- Open the scanner in the employee app and scan the first code shown on the screen.
- Scan the second code at the screen's pace.
- Scan the third code — which records attendance directly — and confirm the message.
Devices and import
Biometric devices, connectors, and import files per model compatibility — confirm with support before buying.
Compatible biometric devices (ZKTeco via ADMS): model and protocol compatibility is checked before purchase, and each device is registered by the administration before its punches flow in.
A LAN connector where applicable, and a separate file-import path (USB/CSV): review with a preview, then confirm, with rollback where appropriate.
Processing device punches needs a stable connection, and compatibility is practical per model.
Corrections and day status
Every edit carries evidence and stays reviewable, flowing into reports and payroll. Approved-leave conflicts with attendance are resolved before payout.
Manual entry
When an employee misses check-in (a forgotten punch or a device outage): the manager records from the management app the staff member, branch, date, and time with a mandatory written reason. Manual entry is an administrative exception under branch policy, never accepts a future time, and staff cannot record it themselves.
Correcting an existing record
Correcting a recorded time keeps the original times and evidence, with protection against concurrent edits: a correction is a documented edit with a reason, not a new punch and not free overwriting of evidence.
Day status and leave conflicts
Each day is marked (present, absent, leave, holiday, weekly rest). When recorded attendance conflicts with approved leave, the conflict is resolved after one management decision by a person authorized with both attendance and leave permissions before payout — never by overwriting the actual punch evidence.
Details on the shifts and attendance rules page and the reports and export page.
Code differences
The activation code invites staff once and differs from the daily attendance code.
The activation code invites staff once, the attendance code records daily check-in with location, and the changing screen code serves the branch point.
Guided enrollment is a one-time setup, not a punch.
How to choose for your branch
Field teams use location, single entrances use the code, stable offices use the network or face with network, mobile crews use the supervisor, busy branches use the shared point — by phone scan or phone-free recognition within the target release.
Illustrative example: enclosed office: face with network for in and out with no GPS use. Single-entrance store: face with location combining face verification with an area check. Crowded shift entrance: kiosk recognition for a fast phone-free queue — after a one-time enrollment.
FAQ
Does it work offline?
No. An unrecorded request is not counted — retry when the connection returns.
What if the internet drops?
Record when the connection returns under branch rules; any later correction is justified and documented.
Is face available?
Face is within the approved target release: your face with your branch location (Face + GPS) or with the branch network without location (Face + Wi-Fi) from your phone after a one-time enrollment, or phone-free recognition at the branch point (1:N) — actual availability is announced with the release.
How do I enroll my face first?
Once, guided from the employee app: an activated account, explicit consent, then on-screen guidance for light and framing, and the server result — afterwards you check in daily with your chosen method. This is a setup enrollment, not a punch.
What are the code differences?
The activation code invites staff once, the attendance code records daily check-in with location, and the changing screen code serves the branch point.
Start with the right method
Set each branch method for how it works, and invite your team with the activation code. Register your account now, or write to support for help, and the start steps are on the getting-started page.