Time Tracking With Screenshots: How to Do It Fairly for a Remote Team

Who wrote this: the team behind WopeAI Tracker, a product built by Wope. We mention it where it fits, alongside other ways to do the same thing.

Time tracking with screenshots is fair when it captures only while a person's timer is running, takes screenshots at random rather than constantly, tells people in writing exactly what is recorded and who sees it, lets them see their own data, and deletes it after a set period. Used that way it proves billable hours to clients; used as hidden, always-on surveillance it damages trust and, in the UK and EU, is hard to justify legally.

We sell engineering by the hour, so we have to be able to show a client what each hour was spent on. Our own team logs every hour in a screenshot-based tracker we built. This guide is what we have learned about doing that without making good people feel watched. It is general information, not legal advice.

Why teams use screenshot time tracking

Three situations account for most of it:

• Billing clients by the hour. An agency invoice that says "42 hours" invites the question "on what?". Hours logged against a task, with a visual record behind them, answer it before it is asked.
• Remote and distributed teams. When nobody shares an office, a timesheet filled in on Friday from memory is the weakest record you have. A tracker that runs while the work happens is a better one.
• Contractors paid by the hour. Both sides benefit from a record neither had to reconstruct. A contractor with screenshots and task notes has an easy answer to a disputed invoice.

Notice what is not on the list: checking whether people are working hard enough. That is a management problem, and screenshots are a poor answer to it.

The real downsides

• Trust. Tracking tells people something about how they are seen. Senior people in particular may read it as "we do not believe you", and some will leave.
• Privacy. A screenshot captures whatever is on screen: a personal message, a bank tab, a medical appointment booking. Even a careful person will sometimes have something private visible.
• Sensitive client data. Screenshots of a client's production database, customer records or credentials are now data you hold, store and must protect. That is a security and contractual question as much as a privacy one.
• Morale and gaming. Fixed-interval capture and crude activity scores teach people to look busy. Mouse-jigglers exist for a reason.
• Misreading the data. Low keyboard activity during an hour of reading a specification is not idleness. Managers who treat activity counts as a score will draw wrong conclusions about their best people.

How to do it fairly

1. Tell people exactly what is recorded. Screenshots, how often, activity counts, which app or device, who can see it and for how long it is kept. In writing, before they start. No surprises later.
2. Only while a timer runs. The person decides when tracking is on. Nothing is captured on a break, at lunch or after they stop for the day. This one rule removes most of the "surveillance" feeling.
3. Random, not constant. A screenshot at a random moment within a window of several minutes gives an honest sample of the work. Constant recording or video is far more intrusive and rarely needed for billing.
4. Let people see their own data. Each person should be able to see what was captured about them and raise anything that should not be there.
5. Set a retention limit. Keep screenshots as long as you need them to settle an invoice or a dispute, then delete them. Write the period down.
6. Do not score people on activity counts. Use keyboard and mouse counts to spot a timer left running on an empty desk, then look at the task and the output. Never rank or pay people on activity alone.
7. Restrict who can look. A small number of admins, for a stated purpose. Not every team lead browsing screenshots out of curiosity.

How often should a time tracker take screenshots?

There is no legal or industry standard number. The question is what the screenshots are for. If the purpose is to back up billable hours, a handful per hour is enough to show what the work looked like. More frequent capture adds intrusion without adding much proof.

Timing matters more than frequency. Randomised capture within an interval is better than a fixed schedule, because nobody can arrange their screen for the moment it fires. Tools in this category commonly let admins set the interval, and some, such as Hubstaff and Time Doctor, also offer a blur option that hides on-screen detail while still showing that work is happening. Blur is worth using for roles that handle sensitive data.

Is screenshot monitoring legal?

Often yes, under conditions. A short overview, not legal advice:

