TAC HRTAC HR
How to Stop Employees Clocking In From Outside the Work Site
Attendance, work periods and field reps

How to Stop Employees Clocking In From Outside the Work Site

Five controls that stop off-site clock-ins: a system-checked geofence, a bound device, fake GPS rejection, fingerprint or face check, and a rejected log.

5 min read

You stop off-site clock-ins with five controls that work together: a geofence checked by the system rather than the phone, an account bound to one device, rejection of fake locations, fingerprint or face verification before the punch is recorded, and a log of rejected attempts that management reviews. No single control is enough, because each one closes a gap the others leave open.

Why is it not enough for the app to send a location?

If the app alone decides whether the employee is inside the geofence, everything the system receives is what the device says about itself. If what the device sends is altered, the punch arrives looking clean. So the decision belongs to the system: it receives the location, compares it with the geofence of the site assigned to that employee, and accepts or rejects the punch.

What are the five controls?

1. A geofence checked by the system

The company defines a geofence on the map for each work site, and sets a punch location for each employee: anywhere, one location, or several. A branch employee's punch is accepted only inside the branch geofence. An employee who moves between two sites is assigned both.

2. One device per account

An employee's account is bound to one device. If they sign in on a new device they are blocked, and a dialog sends a device change request to management. This stops a colleague from borrowing another colleague's phone to punch for them, because the account only works on a device management has approved.

3. Rejecting fake locations

The system rejects the punch when the location comes from a mock location provider, or when a mock location app is enabled in developer options. The app also checks the integrity of the device:

  • Jailbroken or rooted phones.
  • Emulators.
  • USB debugging.
  • A mismatch between the satellite location and the network location.
  • Approximate location.
  • The device integrity check from Google Play.

On any of these the punch is rejected and management is notified.

4. Fingerprint or face verification before the punch

When the company turns this option on, the app asks the phone to verify its owner before attendance is recorded. The system issues a one-time challenge valid for 5 minutes, so the same approval cannot be reused for another punch. The aim is that the person punching is the account holder, not someone holding an unlocked phone.

5. A log of rejected attempts

Every rejected attempt is recorded and appears to management on the web only, never in the employee's app. The value is operational: management can see the pattern. One stray attempt from someone who forgot they were outside the geofence looks different from repeated attempts with a fake location.

What does the system not do?

  • It does not record a punch without internet. System verification needs a connection, and TAC HR has no offline attendance.
  • It does not capture a photo of the employee at the punch.

So the controls reduce fraud rather than promise to eliminate it, and reviewing the rejected log regularly is part of running the system.

Checklist before you turn it on

  1. Draw each site's geofence on the map so it covers the building and the parking area without extending far past them.
  2. Assign each employee a punch location: one site, several sites, or anywhere for field staff.
  3. Keep device binding on, and decide who approves device change requests.
  4. Turn on fingerprint or face verification at the branches you consider highest risk.
  5. Choose who receives the rejected-attempts alert, and review it at least weekly.
  6. For branches where staff do not carry suitable phones, use a compatible fingerprint terminal so its punches reach the same record.

Example: an employee punches from the cafe next door

An employee arrives at the cafe opposite the branch 10 minutes before the start of the shift and tries to punch. The system receives the location, finds it outside the branch geofence, rejects the punch and records the attempt. The employee tries again after walking in and the punch is accepted. The rejected log shows one attempt with its time and location, so the manager knows it was a stray attempt without having to ask.

If the employee had used a mock location app to place the phone inside the branch, the punch would be rejected for a different reason that shows in the log, and management would be notified. The difference between the two cases decides how to respond.

Attendance in TAC HR

TAC HR offers mobile punching with the geofence verified in the system, device binding, fingerprint or face verification when the company turns it on, more than one work period per employee, and it calculates lateness, early departure and partial absence. See the attendance service, the geofence setup guide and the field supervisor dashboard.

Frequently asked questions

Can an employee punch for a colleague?

The account is bound to one device, and with fingerprint or face verification on, the phone verifies its owner before recording. A punch from an account on a device management has not approved is not accepted.

Does the employee see their rejected punches?

No. Rejected attempts appear to management on the web only.

What happens if the signal is weak at the site?

No punch is recorded without internet, because the system does the verification. The employee retries when the connection returns, and the company decides who corrects a forgotten punch through a missed punch request.

Does a field employee need a geofence?

Their punch location can be set to "anywhere", and their visits are followed instead, with location proof inside the customer's geofence. The field attendance guide covers it.

Does this work with fingerprint terminals?

Compatible terminals connect with a key for each device and a log of rejections, and their attendance reaches the same record.

Practical guides for this procedure

Show us how you work, and we'll show you the difference.

In the demo we walk through a full day in your company: the morning punch, a request, the month's payroll, and the rep in the field, on data like yours.