What Counts Towards a Limit

Every limit is a number applied to a quantity, and the quantity is defined somewhere other than where the number is. Organisations read the number, implement it against whatever their system already counts, and are confident they are compliant.

The threshold discussed in “What Counts Towards a Limit” is useful only when hours can be reviewed before the decision becomes irreversible. A team evaluating more information for workforce analytics software should test current totals, manager alerts, corrections and employee access while keeping the applicable legal limit outside the software as a documented rule.

That confidence is usually misplaced in one direction: the system counts less than the rule does. The categories it misses are the same ones everywhere, and every one of them exists in some other record.

For an independent reference relevant to “What Counts Towards a Limit”, consult the Grants.gov policy resources. Use it to test working-time definitions, recordkeeping, access, retention and exception handling against the organisation’s real process rather than treating one software report as conclusive.

The categories that are routinely missed

Travel during the working day, between assignments or sites, which in most regimes is working time and in most systems is not recorded at all.

On-call and standby where the person is constrained — required to be at a place, or to respond within a window short enough to govern their time. Whether and how much of it counts varies, and the answer is almost never zero.

Training the employer requires, including the kind done at home on a laptop because there was no time during the shift.

Handovers, briefings and preparation before a shift nominally starts. Changing, where it is required and must happen on site.

And in some regimes, time spent available at the workplace even without being given work.

Why the system counts less

Because a time and attendance system records what it was built to record, which is attendance at a place where a clock exists. Everything in the list above happens somewhere else: in a job management system, in a learning platform, in a rota as an on-call flag, or nowhere at all.

So the gap is not a data problem in the ordinary sense. The data exists, in four systems, and nobody has joined it, because joining it is somebody's project and the current arrangement produces a number that looks fine.

The honest first step

Write down what your system counts. Then write down what the rule says counts. Put them side by side.

That is an hour of work and it produces the actual finding of this section: a list of categories that are working time and are not in the figure. Nobody can tell you the size of the gap until that list exists, and once it does, the size is usually estimable within a day.

Sizing it without building anything

Take ten people across the affected groups and reconstruct one week each from all available sources — the time system, the job records, the vehicle telematics, the training platform, the on-call rota.

Ten weeks of reconstruction is a day of somebody's time and it gives a defensible multiplier: the real figure is between this much and that much above the recorded one. That multiplier is enough to decide whether anything needs building, which is the decision that otherwise gets deferred for years.

What to do when the gap is large

Not panic, and not immediately rebuild the systems. The sequence that works is to establish the size, decide which categories matter most, and capture those first.

Travel is usually the largest single category and it is frequently already recorded in a job or vehicle system. Bringing one category into the working time figure is a small integration rather than a programme, and it typically closes most of the gap.

The categories that genuinely do not count

Ordinary commuting to a fixed place of work, in most regimes. Rest breaks taken as rest. Voluntary training the employer did not require. Time at home genuinely free of obligation while on a low-constraint standby arrangement.

Knowing which these are matters as much as knowing the others, because a figure that over-counts is also wrong and it produces rotas constrained by hours nobody is obliged to count. The point of the exercise is an accurate number, not a conservative one.

Saying what the figure excludes

Until the gap is closed, every figure the organisation produces should carry a short statement of what it leaves out. One line at the top of the report: this figure includes hours recorded at a terminal and excludes travel, on-call and training.

That line is the difference between a lower bound and a claim. It costs nothing, it is accurate, and it prevents the specific failure where a figure assembled for operational convenience is later relied on as a complete record of somebody's working time — including, occasionally, by the organisation's own lawyers.