UK (and, broadly, the EU under GDPR). The UK Information Commissioner's Office guidance on monitoring workers says employers must identify a lawful basis for monitoring, and that consent is usually not appropriate because of the imbalance of power between employer and worker. You must tell workers about monitoring in a way that is accessible and easy to understand, and choose the least intrusive means of achieving your purpose. A data protection impact assessment is required before processing likely to cause high risk, with keystroke monitoring given as an example, and the ICO recommends one even where there is no specific high risk. Workers can ask for the monitoring data held about them, and you must not keep it longer than necessary. Covert monitoring is very hard to justify.

US. Rules on notifying employees about monitoring vary by state. New York, for example, requires private employers to give written notice of electronic monitoring on hiring, get the employee's written or electronic acknowledgement, and post the notice where employees can see it. Other states have their own rules, so check where your people actually work.

Contractors and other countries. If your team is spread across countries, the law where each person works usually matters. Contractors are not exempt from privacy law just because they are not employees.

If you are setting this up for the first time, have an employment or privacy lawyer review your policy. It is a small cost next to a complaint.

A practical policy checklist

What to look for in a tool

• Timer-bound capture. Nothing recorded when the timer is off.
• Random intervals you can configure, and the option to blur or disable screenshots by role.
• Task-level time. Hours against a project and task, so a report shows what the time was spent on, not just how much.
• Visible to the person. They can always tell tracking is on, and can see their own record.
• Access controls and retention settings on the admin side.
• Reports a client can read. If you bill by the hour, the output should make sense to the person paying the invoice.

Well-known tools in this category include Hubstaff and Time Doctor. Hubstaff says its screenshots are captured only during active tracking sessions, with adjustable frequency and an irreversible blur option. Time Doctor's help centre says screenshots are taken at random times within an interval the admin chooses, with blurring available for all users or selected ones. Compare them on the fairness points above as well as on price.

How we do it at Wope

We built WopeAI Tracker for our own engineers, because every hour on a Wope plan has to be provable to the client paying for it. You can see where it fits in our process in how we run the work. It is a desktop app, and it works like this:

• Each person checks in from their registered computer at the start of the day and checks out with a short written summary of what was done.
• Time is logged against a project, module, milestone and subtask, so the client report shows what the hours were spent on.
• While the timer runs, it takes a screenshot at a random moment every 2 to 12 minutes, with shorter gaps early in a session and longer ones later, and records keyboard and mouse activity counts with each one.
• No screenshots are taken when the timer is stopped, and each person can see that they are checked in and the timer is running.
• Admins see who worked on which project, for how long, with the screenshots, on one dashboard.

We use activity counts to catch a forgotten timer, not to rank anyone. The written check-out summary usually tells us more than the numbers do.

WopeAI Tracker is not a public download. If you would like it for your own team, including a white-label version under your own brand, register your interest and we will get in touch. If you are weighing up hourly engineering help more broadly, our guide to fractional AI engineer cost covers how that is priced.

Frequently asked questions

Is screenshot monitoring of employees legal?

Often yes, but with conditions. In the UK, the ICO says employers need a lawful basis, must tell workers about monitoring in clear terms, and should choose the least intrusive method; in the US, rules vary by state, and New York, for example, requires written notice that employees acknowledge. Take legal advice for your own situation.

How often should a time tracker take screenshots?

There is no legal standard. A screenshot at a random moment every few minutes to every ten or so minutes, only while the timer is running, is enough to show what the work looked like without recording someone's whole day. Random timing is better than a fixed schedule because nobody can perform for the camera.

Should employees be able to see their own screenshots?

Yes. Letting people see what was captured about them builds trust and lets them flag anything sensitive. In the UK, workers can also request the personal data collected through monitoring with a subject access request.

Do I need a DPIA for screenshot time tracking?

In the UK, the ICO says a data protection impact assessment is required before processing likely to result in high risk, names keystroke monitoring as an example, and recommends a DPIA for monitoring even without a specific high risk. In practice, plan to do one.

Are keyboard and mouse activity counts a good measure of productivity?

No, not on their own. Reading, thinking, design review and calls produce little input but are real work. Use activity counts to spot an idle timer, then look at the task and the output before drawing any conclusion.