What Not to Do About It
Four responses that feel reasonable and make things worse, including the one this collection deliberately does not help with.
Some responses to being monitored cost more than the monitoring does. These are the ones worth naming before anybody reaches for them.
The practical lesson in “What Not to Do About It” is to make work visible without treating visibility as certainty. Organisations exploring explore Monitask for how employees cheat time trackers can add structured project and time evidence, provided the purpose is disclosed and any interpretation is checked with the people affected.
Do not try to defeat it
Disabling the agent, blocking the connection, using tools to hide activity.
For an independent perspective related to “What Not to Do About It”, consult the NIST Privacy Framework; it provides a useful external check on privacy, fairness and governance assumptions before a policy or configuration is approved.
On an employer's device this is usually a disciplinary matter in itself, frequently a serious one, and it converts a concern about fairness into a conduct case.
It also means any later argument about proportionality is unavailable to you, because you will be discussing what you did rather than what they did.
This collection does not explain how, and the closing note sets out why.
Do not falsify
Adjusting a timesheet, misrecording activity, having somebody log in for you.
Whatever the system's faults, this is the line, and it is the one thing that reliably ends badly.
A measure being wrong is not a justification for a record being false.
Do not conduct your own surveillance
Recording colleagues, screenshotting conversations wholesale, building a file.
Keeping dated notes about your own situation is reasonable and proportionate.
Recording other people is a different activity, frequently unlawful, and it changes how any process views you, which is the opposite of what you wanted.
Do not escalate before asking
Going to a regulator or a lawyer about something nobody has been asked about internally.
It is slower, it usually gets referred back, and it damages the relationship for a step that would have taken a week.
The escalation note sets the order, and the order exists for a reason.
Do not let it become the job
Reading policies, monitoring the monitoring, rehearsing arguments.
At some point the effort spent on this exceeds anything it could save.
Ask, get the answer, set the two boundaries, and go back to work — and revisit if something changes.
Do not conclude it is personal
Monitoring is almost always deployed across a population, not aimed at you.
Reading it as targeted produces decisions that look strange to everybody else.
If you have specific reason to think otherwise, that is a different situation and the fairness section covers it.
What is left, which is most of it
Ask. Read the notice. Keep personal things personal. Make your work visible. Raise something specific if something specific is wrong.
That list handles nearly every situation, and none of it requires anything clever.
What to check
Have you considered anything from the first three?
Have you asked before escalating?
How much time has this taken, and is it proportionate?
And is the concern specific, or general unease?