A familiar action at the start and end of a shift
A worker sets up the app using a company code, their employee ID or legacy worker code, and a PIN. The personal device is remembered after onboarding. For daily attendance, the worker unlocks the app, completes a blink liveness selfie and supplies a location fix at their assigned site.
The attendance record carries the capture time, location, selfie and liveness result. When received, the server checks the worker’s device authorization and applicable attendance requirements before accepting the record. A captured event and an accepted event are different states.
What happens when the day is imperfect
An onboarded personal device can save a capture while internet connectivity is unavailable. The app displays its pending count and retries synchronization when it can connect and run. A terminal rejection is shown to the worker and the rejected capture is removed locally. The worker should contact a supervisor if a genuine working period is missing.
No internet connection and no usable location fix are different problems. Offline capture does not remove the need for the app’s capture checks. Initial onboarding and device restoration require connectivity.
From worker action to supervisor review
Imagine a technician completes check-in at a customer site, then loses connectivity before checkout. The phone may hold the checkout locally while the dashboard still shows the last accepted check-in. Once the event is accepted, it can contribute to the timesheet. If it is rejected, a supervisor reviews the situation and can record a reasoned correction.
That is a record of attendance evidence, not proof of continuous presence, completion of a service job or payable travel time. Those decisions need the company’s work policies and review process.
Plan the first use
Confirm device compatibility, camera and location permissions, the actual site entrance, connectivity for setup and a named supervisor for exceptions. Android and iOS apps are implemented; arrange the current installation and rollout process with Attendify. Do not assume public app-store distribution or immediate account activation.