Efficiency, Productivity and Proficiency Are Three Different Ratios

Three numbers, used interchangeably in most workshops, measuring three different things. When one of them moves, the response depends entirely on which one it was — and treating them as one number is how a scheduling problem gets addressed with technician training.

Terminology varies by market and by manufacturer. Some networks use "utilisation" for what others call productivity. What matters is which quantities are being divided, not the label — check the definitions in use before comparing anything to a benchmark.

The three quantities

Everything below is built from three measurements.

Clock hours. Time the technician was at work and available.

Worked hours. Time the technician was actually working on a job — the clock running against a repair order.

Sold hours. Hours billed, usually the flat-rate or book time for the operations performed. See flat rate and clock time.

The three ratios

Productivity = worked hours ÷ clock hours.

What share of the paid day was spent on jobs. A technician present for 8 hours who worked on jobs for 6 has 75% productivity.

This is a workshop management measure, not a technician measure. The gaps are usually waiting for parts, waiting for a job to be dispatched, waiting for authorisation, moving vehicles, cleaning up, or being pulled onto something unbilled. Very little of that is within the technician's control.

Efficiency = sold hours ÷ worked hours.

How the technician performs against the book time. A technician who completes 8 hours of book work in 6 hours of clock work is at 133% efficiency.

This is the technician measure, and it is the one most sensitive to skill, tooling and repeated exposure to the same job.

Proficiency = sold hours ÷ clock hours.

The combination — what the workshop actually got out of the day. It is productivity multiplied by efficiency.

Why the distinction changes what you do

A technician at 130% efficiency and 55% productivity is not a performance problem. They are fast and they are sitting idle. The problem is dispatching, parts or scheduling, and sending them on a training course will not touch it.

A technician at 100% productivity and 70% efficiency is the opposite. They are working all day and taking longer than book time. That may be skill, tooling, job mix, or being given the difficult diagnostics.

Proficiency alone cannot distinguish these, and proficiency is frequently the only number reported. A workshop looking at a proficiency figure of 72% has no idea whether it has a scheduling problem or a capability problem.

Report all three, per technician and for the workshop. The pattern between them is the diagnosis.

The traps

Comparing efficiency across job mix

A technician doing repetitive maintenance will show higher efficiency than one doing diagnostics, because book times for routine operations are generous relative to a practised hand, and diagnostic work is where the book is least reliable.

Ranking technicians on raw efficiency ranks the job mix. If diagnostics are given to the best technician, the ranking will suggest they are the worst performer.

Compare like work, or segment by job type before comparing anything.

Treating productivity as a technician metric

The most common and most damaging error. Productivity measures how well the workshop kept a technician supplied with work.

Holding technicians accountable for it produces predictable behaviour: clocking on to jobs they are not working on, staying clocked on during breaks, and reluctance to report a parts delay. Once that starts, the data stops being usable for anything.

Not counting unbilled work

Comebacks, internal repairs, warranty work with reduced times, helping another technician, road tests, workshop cleanup. If these are not recorded somewhere, they appear as lost productivity and nobody knows where the time went.

Give them a code. Unbilled work that is recorded is a management problem you can see; unrecorded, it is a mystery in the numbers.

Benchmarks without definitions

Industry figures circulate without stating which quantities were divided. A published "productivity" benchmark may be what you call proficiency.

Before comparing to any external figure, establish what it measured. Otherwise you are chasing a number that means something else.

What moves each one

Productivity is moved by the workshop: dispatch, scheduling, parts availability, authorisation turnaround, bay availability, and how much unbilled work is being absorbed. See what time data tells you about capacity.

Efficiency is moved by the technician and their equipment: skill, familiarity with the model, tooling, information access, and how appropriate the book time is for the work.

Proficiency is moved by both, which is why it is a scorecard number and a poor diagnostic.

And the constraint is usually productivity. Most workshops have more room in scheduling and parts than in technician speed, and efficiency has a practical ceiling that productivity does not.

Reading the pattern

Productivity	Efficiency	Likely issue
Low	High	Scheduling, dispatch, parts — technician is waiting
High	Low	Skill, tooling, job mix, or book times
Low	Low	Both, or a data problem — check recording first
High	High	Working well; check the hours are real

That last row deserves a look rather than a celebration. Sustained figures well above the norm on both measures sometimes mean excellent operation and sometimes mean the time recording has drifted from what happened.

Making the numbers trustworthy

None of this works if the underlying time is wrong.

Recording has to be easy at the point of work. A system requiring a walk to a terminal produces batched entries at the end of the day, which are estimates. See time recording technicians will actually use.

Everyone must understand what each number is for. A technician who believes productivity is their performance measure will behave accordingly.

Unbilled categories must exist and be used.

And review the numbers with the technicians, not just about them. The person who knows why efficiency dropped on a job type is the person doing it.

The short version

Productivity is worked over clock — a workshop measure.

Efficiency is sold over worked — a technician measure.

Proficiency is sold over clock — the combination, and a poor diagnostic on its own.

The pattern between them is the diagnosis, and reporting only one guarantees the wrong response.

And check definitions before comparing to any benchmark — the same words mean different ratios in different networks.

For independent productivity definitions and data, consult BLS productivity program.