Every repair order has a moment where a tech stops and looks something up: a torque spec, a connector pinout, a TSB, a labor time. Reading the answer is part of the job. Finding it often isn’t. Nobody bills for menu clicks, wrong-engine selections, or the walk back to the desk terminal, and across a full team those minutes add up to hours. The number is different in every shop, so this guide gives you the formula, a worked example, and a one-week method for measuring it in your own bays.
Quick Answer: Lost lookup hours per week = technicians × lookups per tech per day × avoidable minutes per lookup × workdays ÷ 60. Avoidable minutes are the time spent finding the right page (menu navigation, selecting the wrong year or engine, walking to a shared terminal, cross-checking a forum), not the time spent reading the procedure. With example inputs of 4 techs, 6 lookups each per day, and 3 avoidable minutes per lookup, a shop loses 6 hours a week, about 26 hours a month. At Tekmetric’s U.S. average labor rate of $132 per hour, that is roughly $3,430 a month in labor capacity. That capacity only turns into lost revenue when another repair order is waiting for the bay, so log your own lookups for one week before trusting any average, including this one.
What Counts as Lost Billable Time in a Lookup?
Lookup time has two parts, and only one of them is a problem. Read-time is the minutes a tech spends reading the procedure, checking the spec, and tracing the circuit. That work is part of the repair, and it belongs on the job. Find-time is everything before that: choosing the right menu path, correcting a wrong submodel, scrolling a document list, or confirming that a forum answer matches the vehicle in the bay.
Find-time is the part a shop can recover. It produces nothing the customer pays for, and it happens on almost every job. That is why the cost of searching before every repair order rarely shows up on a report: it is spread across dozens of small interruptions instead of one large one.
Automotive-specific research on this is thin, and it is worth saying so plainly. The clearest published figure we found comes from a different industry. A Kothes Insight-Report survey of service technicians, discussed in a 2023 Fluid Topics webinar, found that over 80% of service technicians spend between 30 minutes and 2 hours a day searching for information, and 10% spend more than 2 hours. Those respondents service machines and equipment, not cars, so treat the number as a signal that the problem is common, not as a benchmark for your shop. Closer to home, PartsTech’s 2025 State of General Auto Repair Shops report, as summarized by MOTOR, lists limited repair data access as a top challenge for 13% of shops, behind training for complex vehicles at 20%.
Where Does Lookup Time Actually Go?
Find-time is rarely one long search. It usually comes from five repeat offenders:
- Menu navigation. Year, make, model, engine, system, subsystem, document type, and then the right document inside a list. Each step is quick; together they are not.
- Wrong vehicle configuration. Picking the wrong engine or submodel returns a procedure or spec that looks right and isn’t. Catching that costs a second search. Missing it costs far more.
- The walk to a shared terminal. When the lookup station is at the front counter, every question means leaving the bay, and sometimes waiting for someone else to finish.
- Forum cross-checking. A forum post or video may be right, but a tech still has to confirm it applies to this year and engine, which is exactly the check that OEM repair information exists to settle.
- Asking the lead tech. When a tech asks the lead tech, a 4-minute question costs 8 tech-minutes, because two people stop working, and one of them is usually the most productive person on the floor.
Some lookups also involve finding a physical part, not just a document. On a packed engine bay, locating a sensor or ground point can take longer than the test itself, which is why OEM component location diagrams matter as much as procedures. For a closer look at the patterns behind these delays, see where technicians’ lookup time goes.
How Do You Calculate Your Shop’s Lost Hours?
The formula
Four inputs are enough to size the problem:
- Technicians who do their own lookups.
- Lookups per tech per day, counting every spec, procedure, diagram, TSB, DTC, and labor time check.
- Avoidable minutes per lookup, meaning find-time only, not read-time.
- Workdays per week.
Multiply all four and divide by 60 to get lost hours per week. Multiply by 4.33 for a monthly figure, then by your door labor rate for the dollar value of that capacity.
What the numbers look like for a four-tech shop
The table below holds three inputs steady (4 techs, 6 lookups each per day, 5 workdays) at a $132/hour labor rate and changes only the avoidable minutes. These are example inputs chosen to show how the math moves, not measured figures from any shop.
| Avoidable minutes per lookup | Lost hours per week | Lost hours per month | Labor capacity per month at $132/hr |
|---|---|---|---|
| 1 minute | 2 | ~8.7 | ~$1,140 |
| 2 minutes | 4 | ~17.3 | ~$2,290 |
| 3 minutes | 6 | ~26 | ~$3,430 |
| 5 minutes | 10 | ~43.3 | ~$5,720 |
Labor rate changes the result as much as minutes do. Tekmetric’s labor rate index, built on data from more than 10,000 shops, puts the U.S. average at $132 per hour as of June 2026. The PartsTech 2025 report, cited by AAA, found that almost half of shops price labor between $120 and $159 per hour. Use your own posted rate, not the average.
Does saved lookup time become billed time?
Not automatically. Recovered lookup minutes only become revenue when the tech has another repair order to move to. In a shop with cars waiting on the lot, freed-up time goes straight to the next job, and the full figure applies. In a slow week, a tech who finishes early may simply wait. If you estimate that about half of recovered time would turn into billed work, cut the dollar column in half: the 3-minute row becomes 13 hours and about $1,720 a month. That adjustment is the honest version of the number, and it is the one to use when budgeting.
How Does Lookup Time Show Up in Productivity and Flat-Rate Pay?
Shops usually track two numbers, and lookup time hits both. Productivity is billed hours divided by clock hours, a measure of how much paid time becomes sold time. Efficiency is billed hours divided by the hours actually worked on repair orders, a measure of how fast a tech completes the work against the labor guide. Shop consultants commonly set a productivity target of 80 to 90 percent, which leaves 10 to 20 percent of clock time for everything that can’t be billed.
Lookup time spends that allowance quickly. In the four-tech example, 160 clock hours a week at an 85% target leaves 24 non-billable hours for test drives, parts runs, comebacks, and meetings. Six hours of find-time uses a quarter of that allowance before anything else happens.
On flat rate, the cost lands on the technician first. Take a job with 1.5 hours of book time. If the tech spends 12 minutes finding the procedure and torque spec, and the repair itself takes exactly book time, the job takes 1.7 clock hours and the tech’s efficiency on it drops from 100% to about 88%. The flag hours stay the same; the time to earn them doesn’t. The shop loses too, because OEM labor times are built on how long an experienced technician takes to do the work, not on time spent finding the procedure first. Twelve minutes of find-time on each of four jobs is most of an hour the bay could have sold.
Diagnostic work is where this matters most. Labor guides price replacing a part, not the research needed to find which part failed, so diagnostic lookup time often has no book number at all. A shop that doesn’t charge a separate diagnostic fee absorbs every minute a tech spends tracing a circuit. That is where OEM wiring diagrams for electrical diagnostics earn their place, and where a documented fix can end the search early: if the symptom matches a known issue, a technical service bulletin may already describe the cause and the repair.
How Can You Measure Lookup Time in One Week?
An average from another shop tells you little about your own. A one-week log gives you real inputs for the formula, and it takes almost no setup:
- Put a tally sheet at every bay. One line per lookup, filled in by the tech at the moment it happens, not reconstructed at the end of the day.
- Record what was needed. Spec, procedure, wiring diagram, component location, TSB, DTC, or labor time.
- Record where the tech looked. Shop software at the counter, a phone, a forum or video, or another tech.
- Split find-time from read-time. Note the minutes until the right page was open, separately from the minutes spent using it. Rough estimates to the nearest minute are enough.
- Mark wrong-vehicle results. Flag any lookup where the first answer turned out to be for the wrong year, engine, or submodel.
- Total it on Friday. Average lookups per tech per day and average find-minutes per lookup, then run the formula with your labor rate.
Look for two things in the totals. First, check whether a few lookup types account for most of the find-time. Second, check the “another tech” column, which shows how much of the lead tech’s day goes to other people’s questions. Both tell you where to fix the process before spending money on anything.
What Changes When Lookup Is One Question?
Find-time exists because most repair information is organized as a library: the tech has to know where a document lives before reading it. Jayda changes the access model. A tech asks the question the way they’d say it to another tech (for example, “cam phaser replacement procedure, 2018 F-150”) and Jayda returns the matching OEM document for that vehicle, with the source shown.
The data behind it is licensed from MOTOR Information Systems, a Hearst company operating since 1903, and covers 43 manufacturers from 1985 to 2026 across more than 63,000 specific vehicle configurations. Jayda’s AI searches and retrieves OEM content; it does not write repair steps. When a procedure isn’t in the database, Jayda says so instead of filling the gap. That design choice, explained in why AI should search repair information rather than generate it, is why every answer can be checked against the manufacturer’s page before a tech relies on it.
Jayda does not publish a minutes-saved figure, and you don’t need one. The break-even math is simple division using your labor rate:
- Business ($149/month, 12-month agreement, up to 10 techs): at $132/hour, the plan equals about 68 billed minutes a month for the whole shop, or roughly 3 minutes per workday.
- Pro Tech ($14.95/month, one user): at $132/hour, the plan equals about 7 billed minutes a month.
The cleanest test is to run the one-week log twice. Log a normal week first, then log a week using Jayda beside the system your shop already uses, and compare find-minutes per lookup. The Business plan’s 7-day trial matches that window; it is activated through the Jayda team rather than self-serve signup, and a trial that converts to paid starts the 12-month agreement. For a wider set of criteria when comparing platforms, including data source, coverage, and how answers are delivered, see how to choose OEM repair software.
