Consulting Before You Deploy

Introducing a clock-in system that checks location touches pay and privacy at once. In several jurisdictions that makes consultation a legal requirement rather than good manners.

Why it is required

Technical systems capable of monitoring employees trigger co-determination rights in a number of European jurisdictions, and a works council can block deployment.

Changes to how pay is determined engage consultation duties in their own right.

Collective agreements may impose requirements independently.

And an impact assessment expects the views of affected people to be sought where appropriate.

Why it improves the design

Workers know where the phone does not work. The corner of the basement, the stockroom, the lift lobby — a fortnight of asking saves a month of investigating refusals.

They know the shift-change queue and how long a punch can take before it causes a bottleneck.

They know who does not have a suitable phone, which is the question nobody asks until someone is unpaid.

And they raise the fallback question first, which is the thing most deployments leave undesigned.

What to consult on

What is checked and when, stated plainly.

Whether the app can see location at other times.

The radius and how it was chosen.

What happens when a punch is refused — this is the question people actually have.

Whether anyone without a working phone has another route.

Whether flagged punches will be used in disciplinary matters.

Retention.

The questions you will be asked

Prepare these, because they arrive every time.

"Can you see where I am when I'm not at work?" A yes or no, and if the honest answer is uncomfortable the design is the problem.

"What if it won't let me clock in?"

"What if my battery's dead?"

"Will I be paid if the app fails?" The answer must be yes, plainly.

"Do I have to use my own phone?"

Doing it properly

Before procurement, not after a contract is signed.

With representatives where they exist, which in several jurisdictions is not optional.

With someone present who can change the design, because the radii should come out of this conversation.

With a written response to every point, published to everyone consulted.

Say what changed. Something should have, and if nothing did, the consultation was an announcement.

The radii should come out of it

What makes this consultation different from a formality.

Workers know where the phone does not work.

A fortnight of asking replaces a month of investigating refusals.

Bring the site measurements and discuss them.

A consultation that produced no change to the radii did not use the information in the room.

Turn the principle into a test

For an example that can make this requirement testable, consult this operational use case. Treat the page as a starting point rather than proof and reproduce the workflow with real roles and failures.

Independent reference

For an external point of reference, see ACAS guidance. Consult the current material directly because technical and legal details can change.