What is wrench time in maintenance?

Wrench time is the percentage of a technician's paid time spent with hands directly on the work, repairing, adjusting, installing, divided by their total available time. It excludes travel, waiting for parts, getting instructions or permits, and paperwork. It measures how well the shop is organized to let skilled people work, not how hard those people try.

What is a good wrench time percentage?

Commonly cited benchmarks put a typical maintenance organization at 25-35%, a well-planned shop around 45%, and world-class near 55%. Compare only against consistent definitions, one shop counting travel as wrench time and another excluding it are not measuring the same thing. The realistic goal for most plants is moving from the low thirties into the mid-forties through planning.

Why is wrench time so low?

Because most of the day disappears into waiting and walking, not idleness. The biggest losses are usually waiting for parts, traveling to and locating jobs, obtaining instructions and permits, and administration or data entry. Every one of these is an organizational gap the technician cannot close alone, which is why low wrench time is a management finding, not a worker one.

How does planning improve wrench time?

Planning removes the waits before the job starts. A planner scopes the job, lists parts and tools, writes the procedure, and clears permits, so the technician arrives to a ready, kitted job instead of hunting for materials. Kitting parts, scheduling jobs in geographic clusters, and capturing data at the point of work each attack a specific loss category. Together they routinely move wrench time up 10-15 points.

Should you push technicians to raise their own wrench time?

No. Wrench time is a scoreboard for the organization, not the individual. Pushing people to raise it drives them to look busy and rush repairs, hurting quality and safety while the real losses, parts, planning, scheduling, go unaddressed. Fix the system that makes them wait, and wrench time rises on its own without anyone moving faster.

Does higher wrench time mean lower quality work?

Not when you raise it the right way. If you gain wrench time by removing waits, kitting parts, planning jobs, cutting travel, quality is unaffected or improves, because technicians work from prepared plans with the right parts on hand. Quality only suffers if you chase the number by pressuring people to rush, which is why you fix the system rather than the person.

Wrench Time: Measuring and Improving It

Q: How do you measure wrench time?

By work sampling: an observer takes many randomized instantaneous observations across the crew over days or weeks and records, for each, whether the technician is on-tool or in a delay category. The share of on-tool observations estimates wrench time. Take enough samples that one bad day does not skew it, and make clear you are measuring the system, not individuals.

What wrench time really measures, the benchmarks worth trusting, where the rest of the day goes, and how planning lifts it without pushing anyone to rush.

Wrench time is the fraction of a maintenance technician's paid time spent with hands directly on the work, the actual repairing, adjusting, and installing, as opposed to traveling to the job, waiting for parts, tracking down a drawing, or entering data. Put simply: wrench time = hands-on task time ÷ total available time as a percentage.

It is one of the most misread metrics in maintenance. A low number does not mean your technicians are lazy; it almost always means the shop around them is disorganized, the parts were not staged, the job was not planned, the permit was not ready. This guide covers the honest benchmarks, where the missing hours actually go, how to measure wrench time without alienating the crew, and how planning lifts it. It sits alongside maintenance planning and scheduling as the metric that proves planning is working.

What is wrench time, exactly?

Wrench time is hands-on time as a share of paid time. The important word is hands-on: the definition counts the technician physically working on the asset and excludes everything that surrounds it, however necessary that surrounding work is.

Getting parts, reading the job plan, walking to the job, and closing out the work order are all legitimate parts of the day, but none of them are wrench time. That is the point of the metric: it isolates the productive core so you can see how much of the day the organization lets a skilled person actually spend being skilled. Measured this way, wrench time is a scoreboard for management, not for the technician.

What is a typical wrench time?

Commonly cited industry benchmarks put a typical maintenance organization at 25-35% wrench time a well-planned shop around 45% and world-class operations near 55%. Notice what that means: even a good shop spends more than half the paid day not turning wrenches, and a typical one spends closer to two-thirds of it on everything but the work.

The benchmarks are humbling. Chasing 100% is neither possible nor desirable, travel, planning, and safety steps are real work, but the gap from 30% to 45% is pure recoverable waste.

Two cautions on benchmarks. First, they only compare if the definition is identical, one shop counting travel as wrench time and another excluding it are not measuring the same thing. Second, do not chase 100%; a tech running to every job with no safety margin is a different problem. The realistic prize is moving a typical shop from the low thirties into the mid-forties, and that is entirely a planning story.

Where does the rest of the day go?

Into waiting and walking. When you sample a low-wrench-time shop, the lost time clusters into a predictable handful of categories, and every one of them is an organizational failure the technician cannot fix alone.

The lost hours are not idleness, they are waiting for parts, walking to find the job, chasing a permit, and re-keying data. Planning attacks each band directly.

