All notes

Everything here, in eight sections. If activity monitoring has been proposed, read the boundary section first. If you operate in the EU, start with the legal duty.

All 50 notes

Grouped by section, each appearing once. The bar under each heading is proportional to the number of notes in that section.

Foundations

5 notes

Four purposes get served by one system and pull in different directions. Separating them decides the legal analysis, the consultation requirement, and how the workforce reads the whole thing.

The legal position

5 notes

In much of Europe recording hours is an obligation that exists to protect the worker. What the standard actually requires, and why accessibility is part of it rather than a feature.

How it gets recorded

6 notes

Accuracy falls sharply with the delay between the work and the entry, which is the one variable you can actually change. Everything else in this section is about reducing it.

The boundary

7 notes

The record is written by the person it describes, which makes cooperation the data collection mechanism. Every way of spending it costs the accuracy that pay and the statutory record depend on.

Billing

4 notes

Where time is a currency rather than a measurement it shapes behaviour. Plus the gap between recorded and billed, which is usually a pricing finding rather than a performance one.

Costing and capacity

7 notes

Billing data omits most of the effort. Costing requires recording the unbilled work, which is the part people are least rewarded for recording and the part that carries the organisation.

Running it

10 notes

Chasing submission produces timesheets, not accuracy. What actually moves recording delay, and the failures that recur with their specific corrections.

Reference

6 notes

The boundary stated plainly: the questions a timesheet cannot answer, the asks that should be declined, and a description of the end state to measure a proposal against.