Wrench time
Wrench time explained: what is wrench time, and what it is not
Wrench time is the share of a technician's shift spent with hands on the asset doing the repair or maintenance work itself, calculated as hands-on-tool hours divided by total available hours. It is the closest thing field service and maintenance have to a direct measure of productive effort.
For field service
Know what the job needs before the van rolls
Venta Capture, a product of VentaVid, lets the customer show you the fault first, so the engineer arrives with the right part or does not need to arrive at all.
Also called tool time or hands-on time. SMRP carries it as metric 5.6.1 in its best practices set, which is worth knowing if you are ever asked to justify the definition you used.
What does wrench time mean in practice?
Wrench time counts only the work that changes the state of the asset. Diagnosing at the machine counts. Fitting the part counts. Testing the repair counts.
Almost everything else does not:
- Travel, both to site and back to the stores.
- Waiting, for permits, isolations, access, a site contact, or a second pair of hands.
- Looking for things, parts, tools, drawings, manuals, the supervisor.
- Paperwork, work order updates, reports, photographs, timesheets, compliance records.
- Briefings and breaks, toolbox talks, handovers, meetings.
None of those are wasted in the sense of being avoidable entirely. A permit is a safety control, not a delay to be deleted. But they are also not repair, and lumping them in makes the number useless.
How is wrench time calculated?
Wrench time equals hands-on-tool hours divided by total available hours, times 100. Available hours is the full shift, not the hours booked to jobs, which is the distinction that separates it from utilisation.
Measuring it honestly is harder than the formula suggests. Three usual methods: direct observation over a sample of shifts, work sampling at random intervals, or timestamped work order data with defined activity codes. Self-reported timesheets are the fourth method and the least reliable, because nobody logs the twenty minutes spent finding a fitting.
How wrench time differs from technician utilisation
These two are the most commonly confused pair in service reporting, and the confusion costs real money because the fixes point in opposite directions.
- Technician utilisation counts booked hours: is the technician assigned to a job?
- Wrench time counts hands-on-tool hours: is the technician working on the asset?
The gap between them is travel, waiting and paperwork, all of which happen inside a booked job. A technician can be 100 percent utilised and have a 30 percent wrench time day, and both numbers are correct.
Which one you manage decides what you do. Manage utilisation and you fill the diary harder. Manage wrench time and you attack the travel, the parts availability and the information gaps that surround the work. Only the second one gets more repairs finished.
Wrench time: a worked example
Observe six technicians across an 8-hour shift, 48 technician-hours in total. Direct observation logs 16 hours with tools in hand, 13 hours travelling, 9 hours waiting for access and parts, 6 hours on paperwork and 4 hours in briefings and breaks. Wrench time is 33 percent. Adding a seventh technician buys another 2.7 hands-on hours. Cutting the waiting in half buys 4.5, from the people already employed.
What the benchmarks say
Reliable Plant, summarising Ricky Smith and R. Keith Mobley's Rules of Thumb for Maintenance and Reliability Engineers, reports most companies running 18 to 30 percent wrench time, world-class organisations at 55 to 65 percent, and national studies across North American industry landing in a 25 to 50 percent band (Reliable Plant).
The spread between typical and world class is the point. It is not a story about technicians working harder. It is a story about planning, scheduling and storeroom discipline, which is where every documented improvement in wrench time has come from.
How wrench time gets gamed or misread
- Widening what counts as hands-on. Fold travel or documentation into the definition and a 28 percent operation reports 45 percent overnight. Publish the activity codes with the number, every time.
- Self-reported data. Technicians who know wrench time is being watched will report it high, and they are not being dishonest. Nobody remembers the interruptions accurately.
- Using it as an individual scorecard. Wrench time is set by planning, parts and dispatch far more than by the person holding the tool. Attach it to appraisals and you lose the data quality that made it useful.
- Chasing the percentage past safety. Skipping isolation steps, risk assessments or clean-up raises wrench time and is a good way to hurt someone.
- Sampling too thin. A single observed day catches one bad delivery or one easy week. Sample across weeks and across job types.
- Reading it as effectiveness. Six hours spent on the wrong repair is excellent wrench time and a failed job. Pair it with first-time fix rate.
What actually raises wrench time
The recoverable hours sit in the waiting, not in the working. Job plans with the parts list confirmed before scheduling, kitted materials, confirmed site access, and a fault description accurate enough that the right person is sent first time.
Diagnostic information is the underrated one. When the fault is understood before dispatch, the travel is not repeated and the parts are on the van, which is the practical argument for structured remote diagnostics and for cutting the avoidable truck roll entirely.
