Time Tracking for Remote Employees: What Actually Works

Most small businesses track remote hours one of two ways, and both are bad.

The first is the honor system: a spreadsheet filled in on Friday afternoon from memory. It is not that people lie — it is that nobody can reconstruct Tuesday by Friday. The numbers come out round, identical week to week, and completely disconnected from what happened. You are not tracking time; you are collecting a ritual.

The second is surveillance software bought in a panic. Screenshots every few minutes, keystroke counts, a productivity score. It generates enormous amounts of data, most of it meaningless, and it reliably costs you the people you least want to lose.

There is a middle, and it is not complicated.

Track the punch, not the person

The thing you actually need is a start time and a stop time, recorded when they happen rather than remembered later. Everything else is optional.

This sounds obvious, but it inverts how most monitoring tools are designed. They start from “what can we capture” and work backward. Start instead from “what does payroll need” and you end up with a much smaller, much more defensible system.

A clock in/out that takes one click from the menu bar produces better data than any amount of screenshotting, because it is recorded in the moment and the employee is the one recording it.

Handle idle time honestly

This is where remote time tracking either earns trust or loses it.

Someone steps away for 40 minutes. Three options:

• Count it silently. You are paying for time that was not worked, and your timesheets are fiction.
• Discard it silently. The employee’s paycheck quietly shrinks and they do not know why. This is how you get a wage claim.
• Ask. “You were idle for 40 minutes — keep it, or drop it?” The employee answers. The record reflects a decision someone made rather than a guess a machine made.

The third option is the only one that survives a dispute. If your tool does not offer it, that tells you something about who the tool was built for.

What to do about “activity level”

Most remote tracking tools report an activity percentage derived from keyboard and mouse input. This number is useful for exactly one thing: noticing that a machine was clocked in and untouched for four hours.

It is worthless for comparing people. A designer in Figma generates constant input. A developer reading a spec generates almost none, and is doing harder work. If you rank your team by activity percentage, you will systematically punish thinking and reward fidgeting.

Use it as an anomaly detector. Never use it as a performance metric. And say so out loud to your team, because they assume you are using it against them until you tell them otherwise.

When application tracking earns its place

Knowing which applications the time went to is genuinely useful in a few situations:

• Client billing. You need to allocate hours across three clients and nobody remembers the split.
• Project staffing. You suspect one project is eating twice its budgeted time and you need evidence before you reprice it.
• Onboarding. A new hire is struggling and you want to see where they are getting stuck.

It is not useful for catching people. If someone is not doing their job, that shows up in their output long before it shows up in an app-usage report — and if it does not show up in their output, you did not have a problem.

When you do turn it on, capture domains rather than full URLs. docs.google.com tells you what you need. The full path tells you which document, which is frequently something you have no business holding.

Screenshots: usually no

Screenshots are the feature most people think of as “monitoring software,” and the one with the worst ratio of value to cost.

The cost is real. Screenshots are indiscriminate — they capture whatever was on screen, including the medical portal, the bank login, the private message. You now hold data you never wanted, and you are responsible for protecting it.

There are legitimate cases: certain government contracts, some client agreements, and regulated industries genuinely require visual proof of work. If you are in one of those, you know it.

If you are not, leave them off. If you must turn them on, at minimum: blur them on the employee’s own machine before upload, take them on a random schedule rather than a predictable one, limit to the primary display, and exclude sensitive applications entirely.

Put remote and field hours in one system

This is the part small businesses get wrong most often. Field crews get one app, office staff get another, and payroll becomes a reconciliation project every two weeks — two exports, two formats, manual merging, and errors that nobody catches until someone’s check is short.

If you already track field crews, extend that system to desk staff rather than buying a second one. One timesheet, one approval flow, one export.

Klees Desk exists for exactly this. It is the Mac and Windows app for staff who work at a computer, and it feeds the same timesheets, approvals, and payroll exports as the mobile app your crews use. Desk hours are marked with their own source so you can tell them apart in reporting, but they live in one place.

It is also the same seat. Klees Desk is included in every plan at no additional per-user cost, and one person can use both — a supervisor who runs a crew in the morning and does payroll from a laptop after lunch is one seat, not two.

Related reading

• Klees Desk documentation
• How to manage remote employees without micromanaging
• Is employee monitoring legal?