How to Set Up Geofenced Attendance for Field Sales Teams (Without Breaking Your Reps' Trust)

By Sufyan · 2026-07-18 · 4 min read

The first geofence I ever set up was 50 meters around a distributor warehouse in Sharjah. Sounded reasonable on paper. In practice, half the reps couldn't clock in because they were parked across the street and the GPS drift pushed them just outside the boundary.

I got this wrong at first. Really wrong.

So if you're about to roll out geofenced attendance for your field sales team — whether that's 20 reps in Karachi or 300 across the GCC — I want to save you the two months I spent tuning radiuses and arguing with sales managers who thought the software was "broken."

Here's how to actually do this.

Step 1: Decide what you're geofencing (and why)

Most people jump straight to "attendance" without thinking about what that word means for a field rep. A rep isn't sitting at a desk. Their "office" moves.

So you've got three real options:

Home-base geofence — the rep checks in when they arrive at their assigned distributor warehouse, depot, or branch office in the morning. This is the most common setup for FMCG teams. Clean, simple, and gives you a real "start of day" timestamp.

Beat-based geofence — the rep checks in at every outlet on their beat. This is what we default to in Zivni for merchandisers and pre-sellers. It gives you outlet-level visit proof, not just a morning ping.

Territory geofence — a big polygon around the entire assigned territory. Honestly, I'd skip this unless you have a very specific compliance reason. It's too loose to be useful.

Pick one as your primary. You can layer the others later.

Step 2: Set the radius (this is where people mess up)

Here's the thing about GPS on a mid-range Android phone in a dense urban area. Accuracy floats between 8 and 40 meters depending on tall buildings, weather, and how long the phone has been outside. In malls or basements it gets worse — sometimes 100m+.

My rules of thumb after roughly 3 years of this:

If your outlets sit in a strip where 6 shops share the same block, don't set 100m radiuses. You'll get false check-ins at the wrong store all day. Tighten to 30-40m and accept a slightly higher retry rate.

Step 3: Handle the edge cases before rollout

This is the part nobody tells you about. The rollout doesn't fail because of the software. It fails because of the 4% of check-ins that don't fit the model.

Things I now build into every geofence check-in software deployment:

GPS spoofing detection. Yes, reps do this. In some markets more than others (I won't name names). Any decent GPS geofencing sales reps setup should flag mock location apps and freeze the check-in for review. Not auto-reject — flag. Innocent reps get caught by fake positives too.

Offline check-ins. A rep in a basement grocery in Manama has no signal. Your app should cache the GPS coordinates and timestamp locally, then sync when they surface. If it doesn't, reps will just skip the check-in and you'll get blamed for the gap.

Battery-saver mode. Android throttles background location. If your reps enable aggressive battery saver, your geofenced attendance field sales data will look like Swiss cheese. Add a check on app open that warns them.

Buffer time. Give the app 15-30 seconds to acquire a proper GPS lock before rejecting a check-in. First reading is almost always the worst one.

Manual override with photo + reason. Sometimes the geofence is genuinely wrong. Store moved. New outlet not yet mapped. Let the rep submit a check-in with a selfie and a reason, and route it to their manager for approval. This one feature reduced our support tickets by something like 60%.

Step 4: Roll it out without a mutiny

Look, reps hate feeling surveilled. And honestly, if you frame geofenced attendance as "we don't trust you," you deserve the backlash you'll get.

What worked for us and for most of our customers:

  1. Announce it 2 weeks before go-live. No surprises.
  2. Explain the why — faster payroll, no more manual attendance sheets, protection against false complaints from managers.
  3. Run a 1-week parallel period where both manual and geofenced attendance are captured. Compare. Fix mismatches openly.
  4. Publish the radius sizes. When reps know a warehouse has a 100m fence, they stop wondering if the system is arbitrary.
  5. Give managers a review dashboard, not an alarm system. Nobody needs a WhatsApp ping every time someone clocks in 4 minutes late.

One distributor we work with in Lahore rolled this out to 84 reps in 11 days using exactly this playbook. Attendance disputes dropped from around 30 a month to 3.

Step 5: Measure the right things after go-live

Not "how many check-ins happened." That's vanity.

Look at: check-in success rate on first attempt (target above 92%), manual override rate (should settle under 5% after week 3), average time between arriving at a location and successful check-in (under 45 seconds is healthy), and the gap between first check-in of the day and first order captured. That last one tells you if reps are checking in from home and driving later. It happens.

If any of these look off after 30 days, don't blame the reps. Blame the radius. Usually it's the radius.

Anyway — that's the version of this guide I wish someone had handed me in 2022. If you're setting this up now and hit a weird edge case, my inbox is open. There's always a weirder one.

© 2026 Zivni. All rights reserved.