If that sounds familiar, you’re not alone. And, the problem almost certainly isn’t the software.
Autoflow founder, Chris Cloutier, has been in the auto repair business long enough to have seen this play out in his own shops. He’s also spent years talking to shop owners across the country who are stuck in the same cycle: invest in a DVI, hit a wall of resistance, and then wonder what went wrong.
“The technician was basically saying, ‘No, I’m not going to do digital inspections. They’re just not my thing,'” Chris recalled in a recent Autoflow webinar on friction in the repair facility.
A Reddit post where a tech openly refused to implement DVIs became the catalyst for a longer conversation about something every shop owner faces: what do you do when your team won’t adopt the process you know is right for the business?
Here’s what we’ve learned.
The Real Reason Techs Resist DVI
Before you can fix the adoption problem, you have to understand what’s actually driving it. Nine times out of ten, it’s not what the technician says it is.
Resistance to DVI software usually shows up as complaints about the tool: the tablet is slow, the templates are too long, or it takes too much time. Those things may be true and worth fixing but are often a surface expression of something deeper.
Chris put it plainly: “If you have a terrible inspection process, or a process where the technician doesn’t value the inspection, you cannot change the result by changing the tool.”
In other words, if your techs weren’t doing thorough inspections on paper, switching to a digital format won’t fix that. The struggle is about whether technicians believe inspections matter, whether they feel accountable for doing them, and if the shop has made clear that this is a non-negotiable part of the job.
There are a few common areas of pushback worth noting:
Speed and workflow concerns. Techs are paid at a flat rate in most shops. Anything that feels like it slows them down is going to get met with resistance. This is a legitimate concern that deserves a real answer, not dismissal. Why Vehicle Inspection Software Should Never Slow You Down is worth sharing with your team directly.
Accountability fear. A thorough DVI creates a record. For techs who have been cutting corners, intentionally or not, that visibility is unwanted.
The “not my job” attitude. This one is usually a symptom of unclear expectations. If the job description never mentioned inspections, or if the previous owner let it slide, techs have no reason to treat it as a requirement.
Old-school skepticism. Some experienced techs see DVI as a sales tool rather than a diagnostic one. They resent the implication that a photo of worn brake pads is more credible than their word.
Understanding which of these you’re actually dealing with changes how you handle the conversation.
Have the Right Conversation First
Most shop owners try to solve DVI resistance by adjusting the tool: simplifying the template, switching software, giving the tech a newer tablet. Chris calls this “painting the problem a different color.”
“How about this pink inspection? I still hate inspections. How about this plaid inspection? I hate inspections. Why? You need to include the person in the problem solving.”
That last part is the move most owners skip. Instead of asking whether a tech will comply, ask them what’s actually in the way.
Dennis McCarron, a business coach and human behavior consultant who joined Chris on the webinar, uses a framework called APAC: Acknowledge, Probe, Answer, Confirm. It’s a structured way to work through resistance without backing down or escalating.
Here’s what it looks like in practice:
Acknowledge. Don’t try to talk the tech out of their position before you’ve recognized it. If a tech says inspections are too slow, the worst thing you can do is immediately explain why they’re wrong. Instead, say, “I hear you. You feel like this is adding time to your day.” That one step diffuses more tension than most owners realize.
Probe. Ask genuine questions to get to the real objection. Not leading questions, not rhetorical ones. “Walk me through what slows you down most” is useful; whereas, a counter-productive question would be, “You don’t actually think inspections take that long, do you?”
“The person asking the question is in control of the conversation,” adds Chris. “Not the one who’s getting angry.”
Answer. Once you’ve actually heard the real concern, address it directly. If the tablet is slow, fix it. If the templates are too long, trim them. If the tech doesn’t understand why DVIs benefit them personally, that’s a conversation worth having.
Confirm. Make sure you’ve actually resolved the concern and that the tech understands what’s expected going forward.
This process works because it separates the emotional resistance from the practical objection. Often, once a tech feels genuinely heard, the real problem turns out to be smaller and more fixable than the original standoff suggested.
Dennis described exactly this happening during a shop consultation: “This guy’s all bristled up. He’s got a problem with the tablet and this and that. I just let him talk. After introducing myself and asking him if there’s any problems, he started talking to me about how he does understand why pictures are helpful. The conversation turned, and he started selling me the tool.”
Make “the Why” Impossible to Ignore
Automotive technicians won’t do something unless they understand why they’re doing it. Chris’ approach is to connect DVI directly to something techs already care about: doing right by the customer.
“Let’s get it through our heads. It’s a good inspection that must be done on a vehicle because if it’s my mother, my daughter, or my sister, I don’t want them stranded on a highway after they just went in for an oil change because a belt busted, and nobody communicated that it was frayed.”
That reframe will matter. When a DVI is positioned as a sales tool, techs who see themselves as craftsmen will resist it. When it’s positioned as the professional standard for thorough, documented vehicle care, it lands differently. The photo of the cracked belt isn’t there to upsell. It’s there so the customer can see exactly what the tech saw, make an informed decision, and trust the shop.
5 Ways to Build Trust with a Digital Vehicle Inspection explores the customer-facing side of this, and it’s worth walking your team through it so they understand the full picture.
Set Non-Negotiables and Stick to Them
Getting techs to understand “the why” is necessary. At Chris’ shops, DVI is not optional. It’s part of the job description, written down, and enforced consistently.
“This is something we do now, not something that’s an option or a choice,” he said. “Maybe so-and-so is having a bad day, and his write-ups aren’t very good. That’s one thing. But, it can’t be that the tech just stopped doing inspections. That’s not okay.”
The distinction Chris draws is between flexibility on quality in a given moment and flexibility on whether the process happens at all. A tech who submits a thinner inspection on a slammed Tuesday gets some grace. A tech who decides inspections don’t apply to them doesn’t.
This requires owners to be honest with themselves about what they’ve been enforcing. If you’ve been looking the other way on DVI compliance for months, the techs have learned that the rule is movable. Re-establishing it as a firm expectation will create friction. That’s unavoidable.
Dennis framed it this way: “If you back down from hostility, people see that as gaining ground. They’re moving their fence out a little further on their property.”
Get the Team’s Input on How, Not If
One of the most effective things Chris does when rolling out or re-enforcing a process is to involve techs in “the how” without making “the what” up for debate.
“It’s not ‘are we going to do this thing?’ It’s ‘hey, we’re going to do this thing. How do you think we should do it?'”
This is a meaningful distinction. Giving techs a voice in how inspections are structured, which items are in the template, how photos should be captured, what the workflow looks like at their particular bays, increases buy-in without creating a situation where the shop owner has to defend the decision to implement DVI at all.
It also produces better outcomes. Techs who work the process every day often have practical insights about what slows things down or what customers consistently ask about. That input makes the inspection itself better.
What it doesn’t do is open the floor to whether inspections will happen. That decision is made. The conversation is about proper execution of the DVI.
Track the Numbers That Prove the Value
Adoption tends to improve once techs can see what it’s actually producing. Show the team what good inspection write-ups are doing for car count, customer trust, and the shop’s average ticket. Increasing Your Auto Repair Shop’s Profit Margin with DVIs breaks down the revenue connection in detail.
When a tech can see that their thorough inspection on a Monday morning translated into a booked appointment for the deferred work weeks or months later, the tool stops feeling like extra work and starts feeling like part of how they contribute to the shop.
Some KPIs worth tracking per tech:
- Inspection completion rate: Are DVIs being performed on every eligible vehicle?
- Average number of photos and line items per inspection
- ARO on vehicles where a full DVI was completed versus those where it wasn’t
The last one is particularly powerful. The data tends to speak for itself.
What to Do When None of It Works
Sometimes a tech is resistant not because of a fixable concern but because they fundamentally don’t want to be held accountable for their work. That’s a different problem.
Dennis’ phrase for this is one worth remembering: you cannot warm hostility. At a certain point, if a tech has been given a clear explanation of the why and how, the right tools to do it, and consistent follow-through from management but is still refusing, the conversation shifts from adoption to the right employee fit for your shop.
Chris is direct about this: some things at his shops are non-negotiables, and when those lines get crossed, he has let people go. That’s not a failure of management; it’s management working as they should.
The goal is not to get every tech to love DVI. The goal is to build a shop where thorough inspections are the standard, customers get accurate vehicle information every time, and the team understands that this is what professional auto repair looks like.
That standard is worth protecting.
Autoflow’s DVI software is built to move fast in the bay, put high-quality inspection results in front of customers, and give shop owners the visibility they need to track what’s actually happening. If you’re navigating a DVI adoption challenge at your shop, we’d be glad to come alongside and talk through it.
