Unattributed Hours
Hours paid and recorded against nothing. What they are, what they are not, and why the word used for them decides what happens next.
Unattributed hours are hours that were paid and recorded against nothing. They are not idle time, they are not waste, and they are not evidence about anybody. They are the measure of how much of the week the recording system does not see, and the word chosen for them decides whether they get fixed or argued about.
The record examined in “Unattributed Hours” is strongest when it is created close to the work and remains open to correction. A team evaluating look through the official resource for ways to track work hours can connect time with projects and work categories, provided people can review entries before they influence payroll, billing or cost reports.
Called idle, they become a conversation about people. Called unattributed, they stay a conversation about the system.
The assumptions behind “Unattributed Hours” can also be checked against Eurostat labour-market data. Record which guidance applies to the real workflow and which points require professional advice.
Where the number comes from
The payroll reconciliation: paid hours less hours recorded against anything, after the ordinary explanations are removed.
Paid hours, less hours recorded against anything, after the ordinary explanations are removed. It cannot be found inside the job system, because by definition these hours are not in it.
It cannot be found inside the job system, because by definition these hours are not in it.
What it usually is
Short tasks below the recording grain. Work done away from the system. Entries abandoned halfway. People who joined or left mid-period. And genuine non-recording, which is the smallest part.
Five causes, four of them structural.
What it is not
Evidence that anybody was idle. The hours were paid, which means somebody was at work; what is missing is the attribution, not the work.
That distinction sounds pedantic until the number is presented to a room, at which point it decides everything that happens next.
The size
One to four per cent in a well-run recording system. Five to twelve per cent where entry is weekly. Above fifteen per cent, the recording is not functioning and no job cost from it should be relied on.
Why it must not be allocated
Spreading it proportionally across jobs makes the arithmetic balance and destroys the only indicator that recording is incomplete.
It also moves cost onto jobs that did not incur it, which is precisely what job costing exists to prevent.
Leaving it visible
As its own line, in the costing report, every period, with its percentage. Named, dated, and not allocated.
A line that stays visible gets improved. A line that is allocated away is rediscovered in two years by somebody new.
Bringing it down
Daily entry, shorter job lists, mobile entry where work happens away from a desk, and a visible daily total that must sum.
Four changes, all mechanical, and together they typically halve the figure within a quarter.
The one that does not work
Reminders. Chasing people to complete timesheets raises compliance with the form and not accuracy, because the gap is filled by reconstruction.
A chased timesheet is a complete timesheet containing invented distribution.
The idle-time trap
An operation that labels this figure idle time will, within two periods, have no unattributed hours — because people will attribute them to something.
The number goes to zero and the information goes with it. This is the same mechanism as a utilisation target and it is worth recognising as one.
When waiting is real
Sometimes people genuinely are waiting: materials have not arrived, the previous stage is late, the system is down. That is a real and important category, and it deserves its own named code.
Named, it points at a scheduling or supply problem. Merged into unattributed, it is invisible; merged into idle, it is somebody's fault.
Where it concentrates
Rarely evenly. It is usually concentrated in particular teams, particular kinds of work, or particular weeks — which means it has a cause rather than being a general condition.
Splitting the residue by team and by week, once, usually locates it in one or two places. That is a much more tractable problem than a percentage spread across the organisation.
The figure after a system change
Expect it to jump, and expect the jump to be the system rather than behaviour. A new entry screen, a changed job list, a migration: each produces a period or two of elevated residue.
Knowing this in advance prevents a routine implementation wobble being read as a collapse in discipline, which is how these things usually get interpreted.
What to say when it is first published
That it is a measure of the recording, not of the people, and that the target is zero by better recording rather than zero by better attribution.
Those two sentences decide whether the figure survives its first quarter in a management pack. Without them it becomes an efficiency metric within two meetings.
What the figure is worth
It bounds the reliability of every job cost. A job costed from a system with eight per cent unattributed hours is understated by up to eight per cent, and nobody can say by how much for any particular job.
Quoting that bound alongside job costs is honest and uncomfortable, and it is the thing that gets the recording fixed.