Use case · Attendance integrity

How to stop employees marking attendance from outside the site

Lock every punch to a geo-fence around the site, verify it with the employee's face, and flag spoofed locations — so attendance can't be marked from the gate, the parking lot, the road outside, or home.

Start free trial

Per-site geo-fence · face check · mock-location detection · offline-safe

Your team knows the drill. The first few reach the actual site. The rest mark present from wherever they are — the bus stop, the flat across the road, the car park — because your attendance app only checks that they're 'somewhere in the city'. By the time the supervisor notices, the day is already logged.

You stop it by making the punch impossible from outside the site. Bazat Tracker disables the punch button until the employee's verified GPS location is inside the site's geo-fence, adds a live face check, and detects fake-GPS apps — so 'near the site' and 'at home' both fail.

Why most attendance apps don't stop this

A punch that only records a photo or a city-level location is easy to make from anywhere.

No location lock

If the app just captures a selfie and a timestamp, the employee can punch from their kitchen.

A radius that's too wide

A one-kilometre 'office area' fence lets people mark present from the market, the parking lot, or a nearby cafe.

Fake-GPS apps

Free mock-location apps let a rooted phone report any coordinates. A plain geo-check believes them.

One phone, many punches

Without a face check, one person on site can mark the whole gang present from a single device.

How Bazat Tracker blocks outside-site attendance

Four checks that all have to pass before a punch is accepted.

Geo-fence lock

The punch button is disabled until the phone's verified location is inside the assigned site boundary.

Right-sized radius

Set the fence to the real perimeter — 50–80 m for a tight urban plot — so standing outside doesn't count.

Mock-location detection

Fake-GPS apps, developer mode and rooted devices are detected, and the punch is flagged or blocked.

Face verification

Each punch is matched to the specific employee, so one phone can't mark several people present.

Offline, still enforced

The location check runs on the device and syncs later — the fence rule applies with or without network.

Logged exceptions only

Genuine exceptions go through a supervisor approval with a reason, recorded separately for audit.

A worked example

A facility management contractor with 200 housekeeping staff across 14 client sites switched on geo-fence lock and face verification. In the first payroll cycle, verified attendance came in about 9% lower than the old register — the gap was punches that used to be made from outside the sites. That 9% was recovered payroll leakage, every month.

How to set it up

  1. 1

    Draw a fence per site

    Pin each site and set the radius to the actual boundary, not a loose area.

  2. 2

    Turn on face verification

    Require a live face match on every punch so shared phones can't produce attendance.

  3. 3

    Enable spoofing checks

    Switch on mock-location and rooted-device detection to catch fake-GPS attempts.

  4. 4

    Define the exception path

    Decide who can approve a manual entry and require a reason on each one.

  5. 5

    Review week one

    Check flagged punches and borderline cases, and tighten any radius that's still too generous.

Selfie app vs wide-radius geo-check vs Bazat Tracker

CapabilitySelfie-only appWide-radius geo-checkBazat Tracker
Punch tied to the real site boundary
Blocks 'near the site' marking
Detects fake-GPS / spoofing
Stops one phone marking many present
Enforced offline
Exceptions logged for audit

Partial = supported weakly, or only for a single loosely-defined location.

FAQ

Stopping outside-site attendance — FAQs

Put a geo-fence around each site and lock the punch button to it. The button stays disabled until the employee's verified location is inside the boundary, so the gate, the parking area, the next building and home all fail the check.

Yes. Bazat Tracker detects mock-location apps, developer mode and rooted or jailbroken devices, and flags or blocks those punches. A face check on punch-in means spoofed coordinates alone can't produce attendance.

Set the radius to match the site. For a tight urban plot, 50–80 metres keeps the boundary at the actual perimeter, so standing across the road doesn't count as being on site.

Yes. Supervisors can approve a manual or regularised entry with a reason, and every such entry is logged separately from the automatic ones for audit.

Yes. The location check runs on the device and the punch is stored offline, then synced when the phone regains signal. The geo-fence rule still applies.

No. Punch-out is also locked to the site boundary, so leaving early and clocking out later from home is blocked the same way.

Try to beat the geo-fence on a live demo

We'll set a fence around one of your sites and let you attempt a punch from inside it, from outside it, and with a fake-GPS app — then show what each one records.

Start free trial