Transparency With the Workforce

Insider programmes are usually described in a single policy line and otherwise unexplained. The resulting beliefs are worse than the reality and they are what people act on.

The programme test in “Transparency With the Workforce” is whether a record leads to a better, explainable decision. Organisations considering this workforce technology resource for employee monitoring data security can use time and project evidence to locate operational questions, while governance, direct conversation and periodic review remain necessary to interpret any pattern responsibly.

What people assume in the absence of information

That everything is read.

For a separate perspective relevant to “Transparency With the Workforce”, consult the SCCE compliance resources. Use it to test the proposed threshold, investigation scope and review process rather than to substitute a generic checklist for the facts of a case.

That the security function builds files on individuals as a matter of course.

That being flagged means being suspected.

That managers can request checks on people they dislike, which the manager note shows is sometimes true and should not be.

Each assumption is corrosive and each is cheaply corrected by saying what is actually the case.

What is worth publishing

What is monitored and what is not. The second half matters more, as it does in every monitoring question.

That alerts are mostly resolved without anybody being named, which is true and is the single most reassuring fact available.

Who can open an enquiry, and that a manager cannot simply request one.

What happens if you are the subject: that you will be told, that you may be accompanied, that you will be informed of the outcome.

And the counts: alerts, cases, findings, for the year.

The counts are the part that works

An organisation publishing that it examined a number of matters, opened a few and substantiated almost none is making a claim that can be checked against people's experience.

It also tells everybody what the base rate note establishes: that being flagged is ordinary and usually means nothing.

Programmes resist this because the numbers look like failure. They are not failure, and explaining why is the whole argument of the base rate note.

What not to publish

Details of detection rules, for obvious reasons.

Anything identifying individuals, including in aggregate where the population is small.

Specific cases, even anonymised, where colleagues would recognise them.

The reporting channel depends on it

The highest-value signal in most programmes is a human report, and people report to a function they believe is proportionate.

A programme perceived as an apparatus for catching people receives fewer reports and worse ones, because the cost of being wrong feels high.

Which means transparency is not only an obligation to the workforce. It is the thing that keeps the programme supplied.

Where to put it

Not in a policy nobody opens. A short page, found where people look, written in plain terms, with the counts updated annually.

And mentioned at induction, briefly, which is the point at which somebody can ask.

Publishing the counts

Alerts, cases, findings, for the year. It looks exposing and it is the most effective thing a programme can do for its own standing, because it tells everybody what the base rate note establishes: that being flagged is ordinary and usually means nothing.

Where the page should live

Not in a policy library. Somewhere people look, in plain terms, mentioned at induction where somebody can ask a question. A transparency statement nobody finds has the same effect as no statement, which is that people assume the worst.

Asking what people believe

Ten people, one question: what do you think the programme does. The gap between their answers and the truth is what should be published, and it is reliably larger than anybody expects.

What not to publish in practice

Detection rules, anything identifying individuals, and specific cases that colleagues would recognise. The constraint is narrower than programmes assume and it does not touch the counts, which are the part that actually works.

What people assume otherwise

That everything is read, that files are kept on individuals routinely, and that a manager can request a check on somebody they dislike. Each is cheaply corrected and each persists in the absence of any statement.

For the file: Ask ten people what they think the programme does. The gap between their answer and the truth is the thing to publish, and it is usually large.