WhatsApp clock-ins: why location attachments beat location requests
17 Nov 2026
If your employees clock in by sharing their location on WhatsApp, how they share it matters more than you might think. We tested both of WhatsApp's location-sharing methods for clocking, and one of them lets an employee place their pin anywhere without leaving a trace.
WhatsApp clocking is popular in South Africa for good reason: no app to install, no hardware on site, and every employee already has it. But a pin on a map only shows where someone says they are. The question for any clocking system is how hard it is to say something untrue, and whether you can tell when it happens.
Two ways to share a location
A business on the WhatsApp Business Platform can receive an employee's location in two ways.
- Location request. The business sends an interactive message with a "Send location" button. The employee taps it and a location-sharing screen opens.
- Location attachment. The employee taps the paperclip (📎), chooses Location and sends their current location, or picks a place from a list or a search.
Both arrive at the business as the same kind of message: a latitude and longitude, sometimes with a place name and address. Meta's webhook reference lists only those fields. There is no accuracy figure and no flag saying whether the coordinates came from the phone's GPS or from where the user pointed.
What we tested
We shared locations every way we could think of and logged what reached our webhook each time. The "reply link" is the field that ties a response to the location request it answers.
Using a location request:
- Shared current location: coordinates only, with a reply link.
- Moved the pin and shared quickly: coordinates only, with a reply link. Identical to the line above.
- Moved the pin only slightly: coordinates plus a street address, with a reply link.
- Searched for a place: coordinates plus a place name and address, with no reply link.
Using an attachment:
- Sent current location: coordinates only.
- Searched for a place: coordinates plus a place name and address.
- Forwarded from another person's chat: marked with WhatsApp's forwarded tag.
- Re-shared an earlier location from the same chat: coordinates only, exactly matching the earlier message.
The first two location-request results are the problem. A genuine current location and a pin dragged somewhere else look the same to the business.
Why location requests are the riskier option
The location request screen lets the employee move the pin. If they move it slowly, WhatsApp looks up a street address and sends it along, which gives the move away. If they move it and share straight away, the address never arrives and the business receives bare coordinates: exactly what a genuine "current location" looks like.
Nothing else in the message helps. Meta's documentation doesn't say whether the coordinates come from the phone's position or from the pin, and the message carries no accuracy figure. The reply link only proves the employee answered your request, not where they were standing.
The feature was designed for things like delivery addresses, where letting someone choose a spot is the point. For clocking, that same freedom is a hole you can't see into.
Why attachments are safer, and where they still fall short
With an attachment, "send your current location" can't be dragged elsewhere. Every other way of sending a different place leaves a mark:
- A searched or listed place arrives with a name and address. A genuine current location doesn't.
- A location forwarded from someone else arrives with WhatsApp's forwarded tag.
- An old location re-shared from the same chat has exactly the same coordinates as before. Two genuine GPS readings almost never match to the last decimal, so an exact repeat stands out.
That makes faking a clock-in noticeable rather than invisible. It doesn't make it impossible:
- Re-shares need memory. You only catch a repeat if you keep every earlier location and compare against it.
- Self-forwarding is a grey area. An employee could send their location to another chat while on site and forward it later. Whether WhatsApp tags that as forwarded is something we're still testing.
- GPS-spoofing apps on Android can fake the phone's position itself. No WhatsApp message can reveal that, whichever method you use.
One practical tip: if you use attachments for clocking, stop sending location request buttons in the same chat. Then a dragged pin has no way to reach you at all.
Going further: proving presence beyond the pin
A location shows where a phone claims to be. To show someone is really on site, pair it with something that only exists there, or that's hard to fake for long.
- Random check-ins. Asking for a fresh location at unpredictable times during the shift. One fake is easy; keeping it up all day is not.
- Patterns over time. Impossible travel between two clock-ins, or a location that never wobbles the way real GPS does.
- People. A supervisor's confirmation, or an occasional selfie checked by eye. Under POPIA, photos are personal information, so tell employees what you collect and why.
Each adds a layer. Together they turn a quiet cheat into one that needs planning, help from a colleague and a spoofing app, and still risks being caught.
Takeaways for employers
- For clocking, ask for an attached current location, not a location request. Requests let a moved pin pass as genuine; attachments leave a trace when something's off.
- Treat a WhatsApp location as a claim, not proof. Neither method tells you how accurate the reading is or whether the phone's GPS was faked.
- Allow some leeway at the boundary. Indoor GPS can be out by tens of metres, so set your site radius with that in mind.
- Add a second check where it matters. For sites where attendance affects pay or safety, combine the location with something only available on site.
- Flag rather than accuse. A suspicious clock-in is a reason to ask, not proof of dishonesty. Phones do occasionally repeat a reading.
WhatsApp is a practical way to run clocking without extra apps or hardware. Used the right way, it's also harder to cheat than many employers assume.