Where technician hours actually go
A technician paid for eight hours delivers rather fewer on the tools. The gap is measurable, largely structural, and almost never measured.
Maintenance planning assumes a supply of labour hours. Almost every organisation calculates that supply from contracted hours: five technicians times thirty-seven and a half equals a hundred and eighty-seven and a half hours a week of maintenance capacity. For a product-side comparison related to analysing where paid hours are spent, see workforce analytics software before deciding which data the operation actually needs.
That number is wrong by a wide margin, and the direction of the error is always the same. The hours exist and most of them are not spent doing maintenance.
The categories
Technician time divides into a small number of buckets, and only one of them is the work.
- Wrench time — hands on the asset, doing the task. The industry term, and the number everyone quotes and few measure.
- Travel — between buildings, between floors, to the stores and back. Dominant on dispersed sites.
- Waiting — for access, for a room to empty, for an isolation, for a second person, for a part.
- Preparation — collecting tools and materials, reading the job, obtaining a permit, setting up.
- Administration — closing jobs, writing notes, filing certificates, briefings, training.
Published wrench-time figures for maintenance organisations that have not deliberately worked on it commonly sit somewhere between a quarter and a half of attended time. The exact number matters less than the fact that it is not eighty or ninety percent, which is what an unadjusted capacity calculation assumes. For a wider operational and compliance reference, consult the Department of Labor field operations handbook.
Attended hours are what you pay for. Wrench hours are what the schedule consumes. Planning with the first while spending the second is the most common structural error in maintenance capacity planning.
Most of the loss is structural
This is the important point and the one most easily got wrong. Low wrench time is overwhelmingly a property of how work is organised, not of how hard people are working.
A technician who walks fifteen minutes to a plant room, finds it locked, walks back for a key, returns, discovers the part in stores is the wrong one, and orders another has lost most of a morning without a single moment of idleness. Every one of those losses has an organisational cause: key management, stores accuracy, job information, planning.
Treating the wrench-time figure as a measure of individual effort is both wrong and self-defeating, because it guarantees the measurement will be resisted and the data will stop being honest.
Where the recoverable time is
In most organisations the same handful of causes account for the bulk of the loss.
Parts. Time spent going to stores, discovering the item is not there, and ordering it. Addressed by kitting planned jobs in advance and by accurate stores data — a stores system that says an item is present when it is not is worse than no system.
Access. Keys, permits, occupied rooms. Addressed by recording access requirements on the asset so they appear on the job, and by booking access ahead for planned work rather than discovering the constraint on arrival.
Job information. Time spent working out what the job means, where the asset is, and what was done last time. Addressed at the point the work order is raised.
Travel. Partly irreducible, substantially reducible by geographic grouping of jobs rather than strict priority sequencing.
Measure it in a way people will tolerate
There are two honest routes and they suit different situations. Sampling — observing or self-recording over a defined fortnight, reported only in aggregate — is cheap, sufficient for a baseline, and much less intrusive than continuous measurement. Job-based capture, where start and finish are recorded against the job in whatever system is already in use, gives continuous data as a by-product but only works where the recording is genuinely low-friction.
Both depend on a commitment that is made before the measurement starts and then kept: the data is used to fix the process, at team level, and never to assess individuals. Break that once and every subsequent figure is fiction.
Use it to fix the ratio, not to raise the target
The purpose of measuring wrench time is not to increase it by exhortation. It is to identify which of the four non-wrench categories is largest in your organisation and remove the cause.
A department that raises wrench time from a third to a half has effectively added capacity without adding headcount, and it has done so by fixing key management and stores accuracy rather than by asking anyone to work faster.