Photographs at Clock-In

General orientation, not legal advice.

A picture at the moment of clocking is offered by most attendance products, frequently as a free module. It is effective and it is a decision.

What it does

Addresses identity directly, which the card, the code and the geofence do not.

Deters rather than detects in most deployments, because nobody reviews the images unless something prompts it.

And that is fine — deterrence is the objective, and a stored image that is occasionally checked achieves it.

The line that matters

A photograph stored for a human to glance at is one thing.

A photograph matched against a stored template of that person's face is another, and in most data protection regimes the second is biometric processing with a higher bar.

Products call both "face verification".

Ask which yours does, because the answer determines the entire legal analysis and the marketing will not distinguish them.

What to decide before enabling

Is it stored or matched?

How long is it kept? The operational need is days for the current pay period, not indefinitely.

Who can see it, and is access logged?

Is it reviewed routinely, or only on a specific prompt? Routine review of everyone's face every day is a different proposition.

What happens on a poor image — bad light, a mask, a hard hat? A refusal here has the same consequences as any other refused punch.

The obligations

Notice, specifically, because people notice a camera and will ask.

An impact assessment, which for a photograph at every punch across a workforce is likely required.

Consultation, where it applies.

And a decision recorded, including the decision not to enable matching if you chose storage only.

Proportionality

Where supervision exists, a photograph is hard to justify — a person is already verifying identity, for nothing.

Where it does not — unmanned sites, lone night shifts, dispersed contract work — the case is real.

State which situation you are in, because that sentence is the whole proportionality argument and it is either true or it is not.

What not to do

Do not enable it because it came with the product.

Do not review images routinely without a reason, which turns deterrence into monitoring.

Do not keep them beyond the pay period unless an investigation requires it, with a hold.

Ask which it does

The question that determines the whole legal analysis.

Stored for a human to glance at, or matched against a template?

Products call both "face verification".

The second is biometric processing with a higher bar in most regimes.

Ask it in writing, because the answer decides what obligations attach and the marketing will not distinguish them.

Reproduce the workflow

For another way to make this requirement testable, consult the form-based example. Reproduce the case with real roles, codes, failures and recovery steps.

Independent reference

For a thematic point of reference, see ICO guidance. Use this established source as an outside check before turning the principle into a system rule.