What This Is Not

The record answers one narrow question. Nearly every problem in this collection comes from asking it a wider one.

Not proof of identity

A punch establishes that a device registered a tap inside a boundary.

Not who held it.

Which is why supervision remains the stronger control against covering for a colleague.

Not a precise arrival time

The minutes between arriving and punching contain queueing, fix delays, retries and the walk to a place with coverage.

A punch window acknowledges this; a one-minute rule pretends it does not.

Not a fire roll call

A system with any refusal rate cannot be relied on to say who is in the building.

This is the one place in the subject where the error costs more than money.

Not a productivity measure

Being clocked in is not working, and everyone involved knows it.

Where to look instead: the work.

Not evidence against a person

Six of the seven causes of a refusal are not the person's doing.

Mock location flags are device settings, not confessions.

Accuracy varies enough that a position near a boundary means little.

Building a disciplinary process on this is how employers lose cases.

Not tamper-proof

Mock location tools exist, work, and are easy to install.

The system deters the casual and not the determined, and saying so internally prevents a later embarrassment.

Not permanent

Coordinates have a short operational life. Keeping them for years is not thoroughness; it is a liability with no use.

What it is

A consistent record that a person registered their arrival at a defined place and time, within a stated accuracy.

That is genuinely useful: it deters clocking in from home, it removes arguments about arrival times, and it produces a pay record that both sides can see.

Claim that and no more. The overclaiming is what makes the whole record less credible when one part of it is challenged.

The four it does support

Worth stating alongside the negatives.

That a punch was registered, at a time.

At a place, within a stated accuracy.

By a device belonging to a named person.

With a record of whether the check passed or was overridden.

Four narrow facts, recorded consistently, and defending that boundary is what keeps them trusted rather than discounted along with the overclaiming.

An implementation prompt

During configuration, the available feature overview can prompt questions about fields, ownership and output. Confirm current capabilities and document each plan, integration or policy assumption.