{"id":2219,"date":"2026-08-19T23:04:44","date_gmt":"2026-08-19T23:04:44","guid":{"rendered":"https:\/\/www.repairshopsolutions.com\/about\/?p=2219"},"modified":"2026-08-20T00:54:49","modified_gmt":"2026-08-20T00:54:49","slug":"tekmetric-dvi-features-repair-shop-solutions","status":"publish","type":"post","link":"https:\/\/www.repairshopsolutions.com\/about\/tekmetric-dvi-features-repair-shop-solutions\/","title":{"rendered":"What Tekmetric Users Want in a DVI \u2014 And Where to Find It Today"},"content":{"rendered":"\n
\n
\"TekMetric
TekMetric’s own feedback board shows thousands of votes for features Repair Shop Solutions has delivered since 2011<\/figcaption><\/figure>\n<\/figure>\n\n\n\n

By Scott Osborn<\/a> \u2013 ASE Master Technician, Author of \u201cMaking Smart Choices<\/a>\u201c<\/p>\n\n\n\n

\n\n\n\n

Tekmetric <\/a>is a solid shop management system with one notable gap \u2014 its DVI feature set<\/a>. Thousands of independent auto repair shops run their business on it every day. But if you’ve spent any time on Tekmetric’s feature request board, you’ve seen something interesting: their own customers are frustrated with the DVI.<\/p>\n\n\n\n

Not with Tekmetric overall \u2014 specifically with the inspection tool.<\/p>\n\n\n\n

We went through every Tekmetric DVI feature request in the Inspections category on their Canny feedback board. We counted the upvotes. We read the comments. What we found was striking: the features Tekmetric users want most are features Repair Shop Solutions has already built<\/strong>.<\/p>\n\n\n\n

Here are the top requests \u2014 straight from Tekmetric’s own community \u2014 and how RSS handles each one today.<\/p>\n\n\n\n

\n\n\n\n

1. Prompt for Mileage When a Technician Starts an Inspection<\/h2>\n\n\n\n

646 upvotes on Tekmetric’s feedback board<\/strong><\/p>\n\n\n\n

This is the single most requested DVI feature in Tekmetric’s entire history. Shops want the system to require mileage entry before a technician can start or complete an inspection. Without it, mileage gets skipped, odometer records are inconsistent, and maintenance interval tracking breaks down.<\/p>\n\n\n\n

One commenter put it simply: “So many times I find a car where techs miss the mileage and I’m checking them and can’t get mileage yet.”<\/p>\n\n\n\n

How RSS handles it:<\/strong> Mileage entry is built into the inspection workflow<\/a>. Shops can require it before the tech proceeds. No workaround, no reminders \u2014 it’s just part of the process.<\/p>\n\n\n\n

\n\n\n\n

2. Canned Jobs Tied to Inspection Findings<\/h2>\n\n\n\n

288 upvotes<\/strong><\/p>\n\n\n\n

Tekmetric users want canned jobs linked to specific findings, not just inspection tasks. The difference matters: a coolant line item might produce a fluid exchange recommendation if the fluid fails a test, or a pressure test recommendation if it’s leaking. Two different findings, two different canned jobs \u2014 but Tekmetric only supports one mapping per task.<\/p>\n\n\n\n

How RSS handles it:<\/strong> Each finding maps to its own canned job. Different findings on the same inspection line automatically trigger different recommended jobs. The estimate builds itself based on what the tech actually found.<\/p>\n\n\n\n

\n\n\n\n

3. Show Previous Inspection Results During a New Inspection<\/h2>\n\n\n\n

199 upvotes<\/strong><\/p>\n\n\n\n

This is one of the most important features in the DVI category and one of the most painful gaps in Tekmetric. When a tech opens a new inspection, they have no visibility into what was found or recommended on the last visit. This creates consistency issues among technicians, leads to embarrassing moments when a prior recommendation disappears from a new inspection, and forces advisors to manually dig through service history.<\/p>\n\n\n\n

One Tekmetric user described the scenario directly: “Previously, we recommended front brakes and a trans service. The customer approved the brakes but not the trans service. But the inspection today says the trans fluid is just fine. The customer looks at you like you’re an idiot.”<\/p>\n\n\n\n

Another user explained the deeper problem: “Having the last inspection shown beside the current inspection so we can see what was found and recommended last service would be so good for consistency between technicians.”<\/p>\n\n\n\n

How RSS handles it:\u00a0When a tech opens a new inspection, all unaddressed items from prior visits automatically carry over and are ready to verify<\/a>. The tech can confirm each one, update findings, or clear it if the work was done. Nothing falls through the cracks, and nothing disappears between visits. Advisors never have to dig through service history to remind a customer what was deferred last time. And, we allow the tech to simply copy over the info, photos, and notes from the previous visit<\/p>\n\n\n\n

\n\n\n\n

4. Private Technician Comments Separate from Customer-Facing Notes<\/h2>\n\n\n\n

109 upvotes<\/strong><\/p>\n\n\n\n

Tekmetric users want two separate note fields on each inspection line \u2014 one private for the tech and advisor, one customer-facing. The problem they describe is common: advisors edit tech notes to make them more customer-friendly and, in doing so, lose the original technical detail the tech recorded.<\/p>\n\n\n\n

One shop owner explained it clearly: “The technician puts in notes under what they are recommending and why, and our advisor goes in and changes those notes so they are more digestible to the guest. We then lose the notes the technician left. There should be 2 spots for notes, one private, and one customer facing.”<\/p>\n\n\n\n

How RSS handles it:<\/strong> We can mark notes as “Internal,”<\/a> which means the shop can see them, but they will not be sent to the customer. Advisors can polish the customer copy without losing what the tech actually wrote. Both are preserved on every line item.<\/p>\n\n\n\n

\n\n\n\n

5. Prioritize Red, Yellow, and Green Findings in the Right Order<\/h2>\n\n\n\n

107 upvotes<\/strong><\/p>\n\n\n\n

Customers need to see urgent findings first. When a shop sends an inspection report with safety-critical items buried randomly in the middle of a list, customers miss them \u2014 and advisors have a harder time selling the work. Tekmetric users have been asking for auto-sorting that puts red findings at the top, yellow in the middle, and green at the bottom.<\/p>\n\n\n\n

One shop put it bluntly: “Having these randomly listed is too visually confusing and makes the service advisors’ job tougher than it needs to be.”<\/p>\n\n\n\n

How RSS handles it:<\/strong> The customer-facing inspection report automatically sorts findings by severity<\/a>. Urgent items appear first. Green items appear last. The customer sees the most important recommendations first, which translates directly into faster approvals and higher sell-through rates for critical work.<\/p>\n\n\n\n

\n\n\n\n

6. AI-Generated Technician Notes<\/h2>\n\n\n\n

93 upvotes for autocorrect alone \u2014 RSS goes further<\/strong><\/p>\n\n\n\n

Tekmetric users asked for basic autocorrect because technician notes were going to customers with spelling errors. Ninety-three shops upvoted that request. One user wrote in all caps: “DOESNT LOOK PROFFESIONAL TO THE CUSTOMER.”<\/p>\n\n\n\n

How RSS handles it:<\/strong> RSS integrates ChatGPT directly into the inspection workflow<\/a>. Techs don’t type notes \u2014 the AI writes them. A technician marks a finding, and the AI automatically generates a professional, complete, customer-facing recommendation. No typos. No grammar issues. No inconsistency between techs. The inspection report reads the same way whether it was written by your most experienced advisor or your newest hire.<\/p>\n\n\n\n

\n\n\n\n

7. Customer Notification When Inspection Is Viewed<\/h2>\n\n\n\n

79 upvotes<\/strong><\/p>\n\n\n\n

Shops want to know the moment a customer opens their inspection link so they can follow up while the customer is actively engaged. Tekmetric sends an email when the inspection is complete but doesn’t notify the advisor when the customer actually views it.<\/p>\n\n\n\n

How RSS handles it:<\/strong> RSS tracks customer viewing activity and notifies the advisor when the customer opens the inspection link<\/a>. The advisor knows exactly when to pick up the phone \u2014 while the customer is still looking at the report.<\/p>\n\n\n\n

\n\n\n\n

8. Add Pictures of the Service Writer and Tech to the Customer Report<\/h2>\n\n\n\n

140 upvotes<\/strong><\/p>\n\n\n\n

Shops want the inspection report to feel personal. Customers trust people, not software. Seeing a photo of the technician who inspected their vehicle and the service advisor presenting the findings changes the dynamic of the interaction entirely.<\/p>\n\n\n\n

One shop owner said it well: “It makes it more personal.”<\/p>\n\n\n\n

How RSS handles it:<\/strong> RSS supports employee photos on the customer-facing inspection report<\/a> for both the technician and the service advisor. It’s a small detail that makes a meaningful difference in how customers receive the inspection.<\/p>\n\n\n\n

\n\n\n\n

9. Unlimited Characters in the Findings Field<\/h2>\n\n\n\n

123 upvotes<\/strong><\/p>\n\n\n\n

Tekmetric caps technician findings at 1,000 characters. For shops doing thorough inspections on complex vehicles, that’s not enough. Techs either truncate their notes or find workarounds that add extra steps to the workflow.<\/p>\n\n\n\n

How RSS handles it:<\/strong> No character limit. Techs write as much as the finding requires. A detailed explanation of a complex suspension issue doesn’t get cut off mid-sentence.<\/p>\n\n\n\n

\n\n\n\n

10. Show the Inspection Before the Estimate<\/h2>\n\n\n\n

169 upvotes<\/strong><\/p>\n\n\n\n

When a shop sends a customer their inspection and estimate together, Tekmetric puts the estimate first. That’s backwards. Customers who see the dollar amount before understanding what was found are more likely to push back or decline. The inspection should tell the story first \u2014 here’s what we found, here’s what it means \u2014 and the estimate should follow naturally from that.<\/p>\n\n\n\n

Tekmetric users have been asking for this order to be flipped for years.<\/p>\n\n\n\n

How RSS handles it:<\/strong> The inspection leads. The estimate follows. Every customer-facing report RSS sends puts the findings and photos first so the customer understands the condition of their vehicle before they ever see a price. When the story is told in the right order, the estimate makes sense \u2014 and approvals happen faster.<\/p>\n\n\n\n

\n\n\n\n

The Bigger Picture<\/h2>\n\n\n\n

Of the 65 most-voted DVI feature requests on Tekmetric’s feedback board, Repair Shop Solutions already delivers 56 of them \u2014 86%. The nine we don’t cover are almost all payroll and time-tracking features that belong in a shop management system, not a DVI tool.<\/p>\n\n\n\n

That’s not a coincidence. RSS was built in 2011 specifically as a DVI platform by ASE Master Technicians who run their own shop. The tool wasn’t designed to be a feature of something bigger \u2014 it was designed to do this one thing better than anyone else.<\/p>\n\n\n\n

The result is a DVI that Midas, NAPA, and independent shops across North America have used to perform millions of inspections. One long-time customer described it this way: “No hard-to-break contracts \u2014 in fact, no contracts \u2014 making it an easy option to try out a DVI without a big financial risk. Reward is the only thing you’ll find with RSS.”<\/p>\n\n\n\n

\n\n\n\n

What RSS DVI Delivers<\/h2>\n\n\n\n