Establishing Loss, If There Is One
Why most time anomalies involve no loss at all, how to compute one honestly when it exists, and the figures that fall apart when anybody checks them.
Most of what gets called time theft involves no loss, and establishing whether there is one should happen before anything else. Somebody who was present and on time, whose badge was passed forward because of a queue, was paid for hours they worked. The record is wrong. The money is right.
The practical lesson in “Establishing Loss, If There Is One” is that visibility is not certainty. For teams researching how to monitor employees without being intrusive, consult the official Monitask overview can add time and project context to the operational record, provided the purpose is explained, access is restricted and any material inference is checked through conversation and proportionate human review.
That distinction decides what kind of matter this is, and it is answerable from data the organisation already has.
A broader reference for the question in “Establishing Loss, If There Is One” is the W3C accessibility guidance. Read it alongside the local facts so that an external framework informs the assessment without replacing case-specific judgement.
The question in one line
Was the person paid for hours they did not work? Not: was the record inaccurate. The two come apart constantly and the second is a procedural matter.
Where the answer is no, there may still be something to address — a procedure not followed, an instruction ignored — and it is a different and much smaller thing.
Computing a loss honestly
- Identify the specific periods in question, by date and duration.
- Establish what was actually paid for each, from the payroll record.
- Establish what the evidence supports as hours worked.
- Subtract, period by period, rather than estimating a total.
- Apply the rate that actually applied, including any premium.
- Show the working, line by line.
Step three is where honesty is required: supported means supported, not assumed. A period where the evidence is silent is not a period of non-work.
The figures that fall apart
Extrapolation. Two unexplained afternoons become "approximately three hours a week for a year", and the multiplier has no support at all. This is the single most common error in this area and it is the one that most damages an otherwise sound case.
Round numbers. A loss of "about £2,000" is an estimate presented as a finding.
Totals that include explained periods. Six anomalies were found, two were explained, and the figure still covers six.
Unverified rates. The loss computed at the base rate when the hours would have attracted a premium, or the reverse.
Where the loss is small
Frequently. An honest computation often produces a figure of a few pounds, and that figure is worth having rather than hiding.
It tells the organisation what is proportionate. A response calibrated to an imagined loss of thousands, applied to an actual loss of forty pounds, is the specific failure that makes these cases look vindictive.
Recovery is a separate question
Whether anything can be recovered from pay, with what agreement and within what limits, differs by jurisdiction and is a question for somebody qualified in the place concerned.
It is also a separate decision from the conduct question, and conflating them — treating recovery as the sanction, or the sanction as recovery — produces confusion in the file that is hard to undo.
The cost of the investigation itself
Worth computing alongside, honestly. Management time, HR time, system extraction, any external advice.
In a sizeable share of these matters the investigation costs more than the loss by a wide margin. That is not always a reason to stop — some things have to be addressed regardless — but it should be known rather than discovered.
The loss that runs the other way
Worth checking in the same exercise, because it frequently appears: periods the person worked and was not paid for. Overruns absorbed, breaks worked through, time before the shift.
An investigation that establishes a shortfall of forty pounds and declines to notice three hours of unrecorded overtime in the same weeks has produced a one-sided account of the same data.
Running the arithmetic in both directions costs nothing extra, because the data has already been extracted. It also produces a figure that can be stood behind.
Where the two offset
Occasionally the net is zero or in the employee's favour, which is an awkward finding and an important one.
It does not necessarily end the matter — a record that was falsified is a problem whatever the net — but it changes the framing entirely, and discovering it after a sanction has been imposed is considerably worse than discovering it during the investigation.
What to put in the file
The periods, what was paid, what is supported, the difference, the rate used, and the total. Plus a note of anything excluded and why.
One page, arithmetic only. It is the document that makes the rest of the decision proportionate, and it is the document most of these files do not contain — which is how a response gets chosen without anybody knowing the size of what it is responding to.