The Employee FAQ: Twenty Questions Your Team Will Ask About Monitoring
Every monitoring rollout generates the same twenty questions. Answers delivered in a meeting evaporate; answers delivered in writing become the reference everyone actually uses - including the ones who were not in the room and the ones who arrive next year. Here is the question list and the honest answer pattern for each.
THE TWENTY QUESTIONS
1. WHAT EXACTLY IS COLLECTED?
Answer: name the categories - worktime, application usage, activity patterns, file events - and the ones that are not collected. The list of exclusions builds as much trust as the list of inclusions.
2. CAN YOU SEE MY SCREEN?
Answer honestly per configuration. If screenshots are off, say so plainly; if they exist in limited cases, describe exactly when.
3. IS EVERY KEYSTROKE RECORDED?
The answer for a well-designed program is no - and the policy should say it explicitly.
4. IS MY LOCATION TRACKED?
Separate on-duty location (if any) from off-duty; name the purpose and the boundary.
5. WHO CAN SEE MY DATA?
Roles, not names: who sees aggregates, who can open individual records, how access is logged.
6. CAN MY MANAGER LOOK AT MY DATA ANY TIME?
The honest answer: subject to access rules and logging; individual reviews require a documented reason in a governed program.
7. HOW LONG IS IT KEPT?
Per category, with the deletion mechanism. "Forever" is never the right answer and should never be the real one.
8. WHAT IS IT USED FOR?
The purposes from the policy - capacity planning, worktime accuracy, security - and the prohibition on repurposing.
9. CAN IT AFFECT MY PERFORMANCE REVIEW?
The rule: patterns start conversations; decisions are made by people using context; any metric used in a review will have been visible to the employee first.
10. DOES IT COUNT MY BREAKS?
How breaks appear in the data, and what the policy says about breaks and idle time.
11. DOES IT RUN OUTSIDE WORKING HOURS?
What is recorded, what is reported, and the disconnect policy in plain words.
12. IS MY PERSONAL PHONE INVOLVED?
Yes or no, and if yes, exactly what a work profile covers and what it cannot touch.
13. WHAT ABOUT WHEN I WORK FROM HOME?
The same policy applies; here is what it means for your role specifically.
14. CAN I SEE MY OWN DATA?
Where and how - and this should be a yes in every program that wants to be trusted.
15. WHAT IF THE DATA IS WRONG?
The correction route, the owner, and the timeline.
16. CAN I OBJECT OR REFUSE?
What local law allows, what the company's process is, and what happens either way - answer honestly, including where the law limits choice.
17. WHAT HAPPENS IF I DECLINE THE MONITORED DEVICE?
The practical consequence, stated plainly - ideally an alternative, not a penalty.
18. DOES THE VENDOR SEE MY DATA?
The vendor role, the contractual limits, and where the data is hosted.
19. IS MY DATA USED TO TRAIN AI MODELS?
The contractual answer: no - and say so in the vendor agreement as well as the FAQ.
20. WHAT CHANGED SINCE LAST YEAR?
A short changelog. Scope changes announced proactively are far less alarming than scope changes discovered.
HOW TO USE THE LIST
- WRITE IT ONCE, DELIVER IT WITH THE POLICY, and keep it in the same place
- ANSWER IN YOUR OWN CONFIGURATION'S WORDS - a generic FAQ that contradicts your deployment is worse than none
- REVIEW IT ANNUALLY with the policy, and after every material change
- LET MANAGERS USE IT: the FAQ is the answer to "what do I tell my team", and consistency beats improvisation
- INVITE THE NEXT QUESTION: the twenty-first question is usually the important one; give it a route and an owner
THE ONE-LINE SUMMARY
Twenty questions, one document, honest answers that match the configuration - published before the rumor version circulates, reviewed with the policy every year.
iMonitor EAM and iMonitor 365 support disclosed deployments where these answers are easy to give. 15-day free trial: imonitorsoft.com


Comments
Post a Comment