One Phone by the Gate
Forty casual workers, one gate, and not one of them has a smartphone the company can register. One shared phone in kiosk mode: employee number, PIN, a photo for HR to look at, and a punch that waits in the phone when the signal does not.
At a flower farm near Naivasha, the 6:30 shift is forty-two people, most of them casual workers on a feature phone or no phone at all. Asking each of them to register a device and clock in from it is not a policy, it is a wish. The paper register at the gate is a policy, and it is the one that produces the buddy punching, the 6:58 arrivals written down as 6:30, and the Saturday spent typing it all in.
Pairing a phone to the gate
On the attendance site’s page, the site manager generates a pairing code for a kiosk, with a name for the device and an exit PIN. The code is shown once, with a QR, and is good for ten minutes and one use. On the shared phone, the AWRA app scans or types it, and the phone becomes the kiosk for that one site. No one is signed in on it. The phone holds a token that reaches that site and nothing else, which the manager can revoke from the same page; a revoked kiosk is told so on its next request.
A punch
-
Employee number
Typed on the kiosk’s keypad.
-
Self-service PIN
The same PIN the employee uses on the no-login self-service portal, with the same five-attempt lockout.
-
Photo
The front camera takes a picture, kept on the attendance record for HR to look at.
-
In or out
The server decides from the day’s record: no punch yet is a clock-in, an open shift is a clock-out.
Nobody chooses “in” or “out” on the screen, so nobody chooses wrong. A second punch within two minutes of a clock-in is treated as a double tap, not a clock-out. Someone who has already clocked in and out today is told the two times. A night-shift clock-out after midnight closes yesterday’s open shift.
The photo is evidence, not identification
Nothing on the phone or the server compares faces. The photo is there so that a supervisor reviewing a disputed punch can see who stood at the gate, and the kiosk screen says so to the person being photographed.
The same rules as a personal clock-in
- Assigned sites only. An employee assigned to the packhouse cannot punch at the greenhouse gate.
- The site’s geofence, checked against the kiosk’s own location when it sends one.
- The site’s clock hours, the shift’s late rule and the timesheet lock, all at the time the person actually punched.
- The PIN lockout, shared with the self-service portal, so five wrong guesses lock the PIN everywhere.
For the employees who do have a phone, the personal route is still there and still requires a registered device, which we described in nobody clocks in until a device is registered. The kiosk does not loosen those rules; it lets the kiosk stand in for the device. Why the personal route checks the phone, the distance from the site and, where a site asks for it, a code on a screen is in the QR that changes every thirty seconds.
When the signal goes
The gate at Naivasha loses signal most mornings around the shift change. The kiosk keeps taking punches. Each is queued on the phone with the time it actually happened and an id of its own, and sent when the connection returns. A punch sent twice gets the first answer back, not a second record. One that arrives more than three minutes after it happened is flagged as synced late and noted on the record, so HR can see which times came in after the fact. A punch older than 72 hours is not applied at all; it goes to HR to record as a correction.
A queued punch keeps the minute it was made. The signal decides when it arrives, not what time it says.
Leaving kiosk mode takes the exit PIN and a connection, so the PIN can be checked, and the app refuses while any punch is still waiting to be sent. A phone cannot be walked off the gate with a morning’s attendance still inside it.
A kiosk for your kind of site
Pairing, PIN punches with photos, site rules and the offline queue are in place. These are the extensions sites ask for after the first month.
Badge punches
A printed QR badge scanned at the kiosk in place of typing the employee number.
A group punch by a supervisor
A gang leader clocking in a picking team that arrives together, with a photo of the group.
A photo retention period
Kiosk photos deleted automatically after a period the workspace sets.
Face matching, as an opt-in
For workspaces that want it and have their workers’ consent, with the wording for that consent.
Three questions for your site supervisor
Who wrote the time on the register for the late arrivals?
What you will probably hear
Whoever was at the gate.
How to read it
Then the register records what was written, not when people came.
What happens to attendance when the network is down?
What you will probably hear
We write it down and enter it later.
How to read it
A punch should keep its time on the device and arrive when it can.
How do you know the person who punched is the employee?
What you will probably hear
We know everyone.
How to read it
Until you have forty casuals in a new season. A PIN and a photo make that checkable.
Where this leaves you
One shared phone at the gate, paired to one site, takes PIN punches with a photo, applies the same site and shift rules as a personal clock-in, and keeps each punch’s real time when the signal drops.
What AWRA OpsHub does today
- Kiosk pairing with a one-time code valid for ten minutes, one device per site, revocable.
- Punches by employee number and self-service PIN, with the shared five-attempt lockout.
- A photo on every punch for review, with no face comparison.
- The site’s rules: assigned sites, geofence, clock hours, late rule, timesheet lock and night shifts.
- Offline punches queued with their real time, de-duplicated, and flagged when they arrive late.
- An exit PIN that will not release the phone while punches are waiting.
More we can add to your workspace
- Badge punches from a printed QR on an ID card. Commission it
- Group punches by a supervisor for a team arriving together. Commission it
- A retention period for kiosk photos, set per workspace. Commission it
- Face matching as an opt-in, with consent wording, for workspaces that want it. Commission it
Where we point you to a specialist
- Photos of workers are personal data. How long you keep them and how you tell your workers about them is your decision under the Data Protection Act, and the kiosk shows the notice but does not decide your policy.
Badge punches are what agricultural and construction sites ask for first.
See the attendance kiosk
A shared phone at the gate, PIN punches with a photo, and an offline queue that keeps the real time.
Explore the kioskFrequently asked questions
Does the attendance kiosk use face recognition?
No. It takes a photo with each punch for HR to look at. Nothing compares faces.
What does an employee need to clock in at the kiosk?
Their employee number and their self-service PIN. They do not need a phone of their own.
Does the kiosk work without internet?
Yes. Punches are queued on the phone with the time they happened and sent when the connection returns. Punches more than three minutes late are flagged, and punches older than 72 hours go to HR as corrections.
Can an employee clock in at a site they are not assigned to?
No. The kiosk applies the employee’s assigned sites, the site’s geofence and its clock hours.
How is a kiosk switched off?
With the exit PIN set at pairing, which needs a connection and an empty punch queue, or by revoking the device from the attendance site’s page.