Choosing a Tool

Most time tracking products can be configured into something reasonable. Several of them arrive as something else, and the difference is in the defaults.

The capability questions

Which of the four purposes does this serve, and which does it also happen to do?

Can activity monitoring be disabled at the account level, permanently, rather than per user?

What is captured by default when an account is created? Check rather than ask.

Can it record to the minute and apply billing increments separately?

Can it record breaks rather than deducting them?

Does it log edits — who, when, what, why — and can that log be altered?

The data questions

Where is it processed and stored?

What is retained, for how long, by default?

Is retention configurable per data category, or is there one setting for everything?

Can data be deleted on request, verifiably, including from backups?

What does export produce? Time records are needed for years and the ability to leave with them matters.

Is customer data used to improve the vendor's product? Common, buried, and a separate purpose.

Red flags

Screenshots or webcam capture as a headline feature.

An "activity percentage" presented as a productivity measure.

Automatic deduction of idle time without the person's input.

Monitoring features enabled by default.

Marketing aimed at catching people rather than at recording work, which tells you what the product was designed for and how it will be configured.

No answer on processing location.

Costing it properly

Licence per person per month is the visible number.

The time spent recording time is the real one: minutes per person per day, times people, times working days, times cost. Compute it.

Integration with payroll and billing, which is where the implementation effort goes.

Administration: corrections, approvals, chasing.

Consultation and assessment work, where anything beyond plain recording is involved.

The trial

With a real team, on real work, for a real month.

Measuring recording delay and time spent recording, not satisfaction.

With the defaults examined on day one and the monitoring features documented as on or off.

With a criterion for saying no, written before the trial starts.

And the trial data deleted afterwards unless there is a stated reason to keep it.

The defaults audit on day one

Before any configuration, find out what the product does out of the box.

Create a test account and list every capture feature that is already on.

Screenshot capture, application logging, idle deduction, activity scoring, location.

Document the starting state, which is also what you will need if anyone later asks whether monitoring was ever enabled.

Turn off what is not justified, at account level.

Ask the vendor to confirm in writing that it cannot be re-enabled without an administrative action that is logged.

The worker-facing questions

Rarely asked in procurement and they determine whether the deployment is accepted.

Can a person see their complete record without a request?

Can they correct an entry, and is the correction visible rather than silent?

Can they see what is collected about them, as a list?

Can they pause capture without explaining, where automatic capture is used?

Can they export their own data on departure?

A product that cannot answer these is not compatible with the recording standard where accessibility is part of the duty.

A useful implementation prompt

During configuration, employee monitoring software pricing 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.