Table of Contents
When a DTC requires calibrations vs when it doesn't
Your scan flags three Diagnostic Trouble Codes (DTCs): a B-code for the forward camera, a U-code on the radar module, and a stored C-code for ride height. The question every tech and estimator wants answered immediately is which code actually requires a calibration?
The answer can be tricky as none inherently trigger a calibration. The true decision depends on why the code was triggered, what the OEM procedure says, and what the rest of the repair looks like.
This blog is your guide to how to make this decision quickly and effectively, and how to document that decision either way.
Why “DTC = calibration” is the wrong rule
DTCs are fault codes that identify symptoms as Joel Adcock explains in his webinar, Pre & Post Scans: The Gateway to Every ADAS Job. He states, “Scans identify faults, OEM procedures identify calibrations.” This provides a clear distinction between DTCs and necessary calibrations, which is a common misconception amongshops.
A fault code tells you something is wrong, but it is the OEM procedure that tells you what to do about it. Calibration is one of the possible remedies for the code, but it could just as well be fixed by replacement, repair, environmental correction, or just a simple clearing of the code. Treating every ADAS-related DTC as a calibration trigger leads to over-calibration, which costs cycle time, supplements, unnecessary tech hours, and insurer pushback.
The inverse, however, is just as costly as skipping a required calibration creates liability exposure, comebacks, and denials on similar work.
Relying on DTCs alone to drive calibration decisions exposes a deeper structural problem with your operation. Research cited in the webinar found that approximately 88% of ADAS calibration requirements do not appear on a scan report at all. They must be identified through OEM research, using a platform like Revv, adasThink, or direct tech/estimator access to OEM repair procedures.
If your shop is using the pre-scan alone to determine what calibrations are necessary, there is a good chance that you’re missing a substantial amount of necessary calibrations.
The four triggers that actually require calibration
DTC or no DTC, these are the conditions that almost always trigger calibration.
1: Physical disturbance of the sensor
Bumper repair and replacement, headlight replacement, windshield replacement, mirror replacement, or other replacements where an ADAS sensor or its mount is removed and reinstalled is a calibration trigger, even when there is no damage to the sensor or mount.
OEM procedure varies by make and change quickly, but most will specify that any physical displacement of the sensor requires calibration to confirm that the sensor is placed properly.
2: Sensor replacement
Sensor replacement often requires calibration. At times, shops assume a direct swap doesn’t require calibration but this is mostly incorrect.
A calibration aims the new sensor to OEM specs, and documenting the new sensor as the old one creates a gap in your repair record and will not satisfy OEM requirements for the work performed.
3: OEM-specified events
Certain repair work triggers calibrations even when the work seems unrelated to ADAS. Wheel alignments, suspension work, battery disconnects on some systems, and software updates all fall into this category depending on the make and model.
If a four-wheel alignment is on the repair order, check whether that vehicle’s OEM procedure flags it as a calibration trigger. For many systems it does but the DTC won’t tell you that.
4: A DTC that explicitly references calibration status
This is the category where DTCs directly call for calibration. Codes described as “calibration required”, “calibration incomplete”, or “calibration not learned” name the necessary work in the description itself.
The distinction to make is between codes that reference calibration state and codes that name a sensor fault without specifying calibration. A camera communication code says the vehicle can't communicate with the front camera. That is a starting point for your diagnosis as it could be a few different reasons, including a disconnected connector, a battery that was disconnected, or something that needs to be cleared and rescanned. Whether calibration follows the DTC depends on what caused the fault and what the OEM procedure calls for after that cause is found.
Common DTCs
U-codes
U-codes are network and communication faults that typically relate to wiring issues, module comm problems, or connector faults and don’t often coincide with calibration needs. The default assumption with a U-code should be to check communication modules first, not scheduling a calibration.
The exception here is when a U-code appears as a symptom of when a module itself is uncalibrated. Address the root cause first and then reference the OEM procedure to determine what follows.
B-codes
Some B-codes indicate sensor faults that require replacement before calibration, while others point to environmental conditions like:
- A blocked sensor
- Dirty lens
- Obstructed housing
In these cases, calibration is not the first step, instead it is maybe needed after clearing the underlying condition. Running a calibration before correcting a blocked sensor won’t clear the code nor satisfy the OEM procedure.
C-codes
These are codes referring to chassis-related issues that include:
- Ride height issues
- Steering angle misalignments
- Suspension-related issues
These codes often require their own fix before an ADAS calibration is necessary. A steering angle reset and a full ADAS calibration are related procedures with different scopes. Substituting one for the other is not effective.
Stored codes from prior events
Codes that are flagged at intake but disappear during the current scan require documentation but may not require a calibration. Capture them, determine what the underlying cause is, and then make a decision. A stored code alone is not a reason to calibrate or skip calibration.
A decision framework: Should you calibrate?
When you’re looking at a scan result and trying to make the call, walk through these steps:
- Does the OEM procedure call for a calibration based on the performed repair? This question is independent of any DTC. If the repair involved a windshield replacement, bumper removal and reinstallation/replacement, or a wheel alignment, check the OEM procedure first.
- Does the scan (pre-, during, or post-) show active codes related to ADAS systems? If yes, determine whether they’re active or stored, and which system they relate to.
- What’s the root cause of the code? Is it the sensor? The wiring? What about the environment? The code names the fault so your diagnosis can determine the root cause and make decisions from there.
- Does the OEM procedure call for calibration as a part of the solution for the root cause? This is the most important question, if the OEM calls for calibration, calibrate it. If not, then leave alone. Either way, you should document your decision.
- Document the decision no matter what No matter your findings, diagnoses, or decisions, make sure to document every step and provide OEM citations.
Documentation when you decide NOT to calibrate
The documentation gap hurts many shops as deciding to not calibrate still requires the same rigorous documentation strategy for when you decide to calibrate. This can help your reputation with insurance adjusters and helps to protect you from liability.
No matter the decision, always be sure the document:
- DTC scan result (pre-, in-process, and post-)
- OEM procedure citation confirming calibration is required (or not required) for the root cause identified
- Description of the solution and process performed
- Post-scan results showing no remaining codes
This documentation strategy protects against insurer denials on similar work as they can’t argue either that you’re performing unnecessary calibrations or skipping them altogether. If a record shows a decision was made based on research and supported by OEM procedure, then you are better protected against denials, adjustments, and liability concerns.
Common mistakes in DTC-driven calibration decisions
Common mistakes with DTCs include:
- Calibrating on every ADAS-related DTC - It feels faster than working through the proper OEM procedure, but it will produce billing issues and insurer pushback on unjustified line items.
- Clearing codes without identifying the root cause - The code comes back, often after returning to the customer. An in-process scan before reassembly would have caught it.
- Skipping calibration on minor jobs that the OEM identifies as a trigger - The OEM procedure doesn’t distinguish between a sensor that was disturbed and one that was removed. If the procedure calls for calibration after that type of adjustment, the calibration is required.
- Treating a relearn as equivalent to a full calibration - If the OEM distinguishes them, then document as separate procedures.
- Letting institutional knowledge substitute for current OEM procedure - OEMs change their positions rapidly so relying on memory, even of your best techs, is dangerous and can trigger issues for your shop.
How Revv supports decisions around DTCs
Revv offers a solution to the DTC decision-making process by mapping VIN-specific calibration requirements to the work performed, not just the DTC list. As this blog shows, the DTC list alone will miss the majority of required calibrations.
OEM procedures are pulled and cited for each decision, reflecting current requirements. In addition, Revv auto-generates OEM-compliant documentation of your entire process. Compatible with estimation software that you’re currently using, Revv does the heavy lifting so your techs can focus on what matters.
Book a demo to see how Revv handles calibration decisions from the first scan all the way through to delivery.
FAQs
Q: Does every ADAS-related DTC require a calibration?
Not necessarily. The DTC indicates a fault while the OEM procedure determines whether calibration is required. Many ADAS-related codes resolve through repair or replacement, with calibration following only when the procedure calls for it.
Q: What's the difference between a calibration and a relearn?
A relearn typically resets stored parameters in the module. A calibration aims the sensor to OEM specification. Some makes and models distinguish them explicitly in procedure documentation, so don't document one as the other.
Q: How do U-codes relate to ADAS calibration requirements?
U-codes are network and communication faults and they usually indicate wiring or module communication issues, not calibration state. Address the root cause first. Calibration follows only if the OEM procedure calls for it after that fix.
Q: Should I calibrate after clearing a stored DTC that's no longer active?
Not on the basis of the stored code alone. Verify whether the underlying event (sensor disturbance, replacement, alignment, or another OEM-specified trigger) independently requires calibration, and follow the OEM procedure from there.
Q: How do I document a decision not to calibrate?
Capture the DTC scan output, the OEM procedure reference that confirms calibration is not required for the root cause identified, the remediation performed, and a clean post-scan. Treat the "no" decision with the same documentation rigor as a "yes." An undocumented decision not to calibrate looks identical to a missed calibration.
