How to tell your team you are adding monitoring

Telling employees about monitoring is the conversation most owners put off until the software is already installed. That is the wrong order. If the first your team hears about screenshots is a notification on their laptop, you have turned a tooling decision into a trust problem, and you will spend the next month fixing the trust instead of using the data.

I have had this conversation badly and then had it properly. The difference was not charisma. It was deciding exactly what I was turning on before I opened my mouth, and writing the message down instead of improvising it.

Decide what you are turning on before you say a word

You cannot answer questions about a policy you have not written. Before you announce anything, write down answers to these six things. Short answers, one line each.

• What gets recorded. Work time only, or also apps and browser activity? Screenshots or not?
• How often. "A screenshot roughly every 10 minutes while the tracker is running" is a real answer. "Periodically" is not.
• When it stops. Does the tracker only run when someone clicks start, or does it run whenever the machine is on? If it runs automatically, what happens at 9pm on a Sunday?
• Who can see it. Just you? Team leads? Can a teammate see another teammate's screenshots?
• How long it is kept. 30 days, 90 days, forever? Pick a number.
• What it is used for. Invoicing clients, payroll, spotting overload, or performance reviews? Be honest, including if the answer is partly performance.

That last one is where owners flinch. If you say "this is not about performance" and then bring up someone's active hours in a review three months later, you have lied to your team. Either commit to not using it that way, or say up front that it is one input among several.

If you genuinely only need hours for invoicing, consider turning screenshots off entirely. Fewer features means a much easier conversation. I wrote more about that tradeoff in time tracking that does not destroy team morale.

A script for telling employees about monitoring

Do it in two steps: a written message first, then a live meeting. Written first, because people need to read bad news alone before they react to it in front of colleagues. Live second, because a message with no meeting feels like a decision being hidden.

The written announcement

Send this a day or two before the meeting. Keep it this short.

Hi all — starting the 20th I am rolling out a time tracking app on work machines. Here is exactly what it does.

It records work time when you start the tracker, takes a screenshot of your screen about every 10 minutes while it is running, and logs which apps and sites you have open during that time. It does not record keystrokes, it does not turn on your camera or mic, and it does not run when the tracker is stopped.

Only I can see the data. It is deleted after 90 days. I am using it for two things: billing clients accurately, and seeing when someone is buried in work before they have to tell me.

I am not using it to compare you against each other, and I am not setting an hours target.

I know this is unpleasant. I would rather tell you a week early and take the questions than have it appear on your laptop. We will talk it through on Thursday at 10. Reply to me directly if you would rather ask in private.

Three things make that message work. It is specific about what is recorded. It is specific about what is not recorded, which is the part people actually worry about. And it names the discomfort instead of pretending this is exciting news.

The meeting

Open with the reason, not the tool. One or two sentences, true ones. "Two clients disputed invoices last quarter and I had nothing to show them" is a reason. "To improve productivity" is a slogan, and your team will hear it as "I think you are slacking."

Then demo it on your own machine. Show the app, start the tracker, let them see what a screenshot looks like in the admin view, show them the stop button. Five minutes of seeing it beats twenty minutes of describing it.

Then shut up and take questions. Do not fill silence with reassurance.

Install it on yourself first

Run the tracker on your own machine for a week before anyone else gets it. Then say so. It changes the conversation from "I am watching you" to "we are all on this." It also means you will find the annoying parts yourself — the tracker you forgot to stop, the screenshot taken while your bank was open — before your team finds them for you.

The questions you will get, and honest answers

"Don't you trust us?" The honest answer is usually: I trust you, and I still need a record. Those are different things. Invoices, payroll and disputes need evidence, not trust.

"Will you see my personal stuff?" If the tracker only runs when started, the answer is: not unless you leave it running while doing personal things, and if that happens, tell me and I will delete that screenshot. Then actually delete it when asked. The first time you honour that request is when the policy becomes real.

"What if my numbers look low?" Tell them what you will do, which should be ask, not assume. Low active hours can mean a slow week, a sick kid, or four hours on a phone call that the software cannot see.

"Is this permanent?" If you are unsure, say it is a three-month trial and you will ask them at the end whether it stays. Then put the review date in the calendar in front of them.

"Can I turn it off?" Say yes or no clearly. "Stop the tracker when you are off the clock, including breaks" is a fine rule. "It runs all day, no exceptions" is also a fine rule if you say it out loud. What is not fine is leaving it vague so people discover the answer by accident.

When someone pushes back hard

Someone may be genuinely upset, not just curious. Take it in private, and listen for which specific part they object to. In my experience it is almost never "time tracking" — it is screenshots, or it is the fear that the data goes into a review.

You often have room to move. You can turn screenshots off for everyone, blur them, lower the frequency, or shorten retention to 30 days. Giving up one setting to keep the team on side is usually a good trade. What you cannot do is make a quiet exception for one person and hide it from the others. Either the rule applies to everyone or you change the rule for everyone.

If someone's answer is a firm no on principle, that is real information. One person refusing is a conversation. Three people refusing means your reason was not good enough, and you should go back and check whether you actually need this data or just want it.

Set it up once, and don't change it silently

The fastest way to burn the goodwill you just earned is to add a feature later without telling anyone. Treat every change — new tracking type, longer retention, a new person with admin access — as a small version of this same announcement. One line in your team channel is enough.

Pick the narrowest tool that answers your actual question, and get it installed in one go rather than drip-feeding changes. If you have not chosen yet, I walk through the shortlist in the 6 best employee monitoring tools for teams under 20, and the install itself is a single afternoon's work if you plan it: how to set up employee time tracking in one afternoon.

I build bibotracker for exactly this size of team: a desktop app that records work time, screenshots and browser activity, and a web admin where you see who worked on what. It is a deliberately small tool, and it is the wrong choice if you need payroll runs, invoicing workflows or deep integrations — buy something bigger for that. But if your problem is that you have no record of the week and a conversation to have with your team, it will do the job without giving you forty settings you then have to explain.