Consulting Before Deployment
A requirement in many jurisdictions and the step that most improves the design. What to consult on, and what to do with the answers.
Procedure
Introducing time recording touches pay, working conditions and privacy at once. In several jurisdictions that makes consultation a legal requirement rather than good manners.
Why it is required
Changes to working conditions generally engage consultation duties, and how working time is recorded is a working condition.
Works councils in a number of European jurisdictions have co-determination rights over technical systems capable of monitoring employees — which covers most time tracking products regardless of how they are configured.
Collective agreements may impose their own requirements independently of statute.
Data protection assessments expect the views of affected people to be sought where appropriate.
Why it improves the result
People know which categories will be guessed at. A project list that looks sensible to a finance team is unusable to the people filling it in, and they will say so.
They know the boundary cases: travel, on-call, handover, the work that starts before the clock.
They know what will be gamed and how.
They surface the confidentiality problems, particularly where narrative fields are involved.
A design that survives consultation produces a more accurate record, which is the entire point of the exercise.
What to consult on
Which of the four purposes the system serves, stated plainly.
What is recorded and what is not, with the negative list explicit.
Whether any activity monitoring is enabled. This is the question people actually have.
How the record is corrected, and who can change it.
Retention, and who can see what.
What happens if the record shows someone working excessive hours, which is a question about the organisation rather than the software.
Doing it properly
Before the decision, not after. Consultation on a signed contract is an announcement.
With representatives where they exist, which in several jurisdictions is not optional.
In work time, which determines attendance.
With someone present who can change the design.
With a written response to every point raised, including where the answer is no and the reason.
What you will be asked
Prepare these, because they arrive every time.
"Will this be used against us?" Answer with the written purpose limitation, and be ready to point at who enforces it.
"Does it watch my screen?" A yes-or-no answer, and if the honest answer is uncomfortable the design is the problem.
"What if I forget to clock out?" A real usability question with a real answer, and the answer must not be "your hours get cut".
"What happens to my data when I leave?" Retention, stated as a period.
"Who sees my hours?" Named roles, not "authorised personnel".
After
Publish the response, to everyone consulted and not only to representatives.
Say what changed. Something should have.
Say what did not and why, including where the reason is cost.
Return at the review point with what the data showed, which is what makes the next consultation productive rather than performative.
Preparing the answers
Five questions arrive every time; have them answered before the meeting.
"Will this be used against us?" The written purpose limitation, and who enforces it.
"Does it watch my screen?" Yes or no, and if the answer is uncomfortable the design is wrong.
"What if I forget to clock out?" A real usability answer that does not involve losing hours.
"Who sees my hours?" Named roles.
"What happens to my data when I leave?" A retention period.
Improvised answers become the policy, which is why they should not be improvised.
Responding in writing
What separates consultation from an announcement.
Record everything raised, including what you disagree with.
Respond to each point specifically.
Say what changed as a result — something should have.
Say what did not and why, honestly, including where the reason is cost.
Publish the response to everyone consulted, not only to representatives.
A consultation with no written response is remembered as a meeting, and the next one gets a smaller turnout and worse information.
A concrete product reference
When translating this principle into a buying test, this consultation prompt provides a concrete feature and workflow reference. Verify the relevant behaviour in a trial, retain the exported evidence and judge it against the purpose and limits described above.