Maintenance KPIs & Reliability

Wrench Time: How to Measure It and Why Planning Raises It

Wrench time is the share of a shift spent hands-on. Learn how to measure it with a simple sampling study and why kitted, planned jobs move it most.

Rovaryn DigitalNovember 13, 20268 min read
Wrench Time: How to Measure It and Why Planning Raises It

A Tuesday shift that looks busy and builds nothing

It is 2:30 on a Tuesday. Your lead technician has been on shift since six, and he is tired. He walked to the crib twice, waited fifteen minutes for a lockout sign-off, drove a cart across the plant for a gasket that turned out to be the wrong size, and filled in three work orders from memory. He has had a wrench on a fastener for maybe two hours.

Nobody was slacking. Every one of those delays was real. But if you asked what the crew produced today, the honest answer is "less than the hours say."

That gap between hours paid and hours spent on the job is what wrench time describes. Most plants never measure it, so they argue about headcount instead of the delays that eat the shift. This article shows you how to measure it with a clipboard and one week of observations, where the hours leak, and which planning habits win them back.

What wrench time actually counts

It is the share of a technician's paid shift spent doing hands-on work on the equipment: turning, adjusting, inspecting, replacing, testing. It is a ratio.

Wrench time = hands-on minutes ÷ paid shift minutes × 100.

What counts as hands-on needs a clear rule before you start, or two observers will score the same moment differently. A workable rule:

  • Counts: working on the asset, reading a gauge as part of the task, using a hand tool or a meter on the job, and a short in-place discussion with the operator about the fault.
  • Does not count: travel, collecting tools or parts, waiting for a lockout or permit, waiting for the machine to be released, getting instructions, filling in paperwork, and breaks.

Notice that some non-counting activity is necessary. A lockout is a safety step. A work-order close-out is a data step. The goal is not 100%. The goal is to know how much of the rest is avoidable.

One more warning. It measures how the shift is used, not how hard people work. Use it to find process delays, never to rank individual technicians. The moment the crew thinks it is a scorecard on them, the observations stop being honest.

How to run a simple sampling study

You do not need stopwatches or software. A work-sampling study takes snapshots of what people are doing and counts them.

  1. Pick a window. Five working days across all shifts you care about gives a first picture. A single day is too noisy.
  2. Tell the crew first. Explain that you are studying delays in the process, not grading anyone. Share the results with them afterward.
  3. Define your categories. Use five or six: hands-on work, travel, waiting for parts or tools, waiting for access or permits, paperwork and planning, and other.
  4. Take random snapshots. At random times, glance at each technician and record the category. Do this 15 to 20 times per technician per day. Random timing matters. If you always check at 9:00, you will always catch the same activity.
  5. Add it up. Count the hands-on tallies and divide by total tallies. That is your measured figure.

A worked example, with round numbers for illustration only: you take 400 snapshots across a week. 120 are hands-on, 80 are travel, 70 are waiting for parts or tools, 50 are waiting for access, 50 are paperwork, and 30 are other. Your figure is 120 ÷ 400 = 30%. Just as useful, the largest non-productive buckets are travel (20%) and waiting for parts or tools (17.5%). Those are your targets.

Sample sizes of a few hundred give a rough but usable answer. Treat it as a baseline with a margin of error, and repeat the study after you change something. The point is the trend and the breakdown, not a decimal place.

What a typical baseline looks like

Once you have your own number, it helps to know where it sits. Industry commentators commonly place typical wrench time well under half the shift, with the rest lost to travel, waiting and paperwork.

If your study lands well under half the shift, you are not unusual, and you are not failing. It means the system around the technician is where the hours go. If it lands well below, look hardest at the biggest leak in your tally.

Do not adopt a general benchmark as your number. Your plant layout, crew size, stores setup and mix of breakdown and planned work are your own. The measured figure from your own floor is the one you can improve and defend.

Where the hours leak, and the fix for each

Every bucket in your tally has a mechanism behind it. Here are the common ones.

Travel. Technicians walk to the crib, the shop, the machine, back to the crib. A plant with scattered storage and one-job-at-a-time dispatch multiplies this. Fix: sequence jobs by area so one trip covers several tasks, and stage common consumables near the equipment they serve.

Waiting for parts or tools. The job starts, the part is not in the crib or is the wrong one, and the technician stops. Fix: identify parts and tools before the job is released, reserve them, and put them in a kit at one pickup point.

Waiting for access. Lockout, permits, and operations releasing the machine all create dead time when no one has agreed a window. Fix: schedule the job with operations in advance so the machine is ready at the planned hour.

Unclear scope. A vague work request ("pump noisy") sends the technician to investigate before they can fix. Fix: a short job plan with the steps, the safety requirements, the parts list, and the estimated hours.

Paperwork. Rewriting the same information on closing a job takes minutes that add up. Fix: pre-printed or pre-filled work orders where the technician only records what changed. The work-order lifecycle article shows where each piece of information belongs.

Notice what these fixes share. None of them ask the technician to work faster. They all happen before the technician reaches the machine. That is planning.

Why planning raises wrench time

Planning is the work of deciding, in advance, what a job needs: the steps, the parts, the tools, the people, the access, and the time. Scheduling then puts that job on a particular day for a particular technician, with operations aware and ready.

A planned job arrives with its kit. The parts are on a cart, the permit is arranged, the scope is written down, and the machine is coming down at a known hour. The technician's first action is touching the equipment, not looking for what they need.

Industry commentators say effective maintenance planning and scheduling can raise the figure substantially, which is roughly equivalent to adding capacity without hiring.

Read that carefully. It is not a promise about your plant, and it does not arrive by buying a tool. It comes from doing the planning work before the job is released. The spreadsheet only holds the plan. For the full method, see the preventive maintenance planning guide.

Emergency work will always exist and will always cut through a plan. The aim is to shrink the share of the week that is scrambling, so each planned job gets its full kit.

Building a week that protects hands-on hours

Here is a practical routine you can start with a spreadsheet.

  1. Know your available hours. List each technician and their real available hours after meetings, training, and leave.
  2. Load planned work first. Place PMs and planned repairs into the week, grouped by area, using the estimated hours from the job plan.
  3. Hold back a reserve. Leave room for breakdowns based on what your own downtime log shows, not a guess.
  4. Check the load. No technician or day should be booked past what its hours can hold. An overloaded plan fails by Wednesday and teaches the crew to ignore the schedule.
  5. Kit the jobs the day before. Confirm parts, permits, and operations release.
  6. Review on Friday. Compare what was planned with what was done, and note why jobs slipped.

The Weekly Work Plan & Technician Assignment Planner is built for steps 1 to 4: tasks and crew hours go in, an assigned week comes out, and it flags where you have overloaded a technician or a day. It is a spreadsheet, so it plans the week you enter. It does not pull in work orders by itself, and it is not a CMMS.

Closing the loop matters too. Completed-on-time PMs feed your PM compliance percentage, and both belong in the wider set of maintenance KPIs that matter. Track them together. If hands-on share rises while compliance falls, ask whether the crew is being pulled onto other work.

Your first month

Run the sampling study this week. Pick the two largest non-productive buckets. Change one thing for each: group jobs by area to cut travel, and kit the next ten planned jobs to cut waiting. Run the study again in four weeks with the same method and the same categories, and compare.

If the number moves, you have evidence for planning. If it does not, your tally will show which leak is still open. Either way you will be arguing from your own data, which is a much stronger position than quoting anyone else's.

Want the observation sheet and a starter weekly plan? Join the newsletter and download the template.

Get more guides like this in your inbox

Related guides