What Time Data Tells You About Workshop Capacity

Capacity is usually discussed in bays and headcount. Neither is the constraint.

The workshop sells hours. Capacity is how many sellable hours it can produce, and the gap between the theoretical figure and the actual one is visible in time data most workshops already collect and few analyse.

The arithmetic

Theoretical capacity = technicians × hours available × days.

Eight technicians at 8 hours over 22 working days is 1,408 clock hours a month.

That number is never achieved, and the reductions are knowable:

Absence — holiday, sickness, training.

Non-productive time — waiting, moving vehicles, cleanup, meetings, unbilled help.

Then efficiency applies. The remaining worked hours convert to sold hours at whatever efficiency the workshop runs.

So: 1,408 clock hours, less 12% absence, at 70% productivity, at 115% efficiency, gives roughly 997 sellable hours. The theoretical figure overstates it by 40%, and a business planned on the theoretical figure is planned wrongly.

Work out your own version of this chain, from your own data, rather than using anyone's benchmark.

Where capacity is actually lost

Time data, coded properly, tells you which of these dominates. See time recording that works.

Parts. Usually the largest single item and the most commonly under-recorded. A technician waiting for a part is producing nothing, and if the wait is not coded it appears as unexplained low productivity.

Authorisation. Work found during inspection, waiting for a customer decision. The vehicle occupies a bay throughout.

Dispatch. The job is ready, the technician is free, and nobody connected them. Frequently visible as a cluster of short gaps rather than one long one, which is why it is missed.

Comebacks. Consume capacity twice and are usually unbilled the second time. See comeback rate.

Job mix. A day of diagnostics produces fewer sold hours than a day of routine service, at identical effort.

Skill mismatch. Work waiting for the one technician qualified to do it, while others are idle. Visible as one technician at high productivity and others low.

Reading the pattern

Low productivity across all technicians points at the workshop — parts, dispatch, scheduling. Not at the people.

Low productivity for one technician is a dispatch or skill-allocation question.

Productivity high, efficiency low means people are working all day and taking longer than book. Skill, tooling, or job mix.

Both high, sold hours still short means the workshop is not full. That is a demand or a scheduling problem, not an operations one.

Gaps clustering at particular times of day point at process — the morning wave arriving together, the post-lunch restart, the end-of-day write-up.

Capacity planning that matches reality

Schedule in clock hours, not book hours. A day scheduled with 8 book hours per technician is overbooked by whatever their efficiency exceeds 100%, minus whatever productivity falls short — and those do not cancel.

Level the load across the week. Most workshops are overbooked Monday and empty Thursday, which wastes capacity at both ends. Moving discretionary work is cheaper than adding a bay.

Hold time for the work you know is coming. Comebacks, warranty, internal. A schedule at 100% of capacity with no allowance is a schedule that will run late.

Match the skill, not just the hour. A booked hour that only one technician can perform is not capacity if that technician is committed.

Plan for the parts lead time, not just the labour. A job scheduled before the part arrives occupies a bay and produces nothing.

When more capacity is genuinely needed

Before adding technicians or bays, the time data usually shows cheaper options.

Recover productivity first. Moving from 68% to 78% productivity across eight technicians is roughly the output of an additional technician, at no headcount cost. In most workshops that is achievable through parts and dispatch.

Extend the day rather than the headcount, where a second shift or staggered start suits the demand pattern. The bays are already there.

Shift the mix. Moving routine work to a quick-service lane frees skilled capacity for the work that only skilled technicians can do.

And check demand before adding supply. A workshop at 70% productivity that is also not full does not have a capacity problem.

What the numbers cannot tell you

Worth stating, so the data is not overused.

Whether the work was done well. Efficiency measures speed against a standard. Comeback rate, warranty rejections and customer feedback measure quality, and speed can be bought at the expense of it.

Why a technician is slow on a job type. The data locates it; the conversation explains it.

Whether the book time is right. The data gives evidence, and the judgement is yours.

And they cannot tell you anything at all if the recording is unreliable — which it will be if technicians believe it is used against them.

A quarterly review worth doing

• [ ] Theoretical capacity computed, and the chain of reductions to actual sellable hours
• [ ] Non-productive time by cause, ranked
• [ ] Productivity and efficiency by technician and by job type
• [ ] Load distribution across days of the week
• [ ] Unbilled work quantified — comebacks, internal, goodwill
• [ ] Book time versus actual by operation, for the operations you do most
• [ ] The largest single cause of lost time, with an owner and a date

One finding acted on beats six recorded.

The short version

Capacity is sellable hours, not bays or headcount, and the theoretical figure overstates it substantially.

Compute your own chain — absence, productivity, efficiency — rather than using a benchmark.

Schedule in clock hours and level the week; most workshops are overbooked Monday and empty Thursday.

Recover productivity before adding headcount. Ten points of productivity across eight technicians is roughly a ninth technician, free.

And the data locates the problem; the conversation with the technicians explains it.

For independent productivity measures and methodology, consult BLS productivity statistics.