Blog Industry

Proving attendance at a post you do not own

6 min read

When a client asks whether its post was manned last Tuesday night, “the guard says so” is not an answer. The employer needs evidence it can stand behind. A punch at a post evidences some things precisely and others not at all, and a punch refused for being outside a boundary would leave the employer with less evidence. Here is what a geofence records, and why recording beats refusing.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes what a punch records in TriblockHR; it makes no claim about patrol verification or location accuracy.

The client’s question

Take an invented guarding firm, Bastion Guard, and one of its clients, an invented property manager running a gated residential estate. One morning, the estate manager writes: a resident says the night gate was unmanned at 02:00 last Tuesday. Was it?

Bastion Guard’s night supervisor could ask the guard, who says he was there all night. That is a statement. The client wants to know what the employer’s own record shows.

The answer depends on what was captured when the guard came on and went off duty.

What a punch at a post records

In TriblockHR, the estate is a division, with a latitude, a longitude, a map address and a geofence radius in metres. The guard on the night gate clocks in and out by one of four capture routes: a terminal, facial recognition on a tablet, the web clock, or mobile.

A punch at the post records:

  • That a punch happened, and when.
  • By whom. At a terminal, the guard is identified on the device by face, fingerprint or keypad, depending on the hardware, and the authentication method is captured on the punch. Biometric time clocks covers the terminal.
  • By which method and on which device, where it was a terminal. The method is reportable, so a face punch and a keypad punch stay distinguishable afterwards.
  • At which division: the division clocked in at.
  • Inside or outside the boundary, for a mobile punch, with its location at that moment.

For Bastion Guard’s night gate, the record shows the guard’s clock-in at 19:02, by face at the gatehouse terminal, and his clock-out at 07:04, the same way. That is the evidence: who started and finished duty at that post, when, and how he was identified.

Outside the fence: recorded, flagged, standing

Suppose instead the guard clocked in on the mobile app, and his punch fell outside the estate’s fence.

In TriblockHR, a mobile punch outside the fence is recorded and flagged, with a notification, and the punch stands. The supervisor sees a same-day exception: this guard’s clock-in was outside the boundary for this division. GPS clock-in and geofencing covers the mechanism.

There are ordinary reasons a punch can fall outside: the guard clocked in while walking from the bus stop to the gate, the fence radius was set tight for a large estate, or the phone’s location was imprecise at that moment. There are also reasons that matter: the guard clocked in from somewhere else. The flag does not decide which. It puts the question in front of a supervisor on the day, while the guard can still be asked and the answer still checked.

A punch with no location at all is refused. That is the one case where a mobile punch does not go through, because a punch with nothing to say about where it was made is not evidence of anything.

Why recording beats refusing

It might seem stronger to refuse a punch outside the fence. Consider what that would leave.

A refused punch loses the hours. If the guard was in fact on duty, and his punch was refused because he was a few metres short of the gate, he is now on the night with no clock-in. Someone has to add his hours later by hand, and the record of his start is a supervisor’s entry.

A refused punch loses the evidence that somebody tried. The fact that a punch was attempted, from a particular place, at a particular time, is itself useful. A refused punch leaves nothing behind.

A flagged punch keeps both. The hours are recorded, the location is recorded, and the exception is in front of a supervisor the same day. If the guard was at the bus stop, the supervisor notes it and moves on. If he was not on the estate at all, the supervisor knows on the day, well before the client writes a week later.

So for Bastion Guard, a flagged punch on the night of the client’s question would be more useful than a refused one: it would show the attempt, its location and whatever the supervisor recorded about it.

What a punch does not evidence

Being exact about the limits is part of standing behind the evidence.

  • Location is captured at the moment of the punch only. It is not continuous and is not tracking. A punch at 19:02 says nothing about where the guard was at 02:00.
  • It is not patrol verification. TriblockHR does not run guard tours or patrol checkpoints, and does not handle incident reporting.
  • It is a detection control. A determined person can influence a phone’s reported location. A geofence makes casual misuse visible; it is not proof of presence.

For the client’s question about 02:00, the punch record shows that the guard came on duty at the gate and went off it, when and how. Whether he was at the gate at 02:00 is a question for whatever patrol or incident systems Bastion Guard and its client use. The security services page covers the wider operation, and TriblockHR Workforce the capture routes.

Questions

What happens to a mobile punch outside the fence?

It is recorded and flagged, with a notification, and the punch stands.

Is a punch with no location accepted?

No. A punch with no location at all is refused.

Does a geofence track guards during a shift?

No. Location is captured at the moment of the punch only.

Is a punch proof that a guard was on post all night?

No. It evidences when duty started and ended, by whom and where. It is not patrol verification.

Keep a record of every punch at every post, so a client’s question has an answer.

Book a demo

  • SOC 2 Type II attested
  • AES-256 at rest
  • 99.9% uptime
  • Built in The Bahamas