Geofencing attendance rejects field staff who are standing at the store when the store’s saved GPS coordinates or check-in radius are wrong, not because the worker is absent. The fix is to correct each store’s location data and radius, then confirm presence with tamper-proof, geo-tagged attendance photos.
The 8 a.m. message every field admin knows
A promoter reaches her assigned store in a mall in Cebu, opens the app to time in, and gets blocked. The screen says she is too far from the store. She sends the message the whole team has learned to dread: “Sir, hindi ako maka-check in, malayo daw.” She is standing at the entrance. The app disagrees.
Multiply that by a field force of merchandisers, sales agents, and deployed staff scattered across provincial routes and mall branches, and the group chat fills up with the same complaint every morning. Supervisors start manually approving time-ins to keep operations moving, which quietly defeats the reason the geofence was turned on in the first place. Attendance data that was supposed to be trustworthy becomes a pile of exceptions.
The reflex is to blame the worker or the phone. Usually neither is the problem. The store’s location record is.
What geofencing attendance actually checks
Geofencing attendance draws a virtual circle around a store’s location. When a field worker tries to time in, the app reads the phone’s GPS position and asks one question: is this coordinate inside the circle? If yes, the check-in is allowed and stamped with a location. If no, it is rejected.
Two values decide the answer, and both live in the store’s master data, not on the worker’s phone. The first is the store’s saved coordinates, the exact latitude and longitude the system treats as the center of the circle. The second is the radius, how far from that center a check-in still counts as “at the store.”
Here is the part most teams never adjust for. GPS on a phone is not exact. The U.S. government’s own guidance puts a typical smartphone’s accuracy at about 4.9 meters under open sky [1]. That is the good case. A peer-reviewed study of smartphone positioning in an urban environment measured an average horizontal error of 7 to 13 meters [2], and dense commercial districts full of glass and concrete make it worse because signals bounce off buildings before they reach the phone. Inside a mall or a covered market, the phone may barely see the sky at all.
So the radius is doing two jobs at once. It is a fraud control, keeping people from timing in from home. It is also an accuracy tolerance, absorbing the normal drift between where the worker actually stands and where the phone thinks they stand. Set the radius tighter than the real-world GPS error, and the system will reject honest workers standing at the door. The fraud control has swallowed the accuracy tolerance.
Why workers get rejected while standing at the store
When a check-in fails for someone who is genuinely there, the cause almost always traces to one of four things.
The store’s saved coordinates are wrong or a placeholder. This is the most common cause, and it usually enters the system in bulk. Store lists get uploaded from a distributor file, a permanent journey plan, or an old spreadsheet, hundreds of rows at a time, and those rows often carry approximate pins, a coordinate for the wrong branch, or a default that points to the head office. Nobody checked each one on a map at upload time. The worker is at the store; the circle is somewhere else entirely. When a store’s location is never verified against the ground, the geofence is guarding an address that doesn’t exist.
The radius is set too tight. A 20 or 30 meter radius looks precise on a map. Against 7 to 13 meters of ordinary urban GPS error, plus a large mall footprint, it is a trap. The worker at the north entrance is measured against a pin near the south wall and lands outside the circle.
The location is indoors or in an urban canyon. Malls, basement retail, and streets walled by tall buildings degrade GPS badly. The phone’s reported position can jump by tens of meters even while the worker stands still.
The store data was fixed, but the change never reached the field app. This is the failure that wastes the most time, because the admin genuinely corrected the record and the worker still can’t check in. Many field platforms only push updated store settings to a worker’s device when that device syncs. If the worker hasn’t synced since the fix, their app is still running on yesterday’s coordinates. The admin sees the corrected store; the worker sees the old rejection. Everyone assumes the fix failed when it simply hasn’t arrived yet.
That last one is worth sitting with, because it turns a solved problem into a support ticket. The diagnostic is not “did I fix the store,” it is “did the fix sync to the person complaining.”
How to fix geofencing attendance the right way
The goal is a geofence tight enough to catch fraud and loose enough to accept every honest worker. That balance is set store by store, in the data, not by lecturing the field team to “stand closer.”
Audit the store master file against reality. Pull the list of stores generating check-in complaints and verify each one’s coordinates. Drop the pin using the store’s real position, not the barangay center or a nearby landmark. Fix the placeholder and duplicate records first, since those produce the most dramatic “malayo daw” failures.
Set the radius to the real GPS tolerance, not an idealized number. Start from the ordinary urban error range of roughly 7 to 13 meters, add margin for the store’s physical size, and widen further for mall and indoor locations. A larger radius on a genuinely remote branch is not a fraud hole if the coordinates are correct and every check-in is photo-verified.
Verify presence with tamper-proof, geo-tagged photos, not the pin alone. A location stamp answers “was the phone near here.” A tamper-proof photo of the storefront, captured live and unable to be uploaded from the gallery, answers “was this person actually here, doing the work.” When presence is confirmed by evidence, you can afford a forgiving radius without losing accountability.
Handle low-connectivity and offline check-ins deliberately. Provincial routes and mall basements drop signal. A field app that captures attendance offline and syncs when the connection returns prevents the “I was there, but the app wouldn’t load” gap. Tarkie’s write-up on offline capabilities in field work apps covers why this matters for Philippine field conditions specifically.
Confirm the fix synced to the worker who reported it. After correcting a store, check that the affected worker’s device has synced the new settings before you close the ticket. Watch the sync log: if the worker hasn’t updated, the corrected coordinates are sitting in the dashboard, not on their phone. Tell them to sync, then confirm the check-in clears. Skipping this step is how a fixed problem reappears in the group chat an hour later.
Review the pattern, not just the incident. If the same three stores fail every week, the data is wrong, not the workers. Monthly, scan which locations generate the most rejected check-ins and clean those records in a batch instead of firefighting one Viber message at a time. The same review surfaces the stores that were never visited at all, since a location nobody can check into is indistinguishable from a location nobody went to until you separate the data problem from the coverage problem.
What good looks like
When the store data is right and presence is photo-verified, the geofence stops being a daily argument and goes back to doing its actual job: giving head office a real-time, trustworthy record of who is where.
This is the ground Tarkie was built for. Field teams in the Philippines don’t work in open fields with clear skies; they work in malls, wet markets, and dense city routes where GPS drifts and connectivity drops. Tarkie’s attendance runs on geo-tagged, tamper-proof photos, so a check-in is backed by evidence, not just a pin, and store assignment and location data are managed centrally by the admin, so a bad coordinate is a five-minute correction rather than a standing complaint. Megasoft uses Tarkie to keep secure attendance and coverage data flowing from 1,500 merchandisers and coordinators. The visibility only holds because the underlying store data and the check-in evidence are both reliable.
A trustworthy geofence is not a stricter geofence. It is a correctly located one, backed by proof of work, and kept in sync with the people who depend on it.
Frequently asked questions
Why does my geofencing attendance app say I’m too far when I’m at the store?
The app compares your phone’s GPS position to the store’s saved coordinates and check-in radius. If the store’s coordinates are wrong or the radius is set tighter than normal GPS drift, you get rejected even while standing at the door. The fix is correcting the store’s location data, not moving the worker.
What is a good geofence radius for field staff attendance?
There is no single number, because it depends on the store. Start from typical urban GPS error of roughly 7 to 13 meters, add margin for the store’s size, and widen it further for malls and indoor locations. Pair a forgiving radius with tamper-proof photo verification so accuracy does not cost you accountability.
How does GPS accuracy affect employee check-ins?
Smartphone GPS is accurate to about 4.9 meters under an open sky and often 7 to 13 meters in cities, and worse inside malls or urban canyons where signals bounce off buildings. A geofence that ignores this normal drift will reject honest workers. The radius has to account for real-world accuracy, not ideal conditions.
I fixed the store location, but the worker still can’t check in. Why?
Many field apps only apply updated store settings after the worker’s device syncs. If they haven’t synced since your correction, their app is still using the old coordinates. Check the sync log, have the worker sync, then confirm the check-in clears before closing the issue.
Can geofencing attendance work in areas with poor signal?
Yes, if the app captures attendance offline and syncs when connectivity returns. Provincial routes and mall basements routinely drop signal, so an app that requires a live connection to time in will strand workers who are genuinely present. Offline capture with later sync closes that gap.
Does a wider geofence radius let people cheat on their attendance?
Not on its own, as long as the store’s coordinates are correct and every check-in is verified with a live, tamper-proof photo. Fraud slips in through wrong data and unverified PINs, not through radius size. Evidence-backed check-ins let you keep the radius forgiving without losing control.