03/18/2026
🚨We had a conversation this week that honestly stopped us in our tracks.🚨
A collision repair facility using 1SourceADAS reached out after being told by an insurance partner that they would not accept “AI scrubbing services” as justification for ADAS-related repair procedures.
That raises a simple question…
If the information being provided is the same OEM-required data you would find manually—just delivered faster and more efficiently—what exactly is the concern?
Because let’s be clear:
The procedures identified in a 1SourceADAS report are not opinions. They’re not “suggestions.” They’re sourced from manufacturer documentation—the same information a technician or estimator would spend hours tracking down across multiple systems.
So is the issue the *information*… or the *efficiency* in how it’s delivered?
It’s a bit like saying:
“We fully support you using a wrench to fix the vehicle… just not a power tool.”
In today’s environment, where vehicles are more complex than ever and ADAS systems are directly tied to safety, the expectation shouldn’t be to slow down the process—it should be to ensure nothing gets missed.
That’s exactly where proper identification and documentation matter most:
✔ Reducing cycle time by eliminating manual research
✔ Capturing ALL required OEM procedures
✔ Protecting the shop from missed operations and liability exposure
✔ Creating clear, consistent documentation to support the repair
If one missed operation can cost more than multiple reports, the real risk isn’t using a tool—it’s not using one.
We’re curious where others stand on this:
👉 Have you experienced pushback on documented ADAS procedures?
👉 Are you seeing differences between “recommended” vs. “required” language in claims?
👉 How are you protecting your shop and your customers in these situations?
Would appreciate thoughts, concerns, and real-world experiences from the field.
At the end of the day, the goal is the same for all of us—safe, complete, and proper repairs.
The question is: are we making that easier… or harder?