Employee Monitoring Doesn't Do What You Think. Here's What Professional Services Teams Should Measure Instead.

Something is happening to the time tracking category, and it's worth naming.

Tools that began as simple timers have been steadily acquiring capabilities that belong to a different product category altogether: screenshot capture, GPS location, activity levels, idle detection. Clockify, one of the most widely used time trackers in the market, now maintains a dedicated page positioning itself as employee monitoring software, offers screenshot capture every five minutes on its Pro plan and above, and publishes guidance on using those screenshots to check whether team members are working on job-related tasks.

To be fair to Clockify, and this matters: these features are optional and off by default. An administrator has to deliberately enable them. Screenshots are blurred unless someone raises the resolution, only run while a timer is active, and are visible only to admins with explicit permission. Clockify also doesn't log which applications or websites someone used — it is considerably lighter than dedicated monitoring platforms like Hubstaff or Time Doctor.

So this isn't a story about one company behaving badly. It's about a direction the whole category is moving in, and whether professional services firms should follow it.

I think the answer is no — for two separate reasons. The first is that monitoring mostly doesn't work. The second, and more important one, is that even if it did work, it would be measuring the wrong thing.

The research is remarkably one-sided

The intuition behind monitoring is simple and feels obvious: people work harder when they know someone is watching. It has the ring of common sense.

The evidence doesn't support it.

A meta-analysis of electronic monitoring research found that monitoring slightly decreases job satisfaction and slightly increases stress. A systematic review of the field concluded there is little evidence that electronic performance monitoring produces positive performance effects, and some evidence of moderate negative ones.

But the most striking finding comes from a study published in Harvard Business Review in 2024. Researchers surveyed over 100 US employees, comparing those subject to workplace monitoring against those who weren't. The monitored group was substantially more likely to break rules — taking unapproved breaks, disregarding instructions, damaging workplace property, even taking office equipment. A second experiment with 200 employees, where half were told they were being electronically monitored, established that the relationship was causal rather than coincidental.

The proposed mechanism is the interesting part. Surveillance appears to erode people's sense of moral agency. When someone is being watched, they unconsciously transfer responsibility for their conduct to whoever is doing the watching. Their own internal compass — the thing that actually governs behaviour most of the time in most workplaces — becomes less relevant to them.

Put plainly: monitoring doesn't just fail to produce the discipline it promises. In a meaningful number of cases, it produces the opposite.

There's also a straightforward retention cost. Survey data indicates that a substantial majority of workers would consider activity-tracking software a legitimate reason to leave a job. In a market where experienced consultants and auditors are difficult to hire and expensive to replace, that's not a footnote.

No screenshots. No GPS. No activity levels.

HourSquad tracks hours against project budgets and squad allocation — the numbers that determine whether an engagement is profitable. Nothing that watches your team.

Try HourSquad free for 28 days →

Even if it worked, it would be the wrong measurement

Set the research aside for a moment and grant the premise. Suppose monitoring did reliably increase time-at-desk. For a professional services firm, it still wouldn't answer the question that matters.

Here's why the context is genuinely different.

In most businesses, hours worked are an input. The company sells a product or an outcome, and hours are one of the costs of producing it. Monitoring, at least in theory, tries to protect that input from waste.

In consulting and auditing, the hour is the unit of value itself. It is what you scope, what you commit to, what you invoice, and what the client scrutinises. The question isn't whether someone was at their keyboard. It's whether this engagement will land inside the hours you committed to, and whether you can stand behind the invoice when the client asks.

A screenshot cannot answer either question. Neither can an activity percentage or a GPS coordinate.

What answers them is structured data: hours logged against a specific project, compared against a planned budget, visible while there is still time to act on a developing overrun. A consultant who spent four focused hours producing a finished work paper delivered more value than one who spent seven distracted hours producing the same thing — and monitoring software would rate the second one higher.

The part my background makes hard to ignore

I spent years in Big Four auditing before running my own practice, and there's an inconsistency here that I find difficult to look past.

Auditing is built on a specific epistemology. You do not assess a control by watching someone perform it. You assess it through evidence, documentation, testing, and outcome. The entire discipline exists because direct observation is unreliable, unscalable, and easily gamed — and because what matters is whether the result can be substantiated, not whether the person looked busy producing it.

A firm that sells that philosophy to clients, and then manages its own team by reviewing screenshots every five minutes, is operating on two contradictory theories of how to know things.

There's a more practical version of this too. If a client disputes an invoice, screenshots are close to worthless as support — they demonstrate that a screen was open, not that work of a particular nature was performed for a particular deliverable. What actually supports an invoice is a clean, structured, tamper-evident record of hours against scoped work. That's an audit trail question, not a surveillance question, and the two are frequently confused.

What to measure instead

Your instinct — hours and deliverables rather than activity — is the right frame. Here's the version I'd make specific:

Planned versus executed hours, per project. The single most useful number in professional services. It tells you whether your estimate was sound, whether the engagement is tracking, and whether next quarter's proposal should be priced differently.

Budget consumption in real time, with a threshold alert. Not a month-end report. A live figure, with someone notified when a project crosses 80% of its committed hours and there is still room to have a conversation with the client.

Squad allocation against capacity. Who is committed to what, for how many hours, this week. This catches the overload problem that monitoring claims to address — but it catches it before it becomes burnout, rather than documenting it afterward.

Deliverable completion against the plan. Milestones met, work papers finished, reviews cleared. Output, not presence.

None of these require watching anyone. All of them require the team to log time consistently and honestly — which, not incidentally, is far more likely in a culture where people don't feel surveilled.

When monitoring is legitimate

I don't think this is an absolute principle, and I'd distrust anyone who argued it was.

There are contexts where monitoring is reasonable and sometimes required. Regulated environments with strict data-handling obligations. Roles with genuine physical safety considerations. Field service work where GPS confirms a technician reached a site. Situations where a specific, documented compliance requirement exists and less invasive alternatives genuinely don't satisfy it.

The distinction worth holding onto is between monitoring adopted for a defined purpose, with the narrowest tool that achieves it, and monitoring adopted as a default posture because a feature was available and it felt prudent. The first is a control decision. The second is a signal to your team about how much you trust them — and they will read it correctly.

For a consulting or auditing firm whose product is the professional judgement of its people, that second signal is expensive in ways that don't show up on any invoice.

Clockify is a registered trademark of its respective owner. HourSquad is not affiliated with or endorsed by Clockify. Feature and plan details cited are drawn from publicly available documentation as of September 2026 and may have changed since publication.

Measure the engagement, not the person.

Planned versus executed hours, real-time budget execution, and squad allocation — built by someone who spent 30 years managing audit and consulting teams.

Flat $5/user/month. No usage fees. No monitoring features, by design.