Automatic Capture

Automatic time tracking observes activity on a device and infers what the person was working on. It solves the accuracy problem by creating a different one.

What it does

Watches application and window focus, and sometimes document titles, URLs, or file names.

Segments the day into blocks of related activity.

Proposes attributions: this block looks like project X, based on the files and applications involved.

The person confirms or corrects, in the better implementations.

What it genuinely solves

No recollection required. The record is built from what happened.

Fragments are captured, including the eleven interruptions.

Nothing is forgotten, which is the main failure of manual and timer methods.

Completeness improves markedly, particularly for internal and unbilled work.

What it costs

It captures what you were doing, not only how long. Window titles and document names are the substance of the work, and for many roles they are confidential.

It captures everything, including the personal: the banking tab, the medical appointment, the job application.

The record exists even if only the summary is used, unless the design discards it.

It is surveillance by the test in the foundations section, and the obligations follow: notice, proportionality, assessment, consultation, and a purpose limitation that holds.

The design that makes it defensible

Process on the device, transmit the summary. The raw activity stream never leaves the machine.

The person reviews before anything is submitted. They see the proposed blocks and correct them, and nothing reaches a manager unreviewed.

Discard the raw stream once the summary exists, on a short timer.

Exclusions by application and domain, configured on the device: banking, health, personal messaging, job sites.

A pause control the person can use without explaining, which is the single feature that distinguishes a tool from a monitor.

No manager visibility of the activity stream, ever — only the resulting time entries, which are the same thing a manual timesheet would have produced.

What makes it indefensible

Transmitting raw activity to a server.

Manager access to application logs.

Screenshots, which are covered separately and which no time tracking purpose requires.

Idle time used to reduce paid hours without the person's input.

Deployed without consultation, where consultation is required or expected.

Enabled by default as part of a timesheet rollout, which is how most organisations acquire it.

The honest position

Automatic capture is the most accurate method and the most intrusive, and those are the same property.

Where it is used, the design decisions above are what separate a tool the workforce accepts from one it resents, and they are mostly settings rather than features.

Where the purpose is billing or costing, ask whether a timer would do. It usually would, at some cost in completeness, with none of this.

Where the purpose is the statutory record of hours, it certainly would: the duty is to record start, end and breaks, and nothing about that requires knowing which application was open.

The device boundary

The design decision that determines whether automatic capture is defensible.

Process on the device; transmit the summary.

The person reviews before anything is submitted.

Discard the raw stream on a short timer.

Exclusions configured on the device — banking, health, personal messaging, job sites.

A pause control usable without explanation.

No manager visibility of the activity stream, ever.

All six, or it is monitoring with a timesheet interface.

Ask whether a timer would do

The question to put before any automatic capture proposal.

For the statutory record: certainly. The duty is start, end and breaks, and nothing about it requires knowing which application was open.

For billing: usually, at some cost in completeness, with none of the intrusion.

For costing: usually, since the question is which project rather than which window.

Automatic capture buys completeness and pays for it in surveillance obligations and in trust.

Name what the completeness is worth before accepting that trade.

A useful implementation prompt

During configuration, remote employee monitoring software can be used as a prompt for questions about fields, ownership and output. Confirm current capabilities with the provider and document any plan, integration or policy assumption behind the decision.