When the Punch Is Refused

Someone is standing at the door, at work, and the app will not let them clock in. What happens next is the whole system.

Why it happens

No fix indoors, which is the commonest cause.

A position estimate outside the boundary despite the person being inside.

Location permission denied or downgraded by an operating system update.

Battery saver reducing location accuracy.

Airplane mode, no signal, a dead battery.

A phone left at home, which is not a system failure and still needs an answer.

The rule that has to hold

The person starts work.

They do not stand outside trying again, and they do not work unpaid.

Which means there has to be a fallback that takes seconds and does not require finding a manager.

Without one, the system converts an ordinary technical failure into unpaid working time, and that is a wage claim in most jurisdictions rather than an inconvenience.

Fallbacks that work

Accept with a flag. The punch goes through, marked as outside the boundary, and is reviewed later. This is the best default and many products offer it.

A supervisor override, logged, for sites with someone always present.

A manual entry the worker submits, approved afterwards.

A second method — a code on the wall, an NFC tag — which has its own note and is the strongest answer.

Any of these beats refusal. The question is which fits the site.

Designing the review

A flagged punch is not an accusation.

Review in batches, weekly, looking for patterns rather than individuals.

A person with many flags is usually at a site with poor coverage, and checking the site's refusal rate first is the correct order.

A pattern at one site is a boundary problem.

Only after both is it a conversation, and by then you will usually know the answer.

What to measure

Refusal rate per site, per week. This is the headline number and most deployments do not track it.

Fallback usage, which tells you how often the primary method is failing.

Time from refusal to resolution, which is the worker's experience of the system.

Flags reviewed against flags raised. If nobody reviews them, the flag is a fiction and the accept-with-flag design has become accept-everything.

The thing not to do

Do not treat a refusal as evidence of anything.

Six of the causes above are not the person's doing, and the seventh — a phone left at home — is not misconduct either.

Do not withhold pay pending resolution, which in most jurisdictions is unlawful and everywhere destroys the arrangement.

Log the failure

The record that settles every later dispute.

Most products store successful punches and discard refusals.

Which means a worker saying "it wouldn't let me clock in" cannot be confirmed or contradicted.

Store each refusal with its time, cause and accuracy figure.

Ask for it at procurement, where it costs nothing, rather than discovering the gap during a grievance.

A concrete product reference

When translating this principle into a buying test, read the feature details provides a concrete workflow reference. Verify current behaviour in a trial and judge it against the purpose and limits above.

Independent reference

For an external point of reference, see GPS.gov. Its published guidance provides useful context for testing the assumptions in this note.