Skip to main content
    Claimory
    Back to all articles
    Technology Without the Hype

    When Is ADAS Calibration Required After Collision Repair?

    April 23, 2026
    10 min read
    Artur A.

    ADAS calibration is required any time a sensor is removed, replaced, or repositioned. Static, dynamic, or both. Scan-and-clear is not calibration. Pre-scan and post-scan reports become part of the audit-ready file.

    When ADAS Calibration Is Required

    ADAS (Advanced Driver Assistance Systems) calibration is required any time a sensor used by an ADAS feature is removed, replaced, repositioned, or has its mounting orientation altered, including windshield replacement on equipped vehicles, front and rear bumper R&I or replacement, suspension or alignment changes, certain wheel alignments, ride-height changes, and any structural repair near a sensor mount. Calibration is not optional and not satisfied by clearing diagnostic codes. Two calibration types apply: static calibration performed in-shop using factory targets and a level surface, and dynamic calibration performed by driving the vehicle under defined conditions while the vehicle's sensors re-learn. Most modern vehicles require both. The OEM service procedure is the source of truth. When ADAS calibration is required, the operation belongs on the estimate or the supplement at the labor rate the calibration vendor charges, plus the OEM-required pre-scan and post-scan reports.

    What ADAS Means and Why Calibration Exists

    Advanced Driver Assistance Systems include forward collision warning and automatic emergency braking, adaptive cruise control, lane departure warning and lane keeping assist, blind-spot monitoring, rear cross-traffic alert, 360-degree camera systems, pedestrian detection, and park assist. Each feature relies on sensors: cameras, radar, lidar on some premium vehicles, ultrasonic. The sensors must be aimed precisely. A camera mounted 2 degrees off vertical produces a wrong picture of where the lane lines are. A radar 1 degree off horizontal produces a wrong distance to the car ahead. Calibration sets the aim within OEM tolerance. Without calibration, ADAS may fail silently, trigger inappropriate warnings or braking, refuse to operate, or pass post-scan but operate dangerously in real-world conditions. This is the safety reason calibration is non-negotiable.

    Specific Trigger Conditions

    The trigger conditions, in plain language:

    • Windshield replacement on a vehicle with a forward-facing camera mounted to the windshield (most modern vehicles)
    • Bumper R&I or replacement when forward or rear radar, ultrasonic sensors, or cameras are mounted to the bumper or its supports
    • Front-facing camera removal or replacement for any reason
    • Radar sensor R&I or replacement for any reason
    • Suspension component replacement that changes ride height or geometry
    • Steering angle sensor service (often part of suspension repair)
    • Battery disconnect and reconnect on certain vehicles where ADAS modules retain calibration in volatile memory
    • Structural repair anywhere near a sensor mount
    • Wheel alignment that changes the thrust angle or ride height meaningfully

    The OEM service information system tells you precisely which conditions trigger calibration on a specific year-make-model.

    Static vs Dynamic Calibration

    Static calibration. Performed indoors with the vehicle on a level surface. Uses OEM-approved targets placed at OEM-specified distances and heights. Requires adequate space (typically 20-30 feet of clear floor in front of the vehicle), a level floor, OEM target boards or laser-projected targets, and a compatible scan tool with OEM-equivalent calibration software.

    Dynamic calibration. Performed by driving the vehicle on roads that meet OEM conditions: a certain speed range, lane markings of certain quality, no precipitation, certain ambient lighting, often a specific distance traveled. The vehicle's sensors capture data and re-learn calibration during the drive.

    Combined static + dynamic. Many vehicles require both. Static first to establish baseline aim, dynamic afterward to refine.

    Key Insight

    Most independent shops sublet ADAS calibration. The vendor brings the targets, the scan tool, and the OEM software. The shop owns the documentation.

    Pre-Scan and Post-Scan Reports

    Before any ADAS-affected operation, run a full pre-scan. The report lists every module on the vehicle, records DTCs (diagnostic trouble codes) that exist before the repair, and establishes the baseline so post-repair codes are clearly attributable. After the repair and calibration, run the post-scan. The report confirms no new DTCs exist, documents that the calibration completed successfully, and records the technician credentials and the scan tool used. Both reports become part of the claim file. Carriers expect both. Customers occasionally request both. DV appraisers often request both.

    Why Scan-and-Clear Is Not Enough

    "Cleared codes are not calibration. Auditors are increasingly looking for the learning event, not just a clean scan."

    A common mistake: the technician runs a scan, sees DTCs related to the calibration trigger, clears the codes, runs a second scan that is now clean, and moves on. This is not calibration. The codes were cleared. The aim was not corrected. The OEM procedure differentiates 'code clearing' from 'calibration.' The post-scan after a calibration shows specific events: 'calibration complete,' 'learning complete,' or vehicle-specific success indicators. A clean scan with no learning event is not calibration. Carriers are increasingly auditing for the difference. A claim with cleared codes but no calibration learning event documentation is exposed to a post-payment audit deduction.

    What Goes on the Estimate

    The supplement language for ADAS calibration:

    • Pre-scan: 0.3-0.5 hours (varies by vehicle complexity)
    • Calibration (static, dynamic, or both): vendor-quoted labor or OEM book time
    • Target setup time on certain vehicles: variable
    • Post-scan: 0.3-0.5 hours
    • Sublet markup if applicable: per shop policy
    • Vendor invoice attached

    Carriers sometimes push back on calibration billing. The defense is the OEM procedure citation and the calibration completion report. With both attached to the supplement, approval is straightforward.

    90%+
    Captured at Estimate
    When ADAS is identified at intake
    50-70%
    Fewer Calibration Disputes
    With structured sublet workflow
    Vendor quoted
    Calibration time basis
    Set by the vendor quote or OEM book time for that year make and model rather than a shop average

    How Modern Shops Handle It

    Shops that flag ADAS calibration at intake based on year-make-model presence and route the claim through a defined sublet workflow typically capture most required calibrations on the original estimate (vs supplement) and cut calibration-related supplement disputes sharply. The driver is identification at intake, not at teardown. Inside Claimory, ADAS sublet operations carry their pre-scan, post-scan, vendor R.O., and vendor invoice in one place on the claim file. The audit packet is complete by default.

    Action Steps

    1. Build a year-make-model ADAS presence reference for the top 30 vehicles your shop sees
    2. Add a 30-second ADAS check at intake to the front-desk script
    3. Establish a sublet calibration vendor relationship if you do not have one
    4. Document every calibration with pre-scan, post-scan, and vendor invoice on every claim
    5. Audit your last 30 claims for calibration documentation gaps; remediate any open ones
    Share this article

    Track every ADAS calibration and scan report inside the claim file

    See how Claimory helps collision shops manage claims, track supplements, and improve operations.

    Claimory Reads

    More on Technology Without the Hype

    Continue exploring insights and strategies in this category.

    Want more collision shop insights?

    Explore our complete library of articles on shop management, claims tracking, and operations.

    Browse All Articles