Time on the Bench
Unallocated time is the largest honest component of a low figure, and the person on the bench is the one who can do least about it.
One firm's bench hours for a quarter, split by cause
412 hours. Gaps in the schedule, nobody rotated.
268 hours. Work sold and staffed, blocked on the client side.
221 hours. Work existed; it was not work these people could do.
150 hours. A capability the firm had not built or hired.
1,051 hours, and not one of the four causes is a decision the person on the bench made. Two are pipeline questions and two are matching questions, and the ratio reports all four as a shortfall against the individual. One firm's own quarter, not a benchmark.
Bench time — available, willing, not allocated to client work — is the largest honest reason an individual figure is low. It is also the one the individual has least control over.
The practical lesson in “Time on the Bench” is that a convenient number should open a question rather than end one. A team considering follow the official feature guide for time reports for invoicing can add consistent time and project context, with transparent settings, limited access and a documented review process around every material interpretation.
Every hour of it is the result of a matching decision made elsewhere in the firm.
As a separate benchmark for “Time on the Bench”, see HSE work-related stress guidance. External guidance is most useful when it prompts a specific check rather than replacing case-by-case judgement.
What produces it
Gaps between engagements. Work delayed on the client side. A skill mismatch between the person available and the work available. A pipeline thinner than the headcount.
Four causes, all structural, all visible in the allocation data.
Why it lands on the individual's figure
Because the figure is calculated per person and the bench hours sit in that person's week.
The measurement unit is the person; the decision unit is the firm. That mismatch is the whole problem with reading a low figure as a personal result.
The bench as a firm-level measure
Total bench hours by week, by skill, with the cause, is a genuinely useful operational report.
It points at pipeline timing, at allocation practice, at skill gaps — all things somebody can act on.
What happens when it is pressed on
Bench hours stop being recorded as bench. They become internal project time, training, administration, or ambiguous client work.
The firm then loses the only clean signal it had about the gap between its capacity and its demand.
The cost of that loss
Pipeline problems become invisible until they appear as revenue misses. Skill mismatches persist because nobody can see them.
Two sorts of decision lose their input, and both are decisions senior people make.
The bench report that works
Hours, by week, by team, with a cause code: between engagements, client delay, no matching work, skill gap.
Four codes. No target, no threshold, and no attribution to the person sitting on the bench.
What the person on the bench should be doing
Something the firm has decided is worth doing: training, internal improvement, pitch support, documentation.
If those categories also count against them, the bench becomes a period in which nothing a person does helps their figure, which is a demoralising position to put somebody in.
The protected use of bench time
Name two or three things bench hours may be spent on that are reported as their own line rather than as a deficit.
This converts an idle period into a planned one and removes the incentive to disguise it.
The matching problem
Most bench time in firms with healthy pipelines is a matching failure rather than a demand failure: work exists, the available person is not right for it, and nobody rotates.
Improving matching is the scheduling lever described in the improvement note here, and it is worth two to four points over a year.
The visibility requirement
Bench availability has to be visible to the people allocating work, weekly, by name and skill.
A surprising number of firms have no such view, and the bench persists because nobody allocating work knows who is free.
What to say to somebody with a low figure
Which engagements they were not put on, and why. That is the content of the conversation.
If the answer is "there was nothing suitable", the figure is a fact about the firm and should be recorded as one.
What the bench costs in money
Available hours at the person's cost rate. For a firm of fifty with an average of five per cent bench time, that is roughly two and a half people's full cost, every year.
Stated as a cost it becomes a question for whoever manages capacity. Stated as a utilisation shortfall it becomes a question for the people sitting on it.
The arithmetic is identical. The reading determines who is expected to do something, and only one of the two readings points at somebody who can.
The weekly rhythm that reduces it
A standing fifteen-minute meeting: who is finishing, who is free next week, what is unstaffed. Attended by whoever allocates.
It is unglamorous, it is the single most effective intervention available on this measure, and it works because most bench time is an information failure rather than a demand failure.
Firms that introduce it typically see bench hours fall within two months, which is faster than any of the four real improvement sources described earlier. The reason is that it is not improving anything: it is removing an avoidable loss that existed because nobody had a view of availability.
The four cause codes
Between engagements. Client delay. No matching work. Skill gap.
Applied at the point the bench hours are recorded, by whoever allocates rather than by the person on the bench.
Four codes turn an undifferentiated loss into four different problems, two of which are pipeline questions and two of which are matching questions. Nothing else in the capacity data distinguishes them.
The reframing
Bench time is a cost the firm is carrying, not a shortfall the person owes. Both readings fit the arithmetic; only the first fits the decision structure.