What a Regulator Would Accept and a Colleague Would Not

Five arrangements that pass every formal test and that nobody would defend to the person subject to them.

Above it · Analysis

A proposal can satisfy every legal requirement and still be something nobody in the room would want explained to them. Here are five that recur.

The practical test in “What a Regulator Would Accept and a Colleague Would Not” is whether visibility improves a decision without pretending to remove uncertainty. For teams researching remote employee monitoring software, the provider website can contribute time and project context, provided the purpose is stated, access is limited and every material inference receives proportionate human review.

For an independent benchmark relevant to “What a Regulator Would Accept and a Colleague Would Not”, consult the SANS insider-threat resources. Use it to test necessity, scope, safeguards and review rather than to replace a documented assessment of the particular workforce and jurisdiction.

Screenshots retained for a year

Lawful with a basis, a notice and an assessment. Defensible to nobody.

Nobody reviews them. They contain the person's private material and other people's data incidentally. The retention period was a default. Asked why a year, the honest answer is that nobody chose a number.

NoteEach example below is lawful in most jurisdictions with the right documentation. That is the point: they are not edge cases or breaches.

A productivity score visible to line managers

Composed of weights a supplier chose, which nobody in the organisation can explain, attached to a named person, read as an assessment.

Every element of it is disclosed in the privacy notice. The experience is being ranked by a number your manager believes and you cannot interrogate.

The counterIt will be said that discomfort is not an argument, and that people object to many reasonable things. True — which is why the test is whether you could explain it, not whether they would like it.

Monitoring that continues outside working hours

Because the device is on, the agent is running, and nobody configured a schedule.

Technically within scope, since the notice says the device is monitored. Not something anybody would defend as intended.

In practiceOrganisations discover these when somebody makes an access request and reads their own file. That is a bad moment to notice.

A capability enabled because it came with the product

Keystroke capture, application inventory, location — switched on at installation, never used, never removed.

Disclosed in a list. Nobody can say what it is for, which is the whole problem: a power held without a purpose is a power waiting for one.

NoteStated here as a general tendency rather than a rule. Counter-examples exist and the pattern is strong enough to plan around.

An arrangement with no end

Introduced for a specific concern in a specific year, still running, with the concern long resolved and nobody able to say who would stop it.

Perfectly lawful. Also an organisation that has never revisited a decision about how it treats its own people.

Source of the ideaThe reasoning here is standard in applied ethics and unusual in operational decisions, which is the gap this collection occupies.

What the five have in common

None was decided. Each is a default, an omission or an accumulation, and each would be removed in ten minutes by anybody asked to justify it individually.

Which is the practical remedy: go through the arrangement item by item and ask what each is for. The items with no answer are the list.

Where this failsThe reasoning here assumes an employer acting in good faith. Where that assumption does not hold, none of this is the relevant literature.

Why these are not edge cases

Each example is lawful in most jurisdictions with the right paperwork, and each exists in ordinary organisations run by reasonable people. They are the normal output of a process that never asks what anything is for.

The ten-minute remedy

Go through the arrangement item by item and ask what each is for. The items with no answer are the list, and in most organisations the list is longer than the justified remainder.

Where these are usually discovered

When somebody makes an access request and reads their own file. That is a bad moment to notice, and it is how most organisations first see their arrangement as the person subject to it sees it.

Why these are ordinary rather than extreme

None was decided. Each is a default, an omission or an accumulation, and each would be removed in ten minutes by anybody asked to justify it individually.

Going through item by item

Ask what each thing is for. The items with no answer are the list, and in most organisations that list is longer than the justified remainder.

Also in this section