Should You Be Watching Your Assistant’s Screen? The Awkward Question Nobody Answers Honestly

Somebody raises it eventually, usually hedged in apologetic language. Would you mind using a time tracker? Nothing personal, it is just how we keep things organised.

The assistant agrees, because saying no at the start of a working relationship feels like admitting something. The client feels vaguely guilty for asking. Neither says what they actually think, and a tool that takes screenshots every ten minutes quietly becomes part of how you work together.

Monitoring software is standard across the remote assistant world, and the conversation around it is almost entirely dishonest. Clients pretend it is administrative. Assistants pretend they do not mind. It is worth being straightforward about what these tools do, when they make sense, and when they are solving the wrong problem entirely.

What these tools actually measure

Time trackers built for remote work typically record far more than hours. Common features include periodic screenshots, an activity score derived from keyboard and mouse movement, application and website logging, and in some cases webcam capture.

The activity score is the one worth understanding, because it is the most widely misread. It measures input frequency, not work. Someone reading a long document, thinking through a problem, or on a call with a supplier will register as inactive.

Someone idly scrolling will register as busy. The number tells you how much a mouse moved, which is not the same thing as whether anything useful happened.

This matters because clients make decisions based on those percentages, and assistants know they are being measured this way. The predictable result is people finding ways to keep the number up, which benefits nobody.

When monitoring is reasonable

There is a defensible case, and it is narrower than the software vendors suggest. Hourly billing on open-ended work is the strongest one.

If you are paying by the hour for tasks with no fixed deliverable, such as ongoing inbox management or research with no clear end point, some record of time spent is a fair expectation on both sides. It protects the assistant as much as the client, since it substantiates the invoice.

Regulated or sensitive environments can justify access logging, though that is usually about knowing who opened what rather than watching how quickly they typed.

New relationships sometimes warrant a lighter version for the first few weeks, provided both parties agree it is temporary and say so openly.

When it is solving the wrong problem

If you are paying a fixed fee for a defined deliverable, monitoring makes very little sense. You have bought an outcome, and how long it takes is the assistant’s business. Someone who finishes in three hours what you expected to take six has done well, not badly, and a tracker will tell you the opposite.

More often, the impulse to monitor is standing in for something else. It usually means you are unclear about what you actually want delivered and by when, so you are measuring effort because you have not defined output. No amount of screenshots fixes that, and the fix itself is straightforward.

It is also worth naming the cost. Being watched changes behaviour, and generally not for the better. People become reluctant to think, to pause, to step away and come back with a better approach, because none of that registers as activity. You end up optimising for visible busyness in a role where judgement is the valuable part.

The legal side, briefly

Monitoring is not a free-for-all, and the rules catch more people than expect them to.

In the UK and EU, monitoring is subject to data protection law, which generally requires that people are told clearly what is being collected, that there is a legitimate purpose, and that the method is proportionate to it.

Covert monitoring is very difficult to justify, and screenshots that capture personal browsing or third-party information create their own problems. Several jurisdictions require an assessment before implementing intrusive monitoring at all.

The complication with assistants specifically is that they are usually contractors rather than employees, working in a different country from the client, often through a platform. That does not remove the obligations, it just makes it less obvious whose rules apply.

Anyone implementing serious monitoring across borders should take advice for their own situation rather than assume the software’s default settings are compliant.

What works better than watching

The approach that produces both trust and results is unglamorous and takes about twenty minutes to set up.

Agree deliverables rather than hours wherever the work allows it, since a defined output is easier to assess than a percentage. Set a reporting rhythm, meaning a short end-of-day or end-of-week summary of what moved, what is stuck, and what is next.

Use shared task boards so progress is visible without anyone being surveilled. Have a brief weekly call, which surfaces more in ten minutes than a month of screenshots.

When you are setting up a new working arrangement, whether through direct hiring or a platform like PA2Assist, settle this at the start rather than introducing it later. Raising monitoring in month three reads as an accusation, while agreeing the arrangement in week one is simply a term of the engagement.

If you are the assistant

You are allowed to have a position on this, and stating it early costs you far less than absorbing it silently.

Ask what the tool records and who sees it. Ask whether screenshots are stored and for how long. If you work on a fixed fee, it is entirely reasonable to say that you would rather be measured on delivery, and to offer a reporting rhythm instead.

If you use the same machine for other clients or personal matters, raise that directly, because it is a genuine confidentiality problem rather than a preference.

Most clients accept the alternative without complaint, largely because what they wanted was reassurance rather than surveillance, and a clear weekly summary provides it.

Final thoughts

The monitoring question is uncomfortable because it is really a question about trust, and both sides would rather discuss software than say that out loud.

Work out what you are actually buying. If it is hours, track hours and say so plainly. If it is outcomes, define the outcomes and stop counting mouse movements. Agree the arrangement at the start, tell people exactly what is recorded, and revisit it once the relationship has settled.

Get that right and the tracker becomes irrelevant, because you will already know whether the work is getting done.

#RemoteWork #VirtualAssistant #EmployeeMonitoring #TrustAtWork #Productivity #WorkingRemotely