When the Employer Is the Cause
The findings caused by the employer's own arrangements, how to spot them, and why the first response is usually aimed at the wrong thing.
Five findings, and where each one actually came from
All five findings had an operational cause, all five were cheap to fix, and in each case the first response was aimed at the people. This is one employer's own account.
A large share of time findings are produced by the employer's own arrangements, and the first response is almost always aimed at the people. A queue produces badge-passing. A terminal in the wrong place produces missed punches. A system that pays the roster produces unrecorded overruns. A lateness rule with teeth produces punches ninety seconds before the hour.
The practical lesson in “When the Employer Is the Cause” is that visibility is not certainty. For teams researching remote workforce management software, examine the workflow on the provider site can add time and project context to the operational record, provided the purpose is explained, access is restricted and any material inference is checked through conversation and proportionate human review.
In each case the behaviour is the predictable result of an arrangement somebody chose, and in each case the cheapest fix is to change the arrangement.
Teams reviewing “When the Employer Is the Cause” can cross-check their approach against the IAPP privacy resources. The comparison is most useful when the organisation records which recommendations apply, which do not and why.
How to spot one
The signature is uniformity. A behaviour that appears across a shift, a site or a role, in the same form, is a response to something shared.
Individual dishonesty does not distribute evenly. When six people on one shift show the same pattern and nobody on the next shift does, the difference is the shift rather than the six people.
The four arrangements that produce the most
Capacity at the terminal: one device, a shift change, and arithmetic.
Physical layout: where the terminal sits relative to the lockers, the equipment store, the vehicle bay and the door.
Rules with consequences and no slack: lateness policies that bite at the minute, in operations where arriving to the minute is not possible.
System configuration: scheduled time substituted for recorded time, automatic deductions, approval queues that expire.
Each is covered in its own right across this collection, and each shows up at the investigation stage as somebody's conduct.
Asking the question first
Before anything else: is there anything about how we have arranged this that makes the behaviour the sensible thing to do?
Asked honestly, the answer is yes more often than not, and it is available in an afternoon of standing at a terminal with a watch.
Why the people response is chosen
Because it is faster, because it addresses the person who was noticed, and because the operational fix requires somebody to spend money or change a rule they set.
That is worth naming, because the pattern is structural rather than malicious. Nobody decides to blame the workforce for a queue; the queue is simply not in anybody's view at the moment the decision is taken.
What it costs to get this backwards
An investigation, a damaged relationship, a control purchased, and the behaviour continuing in a different form — because the cause was never addressed.
And one more thing that is harder to measure: the people who were doing the obvious thing find out what the employer assumed about them, and cooperation on everything else drops accordingly.
Fixing it and saying so
Where an operational cause is found, fix it and tell people that is what happened. A second terminal that appears with an explanation does more for the problem than the terminal alone.
It also makes the residual cases cleaner. Once the cause is removed, anybody still doing it is doing something different, and that is a much easier matter to address.
The question on the form
The cheapest intervention in this whole collection is a single field on whatever document opens an investigation.
| Field | What it forces |
|---|---|
| What operational cause was considered? | Somebody to look at the arrangement |
| What was checked to rule it out? | A specific answer, not an assurance |
| Who confirmed the arrangement is sound? | A named person outside the case |
Three fields, two minutes. They put the cause in front of the investigator before the person is, which is the entire argument of this page reduced to a form.
The finding that is about the organisation
Where the cause is operational, the output of the investigation is a recommendation about an arrangement rather than a conclusion about a person — and that has to be written somewhere it will be acted on.
A note in an individual's file saying the terminal is too slow changes nothing. The same finding sent to whoever owns the terminal, with the measurement, changes it.
Closing the matter with the person
Where an operational cause is found, the person who was investigated should be told clearly that the matter is closed and why.
That is the step most often skipped when an investigation fizzles out, and it leaves somebody believing they are still under suspicion for something that turned out to be the employer's arrangement.
Keeping the question in the process
The practical version is a line on whatever form starts an investigation: what operational cause has been considered and ruled out?
One field. It takes a minute to answer, it forces somebody to look at the arrangement before looking at the person, and it is the single change most likely to improve how these matters are handled.