15-minute idle detection without screenshots: what works

Part of our guide on integrating asana and slack time

Every tracker on this page can flag 15 quiet minutes with the screenshot camera switched off – here is exactly which ones, and what each one costs you in evidence.

What idle detection actually measures

Idle detection watches for input. If nobody touches the keyboard or moves the mouse for the period you set, the tracker declares the timer idle and stops counting – or pauses and asks. Fifteen minutes is the common commercial threshold because it matches a natural break: coffee, a corridor conversation, a school run.

Some tools add app focus to the mix. If an employee is reading a long PDF or watching a training video, keyboard and mouse go quiet but the window is still active. Tools that count app focus treat that as working time; tools that only count input treat it as idle. Know which your tool does before you trust its numbers.

The blind spots matter more than the mechanics. Phone calls, whiteboard sessions, site visits and face-to-face client meetings all register as idle on a desk-based tracker. Anyone whose job is not typing will look idle far more than they are, and you need a policy for that before rollout, not after the first complaint.

• Keyboard and mouse input: counted by nearly every tool.
• App and window focus: counted by some, ignored by others.
• Meetings and calls: invisible to all of them – expect manual edits.

Which trackers flag at 15 minutes without screenshots

Four tools cover this well, and all four let you run activity tracking with screenshots disabled or not offered at all. The key is that the idle timeout is adjustable – if it were fixed at 10 minutes you could not honour a 15-minute policy, and several tools default lower than people expect.

Clockify's desktop app detects idle time and you set the threshold yourself; set it to 15 minutes and the timer pauses with a prompt. Screenshots are not part of its core tracking. Toggl Track similarly detects idle, prompts the user, and has never made screenshots part of the product – the cleanest privacy story of the four.

Hubstaff and Time Doctor are heavier: both offer screenshot capture, but it is a setting you switch off, and both let you configure idle timeout and choose what happens when it trips. They give you richer activity rates and app logs in exchange for a product your team may regard with more suspicion. Pick by how much evidence you actually need.

What happens to flagged time: discard, prompt or approve

Three things can happen when the timer trips. Auto-discard deletes the idle stretch without asking – clean data, but it silently removes hours someone may believe they worked. Auto-keep counts everything, which defeats the purpose. The useful middle is a prompt: the returning employee sees a dialog asking whether those 15 minutes were work or a break.

For payroll, prompt-and-approve is the only defensible setup. The employee keeps honest minutes and discards honest breaks, and every discard carries a timestamp the worker agreed to. That record is what ends a dispute in an afternoon instead of a month.

Auto-discard has one legitimate home: contractors paid purely on tracked output who have agreed to it in writing. Even then, send a weekly summary of discarded time so nobody finds the gap on payday. Silent deletion is how idle detection earns a reputation as a wage-skimming tool, whether or not that was the intent.

The trade-off: no screenshots means weaker dispute evidence

Screenshots exist for one reason: proof. When a client disputes an invoice or an employee disputes a timesheet, a picture of the screen at 2:14 pm settles it. Drop screenshots and you lose that, so you need substitutes, and the substitutes are activity rates and app logs.

Activity rate – the percentage of tracked minutes with keyboard or mouse input – is the honest replacement. A tracked hour with 70 percent activity is strong evidence of work even without images. App and URL logs fill in the what: which programme was foreground, for how long. Together they answer 'was the time real' almost as well as screenshots, and they answer it with less intrusion.

What they cannot do is prove the content of the work. A spreadsheet and a game both show high activity. If your contracts require content-level proof, say so to clients up front and offer activity logs instead – most small-business clients accept this once they see the reporting. The ones who insist on screenshots are telling you the relationship needs different tooling.

How to roll out 15-minute idle detection without a surveillance feel

Order of operations decides whether your team reads this as payroll fairness or spying. Announce it before installing anything, in writing, and lead with what the tool cannot do: no screenshots, no keylogging, no reading of documents. Then install, then set the threshold together.

Follow the sequence below and the whole rollout is one short meeting plus a week of settling in.

The setting that matters most is transparency of data. Give employees access to their own dashboards from day one. People tolerate measurement they can see and correct; they resent measurement done to them. Let them edit their own time with a note – the edit log is your audit trail.

1. Announce in writing: what is tracked, what is not, and why – payroll accuracy, not monitoring.
2. Install the desktop app on work machines only; leave personal devices alone.
3. Set the idle timeout to 15 minutes and switch screenshots off in settings before anyone logs in.
4. Choose prompt-and-approve for flagged time, and show the team exactly what that dialog does.
5. Give everyone access to their own activity dashboard and edit rights.
6. Review the first fortnight's reports with the team and adjust the threshold if roles report false idles.

Common mistakes and myths about idle tracking

Myth: idle time equals wasted time. Fact: fifteen quiet minutes may be a phone call, a whiteboard or hard thinking. Idle detection is a prompt to ask, not a verdict to impose, and treating it as a disciplinary measure poisons the data – people start wiggling the mouse.

Myth: screenshots make tracking accurate. Fact: screenshots make it intrusive and prove only what was on screen, not whether the work was good. Accuracy comes from the right threshold plus prompt-and-approve, not from imagery.

Myth: you can set it and forget it. Fact: thresholds need a review after a fortnight, because roles differ. Your accountant's idle pattern and your designer's will not match, and one number may be wrong for one of them.

The most expensive mistake is docking pay on auto-discarded idle time without a written policy. In several jurisdictions that is a wage calculation error, not just an HR problem. Prompt, log, and pay for what the prompt confirmed.

Questions people still ask

I have run Clockify at 15 minutes with screenshots off for a six-person team for two years; the prompt-and-approve dialog has settled every timesheet question before it became one.