Monitoring is not time tracking
Time tracking records what work took so the person doing it can bill honestly and price the next job better. Monitoring uses screenshots, activity scores and keystroke counts to ask, "are you working?" I think that destroys trust. Once people have to perform for the tracker, the record stops telling you what the work actually cost.
Why do managers ask for proof of work?
Managers ask because they cannot see the work and are responsible for paying for it. A remote manager has lost the office cues: who is at their desk, who looks stuck, who left at three. If they bill clients by the hour, they also sign their name under hours they did not see.
Some have been burned by a person who billed more than they worked. I take that worry seriously. The manager needs evidence they can stand behind when a client questions the bill.
The monitoring vendors offer a tidy answer to that nervousness. Take a screenshot every few minutes, count the keystrokes and mouse movement, turn it into an activity percentage, and put it on a dashboard. It looks like visibility. It is sold as productivity. And for a buyer who is anxious about paying for time they cannot see, it feels like the responsible thing to do.
I think monitoring answers the wrong question and makes the original problem worse. A manager needs to know what the client is paying for. An activity percentage cannot tell them that.
What is time tracking actually for?
Time tracking should help the person doing the work bill honestly, spot jobs that took more hours than they were worth, and quote the next one better. Its value depends on the entries being true.
Say a freelancer logs her hours and learns that a "two-day" website takes four: she raises her price. Say a small agency tracks time per client: it finds out which retainer is quietly losing money. Both learn something they can use on the next job.
Truth is easy when the record works for the person writing it. If my own timesheet helps me get paid properly and stop underquoting, I have every reason to log the messy hour I spent on a dead end, because that hour is exactly the lesson. If you want the practical version of that habit, a short weekly time review covers most of it.
A screenshot every few minutes answers something else entirely. It does not ask what the work took. It asks whether the person was at the keyboard. Those sound similar on a sales page. They are completely different questions, and only the first one helps anyone price a job.
What changes when the tool starts watching?
The people in it change what they tell it. A time tracker that is used for billing and pricing is a record. The same tracker used to judge whether someone is working hard enough becomes evidence, and people treat evidence differently from records. They log what looks good rather than what happened. They round the dead-end hour away. They keep a window open that looks busy.
None of that requires bad people. It is what anyone does when a number is used against them. The manager who installed monitoring to get honest data has made honest data less likely, because the cost of honesty for the person being watched just went up. The dashboard fills with activity, and the one thing the business needed, an accurate picture of what work costs, quietly gets worse.
What does an activity score really measure?
Keyboard and mouse movement, and not much else. Picture a freelance designer whose client installs an activity tracker as a condition of the contract. Her score drops whenever she sketches on paper, or thinks a layout through with her hands off the keyboard. Those are often the most valuable minutes of her day. So she stops doing them, or does them in her own time, unpaid. The work gets worse and the score gets better.
That is what an activity score measures: how much a job looks like typing. For design, writing, planning, reviewing, debugging or talking a client through a decision, it rewards people for doing less of the thinking you hired them for.
Even idle detection, the mildest version, has the same blind spot: it treats a person reading a brief or thinking as someone who has walked away. The difference is whether a tool asks the person about the gap, or reports it to someone else.
What should a manager check instead?
Work that ships. When I want to know whether a project is healthy, I look at three things side by side:
- What moved this week: tasks finished, drafts delivered, problems closed.
- What the client actually received, in their hands rather than in progress.
- The hours logged against it, with a short note on each entry.
If those three agree, there is nothing to investigate. Say a team has logged 30 hours and delivered nothing. I would ask what happened: did the brief change, was a dependency late, or was the task bigger than anyone thought?
If the answer exposes a problem, the manager and the person doing the work need to talk about it. I do not install software to avoid that conversation. More pictures of someone's screen would leave the same question unanswered.
This also scales better than people expect. Reading a week of entries with notes takes minutes, and a note like "rewrote checkout copy after client feedback" tells you more than any screenshot of a text editor. The detail lives in the entry, not in a picture of the screen.
What about the person who really isn't working?
I would look at the work they delivered. Some people bill hours they did not work, and monitoring promises to catch them. In practice it mostly catches the people who do not know how to game it, while anyone determined to look busy soon learns which windows and movements keep the score up.
The three-way check catches the same person without that arms race. Hours that keep rising while delivered work stays flat show up in the weekly reviews, and no amount of mouse movement makes a missing deliverable appear. The difference is who pays for the check. Monitoring makes everyone on the team pay, every day, for a problem one person might have. Looking at the work costs the honest people nothing, and puts the question exactly where it belongs.
How should you answer "are we being watched?"
Say exactly what is recorded, who can see it, what it is used for and what it is never used for. Answer before anyone has to ask twice.
The setup I defend has a short answer: the hours and notes each person enters, visible to them and to whoever bills the client, used for invoices and quotes, never used to rank people. That tells the person what the record is for and where its use stops.
If the honest answer includes "screenshots" or "activity levels", you have already lost the trust the software was supposed to replace. People will say it is fine. Then they will behave as people do when they are being watched, and you will be managing a performance rather than a team.
Is monitoring ever fair?
Almost never. The one case I accept is narrow, and every condition has to hold:
- A client contract genuinely requires proof of hours, not just a manager who would like it.
- The person agreed to it in writing, before the work started.
- It covers that contract only, and switches off for everything else.
- The person sees everything the client sees, the same screenshots and the same numbers.
Without every one of those conditions, I would not run it on anyone. A manager's unease is not enough. If you are a freelancer being asked for screenshots, there are trackers without screen capture that give a client evidence of the time spent.
What does saying no to monitoring cost?
Sales. Monitoring sells, and it sells to the buyer with the budget: the manager who is nervous about remote work, not the person whose screen would be photographed. Timen has no screenshots, activity scores or GPS, and that makes it a harder sale to exactly that buyer. Some of them will pick a tool with a dashboard full of percentages, and I understand why.
I accept that cost. Honest entries tell you what work costs, which lets you price the next job, spot a losing client and pay people fairly. Getting those entries means giving people a reason to record the awkward parts: the dead end, the underestimated task, the client call that ran long. A tracker people fear gives them a reason to hide those parts.
So what should you track?
Track time for the person doing the work, so they can bill it and learn from it. Check the work itself, delivered, against the hours behind it, and ask a question when they disagree. Leave the screenshots out. The proof of work you were looking for was never on the screen. It is in what ships, and in a team that has no reason to tell you anything but the truth about how long it took.
