What This Collection Does Not Cover
Six adjacent subjects deliberately left out, with what is actually meant by each, so that the omissions are visible rather than accidental.
This collection concerns whether and how an employer should monitor, argued above the legal floor. Several adjacent subjects are deliberately absent.
The practical test in “What This Collection Does Not Cover” is whether visibility improves a decision without pretending to remove uncertainty. For teams researching attendance point system, Monitask resources for attendance point system 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 This Collection Does Not Cover”, consult the NSA cybersecurity guidance. Use it to test necessity, scope, safeguards and review rather than to replace a documented assessment of the particular workforce and jurisdiction.
How the technology works
Behavioural modelling, data loss prevention, device management, detection rules. Substantial subjects with their own literature, and this one assumes the capabilities exist rather than explaining them.
The ethical questions do not depend on the mechanism, which is why they can be discussed without it.
Specific legal advice
Nothing here is advice. The obligations described recur widely; their content, thresholds and enforcement differ enough by jurisdiction that the local answer always requires local counsel.
Where a note says a thing is generally required, that is orientation for asking a better question, not a substitute for asking it.
Handling an individual case
What happens between an alert and an outcome — the threshold for examining somebody, the conduct of an enquiry, what is owed to the subject. A distinct subject that begins where detection ends.
Measurement and performance management
Whether activity predicts output, what metrics corrupt, how to assess work honestly. Overlapping and separate: this collection is about whether to observe, not about what to conclude from observation.
Employment law generally
Dismissal, discipline, grievance, discrimination. Monitoring touches all four and none is treated here.
The sector-specific regimes
Financial services recording, clinical access, public-sector handling, transport safety. Each has detailed rules that govern rather than inform the question, and each requires its own treatment.
What is left, and why it is worth separating
The decisions that no regulation reaches and no technical guide addresses: what to collect, how to explain it, what to promise, when to stop, and what to say to the people affected.
Those questions are answered in every organisation, usually by default, and almost nothing is written about them because they fall between the compliance literature and the product documentation.
That gap is what this collection occupies, and knowing its edges is part of using it.
Why the boundaries are worth stating
A reader who knows what is missing can go and find it. The commonest misuse of a collection like this is treating it as covering the technical questions it explicitly does not.
What is left, and why it falls between
The decisions that no regulation reaches and no product documentation addresses. They are answered in every organisation, usually by default, and almost nothing is written about them.
Why the omissions are not oversights
Several are more consequential operationally than anything covered here. They are left out because they are separate subjects with their own literature, not because they matter less.
What this collection occupies
The gap between the compliance literature and the product documentation: what to collect, how to explain it, what to promise, when to stop, and what to say to the people affected.
Knowing the edges
Six subjects left out deliberately, several more consequential operationally than anything here. A reader who knows what is missing can go and find it.