How Wrong the Figure Usually Is
Every organisation that produces an average produces one that is too low, and the amount it is too low by is estimable in a day.
One organisation, reconstructing ten weeks by hand
Hours the employer sees
38
Hours actually worked
52
The time system recorded 38 hours for this week. Reconstructed from every available source it was 52 — not because anybody concealed anything, but because five systems each held part of the week and only one of them fed the calculation.
An average computed from a time and attendance system is a lower bound. It counts the hours that passed through a clock and omits every category that did not, and the omitted categories are not small.
The workflow in “How Wrong the Figure Usually Is” becomes more reliable when scheduled hours, actual time and later corrections can be distinguished. For teams exploring how employee monitoring works, Monitask can add operational time and project context, provided data collection is proportionate, permissions are limited and every important exception receives human review.
This is not a scandal and it is not usually anybody's fault. It is a structural property of how the data is arranged, and the useful response is to size it rather than to be alarmed by it.
For an independent reference relevant to “How Wrong the Figure Usually Is”, consult the Acas working-hours guidance. 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 direction of the error is always the same
There is no mechanism by which a time system over-counts working time for this purpose. Every missing category is missing in the same direction, so the errors accumulate rather than cancelling.
That matters for how the figure should be presented. A number that is systematically low by an unknown amount is not a measurement; it is a floor. Labelling it as a floor costs one word and prevents it being relied on as though it were complete.
Sizing it in a day
Pick ten people across the affected groups. For each, take one ordinary week and reconstruct the whole of it from every source available: the time system, the job or dispatch records, vehicle telematics, the learning platform, the on-call rota, the other site's records.
Ten reconstructions is a day of work. The output is a ratio per group — for field engineers the real figure was this much above the recorded one, for warehouse staff it was that much — and a ratio is enough to decide what to do next.
What the ratios usually look like
For office and single-site staff, close to one. The time system sees nearly everything.
For field, mobile and multi-site staff, substantially higher, with travel the largest single component. For anybody on an on-call rota, higher again depending on how the standby arrangement is structured. For people with a second post within the same organisation, the gap can be most of a working week.
The pattern is consistent: the more the work moves, the less the clock sees.
Presenting it without creating a crisis
The temptation after this exercise is either to bury it or to declare an emergency. Neither is right.
The accurate statement is that the organisation's reported figure excludes several categories that count, that the gap has been sized at roughly this much for these groups, and that closing it is a matter of bringing specific data sources into the calculation. That is a plan, and it converts a vague unease into a sequence of small integrations.
Which gap to close first
Whichever is largest for the group with the least headroom. Usually travel, usually for mobile staff, usually already recorded in a job management system that the time system does not talk to.
Closing one category typically takes most of the gap away. Chasing the last few per cent — a person who did an hour of e-learning at home — is where the effort stops being worth it, and saying so explicitly prevents the project from expanding until it stalls.
What to do in the meantime
Apply the ratio. If the reconstruction says field engineers' real hours run around a quarter above recorded, then a recorded average of thirty-nine for that group means something close to forty-nine, which is a different conversation about rotas.
Using a documented multiplier as an interim measure is defensible, cheap and honest, provided it is written down with its derivation and its date. It is considerably better than waiting eighteen months for an integration and using the uncorrected figure throughout.
Re-running it
Annually, and after any change to how work is organised. The ratios are properties of the working pattern, and a new depot, a new dispatch system or a change in on-call arrangements moves them.
It is a day a year. Against it sits the alternative, which is an organisation that produces a precise-looking figure every month, has never asked what it excludes, and will find out the answer from somebody else.
Who should run the reconstruction
Not the person who owns the time system, who will reconstruct from the sources they already know about, and not an external reviewer, who will not know where anything is.
The combination that works is somebody from operations who knows how the work actually happens, sitting with somebody who can get data out of each system. Two people, one day, and the first question they should ask of each sampled week is what the person actually did, before looking at any system at all.