Attendance for staff who are never at the office
Every attendance system assumes people arrive somewhere. Half your team does not — they go straight to a site, a route or a customer, and the register quietly becomes a formality.
By Edynex Technologies · · 6 min read
Why the gate machine fails this team
A biometric machine answers one question: who walked past this door. For an engineer who drives to a customer at 9 a.m. and never comes to the office, the honest answer it gives is nothing at all.
So most companies do one of three things, and all three cost money.
- ▸Mark them present by default. Simple, and it means attendance carries no information — you are paying for a register that records an assumption.
- ▸Make them come in to punch. Two hours of travel a day, from a person you employ for their time on site.
- ▸Run it on WhatsApp. A morning message, a photo sometimes, and a supervisor who reconciles it into a sheet at month end. It works, until the month it is needed as evidence.
What a field attendance record has to carry
Four things, and any system missing one of them will be argued about eventually.
- ▸Who — a face, not just a login. A password can be shared; a selfie at punch-in is harder to pass around.
- ▸Where — the location at the punch. Not to police people, but because "reached the site" is the single fact that matters for field work.
- ▸When — the real time, including when the punch was made with no network and uploaded later.
- ▸What happened in between — the duty route. Two timestamps eight hours apart tell you nothing about a day spent driving between four customers.
The objections your staff will raise, and the honest answers
- ▸"You are tracking me after work." Record duty hours, say so plainly, and make sure the employee can see their own record. A system staff cannot inspect is one they will not trust.
- ▸"It eats my battery and my data." Partly true, and worth answering with numbers rather than denial: a low update rate, not a constant stream, and no permanent background connection.
- ▸"I have no smartphone." A few people will not. Handle those as office-marked entries with an approver, the same as a missed punch — do not pretend the problem does not exist.
- ▸"The GPS is wrong sometimes." It is, indoors and in basements. That is exactly why corrections must go through an approver and stay visible, instead of a supervisor editing a number quietly.
What to check before you buy any of these
Every vendor demo works. Ask about the bad days instead.
- ▸What happens to a punch made with no network — is the real time kept, or the reconnect time?
- ▸If someone switches location off mid-shift, does anyone find out, and is the gap recorded or silently dropped?
- ▸Who can change an attendance record, and can you see afterwards that it was changed?
- ▸Does the month's attendance reach payroll on its own, or does somebody retype it into a spreadsheet?
- ▸Can an employee see their own attendance, or only their manager?
The last two decide whether the system saves work or adds it. A register nobody trusts gets overridden at month end, and then you are paying for software and doing the work by hand anyway.
A note on proof
Attendance is a payroll document. The day it matters — a dispute, a claim, an audit — you need a record that was not editable after the fact.
That means corrections that carry a name and a timestamp, not a clean-looking final number. A system that lets an administrator silently rewrite last month's register produces tidy reports and no evidence.