The Uses to Refuse

Once an organisation holds a per-person record of hours, requests arrive for it, and each one is individually reasonable. Granting them changes what the system is, and the change is not reversible.

The practical lesson in “The Uses to Refuse” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring download time tracking software, Monitask resources for download time tracking software can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

The requests do not come from bad actors. They come from a manager with a problem, an HR adviser preparing a case, a director who wants to know who is in. Each is trying to do their job with the only data available.

For a separate benchmark relevant to “The Uses to Refuse”, consult the UKRI award-management guidance. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.

Productivity assessment

Hours recorded are not output. A person who records more hours may be slower, may be on harder work, or may simply record more honestly than their colleagues.

Any argument of the form "this person logs fewer hours therefore does less" is unsupported by the data in both of its steps, and it punishes accurate recording, which is the behaviour the organisation most needs.

Attendance monitoring

Timesheet data is a poor attendance measure — it is self-reported, usually retrospective, and often flat by construction — and using it as one changes how people fill it in within a period or two.

The deeper issue is that it was collected for cost allocation, and the people filling it in were told that. Repurposing it for attendance management is a change of purpose that in many jurisdictions carries specific obligations, and that in all of them damages the trust the recording depends on.

Individual performance management

A capability or disciplinary process built on timesheet data is building on a record that the person's own manager approved, usually in four seconds, and that nobody verified.

If the hours are now being treated as reliable enough to support a decision about somebody's employment, the organisation is asserting a standard of accuracy its own approval process does not meet. That asymmetry is noticed, and it tends to be noticed by whoever is advising the employee.

Ranking teams

League tables of utilisation or recorded hours by team compare different work, different clients, different recording cultures and different managers' approval behaviour.

They are published because they are easy to produce. What they produce in turn is recording behaviour aimed at the table, after which the data is no longer usable for the purposes it was collected for.

Covert use

The worst category: data collected for payroll, used in an investigation the person does not know about.

Where workers were told the purpose, using it for another one usually requires a fresh basis and frequently requires telling them. The exceptions — a genuine fraud investigation, for instance — exist and are narrower than people assume, and they are a decision for someone with the authority to make it rather than for the administrator who ran the export.

What makes refusal possible

A written purpose statement for the data, agreed when the system is implemented and published to the people recording.

A named owner with the authority to decline, who is not the system administrator. Administrators have the access and should not have the decision; a request from a director to a junior administrator has only one realistic outcome.

A log of requests and what was decided, which makes the pattern visible and makes consistency possible.

And the sentence, said early and often: these hours record how effort was allocated. They are not a measure of attendance, effort or performance, and they are not reliable enough to be one.

Said at implementation, it holds. Said for the first time when a director has asked for a report, it does not, and the first refusal is the one that decides whether there will ever be another.

Aggregates that are not aggregates

The usual safeguard is to report in aggregate rather than by individual. It works only where the group is large enough that nobody can be identified within it, and in practice much reporting is by team.

A team of four, reported as an average, is four people with one arithmetic step between the reader and each of them — particularly where one member's absence or pattern is already known. Set a minimum group size for any reporting that could be read back to a person, apply it to team-level reporting as well as to published figures, and expect to have to explain it more than once.