Waiting for parts is usually the biggest single band, which is why spare parts inventory management and job kitting move wrench time more than almost anything else. Travel and locating shrink when jobs are scheduled in geographic clusters. Instruction and permit delays vanish when the job plan and safe-work paperwork are prepared before the tech is dispatched. And the admin band collapses when data capture happens at the point of work instead of in a back-office session at shift's end.

How do you measure wrench time honestly?

By observation, not by asking people to time themselves. The rigorous method is work sampling: an observer takes many randomized instantaneous observations across the crew over days or weeks, noting for each whether the technician is on-tool or in one of the delay categories. The percentage of on-tool observations estimates wrench time.

Two rules keep it honest and keep the crew on side. Sample enough moments across enough days that one bad morning does not skew the result. And be explicit, out loud, that you are measuring the system not individuals, because the moment technicians think a stopwatch is grading them, they optimize for looking busy and the number stops meaning anything. Self-reported timesheets are worse than useless here; nobody logs their own idle time accurately, and the exercise breeds resentment for a bad estimate.

Work sampling gives you a periodic snapshot, but it is expensive to run and stale by the time it is analyzed. The emerging alternative is to infer activity continuously from the digital trail a connected workflow already leaves, when a job was dispatched, when parts were issued, when the technician opened the procedure, when findings were logged at the asset. Read carefully and non-punitively, that trail turns wrench time from an annual study into a live signal you can act on this week, not next quarter.

How does planning lift wrench time? A five-step loop

Every point of wrench time you gain comes from removing a wait, and planning is the discipline of removing waits before the job starts. Work the loop:

Measure the baseline by observation. Run a work-sampling study and categorize the losses. You cannot fix waiting-for-parts if you do not know it is 20% of the day. This baseline is also how you will prove the gains later.
Plan jobs before they are scheduled. A planner scopes each job, lists the parts and tools, writes the procedure, and identifies permits, so the work order that reaches the tech is ready to execute, not a one-line complaint. This single practice is the largest lever on the list.
Kit and stage parts ahead of the job. Pull and stage every part before the scheduled date. A kitted job removes the biggest delay band entirely; the tech walks to staged materials instead of hunting the storeroom mid-repair.
Schedule in clusters and protect the schedule. Sequence the week so jobs in the same area run together, and defend that schedule from constant interruption. Fewer trips and fewer break-ins mean more time on tools. Tightening the request-to-work-order flow keeps low-value jobs from breaking into the plan.
Capture data at the point of work and re-measure. Let technicians record findings and actuals where they stand, on a mobile device, instead of a back-office session. Then re-run the work sample. Rising wrench time on a stable headcount is capacity you created for free, capacity that goes straight into reliability work.

What is a point of wrench time worth?

A lot, because it multiplies across the whole crew. Take a 40-technician department, each with roughly 2,000 productive-eligible hours a year, about 80,000 hours of paid capacity. At 30% wrench time, only 24,000 of those hours reach the tools. Lift the shop to 45% and you get 36,000, an extra 12,000 hands-on hours a year, the equivalent of about six full-time technicians at zero additional headcount.

Planning does not make anyone work faster. It shrinks the parts-wait and travel bands, and the hands-on band grows to fill the space, capacity created without a single new hire.

That reclaimed capacity is where the real return sits. Six technicians' worth of freed hours is enough to stand up a genuine predictive maintenance program, work down a backlog of deferred jobs, or actually chase the recurring failures dragging down MTBF the proactive work that reactive shops never find time for. Wrench time, in other words, is not just an efficiency metric; it is the hidden budget line that funds every reliability improvement you have been putting off.

What the numbers say

Wrench time is capacity in disguise. The U.S. Bureau of Labor Statistics projects 13% growth (2024–2034) for industrial machinery mechanics, machinery maintenance workers, and millwrights, much faster than average, with about 538,300 jobs held in 2024 and roughly 54,200 openings a year (BLS Occupational Outlook Handbook). Raising wrench time from 30% to 45% adds half again as much productive capacity from the technicians you already employ, cheaper than hiring in a tight market.
That reclaimed capacity flows into proactive work, where the returns are documented. The U.S. Department of Energy's FEMP O&M guidance, maintained by PNNL, reports proactive programs can cut maintenance costs by 30–40% versus reactive operation, with condition-based approaches saving 8–12% over preventive-only (PNNL, O&M Best Practices: Maintenance Approaches). Wrench time is the hidden supply of hours those programs run on.

Wrench time is the clearest single number for whether your maintenance organization is set up to let skilled people do skilled work. It is low almost everywhere, and it is low for reasons the crew cannot fix, waiting, walking, hunting, re-keying. Plan the job, kit the parts, protect the schedule, and capture data where the work happens, and the number climbs without anyone rushing a repair. To see how one plant cut the waiting and re-keying by connecting the floor to its systems, read the CLS case study or see how Harmony captures work at the point of the job on the features overview.