Table of Contents
A vehicle leaves the shop that is, by all accounts, repaired. The panels line up, the scan is clean, and the customer gets the keys back on schedule. But months later, that same vehicle is involved in a serious crash that one or more ADAS features could have prevented or mitigated the risk of. Now that the repair is under question as to whether every safety-critical procedure was identified, completed correctly, and documented.
That’s the lesson many shops took from what is now referred to as the John Eagle case. It changed how the industry thinks about OEM procedures by showing what can happen when a safety-critical repair decision becomes the center of a catastrophic lawsuit.
Today, ADAS creates a similar liability risk. A repair may look complete, but if a required calibration was missed or the file doesn’t prove the work was done correctly, the shop could be liable in case of an accident.
Read on to learn how ADAS compliance helps shops follow OEM procedures, document required calibrations, and reduce liability risk after safety-critical repairs.
What happened at John Eagle: A quick recap
The 2017 John Eagle case centered on a 2010 Honda Fit that had received a replacement roof after hail damage. Honda’s OEM procedure called for the roof to be welded, but the repair facility used adhesive instead. After the vehicle was later involved in a crash, the plaintiffs argued that the improper repair compromised the vehicle’s structure and contributed to the severity of the injuries.
A Dallas County jury awarded nearly $42 million in damages and found John Eagle Collision Center responsible for 75% of that amount, or about $31.5 million. The case became a turning point because it made clear that OEM procedures aren’t optional when a repair affects safety.
Why ADAS creates the same risk
With new ADAS legislation and federal safety requirements making these systems more common, the liability exposure is only going to grow.
ADAS repairs can fail quietly. A misaligned radar sensor doesn’t always trigger a warning light, and a forward-facing camera issue may not throw a DTC. The vehicle can drive normally (and appear repaired) until the exact moment the customer needs automatic emergency braking, lane keeping, adaptive cruise control, blind spot monitoring, or another safety system to work.
According to our ADAS Industry Benchmark Report, before systematic identification tools, +80% of vehicles requiring calibration left the shop without it. That’s only one in five leaving properly prepared. The numbers look far better now, thanks to VIN identification tools like Revv. However, each missed calibration represents a potential John Eagle scenario waiting to happen.
The risk goes further than whether the calibration was performed. The shop must be able to prove the calibration was required, the correct OEM procedure was followed, the work was completed, and the vehicle was verified before delivery.
If a repair touches a bumper, windshield, mirror, suspension component, radar mounting area, or camera-related component, there’s a very significant chance this could trigger a calibration. Therefore, it’s not enough to show that the visible damage was repaired. Shops need to show documented proof that the vehicle’s safety systems are confirmed to be working as designed.
How ADAS compliance protects you
ADAS compliance comes down to proof. Months after the vehicle leaves, the repair file needs to show what was required, what was recommended, and what was completed. A customer declining an ADAS calibration doesn’t automatically remove the shop’s responsibility to identify the requirement and document the recommendation.
The strongest shops protect themselves by doing three things consistently:
- Following OEM procedures on every job
- Documenting work as it happens
- Making compliance repeatable
Follow OEM procedures on every job
The safest ADAS process begins before repair work starts. Shops need to identify OEM calibration requirements early because many are triggered by the work performed, not by whether the vehicle shows a fault code.
That includes common repair events like:
- Removing or replacing bumpers, mirrors, windshields, or sensor brackets
- Completing alignments, suspension work, or ride-height changes
- Replacing or disturbing cameras, radar, or ultrasonic sensors
That means the process needs to start at the estimate stage. If your shop waits until the post-scan to ask whether calibration is required, the work may need a supplement, the calibration bay may not be scheduled, and the customer may already be expecting delivery.
Shops need a consistent way to identify VIN-specific calibration requirements before the work starts. They also need current OEM procedures, not saved PDFs, memory, or “this is how we did the last one.”
Document everything
A defensible ADAS file tells the whole story of the repair: what the vehicle needed, why it needed it, what procedure was followed, who performed the work, what equipment was used, and how completion was verified.
At a minimum, that file should include:
- Pre-scan results showing the vehicle’s condition before repair work began
- The OEM procedure or requirement supporting the calibration
- Documentation that the calibration was completed
- A calibration certificate or report tied to the specific vehicle
- Post-scan results showing the vehicle was verified before delivery
Having an efficient documentation procedure protects the shop in two ways: it helps defend the repair if there’s ever a safety question, and it helps defend the charge when an insurer asks why the work was necessary.
Our data shows that 77% of shops experience some level of friction with insurers on ADAS charges. The documentation that defends you in a claim dispute is the same documentation that defends you in a courtroom.
This is where Revv helps shops identify required calibrations, access current OEM procedures, and build documentation needed to support the repair from intake through reimbursement. A mobile calibration specialist, Precision Calibration, used to spend hours on manual OEM research for certain vehicles. By using Revv to streamline that research, they achieved 15–20% growth through more proactive, error-free workflows.
Make it a repeatable shop process
A shop can do everything right on one vehicle and still be exposed if the process depends on one estimator remembering to check, one technician knowing a specific OEM requirement, or one manager reviewing documentation before delivery.
Compliance has to be built into your workflow so every qualifying repair answers the same questions:
- What ADAS systems are on this vehicle?
- Which OEM procedures apply?
- Which calibrations are required?
- Who is responsible for completing them?
- Where is the documentation stored?
- Has the vehicle been verified before delivery?
When that process is repeatable, the shop gets consistency across technicians, sublet partners, and locations. That matters whether calibrations are performed in-house, sublet, or handled through a mixed model. If there’s ever a dispute, saying “the sublet handled it” won’t cut it, because the customer entered into the contract with you, meaning liability lies with you.
It also makes training easier because everyone involved in the repair process knows how to perform ADAS calibration services according to the required standards.
There’s also a business case for getting this right
The same documentation that protects your shop legally also helps your shop get paid. If the invoice just says “calibration,” it’s easy for an adjuster to push back. If the file includes the OEM requirement, scan results, calibration certificate, and proof that the work was tied to the repair, that conversation changes.
Clean documentation reduces back-and-forth, supports supplements, and helps you explain why the work was necessary. Over time, it also makes ADAS less of a liability burden and more of a profitable service. ADAS Specialists of Texas saw it firsthand. After implementing Revv’s calibration workflow, the shop boosted revenue by 75% in nine months and reached $1.4 million by 2025.
Build the file before you need it
The lesson from the John Eagle case was that undocumented, non-OEM, safety-critical repair decisions can become catastrophic when something goes wrong.
A sensor can be one degree off, a calibration can be missed, or a required procedure can be overlooked because there wasn’t a warning light. A repair file can look complete until someone asks for the OEM procedure, the calibration record, and proof that the system was verified.
That’s why compliance has to be built into the process before there’s ever a claim. Revv helps shops identify OEM calibration requirements, access the right procedures, and create the documentation needed to support safe, compliant repairs without adding hours of admin work to every job.
Book a demo to see how Revv can help your shop spend less time chasing procedures and paperwork, and more time getting repaired vehicles back on the road.
.avif)